UK VAT return for a small business (pub VAT)
Reads till reports, purchase invoices, bank and card statements. Produces mTD VAT return, client questions, evidence. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.
Narrow questions, each with a check behind it.
Each document's VAT treatment; what's missing
Proven by code: boxes from code; quotes on documents. Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.
| Reads | Till reports, purchase invoices, bank and card statements |
| Produces | MTD VAT return, client questions, evidence |
| Who signs | A person on your team, with every figure traced to its document and every call on record |
| Process | Filings, returns and reporting |
| Industry | Accounting, tax and Treuhand firms |
Every line, decided where it's safest.
An example run. Each stage lights up as a line is decided there; pick a stage to see its lines.
| Date | Line | Amount | Decided by |
|---|---|---|---|
| 02.08 | Invoice · Brakes, foodNet + VAT = gross · VAT number valid | 612.40 | Code · tied |
| 06.08 | Booking platform commissionReverse charge: supplier abroad · 0.94 | 184.00 | Engine · proven |
| 11.08 | Online order confirmationNot a VAT invoice: no VAT reclaimed · 0.92 | 86.97 | Engine · proven |
| 14.08 | Card refund to a guestReverses takings of 09.08, to the penny | −95.00 | Code · matched |
| 19.08 | KL-20817 and KL20817Look-alike invoices 3 days apart: the same one? | 1,140.00 | To a person |
| 22.08 | Invoice billed to another businessAddressed to someone else: not this client's | 430.00 | To a person |
|
Settled 4
To a person 2
Settled wrong 0
| |||
Measured, not promised.
Your volumes in. Your hours out.
In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data.
Start from what's closest.
Filings, returns and reporting in other work
Swiss VAT (MWST) return
Rate and method per line; input tax recoverable
Accounting firmsGerman VAT advance return (USt-Voranmeldung)
Treatment per line, reverse charge
Accounting firmsPersonal tax return preparation (UK self assessment)
Income kinds, reliefs that apply
More for accounting firms
What buyers ask
What happens when Sumarity isn't sure?
Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run.
How are its judgements checked?
Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.
Can we change it to fit how we work?
Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it.
Does it read our files as they are?
Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it.
Where does our data go?
Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland.
How does it get better?
Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission.
Start from this workflow. Run it on your data.
A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison.