---
name: accounts-payable-automation
description: Automate accounts payable processes including invoice capture, three-way matching, approval workflows, and payment execution. Use when users want to implement AP automation, set up OCR for invoices, configure approval chains, integrate AP with ERP systems, reduce AP processing time, or automate payment runs. Triggers on phrases like "automate accounts payable", "AP automation", "invoice capture", "three-way matching", "OCR invoices", "approval workflow AP", "automated payments", "AP processing time", "invoice-to-payment", or related AP automation queries.
---

# Accounts Payable Automation

Design and implement automated accounts payable processes that reduce manual data entry, accelerate processing cycles, improve accuracy, and strengthen controls over the invoice-to-cash process.

## Workflow

1. **Assess Current AP State**
   - Map existing invoice receipt, processing, approval, and payment steps
   - Identify manual touchpoints, bottlenecks, error rates, and processing costs
   - Document current SLAs (average days to process, approval cycle time, payment cycle)
   - Catalog all invoice sources (email, EDI, portals, paper, vendor self-service)
   - Identify exception types and their frequency (mismatches, missing PO, duplicate invoices)

2. **Define Automation Architecture**
   - Select OCR/document capture technology (built-in ERP vs. standalone AP automation tool)
   - Design three-way matching rules (PO ↔ receipt ↔ invoice) with tolerance thresholds
   - Configure approval workflow matrix by dollar amount, cost center, and vendor category
   - Map integration points with ERP (SAP, Oracle, NetSuite, QuickBooks), procurement systems, and payment systems
   - Design exception handling escalation paths

3. **Configure Invoice Capture & Data Extraction**
   - Set up OCR engine for structured and semi-structured invoice formats
   - Configure data field mapping (vendor, invoice number, date, line items, tax, total)
   - Set confidence thresholds: auto-process at ≥95%, flag for review at 80-95%, manual entry <80%
   - Configure duplicate invoice detection (matching on vendor + invoice number + amount + date window)
   - Set up vendor master data validation (blocking invoices from unapproved vendors)
   - Configure EDI 810/820/824 mapping for electronic invoice receipts

4. **Build Three-Way Matching Engine**
   - Configure tolerance rules:
     ```
     AUTOMATIC APPROVAL:
       → Header match: vendor, invoice number, date range ±3 days
       → Line match: quantity within ±2%, price within ±1%, total within ±$5
       → PO status: open, not fully received
     
     PARTIAL MATCH (FLAG FOR REVIEW):
       → Price variance 1-5% (check for approved price changes)
       → Quantity variance 2-10% (check partial shipment)
       → Missing PO reference (check for blanket orders, non-PO purchases)
     
     REJECT / MANUAL:
       → No matching PO
       → Variance > 5% on any dimension
       → Duplicate invoice detected
       → Vendor master data mismatch
     ```
   - Set up partial match resolution workflows (auto-email procurement for PO correction)
   - Configure automatic credit memo application against open invoices

5. **Design Approval Workflows**
   - Build tiered approval matrix:
     ```
     APPROVAL MATRIX TEMPLATE
     ════════════════════════════════════════
     Amount Range          Approver(s)
     ─────────────────────────────────────────
     $0 – $5,000           Auto-approve (if 3-way match passes)
     $5,001 – $25,000      Department Manager
     $25,001 – $75,000     Department Manager + Finance Manager
     $75,001 – $250,000    Finance Manager + CFO
     $250,001+             CFO + CEO
     
     Exceptions:
       → Non-PO invoices: Always require department manager approval
       → One-time/new vendor: Requires finance manager review regardless of amount
       → After-hours submission: Escalate to next business day unless flagged urgent
     ```
   - Configure delegation and backup approvers (vacation coverage)
   - Set up SLA timers with escalation alerts at 50%, 80%, 100% of approval deadline
   - Build mobile approval capability for approvers on the go

6. **Configure Payment Processing**
   - Set up payment method hierarchy by vendor preference and amount:
     ```
     PAYMENT METHOD PRIORITY
     ════════════════════════════════════════
     1. ACH / Electronic Transfer (default for domestic vendors > $100)
     2. Virtual Card (for vendors accepting card payments; earn 1% rebate)
     3. Wire Transfer (international vendors, urgent payments > $50K)
     4. Check (fallback only; vendors requesting paper checks)
     ```
   - Configure payment batch runs (daily, weekly, or month-end based on cash flow strategy)
   - Implement payment terms optimization (capture early payment discounts, avoid late fees)
   - Set up lockbox integration for vendor payment confirmation tracking
   - Configure 2FA/multi-authorization for wire transfers >$25K (fraud prevention)

7. **Implement Vendor Communication & Self-Service**
   - Deploy vendor portal for:
     - Invoice status tracking
     - Self-service invoice upload
     - Payment history and remittance advice
     - Vendor master data update requests
   - Set up automated payment notifications (remittance email, payment confirmation)
   - Configure dispute management workflow for contested charges

8. **Deploy, Test, and Measure**
   - Run parallel processing (auto + manual) for 2-4 weeks to validate accuracy
   - Key success metrics:
     ```
     METRICS DASHBOARD
     ════════════════════════════════════════
     → Processing cost per invoice: Target <$2 (vs. $12-15 manual)
     → Straight-through processing rate: Target >70%
     → Average processing time: Target <3 business days (vs. 10-14 manual)
     → Discount capture rate: Target >85% of available early-pay discounts
     → Duplicate payment rate: Target near 0%
     → AP aging >60 days: Target <5% of total AP
     → Exception rate: Track and reduce month-over-month
     ```

## Integration Points

- **ERP Systems**: SAP, Oracle Fusion, NetSuite, Microsoft Dynamics, QuickBooks
- **AP Automation Platforms**: Coupa, Bill.com, Tipalti, Avidxchange, Merative, Airbase
- **OCR/Document Capture**: Abbyy, Kofax, Rossum, ABBYY FlexiCapture
- **Payment Systems**: ACH processors, wire transfer platforms, virtual card providers
- **Procurement Systems**: Coupa, Jaggaer, SAP Ariba, Oracle Procurement Cloud
- **Email**: For invoice capture from email inboxes (rule-based forwarding)
- **Vendor Portals**: EDI networks, supplier collaboration platforms

## Edge Cases & Handling

```
EDGE CASES
═══════════════════════════════════════

1. Non-PO Invoices (Service Invoices, Utilities, Professional Services)
   → Route to "non-PO approval workflow" with mandatory budget verification
   → Require cost center charge code and project code assignment
   → Auto-check against annual budget availability

2. Partial Invoices / Progress Billing
   → Link to contract milestone tracking
   → Validate against cumulative percentage of total contract value
   → Block if cumulative invoiced amount exceeds contract ceiling

3. Multi-Currency Invoices
   → Capture invoice currency and amount
   → Convert to functional currency using spot rate on invoice date
   → Record foreign exchange gain/loss in general ledger

4. Disputed Amounts / Short Payments
   → Allow partial payment with dispute flag
   → Track dispute resolution SLA (target: 15 business days)
   → Escalate to procurement if vendor disputes resolution

5. Recurring / Subscription Invoices
   → Set up pre-approved recurring payment schedule
   → Auto-match against subscription management records
   → Alert on price changes or scope changes

6. Invoices in Non-English Languages
   → OCR with language detection
   → Translation of line items for approver visibility
   → Maintain original language copy in document archive
```

## Compliance & Controls

- Maintain complete audit trail for every invoice (capture → match → approve → pay)
- Implement segregation of duties (creator ≠ approver ≠ payer)
- Require dual authorization for payments above defined thresholds
- Comply with SOX internal control requirements for financial reporting
- Archive invoices per retention policy (typically 7 years)
- Run periodic duplicate payment detection scans on historical data

## Conversation Examples

### Automation Assessment Request
```
User: "We want to automate our accounts payable. Where do we start?"
AI: "Great initiative. AP automation typically delivers a 5-10x ROI by reducing processing costs from ~$12/invoice to under $2. Let me assess your current state:

1. What's your monthly invoice volume and average invoice value?
2. How many invoice formats/sources do you receive from (email, EDI, paper, portals)?
3. What ERP system do you currently use?
4. What percentage of your invoices currently have a matching PO?
5. What's your current average processing time from receipt to payment?

Once I have this, I'll recommend an automation architecture and implementation timeline."
```

### Three-Way Matching Issue
```
User: "Our AP system is flagging too many exceptions on three-way matching. Too many invoices go to manual review."
AI: "High exception rates on three-way matching usually stem from one of three areas. Let me help you diagnose:

Most common causes:
1. PO accuracy — Procurement entering wrong quantities, prices, or delivery dates
2. Receipt timing — Goods received but not properly logged in the system before invoicing
3. Tolerance thresholds — Matching tolerances set too tightly

Let's look at your exception breakdown:
→ How many exceptions are price variance vs. quantity variance vs. missing PO?
→ Are tolerances set at ±1% or ±5%?
→ Is there a process for procurement to pre-approve blanket orders for consumables?

I can help you right-size tolerances, fix upstream PO accuracy, and set up auto-resolution rules for common exception types."
```
