Why Finance Leaders Can't Afford to Keep Running Fragmented Systems

May 20, 2026

The 2025 McKinsey Global Payments Report finds that companies are investing heavily in invoice automation, reconciliation, and working capital tools, with these services now supporting a $2.5 trillion global payments industry and 3.6 trillion transactions annually.

This rising scale and complexity are raising the stakes for organizations worldwide. Companies must now navigate increasing demands for faster settlement and real-time visibility into cash flows. At the same time, geopolitical instability introduces new layers of transaction risk, while macroeconomic shocks compress liquidity and drive up the cost of capital. As these pressures converge, making the right payment at the right time, to the right counterparty, has become a strategic imperative.

However, for organizations where AP and payment systems are still disconnected, that opportunity is often lost to friction. This friction appears in the handoff from approved invoice to payment execution, the gap between AP actuals and treasury visibility, inflexible payment runs across multiple banks, and the hours spent reconciling transactions that should have been straight-through.

Despite substantial investment in ERP modernization, AP digitization, and treasury platforms, these pain points endure because most organizations have automated within functions but not across them. As a result, the invoice-to-pay (I2P) process (from invoice receipt through validation, approval, payment execution, and reconciliation) remains divided across systems that were never designed to share intelligence.

Persistent fragmentation and siloed automation directly affects an organization’s direction and long-term competitiveness:

Hackett Group (2025 Working Capital Survey): The 1,000 largest U.S. public companies carry $1.7 trillion in excess working capital. With the cost of capital still elevated, fragmented AP and payment processes translate directly into measurable liquidity drag.
Association for Financial Professionals (2025 Payments Fraud and Control Survey): Checks alone account for over 60% of fraud incidents, and the most effective defenses are those applied before payment execution. Organizations without integrated controls are carrying unpriced financial risk on every payment run.
Modern Treasury (2025): 51% of companies still execute half or more of their payment operations manually. That gap between AP and treasury creates blind spots in cash visibility precisely when working capital economics demand the highest level of accuracy.

This article is the second in our Invoice-to-Pay series. In the first, we explored how closing the I2P intelligence gap creates the foundation for unified finance. Here, we go further: what does integrated finance actually look like in practice, and where should financial leaders begin?

The answers are practical. The opportunity is large. And the window to act—before competitors do—is narrowing.

30%

Of AP team time lost to manual reconciliation in fragmented I2P (AFP)

62%

Of AP processing costs from labor alone in manual environments (Deloitte, 2025)

51%

Of companies still running half or more of payments manually (Modern Treasury, 2025)

The fragmentation problem: where finance loses control

Finance leaders often describe their current state in similar terms: 'We know the invoice is approved. We just can't see what happens next. That invisibility, the gap between approval and execution, is where fragmented systems extract their real cost.

The data "Dead Zone"

When an invoice clears validation and approval in an AP system, it typically exports to a payment platform as a flat file: amount, vendor ID, and bank details. Everything the AP system learned about that invoice: the supplier's payment history, preferred rails, applicable discount windows, GL codes, and compliance flags, is left behind. The payment system starts blind.
This is the ‘data dead zone,’ and it creates cascading problems, such as:

Payment orchestration defaults to the generic: Without knowledge of preferred rails, discount windows, or supplier terms, payment runs optimize for nothing. The right payment at the right time to the right counterparty becomes a matter of chance rather than design.
Compliance operates without context: New bank accounts, sanctions flags, and tax codes that were visible at the invoice level are absent at execution. Controls that could have been preventive become audits after the fact.
Treasury cannot optimize what it cannot see: Without real-time payment pipeline data flowing from AP, dynamic tools like early payment programs, supply chain finance, and working capital optimization run on assumptions rather than actuals.
Suppliers absorb the gap: When payment timing is driven by system limitations rather than agreed terms, predictability disappears and inquiry volume rises with it.

Payment failures are not random; they are predictable. Up to 15 to 20% of enterprise payments encounter some form of failure or delay when invoice intelligence does not flow through to execution. The cost is not just the failed transaction: it is the reconciliation work, the relationship damage, and the window of exposure that opens up.

— Industry benchmark, Payment Orchestration Research, 2026

The Reconciliation Gap Is a Data Design Problem

Ask an AP Director how much of their team's time goes to chasing payment mismatches, resolving unposted transactions, or manually correlating bank statements against ERP records. The honest answer is “too much.” Reconciliation in fragmented environments is not an occasional exception; it is a structural, predictable drain that recurs every payment cycle.

This isn't a staffing or delegation problem. It's a data architecture problem. The root cause is the loss of shared context at the system boundary. Even where invoices and payments live in the same ERP, the connection between invoice identity and payment identity breaks because the systems operate in silos. The payment system assigns its own reference numbers, the bank assigns transaction IDs, and the ERP records a different identifier entirely. By the time settlement occurs, matching a payment back to its source requires manually correlating these three or more reference schemas at scale, under intense month-end pressure. Most systems lack the intelligence to reconcile figures that don't match exactly. Consider a bank statement where transaction fees need to be posted to a separate GL while the principal reconciles against the invoice entry. This routine scenario turns every exception into a manual task, and in fragmented systems, those exceptions are everywhere.

Up to 20% of enterprise payments encounter some form of failure or delay when invoice intelligence does not flow through to execution. Each failure generates a reconciliation exception. In fragmented environments, those exceptions accumulate; clearing them becomes the AP team's primary occupation.

— Industry benchmark, Payment Orchestration Research, 2026

What Integration Actually Means: One Platform, One Data Model

Many organizations believe they have an 'integrated' I2P process because their AP and payment systems share data through an API or middleware layer. Integration in this sense is better than nothing, but it still leaves the intelligence gap intact. Data that passes through an integration layer loses context. Systems still operate on separate schemas. Reconciliation still requires manual intervention.

True integration means a single data model, where the invoice is not just a trigger for payment, but the intelligence layer that governs how payment happens.

The Invoice as Intelligence Layer

In a unified I2P environment, the invoice carries its full context from intake to settlement:

Supplier context: Payment history, preferred rails (ACH, RTP, vCard, wire), geographic constraints, banking validation status
Financial terms: Net days, early payment discount windows, currency, applicable tax codes
Policy and governance: GL codes, approval trail, spend category, authorization thresholds
Risk signals: New or changed banking details, sanctions flags, unusual amount patterns, KYB status.

When payment execution draws on this full context, rather than a truncated flat file, everything changes. Payment rail selection becomes data-driven. Timing decisions account for actual terms. Compliance checks run against real invoice data. Reconciliation becomes automated because payments and their source invoices carry linked identifiers throughout the workflow, even across complex enterprise environments where systems remain distinct.

What we hear from finance leaders is not, 'we need to replace our bank.' It is, 'we need our invoice data to drive our payment decisions and help support wider business KPI’s.' The value of integration is not disrupting existing banking relationships; it is making those relationships smarter. When payment orchestration draws on the invoice's full intelligence, finance teams get better economics from the rails they already use.

— John Moodie, VP of Payments

The AP–Treasury Alignment Dividend

One of the most underrated benefits of unified I2P is what it does for the relationship between AP and treasury. In fragmented environments, these functions often operate with different views of the same data. AP knows what invoices are approved. Treasury knows what cash is available. But without a shared pipeline, each team is working from a partial picture, and the gaps between them create the exceptions that consume both.

Integration creates a shared operational reality for the payments process itself. AP can see payment status in real time. Exception handling is faster because context travels with the transaction. And because the payment carries the full invoice lineage, reconciliation closes the loop automatically rather than opening a new workstream.

IMA research on finance function integration (2024) found that organizations with unified AP-treasury data environments reduced their month-end close cycle by an average of 2.3 days — largely because reconciliation and payment matching were automated rather than handled manually. That is not a marginal gain. For finance teams managing hundreds or thousands of transactions per cycle, it is the difference between a close process that runs smoothly and one that consistently requires weekend heroics.

How a Shared Data Model Makes Straight-Through Reconciliation Possible

In a unified I2P environment, the invoice reference travels with the transaction from approval through execution and settlement. When the bank confirms payment, the platform already holds the context needed to reconcile it: the originating invoice, the approvals behind it, and the GL codes it maps to. What remains is a confirmation step rather than a search, though one that still accounts for fees, FX movement, and any variance that requires its own posting.

This is straight-through reconciliation: the automated closure of the loop between invoice approval and payment settlement, with no manual intervention required for clean transactions. Exceptions, such as a payment that settled for a different amount than instructed, surface automatically and are routed for resolution. The AP team's reconciliation work shifts from processing routine matches to managing real exceptions.

Research on I2P automation finds that teams using integrated invoice-to-payment platforms reduce reconciliation exceptions by 30% and achieve near-complete automation of routine payment matching, freeing AP capacity for higher-value work and strategic supplier management.

Automatic ERP Posting: Closing the Loop

Reconciliation in isolation is not enough. The value is only realized when settled payment data flows back to the ERP, updating the open invoice register, posting the liability closure, and reflecting the cash movement in real time. In fragmented environments, this ERP writeback is typically a batch process: end of day, or worse, end of week. Accounts remain open longer than they should. Cash balances lag actual positions.

Integrated I2P platforms close this loop automatically. Every payment execution event triggers an ERP update: the invoice is marked as settled, the GL entry posts, and the payment is immediately visible in cash management. The month-end close no longer requires a reconciliation sprint, because the books reflect reality continuously, not just when someone runs a manual update.

When payment data flows back to the ERP automatically, with the invoice reference, GL codes, and settlement timestamp already attached, the matching work disappears. That is not an incremental improvement; it is a fundamental change in how the settlement process is reconciled."

— Andrew Ng, Head of Payments and Embedded Finance

Continue the Invoice-to-Pay series

From fragmented systems to integrated finance

Continue exploring how unified Invoice-to-Pay connects invoice intelligence, payment execution, reconciliation, and working capital decisions across modern finance operations.

Next article How intelligent payment orchestration transforms the finance function See how integrated I2P turns payment execution into a source of commercial intelligence. Enterprise guide From cost center to strategic asset Explore how enterprise finance leaders use integrated I2P to improve governance, efficiency, and working capital visibility. Mid-size company guide Integration pays for itself Learn how mid-size finance teams close the I2P gap while preserving existing systems and banking relationships.

Frequently Asked Questions

We already connect our AP system to our payment platform via an API. Aren't we already integrated?

An API connection moves data between systems, but it does not create a unified data model. When an invoice exports as a flat file, context such as supplier preferences, compliance flags, and GL codes is stripped away. True integration means the invoice reference and its full context travel through settlement, enabling automated reconciliation and pre-execution compliance checks.

Our AP team does reconciliation every month. How much time could we realistically save?

The AFP benchmarks manual reconciliation at up to 30% of AP team time in fragmented environments. Integrated I2P largely eliminates this routine work through straight-through matching: the invoice reference travels with every payment, so settlement triggers automatic posting rather than a manual matching exercise. Your team's time shifts to managing genuine exceptions, rather than processing routine ones.

We have strong banking relationships we do not want to disrupt. Does integrated I2P require us to change banks?

No. Modern payment orchestration works as an intelligence layer alongside your existing banking infrastructure. Your banks remain the execution layer for ACH, wire, and other rails. Integration adds the ability to route payments intelligently across your existing relationships, based on invoice data and organizational policy, without requiring you to change your bank.

Where should we start if we want to move toward integrated I2P without a full transformation program?

Start with a focused supplier segment, typically your highest-volume suppliers, where the reconciliation burden is most visible. Apply integrated I2P capabilities there first and let the results make the case for broader adoption. IDC finds that teams using upfront validation in a focused segment achieve 30% fewer reconciliation issues early on. A narrow starting point reduces risk and builds momentum without requiring a full transformation from day one.

Glossary of Finance and Treasury Terms

Term	Definition
AP (Accounts Payable)	The finance function responsible for managing and paying a company's outstanding invoices and bills to suppliers. AP teams process invoices, route them for approval, and initiate payment.
Cash Position	A real-time snapshot of how much cash a company has available across its bank accounts at any given moment. Treasury monitors cash position to ensure liquidity for upcoming obligations.
DPO (Days Payable Outstanding)	A measure of how long, on average, a company takes to pay its suppliers. A higher DPO means a company holds cash longer, which can be a working capital advantage. However, extending DPO beyond agreed terms can damage supplier relationships.
Dynamic Discounting	A program that allows buyers to offer suppliers early payment in exchange for a small discount on the invoice amount. For example, a buyer might pay 10 days early in return for a 1% reduction. Both sides benefit: the buyer earns a return on idle cash; the supplier receives funds sooner.
GL Code (General Ledger Code)	A numeric code that categorizes a financial transaction for accounting purposes. For example, a supplier invoice for office supplies might be assigned to GL code 6100 (Office Expenses). Correct GL coding is essential for accurate financial reporting.
I2P (Invoice-to-Pay)	The end-to-end process that begins when a supplier submits an invoice and ends when payment is settled and recorded in the ERP. A unified I2P process connects invoice capture, validation, approval, payment execution, and reconciliation on a single platform.
KYB (Know Your Business)	A compliance verification process used to confirm the legitimacy of a business before sending or receiving payments. KYB checks verify company registration, ownership, and sanctions status. It is the business equivalent of KYC (Know Your Customer) in retail banking.
Liquidity	The availability of cash or assets that can quickly be converted to cash to meet short-term obligations. Treasury teams manage liquidity to ensure the company can pay suppliers, employees, and debt obligations on time.
Payment Rail	The underlying infrastructure or network through which a payment moves from payer to recipient. Common rails include ACH, RTP (Real-Time Payments), wire transfer, and virtual cards (vCards). Each rail has different speed, cost, and use-case characteristics.
Pre-Execution Validation	Compliance and accuracy checks performed on a payment before it is sent. This includes verifying supplier banking details, screening against sanctions lists, and confirming authorization levels. Pre-execution validation catches errors and fraud before money moves, rather than discovering them through audit afterward.
RTP (Real-Time Payments)	A payment rail that moves funds between bank accounts within seconds, 24 hours a day, 7 days a week. RTP is increasingly used for urgent supplier payments and situations where fast settlement is required.
Straight-Through Processing (STP)	The automated handling of a transaction from initiation to settlement without any manual intervention. In I2P, STP means an invoice is received, validated, approved, paid, and reconciled entirely by the system, with humans only involved to resolve genuine exceptions.
Three-Way Match	An automated check that compares three documents: the purchase order (what was ordered), the goods receipt (what was received), and the supplier invoice (what is being charged). If all three align, the invoice is approved for payment without manual review.
Treasury	The finance function responsible for managing a company's cash, investments, banking relationships, and financial risk. While AP handles individual invoices and payments, Treasury oversees the broader picture: how much cash is available, where it is held, and how it is deployed.
Virtual Card (vCard)	A single-use credit card number generated for a specific payment transaction. Virtual cards allow buyers to pay suppliers via the card network, often earning rebates in the process. Suppliers receive payment quickly; buyers capture rebate income. Virtual cards are particularly useful for one-time or irregular payments.
Working Capital	The difference between a company's current assets (including cash and receivables) and its current liabilities (including payables). Effective working capital management means holding enough cash to meet obligations while deploying surplus funds productively. I2P integration directly affects working capital through payment timing, discount capture, and DPO management.

by John Moodie VP of Payments

by Andrew Ng VP of Embedded Payment Solutions