Cost Centres in TallyPrime – FAQ
You can disable Cost Centres in TallyPrime when you do not need to use the feature anymore. Before doing so, ensure that you take a data backup. You can refer to the section Disable Cost Centre in TallyPrime in the topic Cost Centre or Profit Centre in TallyPrime.
Currently, there is no provision to import the cost centre classes from one company to another. You need to create it manually.
No, it is not possible to create a Sub Cost Category under a Cost Category.
You can create a Delivery Note with Cost Centre allocations.
However, you cannot use cost centres in a Receipt Note in TallyPrime.
Currently, TallyPrime does not provide an option to view the final accounts cost centre-wise. However, you can check relevant add-ons available in TallyShop.
Yes, you can view Cost Centre details in ledger reports in TallyPrime.
To know more, click here.
If Cost Centre as Employee is enabled and no transactions are allocated, you can delete the cost centre. But if there are transactions recorded, the change cannot be reverted, so it’s best to create a new cost centre instead. To know more, click here.
Cost Centres are meant for tracking income and expenses by departments, projects, or locations, not for managing physical stock or inventory. Therefore, they can only be allocated in accounting vouchers.
Errors & Resolution
Reason: The error occurs when the Cost centre applicability is disabled for the ledger or the cost centre is not allocated to the ledger value. The error may also occur during voucher import from Excel or other software.
Solution: To solve the error, follow the steps below:
-
-
Check if the cost centre applicability is enabled in the ledger
-
In case of purchase, change the mode to as voucher and allocate the cost centres to the ledgers with the correct value
-
In case of other voucher types, cross-check with the ledger value allocated in the Cost centre allocation screen and correct it. Try saving the voucher.
-
This message appears when there is a mismatch in the cost category classification of the cost centre between the importing company and the exporting company.
For example, if the exported data includes a cost centre named C under the Primary Cost Category, but in the importing company, C exists under a Secondary Cost Category, the mismatch triggers this message.
To resolve this, simply update the cost centre in the importing company and reassign it to the Primary Cost Category.
Once updated, you can proceed with importing the transactions smoothly.
