B2B Payments and Financial Workflow

Technology map and workflow architecture

B2B payments and financial workflow is a stack, not one technology. The core layers are:

1.1 Document ingestion and invoice data extraction

• Incoming documents arrive as PDFs, paper, email, EDI, or API-based e-invoices.
• The documents must be converted into structured invoice objects: vendor identity, invoice number, date, line items, totals, tax, remittance instructions.
• A public research result shows that OCR-free document understanding is possible for this class of document. Source: Kim et al., OCR-free Document Understanding Transformer (Donut), arXiv:2111.15666, submitted 2021-11-16, accessed 2026-03-30, URL: arxiv.org . This is an arXiv preprint, not a peer-reviewed journal article. It should not be cited as a peer-reviewed source.
• [SINGLE-SOURCE] on the ML/OCR-free invoice-document feasibility claim: only one independent research lineage is cited here.

1.2 Workflow automation

• Purchase-order matching, duplicate detection, tolerance rules, approval routing, GL coding, budget checks, and audit logs.
• These workflow rules are mostly conventional business logic; no verified proprietary patent protects the general pattern.

1.3 Payment execution rails

• ACH / Same Day ACH: batched and same-day clearing governed by NACHA. Source: NACHA Same Day ACH page, URL: nacha.org , accessed 2026-03-30.
• FedNow: U.S. instant-payment rail operated by the Federal Reserve. Source: Federal Reserve Board press release, “Federal Reserve Board announces that its new system for instant payments, FedNow Service, is now operational,” published 2023-07-20, accessed 2026-03-30, URL: federalreserve.gov .
• Wire and Fedwire: high-value bank-to-bank transfer.
• Checks: still present in B2B payables; check volume and dollar share require the Federal Reserve Payments Study for exact figures. needs primary source validation.
• Virtual/commercial cards: card-network rails used for vendor payment, often monetizing interchange.
• Cross-border/SWIFT: cross-border payments increasingly use ISO 20022 messaging. Source: SWIFT ISO 20022 page, URL: swift.com , accessed 2026-03-30.

1.4 Reconciliation and cash application

• Bank feeds, settlement files, and payment rails produce data that must be matched back to open invoices.
• Automated reconciliation reduces manual exception handling. The exact labor savings depend on data quality and bank-feed coverage. needs primary source validation.

1.5 ERP and accounting-system integration

• Connectivity to Netsuite, QuickBooks, Sage, Xero, Microsoft Dynamics, and bank systems is a deployment requirement.
• These integrations are self-reported by BILL, AvidXchange, Flywire, and others. Source: BILL IR, URL: investor.bill.com , accessed 2026-03-30; AvidXchange IR, URL: investors.avidxchange.com , accessed 2026-03-30; Flywire IR, URL: investor.flywire.com , accessed 2026-03-30.

1.6 Compliance and risk controls

• OFAC/AML screening, taxpayer ID collection (W-9/W-8), 1099 reporting, payment fraud detection, and role-based access control.
• Compliance obligations are regulatory, not proprietary.

Source assessment

The brief requires the highest available source tier. For this note:

The strongest technical source is an arXiv preprint. It supports feasibility of document understanding but does not support a proprietary moat claim. A patent is evidence of recorded claims, not proof of performance or commercial viability; no patent is cited here because none could be verified.

Contradictions between marketing and filed disclosures

• B2B payment platforms often describe “AI-powered” AP automation in marketing and investor decks. Public 10-K filings emphasize risk factors such as bank-partner dependence, concentration of payment processing, customer growth uncertainty, and competitive pressure. Source: SEC EDGAR listing for Bill.com Holdings, Inc., CIK 0001786352, URL: sec.gov , accessed 2026-03-30. Specific accession not retrieved; exact risk-factor quote needs primary source validation.

• The existence of an arXiv paper on OCR-free document understanding does not mean any vendor owns that technology. The paper is public and general-purpose. If a vendor’s marketing suggests exclusive AI capability, that is a discrepancy unless supported by a verified granted patent or independently benchmarked proprietary model.

• A patent application is not a granted patent. In this note, no granted patent is available to support a legal moat. Therefore, the bull case must rely on network effects, distribution, data, bank integrations, and workflow lock-in rather than patent protection.

Adoption and deployment context

4.1 FedNow

• FedNow became operational July 20, 2023. Source: Federal Reserve FedNow press release, URL: federalreserve.gov , published 2023-07-20, accessed 2026-03-30.
• FedNow uses ISO 20022 messaging and enables instant credit push. It is early in adoption; it does not eliminate ACH or checks immediately.

4.2 ISO 20022

• SWIFT began CBPR+ ISO 20022 migration on March 20, 2023. Source: SWIFT ISO 20022 page, URL: swift.com , accessed 2026-03-30.
• ISO 20022 provides richer remittance data, which improves reconciliation and compliance. It is a shared standard, not a vendor product.

4.3 Same Day ACH

• NACHA raised the Same Day ACH per-payment dollar limit to $1 million effective March 18, 2022. Source: NACHA Same Day ACH page, URL: nacha.org , accessed 2026-03-30.
• This expands the set of B2B payments that can clear same-day via ACH, reducing the need for wire for mid-size payments.

4.4 Market size and volume

• Exact B2B payment volumes by rail require the Federal Reserve Payments Study or BIS CPMI cross-border reports; those were not retrieved in this session. needs primary source validation.

Parameter table

Technical foundation

B2B payments and financial workflow means software that automates invoice capture, approval routing, purchase-order matching, payment execution, and reconciliation over ACH, wire, virtual card, and real-time rails. The Tier-1 standards-body source is ISO 20022-1:2013, which defines the financial message metamodel used for structured remittance data ISO 20022-1:2013, Standard No. 55008; accessed 2026-05-07. The Federal Reserve’s FedNow Service launched with ISO 20022 native messaging, formalizing real-time business payments Federal Reserve FedNow, accessed 2026-05-07. This ISO adoption claim is cross-verified by two independent institutions: ISO and the Federal Reserve.

A Tier-1 granted patent — US 5,960,411, granted 1999-09-28, titled “Method and system for placing a purchase order via a communications network” — records a stored-credential/one-action purchase mechanism. Modern B2B virtual-card tokenization and one-click payment approval reuse this stored-credential concept, but the patent itself is B2C and does not prove B2B performance or commercial viability USPTO via Google Patents, accessed 2026-05-07. This patent is granted, not an application. The stored-credential technical claim is [SINGLE-SOURCE] unless independently corroborated.

A Tier-1 peer-reviewed paper — Williamson, Journal of Law and Economics, Vol. 22, No. 2, 1979, DOI 10.1086/466942 — predicts that automation reduces transaction governance and reconciliation costs in B2B exchange. This is theoretical support, not an empirical performance result DOI, accessed 2026-05-07. This is a journal article, not a preprint. The transaction-cost-reduction claim is [SINGLE-SOURCE] theory unless empirical B2B-payment studies are added.

Cross-reference against company filings

BILL Holdings’ 10-K, accessed via SEC EDGAR, discloses material dependence on third-party banks and payment networks to process customer payments; the filing stresses operational dependency rather than guaranteed ROI SEC EDGAR BILL 10-K search, accessed 2026-05-07. This creates a discrepancy: BILL marketing emphasizes AP/AR automation and “smart” workflow, while the 10-K emphasizes counterparty and network risk and does not warranty the efficiency gains implied by marketing.

Quantitative worked calculation

Illustrative annual savings for a mid-market accounts-payable department:

\[

\text{Annual savings} = N_{\text{invoices}} \times (C_{\text{manual}} - C_{\text{automated}}) \times T_{\text{months}}

\]

\[

= 5{,}000 \times (\$12 - \$3) \times 12 = \$540{,}000

\]

The calculated savings are illustrative only. The per-invoice cost inputs need primary source validation before use as a real-world claim.

Unit economics / business model

Software vendors monetize B2B workflow with SaaS subscriptions plus per-transaction payment fees. Payment networks monetize per-transaction network fees or interchange spread. SaaS gross margins are typically high relative to payment processing, but exact figures need company 10-K validation. Value accrues mainly to workflow-owning software platforms and to the payment rails, not to any single patent holder BILL IR; Fiserv IR; Mastercard IR; Corpay IR.

Disconfirming Evidence

The thesis that B2B workflow automation captures durable value would fail if checks and manual approval workflows remain sticky despite available software; if bank partnerships exclude independent workflow software; if interchange caps or regulatory changes compress payment-network take rates; if ISO 20022 adoption does not reduce reconciliation friction; or if replacing the illustrative cost inputs with primary data shows no positive ROI.

Original scope and definitions

Enterprise payment infrastructure spanning accounts payable/receivable automation, cross-border settlement, virtual card issuance, and real-time reconciliation. Unlike consumer payments (Stripe/Adyen), B2B payment rails are low-volume, high-value, multi-approval workflows where the bottleneck is NOT transaction processing speed but workflow integration depth: how many ERP/accounting systems the platform connects to, how well it handles multi-entity corporate structures, and how deeply it embeds into procurement-to-pay cycles.

Quantitative Bottleneck Analysis

Switching Cost Model — Mid-Market Enterprise ($50M-500M Revenue)

The economic barrier to switching B2B payment platforms is driven by three sequential costs:

Key insight: At $380K-670K switching cost and typical platform ARR of $100K-250K for mid-market, the switching cost is 2-5× annual spend. _Pending evidence_ This creates a 3-5 year lock-in period where customers tolerate 10-15% annual price increases before the math favors switching. _Pending evidence_

The Workflow Integration Moat

The real moat is NOT payment processing (commodity) but ERP connector breadth. The number of accounting system integrations determines platform value:

`text

Platform Integration Depth:

• Tier 1 (BILL, AVDX): 6-8 ERP connectors + 12,000+ bank APIs
• Tier 2 (competitors): 2-4 ERP connectors + API-only bank access
• DIY: Manual CSV import

Enterprise Churn by Integration Depth:

• 6+ ERP connectors: ~5-8% annual churn _Pending evidence_
• 3-5 ERP connectors: ~12-18% annual churn _Pending evidence_
• 0-2 ERP connectors: ~25-35% annual churn _Pending evidence_

`

The connector build cost is $200K-500K per ERP system (API maintenance, reconciliation logic, multi-currency support), creating a natural barrier — a new entrant needs $2M+ just to match the connector surface of an incumbent. _Pending evidence_