Your AP Team Says It's Efficient. That's the Problem.

Ask a controller how AP is running. If the answer is "smoothly," that is not a status report. That is a warning.

The most confident finance teams in the market right now are also, statistically, the ones leaving the most working capital, rebate revenue, and fraud exposure on the table. Self-reported efficiency is not a measure of performance. It is a measure of the absence of complaints. Those are different things, and conflating them is what we have started calling the status quo tax.

The Confidence Gap Is Real, and It's Backwards

Recent executive survey data makes the disconnect almost embarrassing to read. A reported 94% of businesses say they pay suppliers on time, 86% say their AP operations are efficient, and 82% report strong visibility into cash flow (Source: PYMNTS Intelligence/The Clearing House, https://www.pymnts.com/news/faster-payments/2026/businesses-find-roi-real-time-payments-grows-experience/).

If those numbers were true in any operational sense, the conversation about AP transformation would be over. It is not over. Not even close.

Look at what the same population actually does. Over 90% of AP teams have digitized their processes, but more than half remain stuck at medium automation levels of 25 to 50%, and another 30% are below 25% (Source: ERP.today, https://erp.today/the-ap-transformation-blueprint-how-leaders-are-rewriting-the-rules-of-finance/). So nine out of ten teams have "digitized," and four out of five are doing less than half their work without human touch.

That is not efficiency. That is a team that has stopped noticing the friction because the friction has become the job.

Self-Reported Efficiency Is a Lagging Indicator of Underinvestment

Here is the frame worth holding. In most operating functions, satisfaction surveys measure performance. In AP, they measure adaptation.

An AP team that has spent five years working around a brittle approval workflow, a vendor master that nobody owns, and a payment mix that is heavily weighted toward paper checks will eventually describe that environment as "fine." Not because it is fine. Because the team has built muscle memory around every workaround, and the workarounds no longer feel like work. They feel like the process.

This is why "we're efficient" almost always precedes "we don't need to change anything right now." And it is why the same teams that score themselves highest on AP performance also tend to score lowest on the ROI of the tools that would actually move the number.

The data backs this up at the payment rail level. RTP and FedNow users rate their payment ROI up to 21 points higher than nonusers, with nonusers assigning ROI scores of roughly 52 out of 100 (Source: PYMNTS Intelligence/The Clearing House, https://www.pymnts.com/news/faster-payments/2026/businesses-find-roi-real-time-payments-grows-experience/). The teams that have not tried the modern rail rate it as mediocre. The teams that have tried it rate it as transformative. Confidence in the status quo is not a signal of performance. It is a signal that the comparison set is too narrow.

What the Status Quo Tax Actually Costs

The status quo tax shows up in three line items, and almost no AP team tracks them as taxes. They show them as overhead.

Invoice processing cost. Best-in-class finance teams reduce invoice costs from $10 to $15 down to $2 to $3, shorten cycle times to roughly 3 days, and achieve 80 to 90% straight-through processing (Source: ERP.today, https://erp.today/the-ap-transformation-blueprint-how-letters-are-rewriting-the-rules-of-finance/). If your team is at the high end of that range and calling itself efficient, you are running a four-to-five-times cost penalty against the peers you compete with for talent and capital. That gap is not a rounding error. On a million invoices, it is the difference between a fraction of that cost and multiples of it in operating expense.

Rebate revenue not earned. Every check and ACH payment in your mix is a payment that could have been a virtual card, generating rebate income that hits the P&L as pure margin. Teams that report high efficiency are almost always teams that have not seriously rationalized payment mix, because nobody is complaining. The check process works. It just works at a yield of zero.

Fraud exposure underwritten by the business. Checks were the payment type most impacted by fraud in 2025, exceeding ACH and wire transfers, with 58% of organizations reporting check-related fraud (Source: AFP 2026 Payments Fraud and Control Survey, https://www.afponline.org/). Business email compromise continues to be the most prevalent form of payments fraud, affecting roughly three-quarters of organizations (Source: AFP 2026 Payments Fraud and Control Survey, https://www.afponline.org/). An AP team that says it is efficient and still pays a meaningful share of vendors by check is not efficient. It is subsidizing fraud losses with retained earnings and calling the subsidy "the way we do things."

Why the Survey Question Is Wrong

The standard CFO question, "Is AP running efficiently?", gives you bad data because it asks the team that owns the process to grade its own work. The answer will always trend toward yes, because the alternative is to admit that the last three years of work should have been organized differently.

Replace it with these four questions instead. The answers are harder to fake.

1. What share of our supplier payments generate revenue versus consume cost? If the answer is "I don't know" or "most of them cost us money," you are not efficient. You are leaving money on the table at scale.

2. How many vendor master records were added or edited in the last quarter, and how many of those edits were verified by a human against a second source? If the answer is fewer than all of them, your fraud surface is growing faster than your controls.

3. What is the cycle time from invoice receipt to payment cleared, and what is the standard deviation around that number? Average cycle time hides everything. Variance is where the workaround economy lives.

4. If we doubled invoice volume tomorrow, what would break first? An efficient AP team can name the bottleneck in one sentence. An inefficient one says "we'd figure it out."

The Regulatory Floor Just Moved

There is one more reason "we're efficient" is the wrong answer this year. The floor moved underneath it.

The Nacha fraud-monitoring rule went live March 20, 2026, eliminating the prior "commercially reasonable" detection standard and replacing it with "risk-based" processes (Source: Nacha, https://www.nacha.org/). Translation: the regulatory baseline for what AP teams are required to do on ACH fraud detection just got harder to satisfy by doing nothing.

If your team's posture is "we're efficient, no changes needed," and the change is now mandatory, you have a compliance gap dressed up as operational confidence. That is the most expensive version of the status quo tax, because the bill arrives as a control failure rather than as a line item you chose to accept.

The Operational Playbook to Get Out of the Trap

Finexio works with mid-market and enterprise AP teams that have done the honest version of this exercise. The pattern that gets teams out of the efficiency trap is consistent.

Reframe AP as a revenue function, not a cost center. The first move is not technology. It is accounting. Until rebate income from card payments is reported alongside processing cost in the AP scorecard, nobody in the function has a reason to push payment mix toward higher-yielding rails. Finexio's monetize AP payments approach is built on this reframe, and it starts with making the revenue visible before optimizing for it.

Rationalize payment mix at the supplier level, not the invoice level. Most teams approach card conversion one invoice at a time and stall. The faster path is supplier segmentation: identify which suppliers will accept card, which will accept ACH-plus, and which will only take check, then move the population in tranches. Supplier management is where the use is.

Put a fraud guarantee behind the rails you actually use. If check is in the mix because "the vendor insists," the right answer is not to keep underwriting the fraud risk yourself. It is to move the vendor onto a rail with built-in protection. Finexio Shield carries a $2M fraud guarantee on payments executed through the platform, which is a different risk posture than self-insuring check fraud out of retained earnings. See Shield.

Use the three-party model honestly. Finexio is the orchestration platform. J.P. Morgan Chase is the issuing bank. Mastercard and Visa are the networks. With over 10 years in market and more than $75M in investment behind the platform, the model exists because no single party should be doing all three jobs. AP teams that try to run orchestration in-house on top of a single banking relationship are usually the same teams that report being "efficient" while running a heavily check-weighted payment mix.

FAQ

Is high on-time payment rate a good measure of AP performance?

On its own, no. On-time payment measures whether you hit the due date. It says nothing about the cost of hitting it, the rebate revenue you forfeited to hit it, or the fraud risk you carried while hitting it. A team paying on time by check at a high cost per invoice is not outperforming a team paying on time by virtual card at a fraction of that cost and earning rebate income on the spread.

How do we know if we're in the efficiency trap?

Ask the four questions in the section above. If you cannot answer share of revenue-generating payments, vendor master edit verification rate, cycle time variance, or first bottleneck under double volume, you are operating on confidence rather than data. That is the trap.

Does payment automation actually deliver, or is it overhyped?

The teams that have implemented it tell a different story than the teams that have not. Leaders are slashing manual entry from 30% to 5% and achieving 52% touchless processing (Source: ERP.today, https://erp.today/the-ap-transformation-blueprint-how-leaders-are-rewriting-the-rules-of-finance/). The gap between perceived ROI among users and nonusers of modern payment rails is one of the widest in finance technology right now. The skepticism is concentrated in the population that has not tried it.

Stop Grading the Process. Start Pricing the Tax.

If your AP team reports that things are running smoothly, do not take it as good news. Take it as a prompt to price the status quo tax in actual dollars. Cost per invoice above best-in-class. Rebate revenue not earned on the current payment mix. Fraud exposure carried on the check population. Compliance gap against the new Nacha standard.

When those four numbers are on the page, "we're efficient" stops being a defense and starts being a hypothesis. Most of the time, the hypothesis does not survive contact with the math.

To pressure-test your AP operation against the framework above, Book a Consultation with the Finexio team.

Sources

- PYMNTS Intelligence/The Clearing House: https://www.pymnts.com/news/faster-payments/2026/businesses-find-roi-real-time-payments-grows-experience/ - ERP.today, AP Transformation Blueprint: https://erp.today/the-ap-transformation-blueprint-how-leaders-are-rewriting-the-rules-of-finance/ - AFP 2026 Payments Fraud and Control Survey: https://www.afponline.org/ - Nacha, Fraud Monitoring Rule: https://www.nacha.org/