VAT-02 · FlowCount VAT

VAT return ↔ GL ↔ e-invoice reconciliation

Rebuild every VAT return line from the ledger and from e-invoices.

إقرار ضريبة القيمة المضافة مطابق للدفاتر والفواتير

Pilot availableFor: VAT manager · Financial controller · Head of Tax

90,605

VAT at risk across 12 exceptions in a 30-line, three-entity sample

Basis: illustrative sample engagement (fictional data)

The problem

A VAT return is a set of boxes that should each rebuild from the ledger and from the e-invoice population. Today that check lives in a quarterly working file: output and input listings pasted from the ERP, a tab for customer advances, a tab for non-Saudi customers, a sample tab, and formulas that break when the extract changes. When the boxes don't rebuild, nobody knows whether the return, the ledger or the e-invoice data is wrong until an audit asks.

“If your VAT return can't be rebuilt from your ledger, it can't be defended.”

What FlowCount does

A three-way reconciliation of the ERP ledger, the e-invoice population and the VAT return, run before filing. Every difference is classified as timing, mapping, data quality, missing document, duplicate or a true tax exception, quantified, and routed to a reviewer. Material unresolved differences block "ready to file".

AI and rules used
Rules first; LLM VAT-treatment proposals for untagged lines; anomaly detection
Builds on
FlowCount data contract and client mapping memory

How it works

Who does each step

  1. 01Rules

    Standardise the data

    Map client columns to the FlowCount data contract; normalise dates, tax codes and sign conventions, keeping the raw values beside them.

  2. 02Rules

    Reconcile three ways

    ERP invoices missing from the e-invoice population and the reverse; period, taxable value and VAT differences; duplicates, orphan credit notes and cancelled invoices still posted.

  3. 03AI

    Read what rules cannot

    Propose a VAT treatment for descriptions and manual journals with no tax code, quoting the words relied on, for reviewer confirmation.

  4. 04Reviewer

    Clear or correct

    Confirm timing items and manual adjustments; correct the rest. The client mapping is stored and reused next period.

What you send

  • GL detail with VAT codes, journal source and posting user
  • Sales and purchase registers
  • E-invoice extract (UUID, clearance status)
  • Filed or draft VAT return
  • Customs declarations for exports and imports (optional)

What you receive

  • Three-way reconciliation by return box
  • Exception register with cause, VAT effect and owner
  • Excel working paper in the tab structure your team already uses
  • Correction schedule and reviewer sign-off

Controls built in

  • Material unresolved differences block "ready to file"
  • Manual journals to VAT control accounts flagged when they match no invoice
  • AI-coded journals always reviewed
  • Over-declared VAT reported apart from VAT at risk, never netted

KPIs we report

  • Unexplained variance per period (target 0)
  • Exceptions cleared before the filing deadline
  • Time to close the VAT file

Sample input → expected output

What the result looks like

Basis: illustrative sample engagement (fictional data)

Headline from the sample (30 lines, three entities, Jun to Sep 2025)
MeasureAmount
Output VAT under-declared (wrong rate, wrong VAT amount)22,100.00
Input VAT at risk (zero-rated purchase claimed; invoice without the buyer VAT number)24,180.00
Reverse charge not self-assessed (imported cloud services booked as domestic)19,200.00
Zero-rated export with no export evidence on file25,125.00
Total VAT at risk90,605.00
Over-declared: VAT charged on an exempt supply, and a credit note with the wrong sign (reported separately, never netted)12,600.00
Declared in the wrong period (a June invoice in Q3)13,500.00
Expected output: exception register from the sample
LineEntityDocumentWhat the check foundCauseVAT effectStatus
6Electronics distributorTax invoice, domestic sale5% rate on a standard-rated supply; expected 15%True exception15,600.00FAIL
16IT services companyTax invoice, software milestoneVAT 25,000.00 on 210,000.00; expected 31,500.00True exception6,500.00FAIL
24Food manufacturerTax invoice, residential rentVAT charged on an exempt supplyTrue exception(11,250.00)FAIL
26Food manufacturerPurchase, basic food ingredientZero-rated invoice mapped as standard-rated; input VAT claimedMapping13,500.00FAIL
18IT services companyImported cloud servicesBooked as a domestic purchase; reverse charge not self-assessedMapping19,200.00FAIL
4Electronics distributorExport saleZero-rated on the e-invoice, standard-rated in the ERP mapping: wrong return boxMapping0.00FAIL
12Electronics distributorCredit noteCredit note entered with positive amounts: output VAT overstatedData quality(1,350.00)FAIL
23Food manufacturerTax invoice dated 28-Jun-2025Prior-period invoice included in Q3Timing13,500.00FAIL
7Electronics distributorTax invoiceInvoice number already used on line 1, with a different customer and UUIDDuplicate0.00FAIL
9Electronics distributorPurchase invoiceBuyer VAT number missing; input VAT claimedMissing document10,680.00INDETERMINATE
5Electronics distributorExport saleZero-rated, with no export declaration on fileMissing document25,125.00INDETERMINATE
29Electronics distributorTax invoiceRemark says a discount was applied; the discount field is nilData quality0.00INDETERMINATE

Bracketed amounts are over-declared and reported apart from VAT at risk. Line 23 is a timing item: the VAT is due, but in Q2, so the question is whether Q2 needs a correction. The other 18 lines passed, including three reverse-charge purchases, two imports with VAT paid at customs, three credit notes, two zero-rated exports with evidence on file and a business-to-government sale.

How every difference is classified
CauseWhat it meansWho clears it
TimingRight amount, wrong period: invoice date, posting date and tax point disagreeReviewer confirms; corrected in the right period
MappingThe tax code or return box does not match the substance of the supplyReviewer; the corrected mapping is remembered for next period
Data qualitySign errors, missing fields, values that do not reconcileFinance team fixes at source
Missing documentA tax invoice, export declaration or buyer VAT number is not on fileRequest raised; INDETERMINATE until received
DuplicateThe same invoice number, UUID or amount appears more than onceFinance team cancels or reissues
True tax exceptionThe VAT treatment is wrong and the return is misstatedCorrected before filing, or by voluntary disclosure
Expected output: line-level reconciliation, one period (illustrative)
Return lineFiledGL rebuildE-invoice rebuildFiled − GLCauseStatus
Standard-rated sales4,820,000.004,820,000.004,795,000.000.001 credit note in GL not reported to FATOORAFAIL
Zero-rated / exports610,000.00610,000.00610,000.000.00PASS
Reverse-charge imports0.00225,000.00n/a(225,000.00)Management fee RCM not declared (see reverse-charge VAT)FAIL
Standard-rated purchases2,140,000.002,152,300.00n/a(12,300.00)Manual journal JV-0412 with no VAT code: AI proposal, then reviewINDETERMINATE

Portfolio scorecard

Where it sits on the roadmap

Value

4.90 / 5

Feasibility

4.00 / 5

Priority index

6.53 · rank 11 of 27

Quadrant

Quick win

Delivery

Wave 1 (0-3 m)

T-shirt size M: 4 to 8 weeks with 2 engineers + 1 tax SME + 0.25 QA, indicative build 120k to 275k. New data source or document type + rules + review-UI changes. How we score and sequence →

Rebuild every VAT return line from the ledger and from e-invoices.

A pilot runs on your own data, under the full G0 to G7 gate model, with a partner signature on every conclusion.