Sumarity
Accounting, tax and Treuhand firms

Swiss VAT (MWST) return

Reads sales and purchase ledgers, invoices, bank statements. Produces mWST return, evidence. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

What it decides

Narrow questions, each with a check behind it.

Rate and method per line; input tax recoverable

Proven by code. 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.

ReadsSales and purchase ledgers, invoices, bank statements
ProducesMWST return, evidence
Who signsA person on your team, with every figure traced to its document and every call on record
ProcessFilings, returns and reporting
IndustryAccounting, tax and Treuhand firms
See it run

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.

Swiss VAT (MWST) return · example run Example run
RefItemValueDecided by
SR-0912Restaurant sales, dine-inNormal rate on food consumed on site18,400.00Code · rated
SR-0913Takeaway salesReduced rate · 0.94 · takeaway till key6,210.00Engine · proven
PI-3341Cleaning services, BaselInput tax claimable, invoice complete1,840.00Code · claimable
PI-3350Car leasePrivate share? · 0.701,200.00To a person
PI-3355Software from abroadReverse charge applies · 0.95480.00Engine · proven
Settled 4 To a person 1 Settled wrong 0
Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees.
What it could save

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.

By hand today80 ha month
With Sumarity24 ha month, for the items people decide
Saved56 hCHF 53,760 a year
Questions

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.