Chapter 05
Ongoing: AI systems drift. This is the part that keeps them honest.
Tax rules change, and each client's deadlines depend on entity, year-end and filing obligations. A reminder system that is a year out of date is worse than none.
Illustrative
A composite company, not a client. We model the inputs and the queue examples, then derive every total from the assumptions shown. A real audit measures each workflow in your operation.
- Profile
- Accounting firm
- Revenue
- €6M
- People
- 40
- Offices
- 2
What the build changes
What the build changes
Before
After
Chase rounds done by hand
Before: 4 by hand
After: 1 by hand
Preparing one annual accounts and tax pack
Before: 1 hr 20
After: 35 minutes
Peak-season workload
Before: chasing spread across the team
After: exceptions visible before review
Who does the chasing
Before: the accountant
After: the system; manager on exceptions
What we keep doing
Better models, on your say-so
We test candidate models against approved cases. We show you the model, version, region and error changes. We switch only after a named person approves, and there is a rollback path.
When the work changes
Tax rules, statutory calendars, engagement terms and team procedures change. We version the rules, test affected workflows and retain the named approver.
The next process
Once the first workflow holds, we agree and price the next process in the audited roadmap before work starts.
- Monthly
- A summary of weekly checks: unmatched documents, reminder errors, deadline exceptions, reviewer overrides and client corrections. One page, with professional decisions kept out of automation.
- Quarterly
- Sit down with the numbers, decide what is worth building next, and price it before anything starts.
Your own version of this
Two weeks, and the arithmetic is about your company.
The audit is where these composite numbers become yours: your processes, your hours, your build order. The first call is free. If it finds nothing worth building, you don't pay.