Fixing Cost Break-up Total Mismatch Error in TallyPrime

When entering payments, receipts, or journal vouchers with cost centres enabled, TallyPrime requires you to allocate the ledger expense to specific cost units. If the sum of these allocations does not match the ledger total, Tally blocks the entry.

In TallyPrime, Cost Centres are a powerful tool for tracking expenses and income across departments, projects, branches, or employees. By breaking down costs, businesses gain detailed insight into operational efficiency. However, TallyPrime enforces strict double-entry and ledger allocation checks. If the sum of the allocations assigned to your cost centres does not match the primary ledger value, TallyPrime will prevent you from saving the voucher. This guide covers how to identify, resolve, and prevent cost break-up mismatch errors in your database.

Why Allocation Mismatch Errors Occur

This error occurs when the mathematical checks built into TallyPrime fail to validate the ledger breakdown. This typically happens in three scenarios:

Understanding Multiple Cost Categories and Mismatches

TallyPrime allows you to create **Cost Categories** to track expenses across different dimensions. While a Cost Centre represents a specific department (e.g., 'Sales' or 'Admin'), a Cost Category represents a separate classification metric (e.g., 'Projects' or 'Employees').

For example, if you pay a consultant ₹1,00,000, you might want to allocate this expense across two dimensions:

1. Category 1 (Projects): Allocate ₹60,000 to Project A and ₹40,000 to Project B.
2. Category 2 (Departments): Allocate ₹50,000 to Marketing and ₹50,000 to Research & Development.

In this scenario, TallyPrime opens a sub-screen for *each* active category. The allocation sum for **each category** must equal the primary ledger amount of ₹1,00,000. If Category 1 sums to ₹1,00,000 but Category 2 sums to ₹99,990 due to a rounding error, Tally will trigger a Cost Break-up Mismatch.

How to Resolve the Allocation Mismatch

The method for resolving the mismatch depends on whether you are entering vouchers manually or importing data from external files.

1. Resolving Manual Entry Errors

If you are typing a transaction and TallyPrime displays a popup alert preventing you from saving:

1. Review the total expense amount entered on the main voucher screen (e.g., Rent Expense = ₹50,000.00).
2. On the Cost Allocations sub-screen, check the listed amounts for each cost centre.
3. Look at the **Total** row at the bottom of the allocation table. If it shows ₹49,999.98 or ₹50,000.02, adjust one of the allocations to resolve the discrepancy.
4. Ensure the total allocation matches the primary ledger amount exactly, and press Ctrl+A to save the allocation sub-screen.

2. Fixing XML Import Payload Mismatches

If you are importing data via XML or ODBC and see this error in your import logs (tally.imp), the issue lies in your data payload structure. Tally's schema requires that the parent ledger's AMOUNT tag matches the sum of the nested AMOUNT tags under the COSTCENTRE.LIST node.

Below is a sample of a correctly formatted Tally XML node showing a balanced expense allocation:

<ALLLEDGERENTRIES.LIST>
  <LEDGERNAME>Rent Expenses</LEDGERNAME>
  <ISDEEMEDPOSITIVE>Yes</ISDEEMEDPOSITIVE>
  <AMOUNT>-50000.00</AMOUNT>
  <CATEGORYALLOCATIONS.LIST>
    <CATEGORY>Primary Cost Category</CATEGORY>
    <COSTCENTREALLOCATIONS.LIST>
      <NAME>Mumbai Branch</NAME>
      <AMOUNT>-30000.00</AMOUNT> <!-- 60% allocation -->
    </COSTCENTREALLOCATIONS.LIST>
    <COSTCENTREALLOCATIONS.LIST>
      <NAME>Delhi Branch</NAME>
      <AMOUNT>-20000.00</AMOUNT> <!-- 40% allocation -->
    </COSTCENTREALLOCATIONS.LIST>
  </CATEGORYALLOCATIONS.LIST>
</ALLLEDGERENTRIES.LIST>

In the XML example, the sum of the two cost centre allocations (-30000.00 and -20000.00) equals the parent ledger's amount of -50000.00. If these values do not balance, TallyPrime will reject the voucher and log an error.

Using Exception Reports to Find Mismatches

TallyPrime features a dedicated Exception report tool to scan historical transactions and find cost allocation anomalies:

• Go to Gateway of Tally > Display More Reports > Statements of Accounts > Cost Centres > Ledger Break-up.
• Press F6 (Category-wise) to review transactions sorted by categories.
• Look for any ledger balance that contains unallocated amounts. Open the transactions and correct the allocations.

Disable Cost Centres for Non-Expense Ledgers

Many mapping errors are caused by cost centre settings being enabled on ledgers that do not require them (such as tax ledgers, round-off ledgers, or asset accounts). To review and clean up these settings:

1. Go to Gateway of Tally > Chart of Accounts > Ledgers.
2. Click Multi-Alter (or press Alt+H) and select All Items.
3. Look at the **Cost Centres Applicable** column. Change the setting to No for all balance sheet, tax, and non-departmental ledgers.
4. Press Ctrl+A to save the changes. This prevents TallyPrime from displaying the allocation sub-screen for these accounts.

Prevent Import Failures with TrulyInvoice

Manually checking cost centre allocations for hundreds of monthly invoices is a slow and error-prone process. If you use custom PDF templates or legacy import utilities, even a single rounding error can stop the import.

Using TrulyInvoice helps you avoid these import errors. TrulyInvoice automatically extracts invoice details, validates ledger mappings, and verifies that tax allocations and totals are perfectly balanced. The system detects rounding differences and balances the payload, ensuring a smooth, error-free sync to TallyPrime.