When you export expenses for Tally, each expense category is meant to become an expense ledger, each account (bank, card, wallet) becomes a bank or card ledger, and each transaction becomes a voucher between the two. The export only works smoothly if the names on your side match the ledger names your accountant already has. Agree those names before you import, not after.
How do the pieces line up?
Tally keeps books in ledgers, and a voucher records money moving from one ledger to another. An expense tracker keeps transactions, each tagged with an account and a category. The two line up like this.
| In your tracker | Becomes in Tally | Example |
|---|---|---|
| Category | Expense ledger | Software subscriptions |
| Account | Bank or card ledger | Savings account, credit card |
| Transaction | Voucher | A ₹1,180 payment on 14 July |
| Date | Voucher date | 14 July |
| Merchant or note | Narration | Monthly plan renewal |
SpendixAI's Export centre has a Tally template, so the file arrives in a shape built for this. What it cannot do is know what your accountant has already named things in their company data. That part is a conversation.
What should I agree with my accountant first?
Five questions cover almost everything. Ask them in one message.
- Do you want me to use your existing ledger names, or will you create new ones from my categories?
- Which of my accounts should be treated as bank ledgers and which as credit card ledgers, and what names should they carry?
- Should GST be shown separately, or will you handle it from invoices?
- Do you want one file for the full year, or a file per month?
- Is there a cut-off date, such as the last day of a quarter, after which entries wait for the next file?
What if my categories do not match their ledgers?
They often will not at first. You might have Eating out, Cafes and Lunch, while your accountant keeps a single ledger called Staff welfare or Meals and entertainment. There are two sensible ways out.
- Rename your categories to match their ledger names before exporting. This is cleaner when the books are mainly for a business.
- Keep your own categories and send a short mapping list: your category on the left, their ledger on the right. This is easier when you also use the tracker for personal insight.
- Never merge categories that your accountant treats differently just to make the list shorter.
Is it safe to import everything at once?
Not on the first attempt. Ask your accountant to import a single month into a test copy of the company data, then check ledger totals against your own reports. If one ledger looks wrong, the mapping is probably wrong, and one month is a cheap place to find that out. A separate article covers this trial habit in detail.
Also remember that an import creates entries inside someone's books. It is their data and their responsibility, so let them do or supervise the import rather than doing it yourself on a live company.
What does not travel across?
Receipts stay attached to transactions in the tracker; they are not stuffed inside a Tally file. If your accountant needs a document, send it separately and name the transaction. GST figures in the tracker are estimates, so treat them as a starting point for your accountant, who works from invoices.
A worked line makes the mapping concrete. Say you paid ₹1,180 on 14 July from your credit card for a monthly software plan. In the books that becomes one voucher: the Software subscriptions expense ledger on one side, the credit card ledger on the other, dated 14 July, with the plan name as narration. Every transaction follows the same pattern.
A short pre-import list
- Category and account names agreed in writing.
- Period chosen and review queue cleared, so nothing is missing.
- One month tested first.
- The mapping list saved next to the exported file for next time.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


