Operate: keeping it correct after go-live
An agent that was right in March starts being wrong in September. Vendors change document formats, thresholds drift away from practice, models get deprecated, and the process the audit mapped quietly moves. The Finance Engine is infrastructure, and infrastructure gets maintained.
| Measure | Before | After | Change |
|---|---|---|---|
| Close cycle | 9 days | 6 days | 33% faster |
| Exceptions cleared without a person | 31% | 79% | +48 pts |
| Manual hours per year in scope | 18,800 | 6,016 | 68% removed |
| Coding accuracy | 91.2% | 97.8% | +6.6 pts |
| Cost per invoice processed | $6.10 | $3.90 | 36% lower |
- W0Go-live91.2%
- W4Corrections start retuning the classifier94.1%
- W8New vendor invoice format detected96.3%
- W12Confidence floor raised to 0.8297.8%
| Point | Value |
|---|---|
| W0 | 91.2% |
| W2 | 92.6% |
| W4 | 94.1% |
| W6 | 95.4% |
| W8 | 96.3% |
| W10 | 97.1% |
| W12 | 97.8% |
Accuracy climbs because corrections from your team are fed back, not because the model improved on its own. The marked weeks are the events that moved it. Each Engine reaches a different plateau, because each starts from a different baseline and a different exception mix.
Model swaps
Providers deprecate models and better ones arrive. We re-benchmark against your own captured decisions before anything changes, so a swap is measured rather than assumed.
Process drift
Vendors change invoice layouts, the chart of accounts gains cost centres, and a threshold that was right in March is wrong in September. Drift gets detected and the agents retuned against it.
Next workflow along
Collections correspondence and expense review share most of the pattern already built. Scoping the next one is part of the quarterly review rather than a new engagement.
- Drift report: where practice has moved away from what the agents were built against
- Threshold tuning against the decisions your team actually made
- Document and format updates as vendors and systems change
- Accuracy review by exception type, not one blended number
- Business review against the baseline the audit set
- Scoping the next workflow, usually the one adjacent to what already runs
- Model re-benchmarking against your own captured decisions
- Roadmap for the following quarter, with what we would not build and why
Start with the finance workflow that costs you the most
The audit runs 3 to 4 weeks on site at $15–25k, credited in full against a build signed within 90 days. It produces the system map, the exception taxonomy and a build plan, and you own all of it whether or not the build follows.
The before and after columns are modelled from the basis company, and the accuracy curve is the shape we build toward rather than a measurement. Eidral has run no client engagement, so there is no delivered result to show here, and a curve presented as measured would be the one claim on this site that could not survive a reference check.