← All guides

Accounts Payable Automation Project Plan

Plan an AP automation implementation with a project timeline covering invoice capture, workflow configuration, ERP integration, and change management.

Accounts Payable Automation Project Plan

Automating AP Is Not Just Software — It's a Process Redesign

The most common AP automation failure mode: a company buys an OCR and workflow tool, configures it to mirror the existing manual process, and gets incremental efficiency gains instead of the transformation they expected. Invoices that used to take 12 days to process now take 8 days. The CFO asks why the AP team size hasn't changed.

AP automation delivers real results — cycle time cut by 60–70%, cost per invoice reduced from $12–15 to $2–4 — only when the underlying process is redesigned at the same time as the technology is implemented. You can't automate a bad process. Here's how to structure the project to do both.

Phase 1: Process Assessment (Weeks 1–3)

Before evaluating any software, document the current state honestly.

Measure baseline metrics:

  • Invoice volume: how many invoices per month, by type (PO-backed vs. non-PO, electronic vs. paper)
  • Cycle time: average days from invoice receipt to payment authorization
  • Cost per invoice: fully-loaded AP team cost ÷ monthly invoice volume
  • Error rate: percentage of invoices requiring manual correction or rework
  • Aging: what percentage of invoices are past due at any given time?

Map the current process end-to-end:

  • How do invoices arrive? Email, mail, vendor portal, EDI, fax?
  • Where are they received and by whom?
  • Who performs data entry?
  • How are invoices matched to POs and receipts?
  • Who approves? What triggers escalation?
  • How are exceptions handled: mismatches, missing POs, duplicate invoices?
  • How does approved invoice data reach the ERP for payment?

The process map will reveal: how many handoffs, how many manual touch points, where invoices sit waiting. Every waiting step is a candidate for elimination, not automation.

Phase 2: Vendor Selection (Weeks 3–6)

With process metrics and pain points documented, evaluate solutions against actual requirements.

Core requirements:

  • Invoice capture: OCR extraction for PDF invoices, EDI integration for electronic invoices, supplier portal for high-volume vendors
  • Workflow: configurable approval routing by vendor, amount, department, cost center
  • Three-way match: automated matching of invoice to PO and receipt
  • Exception handling: workflow for mismatches that require manual resolution
  • ERP integration: pre-built connector or API to your ERP for vendor master, GL coding, and payment

Vendor shortlist:

  • Tipalti: strong for global AP, multi-currency, tax compliance
  • Bill.com: SMB-focused, easy setup, bank integration
  • Coupa: enterprise, integrated procurement and AP
  • SAP Ariba: enterprise, deep SAP integration
  • Stampli: strong collaboration features, AI-assisted coding

Evaluation approach:

  • Demo using your actual invoices and exceptions — not the vendor's sanitized demo data
  • Ask specifically: what is your average OCR extraction accuracy rate for our invoice formats?
  • Reference check: call AP managers (not IT or finance leaders) at companies of your size

Phase 3: Process Design (Weeks 7–9)

Design the future-state process before configuring anything. This is where the transformation happens.

Invoice receipt:

  • Centralize all invoice receipt to a single email inbox (ap@company.com) and/or supplier portal
  • Eliminate the practice of invoices going directly to department managers
  • Define what happens to paper invoices: scan and destroy, or vendor onboarding to eliminate paper

Approval routing design:

  • Define routing rules by invoice attributes: vendor type, amount threshold, department
  • Example: PO-backed invoices under $5,000 with clean three-way match → auto-approve
  • Non-PO invoices under $500 → department manager approval only
  • Non-PO invoices $500–$10,000 → department manager + controller approval
  • All invoices over $10,000 → VP Finance approval

Exception handling design:

  • Price variance: invoice price differs from PO price by >X% → route to buyer for resolution
  • Quantity variance: invoice quantity differs from receipt → route to receiving
  • Duplicate invoice: exact match on vendor + amount + date → hold for review
  • Missing PO: invoice with no PO reference → route to AP manager for coding or return to vendor

Vendor communication:

  • Define how vendors will be onboarded to electronic submission
  • Design the rejection notice for non-compliant invoice submissions

Phase 4: System Configuration (Weeks 9–14)

Configure the system to implement the designed process — not the old process.

Tasks:

  • OCR template configuration: build extraction templates for top 20 vendors by invoice volume; these vendors account for 60–70% of volume in most AP operations
  • Approval workflow setup: configure routing rules defined in Phase 3
  • ERP integration: vendor master sync, GL account coding lookup, payment file export
  • Email capture: configure the AP inbox to auto-route inbound invoices to the capture queue
  • Supplier portal: set up vendor-facing portal for electronic invoice submission
  • Reporting: configure dashboards for cycle time, exception rate, aging, approval status

Phase 5: Vendor Onboarding (Weeks 12–16)

High-volume vendors submitting paper or email PDF invoices need to migrate to electronic submission.

Tasks:

  • Rank vendors by invoice volume (monthly invoice count, not spend)
  • Identify top 50 vendors by invoice volume — these drive most of the efficiency gain
  • Send vendor communication: instructions for new submission method, portal registration link, contact for questions
  • Set onboarding deadline: vendors who haven't migrated by Date X will receive payment delays (this creates urgency)
  • Track vendor onboarding status weekly

Target: 80%+ of invoice volume through electronic channels by go-live.

Phase 6: Testing and Training (Weeks 14–17)

Testing:

  • Process a batch of 50 real invoices through the system end-to-end
  • Confirm OCR extraction accuracy for each invoice type
  • Test all approval routing scenarios: each approval tier, each exception type
  • Verify ERP posting: approved invoices post correctly to GL with correct coding
  • Test payment file export and ERP invoice clearing

Training:

  • Train AP processors: how to review the exception queue, how to manually correct OCR errors, how to resolve exceptions
  • Train department approvers: how to approve or reject invoices in the approval tool (must be mobile-friendly — approvers are not at their desks)
  • Train AP manager: reporting, escalation management, vendor onboarding

Phase 7: Go-Live and Optimization (Weeks 17–20)

  • Run parallel processing for 2 weeks: process invoices in both old and new system, reconcile
  • Cut over fully: all new invoices enter the new system only
  • Monitor exception rate daily in first month — high exceptions indicate OCR configuration issues
  • Track cycle time improvement vs. baseline
  • Set 90-day targets: cycle time, exception rate, electronic invoice percentage

gantt-chart.io is useful for AP automation projects because the seven phases have tight dependencies and multiple parallel workstreams. Process design must complete before system configuration can begin; vendor onboarding should run in parallel with configuration. Build the full timeline with phase dependencies and share it with your AP team and implementation vendor to keep everyone on the same schedule.