VAT working papers that survive an inspection.

1. Why working papers matter

Cyprus requires VAT records to be kept for at least 6 years, and an inspection can reach back across that whole window. When it does, the question is never just “what did you file?” — it is “show me how you got there.” A return without workings is an assertion; a return with workings is evidence.

Good working papers also pay for themselves outside inspections: they make quarter-on-quarter anomalies visible, they let a new staff member pick up a client cold, and they turn the annual audit's VAT section from an excavation into a handover.

2. Anatomy of a defensible VAT file

One file per period, with a consistent internal structure:

• A one-page summary mapping the workings to each box of the return — the page an inspector reads first.
• Per-supplier schedules: every purchase document listed with date, reference, net, VAT rate, VAT amount, and gross, subtotalled per supplier and reconciled to supplier statements where they exist.
• A sales schedule reconciling output VAT to the invoicing system or till records.
• A reverse-charge schedule: foreign services and construction purchases listed separately, with their Box 1 / Box 4 entries.
• An adjustments note: rounding, corrections, anything inferred — each with one line of reasoning.
• The evidence: the source documents themselves, attached or embedded, not filed in a separate archive that drifts.

3. Every figure traces to a document

The core discipline is traceability: any figure in the workings can be followed to the document that produced it in under a minute. In practice that means the schedule row carries the document reference, and the document is in the file — embedded next to the row, not in a drawer or a shared drive with its own naming convention.

This is the single biggest difference between a file that survives an inspection comfortably and one that turns into a week of archaeology. It is also the part manual processes drop first under deadline pressure, which is why we built the workbook output around it: every extracted row carries its source image inside the workbook itself.

4. Reconcile to the bank, within the period

A VAT file that reconciles to itself but not to the bank is only half-checked. The statement is the external truth: payments that appear in the bank but not in the purchase schedules are missing documents; documents with no corresponding payment are accruals, disputes, or duplicates worth a look.

Doing this reconciliation inside the period workflow — statements processed in the same pass as the receipts — catches the gaps while the trail is warm. Doing it at year end means reconstructing what March looked like, in February of the following year.

5. Adjustments worth documenting

Three categories of adjustment recur in every Cyprus VAT file, and each deserves a written line rather than a silent fix:

• Cash rounding. The 5¢ till rounding means Net + VAT misses the printed total by a cent or two. Show the gap in its own column; never bend the VAT figure to force the tie-up.
• Inferred rates. Where a document did not print its rate and one was inferred, the inference and its basis should be visible — a flagged row with the source wording preserved is exactly that.
• Corrections. A duplicate caught, an inclusive total re-read, a miscoded rate fixed: one line each, what changed and why. If the period is later corrected on TFA, this note is the story behind the replacement return.

6. From workings to the return — and to the ledger

The last step is mechanical if the structure held: the summary page totals flow into the return boxes (see the TFA filing guide for the portal side), and the confirmed entries flow into the ledger — posted to Xero or QuickBooks, or imported from the Excel.

The discipline worth keeping: the ledger and the return should be generated from the same workings, not assembled twice. Two parallel preparations is how the books and the return drift apart — and a reconciliation between your own two artifacts is work nobody should be doing.

7. One workbook per supplier — a structure that scales

The per-supplier structure is what keeps the file readable at any size. Ten suppliers or two hundred, the shape is the same: a tab per supplier, a control total per tab, the source documents embedded behind the rows. Questions arrive supplier-shaped (“show me everything from this vendor”), and the file answers them in one click.

This is the structure Pileform outputs natively — which is not a coincidence. The workbook automation page covers how the pile becomes that file without anyone building it by hand.

8. Tools that help

Working papers are a byproduct of a good process, not extra work bolted on:

• Receipt extraction produces the per-supplier schedules with rates per line, inferences flagged, and the rounding shown.
• Quarter-end PDF processing handles the whole period in one drop, statements included, so the bank reconciliation happens inside the workflow.
• Workbook automation embeds the source document next to every row — the traceability of section 3, by default.

The file that survives an inspection is the file you did not have to assemble specially for it.

9. References

• Cyprus Tax Department — record-keeping requirements and retention rules.
• EU VAT Directive (consolidated) — the underlying record and invoice requirements.

For the rest of the quarterly cycle, start at Cyprus VAT essentials.

Want a second pair of eyes on your file structure? Send a redacted example to contact@pileform.com — a person reads it and replies within one business day.