DLT ID Difference: Entity vs Header vs Template Guide

Understanding the DLT ID difference is crucial for TRAI compliance in bulk SMS. If you’re new to DLT (Distributed Ledger Technology) regulations, the terminology can be overwhelming. Entity ID, Header ID, Template ID—what’s the DLT ID difference, and how do they work together? In this comprehensive guide, we’ll break down the DLT ID difference, explain each component with real examples, and show you exactly how they fit into the SMS compliance puzzle.

The DLT ID Difference: Quick Overview

Before diving deep into the DLT ID difference, it’s important to understand that DLT compliance  requires three core components working together:

1. Entity ID – Your business identity
2. Header ID – Your sender name/number
3. Template ID – Your pre-approved message format

The fundamental DLT ID difference is simple: Entity ID identifies WHO you are, Header ID shows HOW you appear to recipients, and Template ID defines WHAT you’re sending. Think of it like sending a letter—you need your return address (Entity ID), your name on the envelope (Header ID), and the approved format of your message (Template ID). Understanding this DLT ID difference is the first step to compliance.

What is an Entity ID? Understanding the First DLT ID Difference

Definition

An Entity ID (also called PE ID – Principal Entity ID) is a unique 19-digit identifier assigned to your business when you register on the DLT platform. This is the first DLT ID difference you’ll encounter—it’s your digital identity in the SMS ecosystem.

Key Characteristics

• Format: 19-digit alphanumeric code (e.g., 1201234567890123456)
• Uniqueness: One per business/organization
• Registration: First step in DLT compliance
• Validity: Permanent (unless voluntarily surrendered)
• Hierarchy: Parent to all Header IDs and Template IDs

The DLT ID Difference: What Entity ID Represents

Your Entity ID proves that:

• Your business is registered and verified
• You’re authorized to send commercial communications
• You’ve agreed to follow TRAI’s TCCCPR 2018 regulations
• Your business details are on record with telecom operators

This is a critical DLT ID difference—while Header IDs and Template IDs can be multiple, you only get ONE Entity ID per organization.

Registration Requirements

To obtain an Entity ID, you need:

• Business registration documents (GST, PAN, Certificate of Incorporation)
• Authorized signatory details with KYC
• Business address proof
• Contact information

Real-World Example

ABC Bank Ltd registers on the DLT platform and receives Entity ID: 1201159876543210987. This ID represents ABC Bank across all telecom operators and is used for all their SMS communications. This illustrates the first DLT ID difference—Entity ID is organization-wide, not message-specific.

What is a Header ID? The Second DLT ID Difference

Definition

A Header ID (also called Sender ID) is the name or number that appears as the sender when recipients receive your SMS. This is where the next DLT ID difference becomes important—it’s your brand identity in the recipient’s inbox.

Types of Headers: A Critical DLT ID Difference

1. Alphanumeric Headers (6 characters)

• Format: Letters and numbers (e.g., ABBANKK, RETAIL, HOSPTL)
• Used for: Transactional, Service Implicit, Service Explicit messages
• Visibility: Shows your brand name
• Example: When you receive an OTP from “ABBANKK” or order update from “AMAZON”

2. Numeric Headers (6 digits)

• Format: Numbers only (e.g., 567890, 123456)
• Used for: Promotional messages ONLY
• Visibility: Generic number appearance
• Example: Marketing SMS from “567890”

Understanding this DLT ID difference between alphanumeric and numeric headers is crucial—using the wrong type will cause message rejection.

Key Characteristics: DLT ID Difference from Entity ID

• Multiple Headers: One Entity can have multiple Header IDs (unlike Entity ID)
• Approval Required: Each header needs operator approval
• Category-Specific: Must match message type
• Brand Recognition: Alphanumeric headers build trust
• Linked to Entity: Always connected to your Entity ID

Registration Process

1. Log into DLT portal with your Entity ID
2. Submit header request with justification
3. Provide trademark certificate (for brand names)
4. Wait for operator approval (2-3 working days)
5. Receive approved Header ID

Critical Rule: Understanding This DLT ID Difference

Promotional messages CANNOT use alphanumeric headers. This is the most common mistake when people don’t understand the DLT ID difference. If you’re sending marketing SMS, you MUST use a 6-digit numeric sender ID.

Real-World Example: DLT ID Difference in Action

ABC Bank Ltd (Entity ID: 1201159876543210987) registers multiple headers:

• ABBANK – For transactional OTPs
• ABCLOAN – For loan-related service messages
• 567890 – For promotional credit card offers

This example shows the DLT ID difference clearly—one Entity ID can have multiple Header IDs, each serving a specific purpose.

What is a Template ID? The Third DLT ID Difference

Definition

A Template ID is a unique identifier assigned to each pre-approved message format. This is the final DLT ID difference you need to master—every SMS you send must match a registered template exactly (except for variable parts). Learn more about DLT Template ID registration.

Key Characteristics: DLT ID Difference from Other IDs

• Format: Alphanumeric string assigned by operator
• Content Lock: Cannot edit after approval (major DLT ID difference)
• Variable Support: 2-3 dynamic fields using {#var#}
• Category-Bound: Must match header category
• Validity: Active until surrendered or deactivated
• Quantity: Unlimited templates per Header ID

Template Categories

Templates are classified into four categories, another important DLT ID difference to understand:

1. Transactional: Banking OTPs only
2. Service Implicit: Order updates, delivery notifications
3. Service Explicit: Offers to existing customers (with consent)
4. Promotional: Marketing messages to opted-in users

Template Structure

A template consists of:

• Fixed text: Unchangeable content
• Variables: Dynamic content marked as {#var#}
• Brand name: Must be included
• Call-to-action: Optional links/instructions

Real-World Example: Complete DLT ID Difference

Template for ABC Bank:

Category: Transactional
Header: ABBANK
Content: Dear Customer, {#var#} is your OTP for completing transaction of Rs.{#var#}. Valid for 10 minutes. Do not share. – ABC Bank
Template ID: 1307168574839201234

When sending SMS:

• {#var#} ← “547892” (OTP)
• {#var#} ← “5000” (Amount)

Delivered SMS: “Dear Customer, 547892 is your OTP for completing transaction of Rs.5000. Valid for 10 minutes. Do not share. – ABC Bank”

This demonstrates the complete DLT ID difference—Template ID defines the exact message structure, unlike Entity ID (business identity) or Header ID (sender name).

The Complete DLT ID Difference: Side-by-Side Comparison

Understanding the DLT ID difference is easier with a direct comparison:

Aspect	Entity ID	Header ID	Template ID
What It Is	Your business identity	Your sender name/number	Your message format
Purpose	Identifies who you are	Shows who sent the message	Defines what you’re sending
Format	19-digit alphanumeric	6-char alpha OR 6-digit numeric	System-generated code
Quantity	One per organization	Multiple allowed	Unlimited per entity
Visibility	Backend only	Visible to recipients	Backend only
Registration	First step	Second step	Third step
Approval Time	2-3 days	2-3 days	2 working days
Can Be Edited?	Limited (contact details)	No	No
Linked To	Business documents	Entity ID	Header ID + Category
Example	1201159876543210987	ABBANK or 567890	1307168574839201234

This table clearly shows the DLT ID difference across all three components.

Understanding the DLT ID Difference in Practical Terms: How They Work Together

Understanding how these three IDs interact is crucial for grasping the complete DLT ID difference. Here’s the workflow:

Step 1: Entity Registration

Business → Register on DLT Platform → Receive Entity ID

 

You provide business documents, complete KYC, and get your unique 19-digit Entity ID. This is the foundation of the DLT ID difference hierarchy.

Step 2: Header Registration

Entity ID → Apply for Header(s) → Receive Approved Header ID(s)

 

Under your Entity ID, you register sender IDs. The DLT ID difference here: you can have multiple Header IDs under one Entity ID.

Step 3: Template Creation

Header ID → Create Message Template → Receive Template ID

 

For each header, you create message templates. The DLT ID difference: each Template ID is linked to a specific Header ID.

Step 4: Linking & Activation

Entity ID ← Header ID ← Template ID

 

All three must be properly linked. This hierarchical DLT ID difference is critical for compliance.

Step 5: SMS Sending

Your System → API Call with (Entity ID + Header ID + Template ID + Variables) → SMS Delivered

 

Visual Representation: Complete DLT ID Difference

ABC Bank Ltd

    ├─ Entity ID: 1201159876543210987

    │

    ├─ Header: ABBANK (Alphanumeric)

    │   ├─ Template ID: 1307168574839201234 (Transactional – OTP)

    │   ├─ Template ID: 1307168574839201235 (Service – Account alerts)

    │   └─ Template ID: 1307168574839201236 (Service – Balance inquiry)

    │

    ├─ Header: ABCLOAN (Alphanumeric)

    │   ├─ Template ID: 1307168574839201237 (Service – Loan approval)

    │   └─ Template ID: 1307168574839201238 (Service – EMI reminders)

    │

    └─ Header: 567890 (Numeric)

        ├─ Template ID: 1307168574839201239 (Promotional – Credit card offers)

        └─ Template ID: 1307168574839201240 (Promotional – Special discounts)

 

This diagram perfectly illustrates the DLT ID difference and hierarchy.

Why the DLT ID Difference Matters for Compliance

Understanding the DLT ID difference is not just academic—it has real compliance implications:

For Entity ID:

• Wrong Entity ID = Complete delivery failure
• One mistake affects ALL your SMS communications
• Cannot send any messages without valid Entity ID

For Header ID:

• Wrong header type = Category mismatch rejection
• Using alphanumeric for promotional = Instant blocking
• Each header must match its intended use case

For Template ID:

• Content mismatch = Individual message rejection
• Variables exceeding limits = Template disapproval
• Wrong category = Delivery failures

The DLT ID difference means each component has distinct failure modes and compliance requirements.

Common Mistakes: Misunderstanding the DLT ID Difference

Mistake #1: Using Wrong Header for Message Type

Problem: Not understanding the DLT ID difference between alphanumeric and numeric headers
Impact: Message rejection, possible penalties
Solution: Always use numeric headers (6-digit) for promotional messages

Mistake #2: Not Linking Template to Correct Header

Problem: Ignoring the DLT ID difference in template-header relationship
Impact: Template rejection, delivery failures
Solution: Verify header category before creating templates

Mistake #3: Multiple Entities for Same Business

Problem: Not understanding the DLT ID difference—thinking each department needs separate Entity ID
Impact: Fragmented management, compliance issues
Solution: Use one Entity ID with multiple headers

Mistake #4: Reusing Template IDs Across Headers

Problem: Misunderstanding the DLT ID difference—assuming same template works for different headers
Impact: Delivery failures
Solution: Register separate templates for each header

Mistake #5: Editing Approved Components

Problem: Not knowing the DLT ID difference in editability
Impact: Not possible; requires new registration
Solution: Plan carefully; create new ones if changes needed

Registration Sequence: The DLT ID Difference Timeline

Following the correct sequence respects the DLT ID difference hierarchy:

Phase 1: Entity Setup (Week 1)

1. ✅ Gather business documents
2. ✅ Complete Entity registration
3. ✅ Receive and verify Entity ID
4. ✅ Set up authorized users

Phase 2: Header Registration (Week 2)

1. ✅ Plan header strategy (understanding DLT ID difference)
2. ✅ Prepare trademark documents (if applicable)
3. ✅ Submit header applications
4. ✅ Await operator approval (2-3 days each)

Phase 3: Template Creation (Week 3-4)

1. ✅ Draft message templates with variables
2. ✅ Categorize correctly (respecting DLT ID difference)
3. ✅ Link to appropriate headers
4. ✅ Submit for approval (2 working days)
5. ✅ Test with sample messages

Phase 4: Integration & Testing (Week 5)

1. ✅ Update SMS gateway with all IDs
2. ✅ Configure API parameters (all three IDs)
3. ✅ Run test campaigns
4. ✅ Verify delivery and content

Total Timeline: 4-5 weeks for complete setup

Practical Scenarios: DLT ID Difference in Real Businesses

Scenario 1: E-Commerce Business

Business: OnlineRetail.com

Entity ID: 1201234567890123456

Understanding the DLT ID Difference:

• ONLSHOP (Alphanumeric Header)
  • Order confirmation Template ID: 1307165678901234567
  • Shipping updates Template ID: 1307165678901234568
  • Delivery notifications Template ID: 1307165678901234569
• ONLSALE (Alphanumeric Header)
  • Cart abandonment Template ID: 1307165678901234570
  • Personalized offers Template ID: 1307165678901234571
• 567891 (Numeric Header)
  • Flash sale alerts Template ID: 1307165678901234572
  • New arrival announcements Template ID: 1307165678901234573

The DLT ID Difference Here: One Entity ID, three Header IDs, seven Template IDs—all working together.

Template Example:

• Header: ONLSHOP
• Template: Your order #{#var#} is out for delivery. Expected by {#var#}. Track: {#var#} – OnlineRetail
• Template ID: 1307165678901234567

Scenario 2: Healthcare Provider

Business: City Hospital

Entity ID: 1201987654321098765

DLT ID Difference Application:

• CITYHOS (Alphanumeric Header)
  • Appointment confirmations Template ID: 1307162345678901234
  • Test results ready Template ID: 1307162345678901235
  • Prescription reminders Template ID: 1307162345678901236
• 567892 (Numeric Header)
  • Health checkup packages Template ID: 1307162345678901237
  • Vaccination drives Template ID: 1307162345678901238

Template Example:

• Header: CITYHOS
• Template: Dear {#var#}, Your appointment with Dr. {#var#} is confirmed for {#var#} at City Hospital. – CityHospital
• Template ID: 1307162345678901234

These scenarios demonstrate the DLT ID difference in practical applications across industries.

Technical Integration: Using the DLT ID Difference in APIs

When integrating with your SMS gateway, you’ll use all three IDs. Understanding the DLT ID difference helps you structure API calls correctly:

{

  “entity_id”: “1201159876543210987”,

  “header_id”: “ABBANK”,

  “template_id”: “1307168574839201234”,

  “mobile”: “919876543210”,

  “variables”: {

    “var1”: “547892”,

    “var2”: “5000”

  }

}

 

The gateway validates based on DLT ID difference:

1. ✅ Entity ID exists and is active
2. ✅ Header ID belongs to this Entity
3. ✅ Template ID is linked to this Header
4. ✅ Message content matches Template (with variables filled)
5. ✅ Recipient has not marked sender as spam

Only when all validations pass—respecting the DLT ID difference at each level—will the SMS be delivered.

Compliance Checklist: Mastering the DLT ID Difference

Before going live, ensure you understand the DLT ID difference at each level:

Entity Level

• [ ] Entity ID received and verified
• [ ] Business documents uploaded
• [ ] Authorized signatories added
• [ ] Contact details updated

Header Level (Understanding DLT ID Difference)

• [ ] All required headers registered
• [ ] Alphanumeric headers for service/transactional
• [ ] Numeric headers for promotional
• [ ] Trademark documents submitted (if needed)
• [ ] Headers approved by operators

Template Level (Respecting DLT ID Difference)

• [ ] Templates created for all message types
• [ ] Correct category assigned to each template
• [ ] Variables limited to 2-3 per template
• [ ] Brand name included in all templates
• [ ] Templates linked to correct headers
• [ ] All templates approved

Integration Level

• [ ] SMS gateway configured with all three IDs
• [ ] API parameters correctly mapped (respecting DLT ID difference)
• [ ] Test messages successfully delivered
• [ ] Error handling implemented
• [ ] Logging and monitoring active

FAQs: Quick Answers on DLT ID Difference

Q: What’s the main DLT ID difference between Entity, Header, and Template IDs?
A: Entity ID identifies your business (WHO), Header ID is your sender name (HOW you appear), and Template ID is your message format (WHAT you send). The key DLT ID difference is hierarchy: one Entity can have multiple Headers, and each Header can have multiple Templates.

Q: Can I use the same Template ID with multiple Header IDs?
A: No. This violates the DLT ID difference principle. Each Template ID is specific to one Header ID. You need to create separate templates even if the content is identical.

Q: How many Header IDs can I have under one Entity ID?
A: There’s no fixed limit, but understanding the DLT ID difference means creating only necessary headers. Each requires justification.

Q: Do I need separate Entity IDs for different business units?
A: No. The DLT ID difference hierarchy allows one Entity ID for your entire organization with multiple headers for different departments or brands.

Q: Can I transfer Template IDs between headers?
A: No. Templates are permanently linked to their headers. The DLT ID difference in linking means you must create new templates for different headers.

Q: What happens if I don’t respect the DLT ID difference?
A: Messages will be rejected by operators. You’ll receive delivery failures, and repeated violations can lead to suspension. Understanding the DLT ID difference is mandatory for compliance.

Next Steps: Applying Your DLT ID Difference Knowledge

Now that you understand the DLT ID difference, here’s your action plan:

Immediate Actions (This Week)

1. Assess your business SMS requirements
2. Identify how many headers you’ll need (considering DLT ID difference)
3. Draft your most common message templates
4. Choose your DLT platform (Airtel, Jio, Vi, or BSNL)

Registration Phase (Weeks 1-3)

1. Complete Entity registration with documents
2. Apply for all required headers (respecting DLT ID difference)
3. Create and submit templates for approval
4. Set up consent management (for promotional)

Implementation Phase (Weeks 4-5)

1. Integrate all three IDs with your SMS gateway
2. Configure API with proper parameters (understanding DLT ID difference)
3. Run test campaigns across all templates
4. Train your team on compliance requirements

Ongoing Maintenance

1. Monitor template usage monthly
2. Conduct quarterly re-verification (as per TRAI 2023 rules)
3. Surrender unused templates
4. Update templates when business needs change

Conclusion: Mastering the DLT ID Difference

Understanding the DLT ID difference between Entity ID (who you are), Header ID (how you appear), and Template ID (what you send) is fundamental to TRAI DLT compliance. The key DLT ID difference points to remember:

• Entity ID establishes your business identity (ONE per organization)
• Header ID builds your brand recognition (MULTIPLE per entity)
• Template ID ensures message consistency (UNLIMITED per header)

The DLT ID difference in hierarchy, quantity, and purpose means each component has a distinct role. Getting all three right from the start—and understanding the DLT ID difference at each level—will save you from delivery failures, compliance issues, and customer complaints.

For detailed guidance on creating compliant templates, refer to our comprehensive DLT Template ID Registration Guide. If you need help with bulk SMS implementation or have questions about the DLT ID difference, our team at TechtoNetworks is here to assist you.

Ready to implement your DLT compliance with complete understanding of the DLT ID difference? Contact us today or explore our bulk SMS solutions designed for seamless TRAI compliance.