This is not tax advice. VAT obligations, reporting periods, and filing rules depend on your context. Confirm specifics with your accountant/tax advisor.
The goal of this post is operational:
Create a VAT payment workflow that is repeatable and auditable.
If you want the product overview first:
Why VAT payments go wrong (even when teams are competent)
VAT payments become risky when:
- the “VAT number” is calculated in a spreadsheet without a clear source of truth
- adjustments are made without explicit reasons
- the payment reference is stored somewhere else (bank portal notes, email, etc.)
- evidence (tax invoices) is incomplete at close
None of those are accounting problems. They are workflow problems.
Step 1: make the VAT period explicit
A VAT payment should always have:
- period start date
- period end date
- a clear calculation moment (“this is the position we reviewed”)
If the period is not explicit, you cannot reliably reconcile later.
Step 2: calculate the VAT position from a ledger foundation
The VAT calculation should be derived from structured VAT records (not copied from ad-hoc totals).
Operationally, that means:
- input VAT and output VAT are tracked with consistent categorization
- every record ties back to an operational source (invoice/payment/journal)
- evidence is retrievable when needed
Start here if your evidence trail is weak:
Step 3: treat adjustments as first-class records
Adjustments happen. The control is not “avoid adjustments”.
The control is:
- every adjustment is explicit (value + reason)
- ownership is clear (who applied it)
- it can be reviewed later without guessing
If adjustments live in someone’s spreadsheet comments, you are accumulating risk.
Step 4: record payment references and context
At minimum, capture:
- payment date
- payment reference (from the bank/payment system)
- notes (what this covered, any anomalies)
If your business requires evidence for payment approvals, pair this with:
Step 5: make the workflow safe to re-run
In real finance ops, retries are normal:
- the first calculation is reviewed and then questioned
- evidence arrives late
- a data issue is fixed and you re-run the period
Your workflow should be designed so re-running is safe.
“Just re-run it and then clean up duplicates” is not enterprise-grade.
A minimal VAT payment runbook (copy/paste)
Use this runbook each period:
- Confirm evidence completeness (missing invoice queue is small and explicit)
- Select the VAT period
- Calculate VAT position (input/output + net payable)
- Apply adjustments with reasons (if needed)
- Record VAT payment (date + reference + notes)
- Keep the audit trail stable (no silent edits)
In Gestio, that maps directly to:
What to do next
If your VAT payment process currently depends on one person and one spreadsheet:
Start by making the period, adjustments, and evidence links explicit.
If you want help designing a clean end-to-end workflow, contact us: