Field guide / Receive-side B2B payments
From payment receipt to clean ERP posting.
Why “the buyer sent the payment” is only the beginning of the supplier’s workflow—and what it takes to finish reliably.
Updated July 18, 2026 · 8 minute readWhat happens after a business receives a B2B payment?
The supplier must collect the payment notice and remittance, complete any method-specific processing, confirm settlement, match funds to the correct customer and invoices, investigate fees or exceptions, reconcile the result, apply approvals and accounting policy, and post it to the ERP. When payment and remittance arrive separately, this workflow becomes a data and interoperability problem—not just a payment problem.
Most payment software focuses on initiation: choose the supplier, choose the method, send the funds. Supplier-side completion is a second system made of inboxes, portals, bank records, remittance artifacts, people, policies, and accounting entries.
Payment notice arrives
A supplier may receive an email, card notification, ACH detail, bank line, check, wire notice, portal update, or processor event. The notice, funds, and remittance may arrive through different channels.
Remittance is captured
Invoice references, amounts, credits, deductions, payer detail, payment metadata, and attachments are collected and tied back to their source.
The payment method is completed
A virtual card may need retrieval and processing. A portal may need a login. A check may need deposit. An ACH or wire may need bank confirmation. Method-specific work affects timing, fees, and evidence.
Funds and data are normalized
Inconsistent payer names, formats, dates, references, fees, and remittance descriptions are converted into canonical fields without losing provenance.
Open receivables are matched
The workflow connects the payment to the right customer, invoices, credits, and deductions. Confidence and rationale matter when the data is incomplete or ambiguous.
Exceptions are resolved
Short-pays, overpayments, missing invoices, duplicate references, fees, disputes, and settlement differences are surfaced to the right owner instead of disappearing into unapplied cash.
Policy and approval are applied
Automation checks permissions, payment acceptance rules, confidence thresholds, accounting policy, and required approvals before any high-authority action.
Accounting output is created
The result becomes an export-ready record or a reviewed ERP posting with the payment, invoices, exceptions, coding, approval, and evidence linked.
The useful definition of completion
A B2B payment is complete for the supplier when the funds, remittance, invoices, fees, exceptions, approvals, and accounting entry agree—and the record can explain how that conclusion was reached.
Where agentic automation helps
Agents are most useful where the work is variable and unstructured: reading emails and PDFs, navigating portals, connecting separated evidence, proposing matches, checking status, and preparing exception or posting actions. Deterministic rules and human review remain essential where authority, risk, or accounting policy require them.