While checking a bank ledger, cash ledger, party ledger, or any other account in TallyPrime, you may notice that transactions entered on the same date do not appear in the sequence you expected.

For example, Payment vouchers entered with voucher numbers:

3881, 3882, 3883, 3884, 3885, 3886, 3887

may appear in the Ledger Vouchers report as:

3881, 3882, 3887, 3886, 3885, 3884, 3883

At the same time, Contra or Receipt voucher numbers such as 288, 289, 83, 290 may appear between Payment vouchers.

This can make the ledger look random, uneven, or incorrectly arranged, even though the vouchers themselves may have been entered correctly.

In many cases, this is not data corruption. The apparent disorder can result from how TallyPrime displays transactions, the use of different voucher types and numbering series, the voucher date, and other voucher/report attributes.

---

Understanding the Problem

Consider a bank ledger containing transactions like:

A user may expect:

3881 → 3882 → 3883 → 3884 → 3885 → 3886 → 3887

But TallyPrime may display a different sequence.

This raises an obvious question:

Why doesn't TallyPrime show vouchers in exactly the same order in which I entered them or according to Voucher Number?

The answer requires understanding the difference between voucher date, voucher type, voucher number, entry sequence, and report sorting.

---

1. Voucher Number Is Not Necessarily the Ledger's Universal Sorting Number

This is one of the most important concepts.

A ledger can contain transactions from multiple voucher types, such as:

• Payment
• Receipt
• Contra
• Journal
• Sales
• Purchase
• Credit Note
• Debit Note

Each voucher type can have its own voucher-numbering series.

For example:

Therefore, voucher number 83 appearing between vouchers 3881 and 3882 does not automatically indicate a numbering problem.

Voucher No. 83 may belong to the Receipt voucher series, while 3881 belongs to the Payment series.

It would therefore be incorrect to expect every voucher in a bank ledger to follow one continuous numerical sequence.

---

2. Voucher Date Has Major Importance in Ledger Display

TallyPrime accounting reports are fundamentally date-oriented.

If you have transactions on:

• 21-Aug
• 22-Aug
• 23-Aug

TallyPrime will normally keep transactions associated with their respective accounting dates.

The more confusing situation occurs when many vouchers have exactly the same date.

For example:

21-Aug-2025

may contain 10, 20, or even 100 transactions.

The date alone can no longer determine the exact visual sequence of those transactions.

Other internal/report criteria can therefore affect their placement.

---

3. Entry Sequence and Voucher Number Are Different Concepts

Suppose you create these Payment vouchers:

1. Voucher 3881
2. Voucher 3882
3. Voucher 3883
4. Voucher 3884
5. Voucher 3885

You might naturally expect the ledger to always display:

3881 → 3882 → 3883 → 3884 → 3885

However, entry sequence and report display sequence should not automatically be treated as the same thing.

A voucher number identifies a voucher according to the numbering configuration of that voucher type.

A report, on the other hand, has to decide how to display all transactions retrieved from different voucher types and ledgers.

Therefore:

Voucher Number ≠ Universal Transaction Sequence

and

Data-entry sequence ≠ Guaranteed report-display sequence

---

4. Different Voucher Types Make the Ledger Look More Uneven

A bank ledger is a particularly good example because it normally contains several voucher types.

You may see:

Payment 3881

followed by:

Contra 288

then:

Payment 3882

then:

Receipt 83

then:

Contra 289

This doesn't necessarily mean the numbering is damaged.

There may actually be three independent series:

Payment series

3881, 3882, 3883...

Contra series

288, 289, 290...

Receipt series

83, 84, 85...

These numbers should generally be evaluated within their respective voucher types, rather than comparing all numbers as if they belong to one common series.

---

5. Why Can the Same Voucher Type Also Look Out of Sequence?

This is the more interesting situation.

Suppose Payment vouchers for the same date appear as:

3881 → 3882 → 3887 → 3886 → 3885 → 3884 → 3883

Now we cannot explain everything simply by saying that different voucher types have different numbering.

All these vouchers belong to the Payment type.

Possible causes that should be investigated include:

• Report sorting/display behaviour
• Vouchers entered or altered later
• Back-dated voucher entry
• Voucher numbering configuration
• Manual voucher numbering
• Different voucher classes/types
• Import of transactions
• Voucher alteration
• Report-specific configuration
• Migration or imported accounting data
• Other voucher attributes used by the report

Therefore, do not immediately assume that the accounting database is damaged.

---

6. Back-Dated Entries Can Cause Confusion

This is extremely common in accounting.

Imagine that on 25-Aug you create Payment Voucher No. 3900.

Later, you realise that a transaction belongs to 21-Aug.

You create or alter a voucher and assign the earlier accounting date.

The voucher now belongs to 21-Aug for accounting purposes even though it was created or modified later.

This can make the report's visual order different from what a user remembers as the original entry sequence.

Example

Entry creation sequence:

3881 → 3882 → 3883 → 3884 → 3885

But voucher dates might be:

The ledger will naturally not show them as one simple numerical sequence across different dates.

---

7. Altering an Existing Voucher Can Also Affect Your Investigation

Accounting staff frequently modify vouchers after creation to correct:

• Date
• Ledger
• Amount
• Narration
• Bank allocation
• Instrument details
• Reference
• Cost centre
• Party details
• Voucher type

Therefore, when investigating an apparently misplaced voucher, open the actual voucher and verify its information rather than relying only on its position in the ledger.

---

8. Check the F12 Configuration of the Report

When the ledger display looks unexpected, one of the first places to inspect is the report configuration.

Open the required ledger:

TallyPrime → Display More Reports → Account Books → Ledger

or access the ledger through the appropriate report.

Then press:

F12 – Configure

Review the available report options.

The exact options can vary depending on the TallyPrime release and the report being viewed, so look for settings associated with:

• Sorting
• Voucher display
• Transaction presentation
• Narration
• Voucher details
• Ledger details
• Additional information

Do not change several options simultaneously.

Change one relevant setting, observe the result, and then proceed.

---

9. Check the Voucher Type Configuration

If the issue appears related to numbering, inspect the affected voucher type.

For example, check the configuration for Payment vouchers.

Important areas include:

Method of Voucher Numbering

Depending on configuration and TallyPrime version, voucher numbering can involve methods such as automatic or manual numbering.

Verify whether the company intentionally uses the selected numbering system.

Also check whether separate numbering configurations are being used.

---

10. Manual Voucher Numbers Need Special Attention

If users are manually entering voucher numbers, there is greater scope for unusual numbering.

For example:

3881

3882

3887

3883

Tally may accept the numbers according to the voucher configuration and workflow, but the numbers themselves do not necessarily represent the actual chronological order of data entry.

Therefore, in troubleshooting, determine:

Is the voucher number generated automatically by TallyPrime, or typed manually by the user?

This distinction is very important.

---

11. Check Whether Vouchers Were Imported

Many businesses now create Tally vouchers through:

• XML imports
• Excel-to-Tally utilities
• Banking software
• ERP applications
• Custom TDL solutions
• API/integration tools
• Bank-statement import utilities
• Third-party accounting applications

Imported transactions may not have been physically entered one by one in the sequence the accountant expects.

If the problem started after importing vouchers, investigate the import source as well.

Check:

Date → Voucher Type → Voucher Number → Ledger → Amount

before concluding that Tally has rearranged data incorrectly.

---

12. Do Not Judge Sequence Only from the Bank Ledger

If you suspect a particular voucher, open it directly.

For example:

Payment Voucher 3883

Verify:

• Voucher date
• Voucher type
• Voucher number
• Bank ledger
• Opposite ledger
• Debit/Credit amount
• Narration
• Reference
• Bank allocation

Repeat the check for nearby vouchers such as 3884, 3885, 3886 and 3887.

This establishes whether the underlying vouchers are correct.

---

13. Check Day Book

The Day Book is extremely useful when troubleshooting transaction order.

Open:

TallyPrime → Day Book

Set the date to the problematic date.

For example:

21-Aug-2025

Now compare the Day Book with the bank ledger.

This helps determine whether the unusual order is specific to the Ledger Vouchers report or is visible elsewhere as well.

---

14. Compare Voucher Register

If the problem primarily concerns Payment vouchers, examine the relevant voucher register/report.

Instead of mixing Payment, Receipt and Contra transactions together, inspect Payment vouchers separately.

You may discover that the Payment series itself is correct, while the combined bank ledger only appears irregular because it contains transactions from multiple voucher types.

---

15. Check Whether the Voucher Dates Are Actually Identical

Do not rely solely on voucher numbers.

Open several affected vouchers individually and confirm the date.

For example:

If all dates are identical but their display order remains unexpected, investigate the report/display behaviour and voucher history/configuration further.

---

16. Do Not Renumber Vouchers Just to Make the Ledger Look Better

This is important for accounting data.

Do not start changing voucher numbers merely because the report looks visually uneven.

Changing voucher numbers unnecessarily can create much bigger problems involving:

• Audit trail
• Voucher references
• Internal accounting controls
• Bank reconciliation
• Supporting documents
• External audit
• User tracking
• Edit Log
• Data exports
• Historical references

The first objective is to understand why the report is displayed that way, not to cosmetically rearrange accounting data.

---

17. Does Uneven Voucher Placement Affect the Balance?

Not necessarily.

Consider:

Opening Balance: ₹1,95,951.40

If the transactions and debit/credit amounts are correct, the closing balance can still be mathematically correct even when several same-date transactions appear in an unexpected visual order.

However, there is an important consideration.

The running balance displayed between transactions depends on transaction sequence.

Therefore, if you are trying to match the ledger line-by-line with a bank statement, the ordering of same-day transactions can become operationally important even when the final closing balance is correct.

---

18. Why Bank Reconciliation Can Make This More Noticeable

Banks may process multiple transactions on the same day in an order different from the order in which they were entered in Tally.

For example, your bank statement might show:

Cheque → Bank Charges → NEFT → Cash Deposit → Salary

while your accounting vouchers were entered:

Salary → Cash Deposit → NEFT → Cheque → Bank Charges

Both sets of transactions may produce the same closing balance after all transactions for the day are considered, but the running balance after each individual transaction will differ.

This is one reason bank reconciliation should focus on transaction identity, amount, dates, instrument/reference details, and reconciliation status rather than expecting voucher numbers alone to mirror the bank statement.

---

19. Recommended Troubleshooting Procedure

When you encounter this issue, use the following sequence:

1. Take a backup of the Tally company data before making structural changes.
2. Open the affected ledger and identify one problematic date.
3. Note the Voucher Type and Voucher Number of all transactions on that date.
4. Separate Payment, Receipt, Contra, Journal and other voucher types.
5. Check whether the apparently irregular numbers actually belong to different voucher series.
6. Open individual vouchers and verify their actual dates.
7. Check whether voucher numbering is automatic or manual.
8. Check whether the affected vouchers were imported.
9. Check whether vouchers were entered or altered retrospectively.
10. Open the Day Book for the same date.
11. Compare the ledger with the relevant voucher register.
12. Open F12: Configure in the affected report and review relevant display/sorting options available in your TallyPrime release.
13. Do not renumber or delete vouchers merely to change their visual position.
14. If behaviour is still unexplained, test the same data in a backup/copy before making corrections to production data.

---

20. Example Diagnosis

Suppose a ledger shows:

Payment 3881

Contra 288

Payment 3882

Payment 3887

Payment 3886

Payment 3885

Payment 3884

Payment 3883

The first conclusion should not be:

"Voucher numbering is corrupted."

Instead, investigate it in two parts.

Part A – Contra 288 between Payment vouchers

This can be perfectly normal because Contra and Payment can have separate numbering series.

Part B – Payment 3887 before Payment 3883

This deserves further investigation because these belong to the same voucher type.

Check:

Date + voucher configuration + report configuration + alteration history + import history + numbering method

This method provides a much more accurate diagnosis.

---

21. When Should You Suspect an Actual Data Problem?

Further investigation is warranted if you find symptoms such as:

• Voucher disappears completely
• Duplicate voucher numbers unexpectedly appear
• Voucher opens with different information
• Ledger balance is incorrect
• Debit/Credit amount changes unexpectedly
• Voucher date changes without authorised action
• Data behaves differently on different systems using the same company
• Tally reports data-related errors
• Vouchers become inaccessible
• Company data fails verification/rewrite checks
• Unexpected alterations appear in Edit Log

A strange display sequence alone is not sufficient evidence of corruption.

---

22. Best Practices for Businesses Using TallyPrime

For cleaner accounting and easier auditing:

Use automatic numbering where appropriate. This reduces manual numbering mistakes.

Restrict voucher alteration rights. Not every user should be able to modify historical vouchers.

Use proper user-level security. Different accounting staff should have rights appropriate to their roles.

Maintain regular backups. Keep multiple historical backups instead of overwriting a single backup every day.

Review Day Book regularly. This makes unusual entries easier to identify.

Use Edit Log where applicable. It can be valuable when investigating who altered accounting transactions and when.

Document third-party imports. If vouchers are imported through Excel, XML, API or another ERP system, maintain a record of the import process.

---

Conclusion

When TallyPrime ledger entries appear in an uneven order, it does not automatically mean that Tally has damaged, misplaced, or corrupted the vouchers.

The most important point is that a ledger can contain transactions from multiple voucher types, and those voucher types can maintain separate numbering series. Therefore, Payment Voucher 3882, Contra Voucher 288 and Receipt Voucher 83 should not be expected to form one continuous numerical sequence.

If vouchers belonging to the same voucher type and same date also appear in an unexpected sequence, investigate the report configuration, voucher dates, numbering method, back-dated entries, voucher alterations, imports and related transaction attributes.

Most importantly:

Do not alter voucher numbers or accounting data simply to make the ledger visually sequential. First determine whether the issue is only report presentation or an actual data/configuration problem.

---

FAQ

1. Why is TallyPrime not showing vouchers in voucher-number order?

A ledger report does not necessarily use Voucher No. as a universal sorting key. Date, voucher type, report behaviour and other transaction attributes can affect how transactions are presented.

2. Why does Contra Voucher 288 appear between Payment Vouchers 3881 and 3882?

Payment and Contra can have separate voucher-numbering series. Therefore, their numbers should not be compared as one continuous sequence.

3. Is my Tally data corrupted if vouchers appear out of sequence?

Not necessarily. Display order alone does not prove data corruption.

4. Why are Payment vouchers themselves appearing as 3887, 3886, 3885 and 3884?

If the same voucher type on the same date appears unexpectedly ordered, check report configuration, voucher dates, numbering method, imports and whether vouchers were altered or entered retrospectively.

5. Can back-dated voucher entry affect the way the ledger appears?

Yes. A voucher entered later can be assigned an earlier accounting date and consequently appear with transactions belonging to that earlier date.

6. Can different voucher types have separate numbering?

Yes. Payment, Receipt, Contra and other voucher types can have independent numbering configurations.

7. Should I manually change voucher numbers to correct the display?

No. Do not renumber accounting vouchers merely for visual appearance without first determining the cause and understanding the accounting/audit implications.

8. Where should I check report settings?

Open the affected report and press F12: Configure. Review the available display and sorting-related options for your particular TallyPrime version.

9. How can I verify whether a voucher itself is correct?

Open the voucher and verify its date, voucher type, number, ledgers, amount, narration, reference and bank-related details.

10. Should I check Day Book?

Yes. Day Book is one of the best reports for comparing transactions entered on a particular date.

11. Can imported vouchers cause unusual ordering?

They can contribute to unexpected sequences, especially when dates and voucher numbers originate from an external application or import file.

12. Does unusual transaction order affect the closing balance?

Not automatically. If all transactions and amounts are correct, the final balance can still be correct. However, the intermediate running balance can differ depending on transaction sequence.

13. Why doesn't my Tally ledger exactly match my bank statement order?

The bank and Tally may process or record same-day transactions in different sequences. Bank reconciliation should therefore compare the relevant transaction details rather than relying only on display order.

14. Should I rewrite Tally data immediately?

No. Do not use repair/rewrite operations merely because voucher display order looks unusual. First establish whether there is evidence of an actual data problem and take a backup.

15. What should I check first?

Start with Voucher Date → Voucher Type → Voucher Number → F12 report configuration → Day Book → Voucher Register → Numbering Method → Import/Alteration history.

 

#TallyPrime #Tally #TallyAccounting #TallySupport #TallyPrimeSupport #TallyTroubleshooting #TallyTips #TallyTutorial #TallyLedger #LedgerEntries #VoucherEntry #VoucherNumber #VoucherNumbering #VoucherSorting #PaymentVoucher #ReceiptVoucher #ContraVoucher #JournalVoucher #TallyPayment #TallyReceipt #TallyContra #TallyDayBook #TallyReports #TallyConfiguration #TallyF12 #BankLedger #BankReconciliation #BRS #AccountingSoftware #AccountingTips #AccountingSupport #Bookkeeping #BusinessAccounting #TallyUsers #TallyTraining #TallyGuide #TallySolutions #TallyTechnicalSupport #TallyData #TallyBackup #TallyEditLog #AuditTrail #VoucherRegister #LedgerReport #AccountingEntries #BankTransactions #TallyIntegration #TallyImport #TallyPrimeTips #TallyPrimeGuide