Six months ago, we set out to make FinControl feel less like an OCR pipeline with a UI and more like a system that AP teams could actually trust at month-end. Spring ’26 is the result.
The release ships three things together because they’re really one thing: a finance team’s confidence that an invoice will land in the ledger correctly, on time, and routed to the right approver — without anyone babysitting it. Here’s what we changed and why.
Approval engine, rebuilt
The old approval engine was a polite linear chain. It worked, but it forced finance leads to fork their thinking: simple invoices got the same ceremony as a $500K capex commitment, and exceptions piled up in a single inbox.
The new engine is a directed graph with conditional routing, parallel approvers, and dynamic thresholds — all configured in a visual editor that doesn’t require a workflow consultant. A few things teams have already started doing with it:
Threshold-based escalation. Anything over €25K auto-routes to the CFO with a Slack ping.
Parallel approvals for cross-functional spend (e.g. marketing + finance both need to sign off on agency invoices).
Exception lanes. If OCR confidence falls under 92%, route through a human reviewer before approval, not after.
Why parallel matters: 38% of the invoices we see in production need two or more approvers. Forcing them to run sequentially adds an average of 1.4 days to cycle time — and that’s before anyone takes a vacation.
Faster OCR on long invoices
Long invoices — utility bills with hundreds of line items, telco statements, multi-page logistics manifests — were the slowest thing about FinControl. They aren’t anymore. We rebuilt the GPU pipeline around batched line-item extraction, and the result is a 38% reduction in median OCR latency on invoices over 5 pages, with a 62% reduction at the long tail.
Multi-currency line items
Multi-entity, multi-currency setups were the most-requested gap in our coverage. Spring ’26 closes it: invoices can now carry line items in mixed currencies, with FX recorded at invoice date, posting date, or a custom rate per line.
How to roll it out
We’ve staged the release behind feature flags so you can ship it on your timeline. The recommended path:
Mirror your existing approval flow in the new engine. Run them side by side on a test pool of invoices for two weeks.
Enable confidence-based exception lanes once the pipeline feels stable.
Migrate live traffic. The new engine logs every routing decision — the audit trail is the same shape as the old one.
What’s next
Summer ’26 is shaping up to be about the post-approval side of the workflow: posting confidence, ledger reconciliation, and a tighter loop with the close itself. We’ll have more to share at our customer summit in Helsinki on June 18.
#release
#approvals
#ocr
#approvals
#engineering
#spring-26
