See what OmniPATH saves you. In hard numbers.
Processing cost reduction. Time saved. Duplicates caught. Match rates improved. Every ROI metric computed from your live platform data - not a spreadsheet estimate, not a sales-deck projection.
Cost. Time. Risk. Quantified.
The four numbers every finance leader asks about - answered with platform data, not estimates. Each metric ships with period-over-period comparison built in.
Eight angles on "is this worth it?"
Cost savings, time saved, accuracy, automation rate, duplicate prevention, match rate, pipeline throughput, anomaly detection. Each one a clear number with a clear source - drawn from the processing analytics and financial analytics modules already running.
Total documents processed × £17.50 manual benchmark, less the platform processing cost at £1.00 per doc. Net savings converted to your org currency at the posting-date FX rate.
Wall-clock processing time vs 12 minutes per doc manual baseline. Returned as both a time_saved_seconds integer and a formatted HH:MM:SS string. Wall-clock accounts for parallel processing - doesn't double-count.
3-signal composite - verified (human-reviewed gold standard) → confidence (AI self-assessment) → quality (pipeline assessment). Uses the highest-priority signal available, returns method so you can see which.
Percentage of invoices that processed without any human edits - touch-free vs single-touch vs multi-touch. Every touch-free document is 12 minutes of finance time eliminated.
Number of duplicate invoice groups detected, plus the total_potential_value at risk. Per-cluster detail with invoice number, supplier, occurrence count and group total - actionable, not just a count.
PO vs GRN vs Invoice match rate. Returns fully_matched, partial_matched, unmatched counts plus the match_rate_pct. Every unmatched invoice is manual investigation work avoided.
Operational throughput of the AI processing pipeline - throughput_per_hour, latency_p50 / p95, processing_p50, avg_queue_time, worker_utilisation. The "is the platform keeping up?" answer.
Clean-vs-flagged document split, plus separate trend endpoints for anomaly rate and fraud rate over time. The flagged-document count - the things a human reviewer would have missed at scale.
From £17.50 to under £1. Per document. [methodology]
The £17.50 manual benchmark is the industry-standard figure for end-to-end AP invoice processing - receipt, data entry, coding, matching, approval routing - sourced from Ardent Partners and IOFM research. The £1.00 OmniPATH cost is the actual platform processing cost per document. The maths is straightforward; the savings compound fast.
- Hardcoded benchmarks ·
£17.50manual /£1.00platform · industry-standard, defensible, consistent across orgs - Multi-currency · ECB FX rate at processing date · totals reflect what the cost was on the day, not today
- Computed per-query · pulled from
/v0/analytics/performanceon every call · always reflects the live data - Filterable · scope by site, area, team, supplier, category, date range · "what's our ROI on FS Foodservice specifically?"
Three signals. One accuracy number.
Model accuracy is hard to express with a single number - every signal has a different cost and confidence. The cascade resolves this: verified (human-reviewed) is the gold standard and used wherever available; confidence falls back when verification is sparse; quality is the last-resort pipeline assessment. The response always tells you which signal was used.
- Verified score · accuracy on human-verified docs only · highest priority · most expensive to produce
- Confidence score · average AI self-assessment across all processed docs · medium priority · always available
- Quality score · pipeline's own quality assessment · lowest priority · safety-net for when no review has happened
- Method declared · response includes
method: "verified"|"confidence"|"quality"· so you know what's behind the number
Every stat. With its delta.
Six trend fields ship on every processing-stats response - totals matter, but the direction-of-travel matters more. Each card surfaces the _diff_pct against the previous matching period.
Plus six trend-chart endpoints for time-series visualisation: touches, anomalies, doc-types, model performance, approvals, fraud.
From "we think it's working" to "here are the numbers".
Most procurement and AP automation tools never get measured. The team feels faster, the spreadsheet shows fewer late payments, but nobody can quantify the actual ROI. OmniPATH ships with the answers built in.
- Cost per invoice unknown - no measurement of manual processing effort
- Time saved is a guess - "we think we're faster" with no data
- Duplicate invoices discovered months later - or never
- Match rates unmeasured - three-way matching done manually or not at all
- Anomaly detection relies on human vigilance - things slip through
- No period-over-period comparison - no way to measure improvement
- Model accuracy unverifiable - "the AI is doing its job" with no proof
- Cost per document tracked: £1 OmniPATH vs £17.50 manual benchmark
- Time saved computed from real wall-clock processing vs 12-min manual baseline
- Duplicate exposure quantified - group count plus £ value at risk
- Three-way match rate measured: fully matched, partial, unmatched with %
- Touch-free rate tracked - % of invoices processed without human intervention
- Model accuracy with 3-signal breakdown: verified, confidence, quality
- Every metric ships with period-over-period
_diff_pctfor trend tracking - Filterable by site, team, supplier, category, date range
Ask LEDGE about your savings.
Every ROI metric is a LEDGE-accessible endpoint. "How much have we saved this month?" returns the figure, the chart and the period-over-period comparison - without you opening a single dashboard.
The practical details.
Where does the £17.50 manual benchmark come from?
Can I change the £17.50 / £1.00 benchmarks to match my own labour cost?
docs_processed figure for an internal report.Is there a single ROI dashboard that puts all eight metrics on one page?
/v0/analytics/roi endpoint today. A dedicated ROI dashboard is on the wish list; flag if it'd matter to you.Can I track cumulative savings since we started?
date_from set to your platform start date, but there's no persistent running total being incremented behind the scenes. Lifetime totals, year-over-year accumulators and "how much have we saved since launch" counters would be reasonable additions if there's demand.Can OmniPATH project our ROI for next year?
Can I get the ROI metrics as a PDF report?
Can I see ROI per supplier?
supplier_id filter - so you can ask "what's the touch-free rate for invoices from FS Foodservice?" or "how many duplicates from Brakes?" individually. What's not built is a per-supplier savings calculation that allocates the £13,893 total down to each supplier's share - that's an aggregation rather than a per-supplier metric. Practically the same answer falls out of dividing total savings by share of docs_processed per supplier, but as a built-in number per supplier, it isn't there.How does multi-currency work for the savings figure?
currency_conversion_rate stored on each purchase at the time it was posted, sourced from ECB rates. So the £13,893 saved figure reflects what the savings were worth on each invoice's posting date, not today's spot rate. Historical numbers don't drift when FX rates move - matching standard accounting practice and avoiding the "your reports change every time the rate moves" problem.What's the difference between verified, confidence and quality accuracy scores?
method.See your ROI from day one.
Bring 50 of your invoices to the demo. We'll process them, return the cost savings, time saved, accuracy and touch-free rate - live, with the underlying data - so you can see exactly what the platform would mean for your AP team.