Your data
Hand your CA the Tally file
Hand your CA a file they can import straight into Tally — sales, purchases, purchase returns, receipts, payments, expenses and opening balances.
Why your CA asks for this
Most CAs in India run Tally. If your books live somewhere they cannot import, every month turns into a re-typing job — and that argument usually ends with the business moving back to whatever the CA prefers.
So Dukaaan exports the vouchers in the format Tally imports.
Exporting it
Go to Reports → Tally export, choose a date range, and download. You get one XML file covering sales, credit notes, purchases, purchase returns, receipts, payments and expenses for those dates — plus your opening balances, when the dates include the day your books begin.
You can export the same range as many times as you like. Nothing is consumed and nothing changes in your books.
What your CA should know before importing
A purchase you entered in Dukaaan comes across the way your books hold it: Purchase for the value of the goods, and the GST your supplier charged on the Input CGST/SGST/IGST ledgers beside it. The Purchase ledger in the file and the one in Dukaaan are the same figure. Claiming the credit is unchanged either way: it comes from GSTR-2B on the portal.
Bills that arrived with a data migration are the exception. Dukaaan holds no input-tax asset for those — they came in as history rather than as entries — so they come across at the full bill value and your CA splits them their usual way.
A receipt you marked as an advance comes across the way it was booked — the money against Cash or Bank, the GST on the output ledgers, and the rest against Advance from Customers rather than against the customer.
Goods you sent back to a supplier come across as Debit Notes — the supplier's ledger debited, and the GST on that return credited back to Input CGST/SGST/IGST, which is how Dukaaan booked it.
Expenses such as rent, salaries and utilities come across as Payment vouchers — the expense ledger for the value, the GST on the Input ledgers where the bill carried any, and Cash or Bank for what actually left. They carry no supplier name, because Dukaaan does not record one on an expense.
Your opening balances come across too, as one Journal voucher dated the day your books begin in Dukaaan — cash, bank, stock, what you already owed suppliers, and your capital. It is only in the file when the dates you pick include that day, so exporting month by month cannot bring it in twice.
If your history came in from another system, what your customers owed you travels with those invoices and receipts whenever the dates you pick cover them.
When the dates leave earlier documents out, each customer and supplier comes across with an opening balance instead — on their own ledger, for what was owed the day before your dates begin. It is one or the other, never both, so nothing is counted twice. Your CA will see the net of those balances under Difference in Opening Balances until they enter the capital side themselves.
Customers and suppliers each get their own ledger, under Sundry Debtors and Sundry Creditors, because that is how Tally expects parties to be held.
Ask your CA to import into a test company first, once. Once you both agree the totals match, the monthly export is a two-minute job.
Checking it went across right
The totals in the file are the same totals as your reports for those dates — they are built from the same figures rather than worked out a second way. The quickest check after an import is your sales total for the period against the same period's report here.
One direction only
This exports out of Dukaaan. It does not import from Tally and it does not sync — there is no live connection between the two, and nothing your CA does in Tally comes back here.