Case StudyAccounts Payable

AP Invoice Automation: 700+ Invoices a Week, Zero Manual Work

A West Coast manufacturer was processing 700–800 invoices every week entirely by hand, with 5–6 people touching each invoice before it reached the ERP. A custom AI-powered invoice pipeline was implemented in just 12 weeks. Today, standard invoices move from inbox to ERP automatically, while the finance team focuses only on exceptions.

Executive Summary

A manual AP workflow handling hundreds of invoices every week became an automated pipeline that processes standard invoices without human touch, while directing exceptions to finance with the context needed to resolve them.

At a glance
700+
invoices processed per week
5–6
manual touchpoints eliminated per invoice
12 weeks
from kickoff to full go-live
100%
client-owned infrastructure, data, and credentials
Client
West Coast manufacturer
Function
Accounts payable
ERP
Enterprise ERP system
Delivered
12 weeks
The Challenge

Five people touched every invoice

Every invoice arrived in a shared AP inbox and required a series of manual steps: downloading and reviewing the document, extracting information, assigning GL codes, matching the invoice to a purchase order, and, for commodity vendors, checking quantities against scale records.

At 700–800 invoices per week, the AP team was spending most of its capacity on repetitive data entry and validation. That left little time for exception handling, auditing, or identifying recurring vendor issues.

The goal was simple: automate the standard invoice workflow end to end, while keeping people involved only when something actually needed their attention.

Before
  • 5–6 manual touchpoints per invoice
  • GL coding based on memory and reference sheets
  • PO matching through manual ERP lookup
  • Paper invoices scanned and routed by hand
After
  • Inbox monitored and processed automatically
  • GL coding applied through a rules engine
  • PO matching and quantity checks automated
  • Exceptions routed with full context and an audit trail
Weekly manual workload
3,500+
manual touches per week — before automation
0
touches on standard invoices — after automation

Based on 700–800 invoices per week and 5–6 manual touchpoints per invoice.

The Approach

An AI pipeline built around the client's existing workflow

Rather than introducing another AP platform, Orbis built a custom automated pipeline around the client's existing systems and processes.

Invoices are continuously pulled from the AP inbox, processed independently, validated against business rules and purchase orders, and posted directly into the client's ERP. When confidence is low or a validation fails, the invoice is routed to the appropriate person with the relevant context already attached.

The workflow
  1. 01
    Invoice arrives
    AP email inbox
  2. 02
    AI extracts
    OCR and structured data extraction
  3. 03
    GL coded
    Rules engine applies coding logic
  4. 04
    PO matched
    Three-way verification
  5. 05
    Posted to ERP
    EDI flat file posts directly to the ERP, with no human involvement on standard invoices
Exception handling
Low-confidence OCR — Held
Fields below the confidence threshold are sent for review rather than guessed.
GL coding failure — Routed
Unknown vendors or line items are routed to the AP lead.
PO mismatch — Held
Invoices outside quantity or amount tolerances are stopped before posting.
Scale record variance — Checked
Commodity invoice quantities are cross-referenced against scale records.
Audit trail — Always on
Every action taken on every invoice is logged.

As new exception patterns emerge, they become new rules, reducing the number of invoices that require human intervention over time.

Why Custom

One workflow, built around the client's business rules

Off-the-shelf AP platforms can automate parts of invoice processing, but a custom build can be designed around the client's exact ERP, GL structure, approval logic, vendor patterns, and operational requirements.

Traditional AP SaaS
Custom Automation
Data ownership
Invoice data is stored on the vendor's infrastructure under its retention and access policies.
Data remains in the client's own infrastructure.
Pricing model
Per-invoice fees or usage-based pricing that scales with volume.
One-time implementation fee plus a fixed monthly retainer.
GL coding rules
Logic is constrained by the platform's mapping and data model.
Rules are built around the client's exact GL structure and posting logic.
Vendor lock-in
Changing platforms requires migration, reconfiguration, and retraining.
The client owns the code, credentials, and infrastructure.
Implementation
Adapt the business process to the platform.
Adapt the automation to the existing business process.
Investment

A $37K first-year investment against $300K of freed payroll capacity

The engagement was structured as a one-time implementation fee plus a monthly retainer covering ongoing support, exception rule-building, vendor templates, and optimization.

The savings estimate is based on four AP staff being freed from manual invoice processing at a fully loaded annual cost of approximately $75,000 per employee.

Build fee
$22,000
Discovery through go-live
  • Inbox monitoring and OCR pipeline
  • GL coding rules engine
  • PO matching and three-way verification
  • ERP connector and fallback automation
  • Training, SOPs, and handoff documentation
Monthly retainer
$2,500/month
6-month term
  • Exception rules as new patterns emerge
  • New vendor template additions
  • ERP configuration updates
  • Monitoring and uptime oversight
Return on investment
$37K
Year 1 cost
$263K
Net return by month 12
8×
ROI multiple
Month 2
Break-even, approximately