01
Client data lives in a dozen systems
Ledger, practice management, payroll, document store, bank feeds, spreadsheets on a partner's desktop. Nobody can answer a portfolio-level question without a week of manual assembly.
FOR ACCOUNTING PRACTICES & CORPORATE FINANCE TEAMS
Every AI pitch to a finance function runs into the same wall: a number that cannot be traced cannot be signed off. We build the layer underneath, reconciled ledgers, classified client data, retention you can evidence, and then put AI on top of it, where it is defensible.
WHAT WE HEAR
Five things come up in nearly every conversation with a practice principal or a finance director. None of them is solved by buying another AI assistant.
01
Ledger, practice management, payroll, document store, bank feeds, spreadsheets on a partner's desktop. Nobody can answer a portfolio-level question without a week of manual assembly.
02
The month-end control that matters most is the one least automated, and the evidence of it lives in someone's inbox rather than in a system.
03
TFNs, bank details and identity documents scattered across systems and archives, with retention obligations that are a policy document rather than a scheduled job.
04
Risk says no, and risk is right, because there's no classification, no access model and no audit trail for what the model would see.
05
Rulings, policy notes, prior-year workpapers and internal precedent sit across SharePoint, email and a wiki. Juniors ask seniors; seniors become the bottleneck.
THE PATTERN
Which is why we fix them in that order, consolidate, reconcile, classify, then automate. AI goes on last, once there's something underneath it worth asking questions of.
THE FINANCE SEQUENCE
Finance teams are not blocked on AI capability. They are blocked on being able to show where a number came from, which is a consolidation and reconciliation problem and has to be solved first.
So what: an AI assistant on unreconciled ledgers is a confident narrator of numbers you cannot defend. The sequence is not bureaucracy, it is what makes the fourth step sellable to your auditor.
One view of each client across engagements, billing, lodgement status and service lines, so partners can see concentration, churn risk and cross-sell without a manual pull.
Source-to-target checks that run every load, flag the exceptions, and leave an evidence trail, written in SQL your team can read and extend.
Find where client identity and bank data sits, classify it, mask what doesn't need to be readable, and automate disposal when the retention period ends.
Rulings, policy notes, templates and prior-year workpapers indexed into one search a junior can actually use, with permissions respected at retrieval.
WIP, realisation, lock-up, utilisation and lodgement dashboards on one agreed set of definitions, so the partner meeting argues about the business rather than the numbers.
Moving ledgers and client records to a new platform, with every object converted, validated and reconciled, and proof that nothing changed in translation.
More in the use-case library: 36 named use cases, each with the data it needs and the proof pattern behind it.
A dashboard that's roughly right is worse than no dashboard. Everything we build carries reconciliation evidence, because a partner's name goes on the output.
PII classification and access control come before analytics, not after. Onshore by design, your client data stays in your Australian environment.
Disposal runs on a schedule and reports on itself. “We think it was deleted” isn't an answer when someone asks.
Code in your repositories, rules in SQL your team reads, documentation and runbooks at handover. No dependency on us to keep the lights on.
RELEVANT EXPERIENCE
MetLife, reconciliation, load audit and organisation-wide PII classification for a global insurer.
Coal LSL, a federal statutory authority's regulated estate moved and reconciled object by object.
RESIMAC & IAG, lending and insurance migrations with regulatory reporting logic and reconciliation frameworks.
HOW TO START
We profile your ledger, practice-management and document systems, find the client PII, and tell you what it would take to put AI anywhere near them.
Fixed price from [YOUR PRICE]
Scope the auditPick one from the list above. We deliver it on your data, in your environment, with an evaluation record and the governed foundation underneath it, which you keep whatever you decide next.
WHAT FINANCE ACTUALLY ASKS FOR
Finance teams open the conversation talking about AI and spend it talking about reconciliation. This is the order the requests actually arrive in across the engagements and conversations behind this page.
So what: the first three items are prerequisites for the fifth. A firm that sells you the fifth without the first three is selling you a demo.
THE EVIDENCE CHAIN
Every number a finance team quotes should be traceable back to the transaction that produced it. An AI assistant does not change that requirement, it raises it, because the assistant will be quoted more often and questioned harder.
So what: this chain is what “show your working” means in practice. It is also the difference between an assistant your auditor tolerates and one they reject.
Thirty minutes with our principal architect. We'll tell you what sits underneath it, what it would take to fix, and whether it's worth fixing at all.