Did invoice processing improve after AI?
Invoices moved faster, ran touchless more often and cost less to approve. The exception rate rose at the same time, so read processing time beside review touches, corrections and exceptions.
Oximy connects AI activity to invoices, reconciliations and forecasts, with the review work and cost still attached.
Oximy matches real AI usage to completed work.
Example stack · Example systems; available sources are confirmed during scoping.
The close, the forecast and invoice processing have different completion clocks.
Invoices moved faster, ran touchless more often and cost less to approve. The exception rate rose at the same time, so read processing time beside review touches, corrections and exceptions.
Matching finished on day one instead of day three and the ledger closed on day four instead of day six, on sixty fewer controller hours. Two more adjustments landed after the close, so keep post-close entries beside the completion date.
One coding suggestion and one human correction produced a posted ledger record in two hours fourteen, at forty-two cents of attributed cost. The approved invoice is the unit; the suggestion on its own is not.
Planning published the rolling forecast four days sooner, and spend checks caught nearly twice as many policy exceptions per thousand reports. An increase in detected exceptions can mean different things; inspect the category before treating it as improvement.