How to Prepare for a TRA Audit in Tanzania

A TRA audit is not an interrogation. It is a reconciliation exercise: the auditor already holds every fiscal receipt your business has transmitted, and they are checking whether your declarations and your records agree with what they hold. That framing changes how you prepare. You are not assembling a defence — you are making it fast and obvious that three sets of numbers agree. This guide covers what triggers a review, the reconciliation that sits at the heart of it, how to build an audit file monthly so preparation takes hours rather than weeks, and how to conduct yourself while the auditor is on site.

Why businesses get selected

Selection is rarely random. The patterns that draw attention are:

• Inconsistent revenue declarations — turnover that moves in ways the business model does not explain, or that diverges from sector norms.
• A high volume or value of credit notes — the ordinary mechanism for reducing declared sales, and therefore the first place suppression would show.
• Missing Z-reports — gaps in the daily sequence, which read as either undeclared trading days or a device that was not transmitting.
• Late or irregular VAT payments — a signal of stress, and cheap for TRA to detect from their own records.
• Industry risk factors — cash-intensive sectors are reviewed more often, which is not a judgement about you.

None of these is proof of anything, and being selected is not an accusation. But each is worth monitoring yourself, monthly, because you would rather find the anomaly than have it found.

The three-way reconciliation

Almost every audit question reduces to one of three comparisons. Get comfortable with all three and very little can surprise you.

Fiscal records versus your ledger

The sum of your Z-reports for a period, net of credit notes, should equal the revenue recorded in your accounts for that period. A variance means one of: a sale recorded in the books without a fiscal receipt, a fiscal receipt never posted to the ledger, or a credit note applied on one side only. All three are fixable; none is fixable quickly if you first notice them a year later.

Your ledger versus your bank

Recorded revenue should trace to money. It rarely traces exactly, and the legitimate reasons are worth being able to recite: card settlements arrive a day or more after the sale; mobile-money settlements often arrive net of fees, so the deposit is smaller than the sale; cash floats and takings banked the next morning shift amounts across a date boundary; and credit sales sit in receivables until the customer pays. An auditor is not troubled by any of these. They are troubled by a variance nobody can name.

Declarations versus both

Your filed VAT and income tax returns should follow from the same numbers. If your return was prepared from a spreadsheet that was never tied back to the fiscal data, this is where the difference emerges — and it is the comparison the auditor can perform without your help, because they hold both the returns and the EFDMS data.

Build the audit file monthly, not annually

The businesses that find audits stressful are the ones reconstructing two years of records under time pressure. The fix is a standing monthly routine that takes well under an hour:

1. Confirm a Z-report exists for every trading day in the month. Investigate any gap the same week, while people still remember the day.
2. Total the Z-reports, net of credit notes, and tie the figure to revenue in the accounts.
3. Tie recorded revenue to bank and settlement movements, and write a one-line note explaining any variance.
4. Export the credit-note register and check every entry has a reason and an authoriser.
5. File the VAT return and keep the acknowledgement with the working that produced it.
6. Drop all of the above into a folder named for the month, and close it.

Twelve of those folders is an audit-ready year. The note explaining a variance, written the week it happened, is worth more than any explanation constructed eighteen months later.

What the auditor will ask for

Fiscal records

• All Z-reports covering the audit period, in sequence and with no gaps
• Your VFD or EFD certificate and registration documents
• Receipt summaries by month
• The credit note register, with the reason and authoriser for each entry
• Evidence that offline transmissions were queued and subsequently sent

Financial records

• Bank statements for every account the business uses, including mobile-money merchant accounts
• Purchase invoices — the input side matters as much as the output side, particularly for input VAT claimed
• Expense receipts supporting deductions
• VAT returns as filed, with the workings behind them
• Payroll records: payslips, PAYE, NSSF, NHIF, SDL and WCF filings and proof of payment

Business documents

• TIN certificate, and VRN certificate where VAT-registered
• Current business licence from your council
• Company incorporation documents from BRELA
• Lease or title for the premises, and utility accounts in the business name

Keep all of it for at least five years. That retention period is also why paper is a poor archive: thermal receipts fade, and a shoebox does not survive a move or a flood.

The pre-audit sprint

Once a review is scheduled, work in this order:

1. Confirm the scope — which taxes, which periods. Do not volunteer material outside it.
2. Run the three-way reconciliation for every period in scope and list every variance you find, with its explanation.
3. Fix what is genuinely wrong and document the correction. A disclosed and corrected error is a categorically different conversation from a discovered one.
4. Assemble the file in the order above, indexed, so any requested document takes a minute to produce rather than an afternoon.
5. Brief your team — one named point of contact, everyone else routes questions to them. Well-meaning improvised answers from staff cause more trouble than silence.

During the audit

Be cooperative, be professional, and be organised — a business that produces documents promptly reads as a business with nothing to hide, and the review moves faster. Beyond that:

• Answer what is asked. Accuracy over volume.
• Keep a written log of every document handed over, with the date.
• Take notes on every query raised, in your own words, as it is raised.
• Ask for clarification when a question is ambiguous rather than guessing at what is meant.
• If you do not know, say you will check and come back — then actually come back.
• Where the amounts are material or the issues technical, involve your accountant or tax adviser early rather than after a position has hardened.

After the audit

Read the findings against your own records before responding to any of them. Where a finding is correct, settle it and, more importantly, fix the process that produced it — a control that prevents recurrence is the only thing that stops the same finding appearing next time. Where you disagree, respond in writing, with the supporting documents attached, and keep the correspondence with the audit file. Then feed every finding back into your monthly checklist so the same question can never be asked twice.

How Tawala keeps you audit-ready

Most of the work above is only hard because the records live in different places. Tawala Finance holds the complete Z-report history, every transaction with its TRA receipt number, the credit-note register with reasons and authorisers, and VAT reports by period — all searchable, all exportable to Excel or PDF, all retained for the full five years. Because sales, fiscal receipts and the ledger are the same data rather than three systems that have to be tied together, the reconciliation is a report rather than a project. Start with the VFD compliance checklist, then read our guides to EFDMS and Z-reports and credit notes — the two areas audits concentrate on.