Understanding LST_XXX.dat Files in TallyPrime Data Folder: Structure, Purpose, and Best Practices

In TallyPrime, company data is not stored in a single database file like traditional SQL systems. Instead, Tally uses a proprietary file-based data architecture, where multiple files together form a complete company dataset.

One of the most commonly noticed file types in the data folder is:

LST_XXX.dat

These files often confuse system administrators and accountants, especially during backups, migrations, or troubleshooting. This article explains their purpose, structure, and handling in a technical yet practical manner.

? Overview of Tally Data Folder Structure

4

A typical Tally company folder (e.g., 10006) contains:

Core Files

• Company.900 → Primary company data
• CmpSave.900 → Save state snapshot
• Manager.900 → Data structure manager
• LinkMgr.900 → Internal linking/index control

Supporting Files

• AddlCmp.900 → Additional company configuration
• *.tsf → Temporary files (during operations)

Data Segment Files

• LST_XXX.dat → List data storage (focus of this article)

? What are LST_XXX.dat Files?

Definition

LST_XXX.dat files are List Data Files used by Tally to store structured collections of business data.

Key Characteristics

• Binary format (not human-readable)
• Auto-generated by Tally
• Each file represents a specific dataset or index
• Number (XXX) is an internal identifier

? Internal Architecture & Working

4

Tally follows a hierarchical + indexed storage model:

1. Data Segmentation

Instead of one large database:

• Data is split into logical segments
• Each segment → separate .dat file

2. Indexed Lists

Each LST_XXX.dat stores:

• Ledger lists
• Voucher lists
• Inventory lists
• Cost centre lists

3. Mapping Mechanism

• Manager.900 → manages structure
• LinkMgr.900 → links records across files
• LST_XXX.dat → stores actual indexed lists

? Examples of Data Stored

⚠️ Note: Exact mapping is proprietary and may vary.

⚙️ Why Tally Uses Multiple LST Files

✅ Performance Optimization

• Faster read/write operations
• No need to load entire database

✅ Scalability

• Handles large data volumes efficiently

✅ Data Isolation

• Corruption in one file does not always affect entire data

✅ Multi-user Environment Support

• Better concurrency handling

? File Behavior & Lifecycle

Creation

• Automatically created when:
  • New masters are added
  • Transactions increase

Modification

• Updated in real-time during:
  • Voucher entry
  • Alteration of masters

Deletion

• Never deleted manually
• Managed internally by Tally

⚠️ Common Issues Related to LST Files

1. File Size Becomes 0 KB

• Possible data corruption
• Improper shutdown

2. Mismatch Errors

• Happens when indexing breaks

3. Data Not Loading

• Linked LST file missing or damaged

?️ Troubleshooting & Recovery

Step 1: Verify Data in Tally

• Open company
• Check for missing vouchers or ledgers

Step 2: Use Tally Repair Utility

• Rewrite company data

Step 3: Restore Backup

• Replace entire company folder

Step 4: Check Disk Health

• Use tools like SMART diagnostics

? Important Do’s and Don’ts

❌ Do NOT:

• Delete LST_XXX.dat files
• Rename files
• Edit using external tools
• Copy partial files

✅ Always:

• Backup complete company folder
• Use Tally’s built-in backup
• Ensure proper shutdown of system

? Backup Best Practices

Recommended Approach:

• Backup full folder:

  Tally Data → Company Folder (e.g., 10006)
  

• Store backups:
  • External drive
  • Cloud storage
  • Network location

? Advanced Technical Insight

• Tally uses a proprietary database engine (not SQL-based)
• LST files act similar to:
  • Indexed tables
  • Data blocks
• Combined with .900 files, they form a complete object database

? Conclusion

LST_XXX.dat files are a critical part of TallyPrime’s internal data architecture. While they may appear confusing, they play a vital role in ensuring:

• Efficient data storage
• Fast processing
• Reliable multi-user performance

Understanding these files helps IT administrators and accountants avoid accidental data loss and manage backups more effectively.