EDI banking that applies payments, not just delivers them.
The X12 820 is only the start. Comparatio handles the bank-specific formats behind it — a major North American bank's remittance handling, workflows routed through Kleinschmidt — then applies each payment to the right invoices in your ERP, even when one remittance covers dozens of them.
- X12 820 & bank-specific formats
- Auto-apply to invoices
- Multi-invoice consolidation
The documents
The EDI banking transactions that matter
Financial EDI services live or die on one document: the 820 payment order and remittance advice. It carries both the payment instruction and the detail of what the payment covers — which is exactly the data your ERP needs to close out invoices without anyone re-keying it.
820 payment & remittance
Inbound and outbound 820s in production — payment orders going to the bank, remittance advice coming back, each one validated before it moves.
Secure bank channels
SFTP and AS2 with encrypted transmission, plus lockbox (823) and application-advice (824) flows where your bank uses them.
ERP-applied, not inbox-delivered
Documents land in your ERP as applied payments and closed invoices — not as files waiting for someone to process them.
Bank-specific formats
Every bank speaks its own dialect. We map them all.
A clean, standard 820 is the exception, not the rule. Real banking EDI means handling the format each bank actually sends — and Comparatio runs those workflows in production today.
Standard X12
The textbook 820 flow
When your bank sends standard X12, Comparatio validates every 820 field by field — payer, invoice references, amounts, adjustments — before anything touches your ERP. Errors get caught on your side of the wire, not discovered at month-end reconciliation.
Bank-specific
The formats banks actually send
A major North American bank's remittance handling and 820 workflows routed through the Kleinschmidt network are examples Comparatio already runs in production. Your bank's dialect gets mapped once during setup, then monitored like every other document — no ongoing manual translation.
Cash application
From remittance to payment reconciliation, automatically
An 820 sitting in an inbox is just a file. Comparatio reads the remittance detail and auto-applies each payment to the matching open invoices in your ERP. When a bank consolidates one payment across multiple invoices — the case that breaks manual cash application — the platform splits the remittance line by line and applies each portion to the right invoice. Anything that will not match cleanly is flagged, and Monitoratio watches for the remittance that never arrived at all.
FAQ
EDI banking, in practice
What is EDI in banking?
EDI in banking is the electronic exchange of payment and remittance documents between banks, their corporate customers, and trading partners. The core EDI banking transactions are the 820 payment order and remittance advice, plus supporting documents like the 823 lockbox and 824 application advice, moving over secure channels such as SFTP and AS2. Instead of PDFs and portal downloads, payment data arrives as structured documents your ERP can act on.
The 820 document, explainedCan one 820 cover multiple invoices?
Yes — banks routinely consolidate a single payment across many invoices, and that consolidation is where manual reconciliation breaks down. Comparatio reads the remittance detail inside the 820, splits the payment line by line, and applies each portion to the matching open invoice in your ERP.
What if our bank uses its own format instead of standard X12?
Most banks do, at least somewhere in the flow. Comparatio maps bank-specific formats as part of the integration — a major North American bank's remittance handling and 820 workflows routed through the Kleinschmidt network are examples already running in production. Your bank's dialect gets mapped once, then monitored like every other document.
Do payments get applied to invoices automatically?
That is the point of the integration. Each remittance is validated field by field, then auto-applied to the right invoices in your ERP — no re-keying from a remittance PDF. Anything that cannot be matched cleanly is flagged for review instead of being applied wrong.
How validation worksYour bank's format, your ERP, one workflow.
Tell us which banks you work with and what they send — standard 820s or a format only your bank uses — and we'll show you payment auto-apply running live.