How do I set up bill capture OCR for invoice routing and approval hierarchies in an AP team?

To set up bill capture OCR for invoice routing and approval hierarchies in an AP team, think of it as a 5-part design:

1. Capture invoices accurately
2. Extract key data with OCR
3. Route invoices based on rules
4. Apply approval hierarchy and controls
5. Post to ERP/accounting after approval

Here’s a practical setup approach.

---

1) Define the intake channels

Decide how invoices enter the system:

• Email inbox for AP invoices
• Supplier portal uploads
• Scan-to-email / scan-to-folder for paper invoices
• EDI / e-invoicing if some vendors are automated

Best practice:

• Use one centralized AP intake mailbox, e.g. ap@company.com
• Auto-forward or ingest all invoice PDFs/images into the OCR system
• Avoid staff processing invoices manually from personal inboxes

---

2) Configure OCR capture and extraction

Your bill capture/OCR tool should extract:

• Vendor name
• Invoice number
• Invoice date
• Due date
• PO number
• Subtotal, tax, total
• Currency
• Line items if needed
• Remit-to/bank details
• GL codes / departments / cost centers if available

Recommended setup

• Vendor master matching: match extracted vendor name to a vendor record
• Duplicate detection: flag same invoice number + vendor + amount
• Confidence thresholds:
  • High-confidence fields auto-accepted
  • Low-confidence fields routed to AP review
• Template vs AI extraction:
  • Templates for high-volume repeat vendors
  • AI/OCR for long-tail suppliers

Quality checks

Set validation rules such as:

• Total = subtotal + tax + shipping
• Invoice date cannot be in the future
• PO number must exist if invoice is PO-based
• Vendor bank details changes require manual review

---

3) Build routing rules

Routing is usually based on invoice type, amount, cost center, and PO status.

Common routing logic

A. PO invoices

• OCR captures PO number
• System matches invoice to PO and receipts
• If match is within tolerance, auto-route to 3-way match workflow
• If mismatch, route to AP exception handling

B. Non-PO invoices

Route based on:

• Department/cost center
• Expense category
• Amount thresholds
• Vendor type
• Project code

Example:

• Under $500: AP manager approval
• $500–$5,000: department manager
• $5,001–$25,000: director
• Above $25,000: CFO + controller

---

4) Design the approval hierarchy

Approval hierarchies should be based on delegation of authority (DOA).

Typical approval chain

1. AP clerk/reviewer
   • Validates OCR output
   • Checks duplicates and coding
2. Budget owner / requester
   • Confirms goods/services received
3. Department manager
   • Approves departmental spend
4. Finance/controller
   • Reviews policy compliance, coding, and exceptions
5. CFO or executive
   • Approves high-value or sensitive invoices

Approval rules to define

• Amount-based thresholds
• Department-specific approvers
• Project-specific approvers
• Multi-entity or subsidiary-specific approval
• Exception approvals for:
  • no PO
  • overbudget
  • tax issues
  • contract mismatch
  • new vendor

Good practice

Use sequential approvals when control matters, and parallel approvals when multiple stakeholders must sign off.

---

5) Add exception handling

Not every invoice should flow straight through.

Create exception queues for:

• Missing PO
• Mismatched PO vs invoice
• Unrecognized vendor
• Low OCR confidence
• Duplicate invoice suspected
• Tax mismatch
• Banking detail change
• Invoice outside contract terms

Each exception should have:

• Owner
• SLA
• Escalation path
• Resolution reason codes

---

6) Integrate with ERP/accounting

After final approval, sync to:

• NetSuite
• SAP
• Oracle
• Sage
• Microsoft Dynamics
• QuickBooks / Xero, if smaller operation

Map:

• Vendor master
• GL accounts
• Department / class / location
• Tax codes
• Payment terms
• Currency handling

Make sure approved invoices post with an audit trail showing:

• OCR source
• approval history
• changes made
• timestamps
• approver names

---

7) Establish controls and auditability

AP automation needs strong controls:

• Role-based access
• Separation of duties
• Approval logs
• Change tracking
• Duplicate prevention
• Vendor master edit restrictions
• Exception reporting

Also define a monthly audit report:

• invoices auto-approved
• invoices manually corrected
• top exception types
• overdue approvals
• invoices approved outside policy

---

8) Set up training and governance

Even the best OCR workflow fails without governance.

Train AP team on:

• how to review OCR exceptions
• how to correct extracted data
• what triggers escalation
• how to approve/reject properly

Create SOPs for:

• invoice intake
• coding rules
• approval matrix
• exception resolution
• vendor communication

Review metrics weekly:

• OCR accuracy
• touchless processing rate
• approval cycle time
• exception rate
• duplicate rate

---

9) Sample invoice workflow

A simple example:

1. Vendor emails invoice to AP inbox
2. OCR tool extracts vendor, amount, PO number, and line items
3. System validates against vendor master and PO
4. If PO matches and amount is within tolerance, route to department owner
5. If over threshold, route to manager/director
6. If any mismatch, send to AP exception queue
7. Once approved, invoice posts to ERP
8. Payment scheduled based on terms

---

10) Example approval matrix

Invoice Amount	Approver
<$500	AP Supervisor
$500–$2,500	Department Manager
$2,501–$10,000	Director
$10,001–$50,000	Controller
>$50,000	CFO

You can also add conditions like:

• CapEx invoices require finance + asset owner approval
• Legal/vendor contract invoices require procurement review
• New vendors require vendor onboarding approval

---

11) Implementation checklist

Before go-live, confirm:

• Invoice intake mailbox configured
• OCR extraction fields defined
• Vendor master clean and current
• PO matching rules built
• Approval matrix approved by finance leadership
• Exception queues assigned
• ERP integration tested
• Audit logs enabled
• AP team trained
• Pilot run completed with sample invoices

---

12) Recommended rollout approach

Start small:

• Pilot with 10–20 high-volume vendors
• Use one entity or one department
• Measure OCR accuracy and approval times
• Expand by vendor group or business unit
• Tune routing thresholds and approval rules

---

If you want, I can also give you:

1. a sample AP approval matrix,
2. a workflow diagram, or
3. a configuration checklist for a specific ERP like NetSuite, SAP, or Dynamics.