Variance (flux) analysis
Reads trial balances for both periods, budget, drivers. Produces explained variances, questions to owners. 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.
Which movements need explaining; what explains each
Proven by code: drivers sum to the movement. 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 | Trial balances for both periods, budget, drivers |
| Produces | Explained variances, questions to owners |
| Who signs | A person on your team, with every figure traced to its document and every call on record |
| Process | Close and accounting |
| Industry | Finance and accounting |
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.
| Ref | Item | Value | Decided by |
|---|---|---|---|
| 6000 | Salaries +8%Two new hires in September explain it | +24,100 | Code · explained |
| 6200 | Rent +0%No change | 0 | Code · no change |
| 6400 | Marketing +45%Trade fair in September · 0.93 · invoices found | +18,300 | Engine · proven |
| 6500 | IT −30%Annual licence prepaid last year · 0.90 | −6,400 | Engine · proven |
| 4000 | Revenue −12%No driver explains it | −92,000 | To a person |
|
Settled 4
To a person 1
Settled wrong 0
| |||
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.
Close and accounting in other work
Balance sheet account reconciliation and certification
What explains each balance; whether support is enough
FinanceManual journal entry review
Whether an entry is supported, authorised, unusual
FinanceAccruals review
Whether an accrual is needed and its size is supported
More for finance
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.