EVERY DOCUMENT READ,MATCHEDAND FLAGGED.
Bank statements, slips, invoices and certificates are read against the same rule set used across the engine, then matched line by line to what the return needs.
the engine
mapped
shelved
types
The documents a practice actually receives
Bank statements
Transactions are read and matched against known merchants and categories, with unclear items surfaced rather than guessed. A bank line posts a journal before it can become a claim.
Slips and invoices
Till slips, tax invoices and receipts are read for amount, vendor and VAT status, and matched to expense categories. A statement is never treated as a tax invoice.
IRP5s and certificates
Employer certificates, medical aid certificates and retirement annuity certificates are read for the figures a return needs, per employer.
What the engine does when it is not sure
Every claim is matched to a section of the Act and a known expense category. Where a document is unclear, incomplete or missing, it is queued for a human decision rather than assumed.
Missing proof
A claim with no supporting document is flagged, not silently dropped or silently assumed.
Unclear vendor names
Where the reader cannot confidently name a vendor or provider, the item is queued for confirmation.
Possible duplicates
Transactions and uploads that look like duplicates are surfaced for review rather than counted twice.
Bank statement to CSV
Statements can be converted to Sage- or Xero-ready CSV files as part of the same reading step.
BRING A CLIENT'S STATEMENTTO THE WALKTHROUGH
The clearest way to judge document reading is to see it against a statement you already know the answer for.