All insights
AI & Automation

The three places AP automation breaks — and how to design around each one

When AP automation is sold to a CFO, the demo looks magical. The first ninety days in production reveal where the system actually breaks — and the three breakpoints are consistent across every deployment.

Published2 min read
The three places AP automation breaks — and how to design around each one
AI & Automation2 min read
Share

Part of: AI-native finance operations: what it actually means

When AP automation is sold to a CFO, the pitch is straightforward. Vendor bills come in, the system reads them, AP processes them, the controller approves them, payment goes out. The demo looks magical. The first ninety days in production reveal where the system actually breaks.

Across the AP automation deployments I have shipped — from professional services firms running MineralTree alongside QuickBooks Online to multi-entity real estate groups operating Bill.com integrated with Sage Intacct — three breakpoints surface every time.

Breakpoint one — vendor master synchronization. The AP system maintains its own vendor list. The ERP maintains its own vendor list. When operations adds a new vendor in the ERP and starts paying them, the AP automation cannot match the invoice. The team manually rekeys — exactly the work the automation was supposed to eliminate. The fix is a daily sync that flows new vendors from the ERP to the AP system automatically, with a matching-gap alert that fires before the first invoice arrives.

Breakpoint two — purchase order matching exceptions. Most AP automation pitches cite three-way matching as a key feature. Production shows POs changed after issuance, partial shipments invoiced in full, and line-item quantities that do not match because operations received three units and the vendor billed for four. The fix is an exception routing framework defined before go-live, with documented business rules for every common mismatch pattern and named approvers for each.

Breakpoint three — approval routing for non-standard invoices. The automation handles the known invoice types. Every business has a tail of non-standard invoices the routing rules do not cover. Without an explicit fallback path, these invoices stall in a queue nobody monitors. The fix is a catch-all routing rule that sends unmatched invoices to a designated reviewer with a forty-eight-hour SLA.

All three breakpoints are predictable. All three are solvable before go-live. None require custom engineering.

Before you buy another AI seat, find out if your data and process are ready to support it.

→ Take the AI Readiness Assessment | bestpracticify.co/services/ai-readiness-assessment

Continue Reading

More From the Insights Blog.

View all insights
From ChatGPT pilot to production system: the architecture decisions that matter
AI & Automation

From ChatGPT pilot to production system: the architecture decisions that matter

The ChatGPT pilot is a conversation. The production system is an architecture. The gap between the two is where the majority of AI deployments die — and it is not because the pilot was wrong. It is because the architecture decisions that determine whether the pilot can scale were never made.

Read post
The handover document every production AI engagement should leave behind
AI & Automation

The handover document every production AI engagement should leave behind

When a production AI engagement ends, there is exactly one artifact that determines whether the system survives the consultant's exit: the handover document. Most engagements do not produce one. The system runs for nine months and then quietly degrades, because the knowledge of how it was built lives in an inbox the consultant no longer reads.

Read post
Why your IT team cannot ship the AI deployment your CFO is asking for
AI & Automation

Why your IT team cannot ship the AI deployment your CFO is asking for

When a CFO asks IT to "deploy AI for payables automation," the request lands in a department that is structurally not configured to deliver it. This is not an IT failure. It is a category error in how the work was assigned. Four structural mismatches: 1. IT teams measure uptime; AI deployments require judgment. IT is graded on whether systems are available. AI is graded on whether the system's outputs match the operational reality of the business. The first is a network problem; the second is a finance problem. They share almost no skills and no metrics.

Read post

Get Started

From Reading to Doing.

Every Best Practicify engagement begins with a 45-minute advisory session — a direct conversation with the practitioner who will lead the work, with enough information at the end to make a sound decision about whether the next step is a proposal, an RFP, or something else.