The problem is the typing, not the software
Most companies don't need a new system. The software is fine and the logins are fine. What eats the month is the part where someone reads something on one screen and types it into another.
A migration is often the answer nobody wants to hear. A week of retraining, a year of climbing back to where you were, and a bill at the end.
What we built for a financial administration
A supplier document comes in and gets read. The system codes it to the right ledger account, cost center, VAT treatment and period. Then it is ready to post.
This happens inside the bookkeeping that was already there, not next to it. The tools, the logins and the reports people trust stay. What changes is that the typing stops.
Code from the document, not from the supplier
This is the rule that makes it reliable. A careful bookkeeper already works by it: you code from the document, never from the supplier's name.
A description on a bank statement easily sends you to the wrong account. And the period in which a service was delivered is often not the period stated in the text.
A person still signs off
A wrong entry that nobody notices is worse than no automation. You don't see the error, and you don't see where it came from. That is why the flow keeps a human step.
What the system is not sure about is held back instead of guessed. The document and the reasoning come with it, so you can see why it stopped. Approval chains stay where they are.
The person who signs off stays. They get a queue of decisions instead of a queue of typing.
When to build on what exists, and when to rebuild
Most of the time we build on what is there. We find the part that still runs by hand and put the model behind it. Nobody has to learn anything new, and that is often the difference between a project that lands and one that is quietly abandoned.
Sometimes the old system really is the problem. The process lives in a spreadsheet, in one person's head or in software that was never going to bend. Then we rebuild, with the AI designed in. That is the more expensive route, and we tell you so up front.
When is it done?
Before we call it finished, it has to meet three requirements.
- It is faster than the old process, measured against that process and not against a presentation.
- It leaves a trail someone can check, even when a number is questioned six months later.
- Someone who doesn't program can run it.