How to prepare VAT return workpapers with an AI agent

Workpapers are what make a VAT return defensible, and the agent can build most of them: reconcile the VAT control account to the ledgers, map transactions to return boxes, and test input VAT for valid invoices and blocked items. The tax manager decides every judgement, reviews the workpapers and submits the return. Submission is the point the agent never reaches.

What goes into VAT return workpapers, and who owns them?

A VAT or similar sales tax return summarises output tax charged on sales, input tax reclaimed on purchases, and the net payable or repayable for the period, along with sales and purchase values. The return itself is short. The workpapers behind it show how every figure was reached and why it is right: reconciliation of the VAT accounts in the ledger, the mapping from tax codes to return boxes, adjustments, and the checks done on recovery.

The tax manager, or the financial controller in smaller businesses, owns the return and signs or submits it. AP and AR teams own the tax codes applied to transactions day to day. Rules differ by country, and many businesses file in more than one; whether an agent can prepare VAT or sales tax returns depends heavily on how clean that day-to-day coding is. The general bounds for finance agents are in AI agents for finance.

What are the steps, and at what depth?

1. Agent, depth 1: extracts transactions. All postings with a tax code for the period, from sales, purchase and general ledgers.
2. Agent, depth 1: reconciles the control account. Opening balance, VAT on sales, VAT on purchases, payments to or from the tax authority, adjustments, closing balance, tied to the ledger.
3. Agent, depth 2: maps to return boxes. Using the approved tax code mapping. Codes without a mapping are listed, not guessed.
4. Agent, depth 1: tests input VAT. Valid tax invoice on file with the supplier's registration number; items blocked from recovery under your rules, such as certain entertainment or cars; purchases that relate to exempt activity, which may need apportionment.
5. Agent, depth 1: tests output VAT. Rates applied by product or service against the approved rate table; reverse charge and cross-border supplies coded correctly; credit notes linked to their original invoices.
6. Agent, depth 2: drafts adjustments. Errors from previous periods, bad debt relief where your regime allows it and the conditions are met, partial exemption calculations, each with working.
7. Person, tax manager: decides. Every adjustment, every borderline item and the treatment of anything unmapped.
8. Agent, depth 2: drafts the return and workpaper file. Figures, workings and evidence index.
9. Person, tax manager: reviews and submits. Under their own credentials.

Why does submission stay with a person?

Filing a return is a declaration to the tax authority by the business. Once filed, corrections follow formal routes and may carry penalties or interest. It is a clear point of no return in the finance calendar. Submission also usually requires credentials tied to a named person or an authorised agent of the business, and those should not be shared with software.

The agent's role ends with a complete, reconciled, evidenced draft. The tax manager's signature means they reviewed it and stand behind it.

Which controls matter, and what evidence does each leave?

Control account reconciliation. The return's net figure equals the movement on the control account, after explained adjustments. Evidence: the reconciliation on the first page of the file.

Mapping under change control. Only the tax manager changes the tax code mapping. Evidence: mapping version and change log.

Invoice validity. Each large input VAT claim has a valid tax invoice on file. Evidence: the test results with invoice references.

Adjustments decided by name. Evidence: the decision log with reasons.

Prior returns consistent. The agent compares box totals with previous periods and flags unusual movements. Evidence: the trend table.

What evidence does each control leave for an inspection?

When a tax authority inspects, it asks how a box figure was built and to see invoices behind sampled transactions. The workpaper file should answer both: every box drills down to transactions, and every sampled transaction links to its invoice. The agent can assemble this index each period, which turns a stressful inspection into a retrieval exercise.

What should you measure?

• Unmapped tax codes each period.
• Input VAT claims without valid invoices found before submission.
• Errors found after submission, by cause.
• Days from period end to submitted return.

Where does it usually go wrong?

Coding errors at source. An invoice coded standard-rated when it was reverse charge flows straight into the return. The agent's tests catch patterns, such as foreign suppliers coded with domestic VAT.

Bad debt relief claimed too early or twice. Relief usually has conditions and must be repaid if the customer later pays. Link claims to the bad debt provision workpapers and to later receipts.

Exempt and taxable activity mixed. A business with some exempt income may recover only part of shared input VAT. The calculation is mechanical once the method is agreed; agreeing the method is the tax manager's job.

Credit notes orphaned. A credit note reduces output VAT without a link to its original invoice. The agent flags any it cannot link.