Every decision is a person’s.
Findings wait for a decision: confirm, reject or ask the client. Signing is blocked while any finding is open, and each decision records who and when.
Trial balance reconciliation
Every trial balance account tied to its lead sheet and schedule, both ways.
Upload the trial balance, the lead sheets, the sub-ledgers, the fixed-asset register and last year’s closing. Deixio proposes the ties, code does every tie and footing, and you decide what differs.
Tie-outs break quietly.
A remapped account, a flipped sign, an opening balance that no longer agrees. Each one is easy to fix and hard to find across lead sheets, schedules and registers.
From the plan to the findings, every decision is yours.
02Tests · The AI proposes, you approve
Tests drafted from the evidence and your intent.
The AI looks through the evidence and proposes each test with what it proves, its population, its sources and what counts as an exception. It lists what it noticed and asks its questions. Nothing runs until you approve the plan.
- Agree each account to the lead sheets and statement lines
- Agree control accounts to their sub-ledgers
- Check the TB balances
- Mapping, sign and class
- Suspense balances
03Run · Code checks every figure
Every number from code. Every figure printed there.
Only the approved tests run, over every row. Each number comes from a read-only query on the engine or is quoted from a document line, and each cited figure is read again at its place.
- Every tie and footing.
- Reconciling both ways: register to TB and TB to register.
- Account codes used as keys.
04Results · You decide each finding
Every finding decided by a named person.
Confirm, reject or ask the client about each finding. Signing is blocked while any finding is open, and the conclusion is yours.
- You approve the plan, decide each difference and sign the workpaper.
- The tie-out per account, with its differences
- Findings
At a glance: Trial balance reconciliation
- Every TB account tied to its lead sheet and schedule, both ways.
- Prior-year closing to current-year opening, checked by code.
What you upload
- The trial balance
- Lead sheets and sub-ledgers
- The fixed-asset register
- Last year’s closing
Tests the AI may propose
- Agree each account to the lead sheets and statement lines
- Agree control accounts to their sub-ledgers
- Check the TB balances
- Mapping, sign and class
- Suspense balances
- Footings
- Last year’s closing to this year’s opening
- Items in one source only
The AI proposes tests from your evidence and intent; these are examples, not a fixed list.
What you get
- The tie-out per account, with its differences
- Findings
- The workpaper
What the auditor sees.
Every figure explains itself.
Open a figure to see the page it was read from, the box around it, how sure the AI was and who accepted it.
Watch one procedure run, figure by figure.
In 30 minutes we run a procedure end to end on sample data and show you where every figure comes from.
- A source for every figure
- Human in the loop
- Append-only, hash-chained audit trail
Questions about trial balance reconciliation
What does “both ways” mean?
Code reconciles from the register to the TB and from the TB to the register, so an item in one source only shows up either way.
Is the prior year checked?
Yes. Last year’s closing is agreed to this year’s opening, by code.
Can it use our account codes?
Yes. Account codes are used as the keys for every tie.
Does it check footings and mapping?
The AI proposes tests for footings, mapping, sign, class and suspense balances. Code does every footing.
Which files do we need?
The trial balance, the lead sheets, the sub-ledgers, the fixed-asset register and last year’s closing, in the formats you already have.