Skip to content
By team · Finance

Measure AI in finance

Oximy connects AI activity to invoices, reconciliations and forecasts, with the review work and cost still attached.

Copilot for FinanceCopilot for FinanceDatarails AIDatarails AIRamp IntelligenceRamp IntelligenceChatGPT EnterpriseChatGPT EnterpriseClaudeClaudeWorkdayWorkdaySAPServiceNowServiceNow
One AP workflow

Follow one invoice from AI suggestion to approval.

The invoice is the thread through the review.

Finance AI tools
Copilot for FinanceCopilot for FinanceCoding and review drafts
Datarails AIDatarails AIPlanning and analysis
Ramp IntelligenceRamp IntelligenceSpend and policy checks
Oximy
Finance systems
WorkdayWorkdayInvoices and approvals
SAPLedger and postings
ApprovalsOwner sign-off and exceptions
Completed workApproved invoice
Beyond one workflow

Answer the finance questions behind an AI rollout.

The close, the forecast and invoice processing have different completion clocks.

Same AP workflow, before and after
Before AIAfter AI
Median processing time3.8d1.9d
Touchless processing18%63%
Review hours per 1,000110h64h
Exception rate4.2%5.1%
Cost per approved invoice$4.80$3.10

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.

Month-end close · matching and certification events
2,180 transactions matchedDay 3 → 1
46 of 46 accounts certifiedDay 5 → 3
Period closed in the ledgerDay 6 → 4

Did the close finish sooner?

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.

Invoice INV-2041 · 2h 14m · $0.42 attributed
StageRecordInvoice receivedINV-2041 entered APAI suggested codingCoding suggestion, GL 6100Finance reviewedCost centre correctedInvoice postedLedger record approved

What is on the record when an invoice is approved?

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 and spend, same measures
Before AIAfter AI
Days to publish the forecast95
Policy exceptions per 1,0003158

Which other finance workflows moved?

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.

Next step