Sources checked: October 30, 2026
B2B EDI Invoice and Remittance Workflows: 810/820 and INVOIC/REMADV
An invoice message describes a billing claim. A remittance message explains a payment or intended payment and the documents it relates to. Their arrival, validation, finance-system processing, funds movement, and cash application are separate events. A reliable integration preserves the references and evidence needed to connect them without turning one message status into an assumed financial outcome.
For Educational and Informational Purposes Only — Not Legal or Financial Advice.
Commerce Systems Review is a free, vendor-neutral research library. This guide is general technical education. It does not provide legal, tax, accounting, financial, credit, collections, or individualized implementation advice. Partner agreements, standards releases, implementation profiles, and configured systems determine document requirements and permitted actions. Financial decisions and treatment belong to the organization's authorized owners and qualified advisers.
Sources checked: October 30, 2026.
Define the document boundary
This guide follows invoice and remittance documents through partner-contract selection, validation, reference matching, duplicates and corrections, exception review, and reconciliation handoffs. It does not prescribe accounting entries, credit policy, collection activity, payment methods, or financial decisions. The receivables and credit-control guide covers broader AR records and holds; PO amendments cover buyer changes and seller decisions; ASN/DESADV covers shipment expectations and physical receipt.
X12's public descriptions define 810 Invoice for billing goods and services and 820 Payment Order/Remittance Advice for making a payment, sending remittance advice, or both. An 820 can instruct a financial institution or carry detail for cash application, with advice sent directly or through an intermediary. It is therefore inaccurate to assume every 820 is advice only, or that every received 820 proves a completed payment.
The checked UN/EDIFACT D.24A INVOIC specification defines a claim for payment under conditions agreed by buyer and seller; with correct qualification it can also represent credit and debit notes. D.24A REMADV describes payment-related detail and generally a notice of payment to be made. Its principles expressly allow dispute-related advice that is not necessarily a payment notice or tied to one settlement date. Those meanings must survive normalization.
These are different standards and profiles, not interchangeable wire formats. GS1's EANCOM 2002 S4 REMADV, Edition 2016 updated 2021, uses reference directory D.01B and subset 005. It is not the D.24A REMADV schema. The operational models below are illustrative controls to adapt; they are not universal segment requirements or status codes.
Establish a partner-specific processing contract
Before enabling a document flow, retain a reviewed contract for each partner, direction, document family, and deployed release. Name its integration owner and the invoice/remittance business reviewer. Document:
- Sender, receiver, buyer, supplier, payer, and payee identifiers and qualifiers; intermediary identities; internal company and finance-account scope. Buyer and payer may differ.
- Exact standard release, syntax, subset, implementation-guide revision, map version, code lists, required and conditional fields, and permitted message functions.
- Invoice/document numbers, line references, PO and shipment references where required, remittance identity, referenced document types, and payment-order or transfer correlation keys where available.
- Amount qualifiers, currency context, signs, decimal interpretation, units, rounding and total checks, and date/time qualifiers. Store the agreed interpretation beside the original value.
- Receipt and acknowledgement expectations, business-response meaning, review windows, duplicate identity, copy/replacement/correction rules, and the allowed destination actions.
- Source payload retention under local requirements, authorized review access, exception escalation, and evidence that closes each handoff.
Version the contract and map together. Do not select an invoice map from a filename alone, or silently accept an unsupported release. A partner-specific requirement can be stricter than a base standard; a conditional standard element is not automatically irrelevant to the agreed implementation. A corrected document and a replay under a repaired map need separate authorization and audit trails.
Preserve distinct checkpoints
Use local states with explicit evidence, rather than a single label such as “accepted” or “paid.” The following labels are illustrative.
| Checkpoint | Evidence and boundary |
|---|---|
| Received | Transport/mailbox result, partner, control identifiers, arrival time, and preserved payload. This establishes the observed delivery step. |
| Technically validated | Selected release/profile/map, syntax and contract checks, and rejected scope. X12's 997 reports syntactical analysis and explicitly excludes semantic meaning; it is not invoice approval. |
| References matched | Resolved party/account, invoice/document and line identities, and related PO/receipt references where required. Ambiguous references remain exceptions. |
| Business reviewed | Authorized invoice or remittance review result and supported partner response. Technical acknowledgement does not imply this decision. |
| Finance import or posting observed | Saved interface, batch, transaction and error references from the configured finance system. A successful job may still contain rejected or partially processed records. |
| Funds evidence observed | Separate bank/provider evidence, its actual status, time, and correlation reference, reviewed by its responsible owner. A requested execution date is not evidence of execution. |
| Cash application and reconciliation observed | Finance-system application records, linked documents, unresolved differences and closure evidence from the authorized finance owner. Advice detail is an input, not proof of application. |
These checkpoints can occur in different orders. Advice may precede funds, funds may arrive without advice, and a document may arrive after the related finance record. Record source occurrence, receipt, import, and review times separately. X12's finance reference describes reassociation as matching payment and remittance information when they travel separately; the public overview supports that distinction, not a complete implementation of its separate best-practices document.
Validate the invoice before handing it onward
Keep envelope/control identity separate from the business invoice identity. Resolve the supplier and buyer account in the intended company context, then identify invoice type/function, number, date, currency, referenced order and lines, and shipment or receipt context at the granularity the partner supplies. Preserve original identifiers alongside normalized internal keys; do not remove meaningful leading zeros or merge accounts because names match.
Validate required fields, code/qualifier combinations, supported functions, item and unit mappings, line references, and totals using the deployed profile. Distinguish header amounts from line amounts and their qualifiers so a summary is not counted again as detail. Monetary consistency checks establish consistency of the document under the agreed rules; they do not approve the invoice or decide tax or accounting treatment.
An invoice line number need not be a PO line number. One invoice can cover several orders or deliveries; an order can have several invoices. Where receipt matching is required, compare against the authoritative receipt records rather than treating an ASN as receipt evidence. Resolve missing or ambiguous references before attaching a claim to an unrelated order. Invoice approval and any resulting finance action remain separately owned.
Correlate remittance detail without guessing application
Match advice within partner, payer/payee, company, account, document type and document-number scope. Retain remittance identity, each referenced invoice or other document, line detail if supplied, qualified amounts, currency context, adjustment reason/reference, and payment-order or other correlation identifiers. An equal amount alone is insufficient: repeated invoice numbers across companies, multiple invoices in one payment, and partial payments can all produce plausible but incorrect matches.
In D.24A REMADV, header RFF references concern the message as a whole; detail DOC identifies a referenced document and detail MOA supplies amounts. Its detail can carry adjustment reasons and optional line information. GS1's checked S4 subset similarly separates document detail from optional DLI line detail, and distinguishes amount due from amount remitted. Keep header, document and line scope explicit. Preserve missing detail as missing; do not fabricate invoice allocations from a total.
D.24A's principles describe one calculation currency even when referenced transactions have different currencies, with a dispute exception to its settlement-date principle. GS1's checked subset specifies remitted amounts in payment currency. Use the exact profile's qualifiers and currency rules, retaining any supplied conversion context; this guide recommends no exchange rate, financial calculation, or treatment. A reported adjustment or discount is the sender's document content, not the receiver's approval of it.
Illustrative correlation example, not EDI syntax or an application instruction: advice R-17 references invoice I-100 for 600 and I-101 for 350 in the same stated payment currency, with a stated total of 950. Preserve two document relationships and verify that the qualified detail explains the stated total. If funds evidence with the agreed correlation key later reports 950, that supports a candidate reassociation for review. It does not establish that the finance system applied either amount. If I-101 is missing or two company accounts both contain I-100, keep that scope unresolved and pass the evidence to its owner.
Distinguish retransmissions, copies, and corrections
Use both message/control identifiers and the partner's business-document identity rules. A retransmission may receive a new envelope while carrying the same invoice; control-ID checking alone can miss it. Retain a payload comparison and the original destination outcome.
- Exact repeat: link to the original document and result; prevent another side effect at the destination's supported duplicate boundary. A repeat before any successful processing is different from replay after a saved import.
- Same business identity, different content: hold a conflict for partner/business review. Do not choose the latest arrival or silently overwrite the original.
- Copy or replacement: interpret the agreed function and prior-document reference. The GS1 edition checked here explicitly distinguishes original, copy, and replacement functions; this does not mean all partners support them or that a replacement authorizes another payment.
- Credit/debit note or other correction document: retain its document type, identity, reference to the original where required, and authorized workflow. Do not convert it into a negative invoice or a delete merely for convenience.
- Timeout after a downstream write: inspect the destination and saved transaction references before retrying. Resending an acknowledgement, reparsing a payload, importing a record, and creating a finance action are different operations.
If an earlier invoice or advice has already been processed, a new source document does not reverse posting, funds movement, or prior cash application. Preserve the original, correction relationship, reviewer decision, affected destination references and observed results. The responsible finance owner determines any permitted finance action; the integration owner verifies the technical handoff.
Assign exceptions and reconcile both directions
| Exception | Next owner and closure evidence |
|---|---|
| Unsupported release, qualifier, malformed payload or total mismatch | Map/profile owner and partner coordinator retain failed scope, agreed interpretation, repaired source/map version, and controlled revalidation result. |
| Unknown account, invoice, PO or line | Master-data/invoice reviewer resolves the scoped identity or records an unresolved reference; no amount-only match. |
| Advice without observed funds, or funds without advice | Payment-evidence and remittance owners compare actual source statuses and agreed references, request missing evidence through the approved process, and preserve unmatched scope. |
| Duplicate, conflicting copy, replacement or late correction | Integration and document reviewers link prior payload and destination result, identify the permitted next action, and verify that replay creates no duplicate effect. |
| Imported message with rejected detail or uncertain posting | Finance-system and integration owners retain accepted/rejected rows, batch/transaction references and errors; check the destination before replaying only the permitted scope. |
| Remittance detail disagrees with application records | Finance owner reviews referenced documents, qualified amounts, currencies and application evidence; integration checks missing or stale updates. Closure requires an observed authorized result, not a successfully delivered message. |
Compare bounded record sets at a documented observation time: invoices received versus imported/reviewed records; remittances received versus referenced documents; payment evidence versus advice; and advice detail versus observed application records. Reconcile in both directions to expose missing documents and destination records without source links. Keep accepted, rejected, unmatched, partially processed, superseded and unresolved scope visible.
Each case needs partner/document references, contract/map version, source and arrival times, failed scope, destination evidence, reason, named next owner, permitted action and closure result. A correction request alone does not close a case. Broader monitoring and repair ownership belong to the data synchronization observability guide; broader order-state ownership belongs to OMS architecture.
Product-specific examples and source limits
Oracle JD Edwards World A9.3.x: the supplied Financial Transactions appendix documents separate EDI interface and batch-processing steps. Its invoice-summary path places information in a batch file for later voucher processing; its inbound 820 path transfers mapped data to Batch A/R Cash Application for further processing. Proof and final modes differ. The appendix warns that final-mode receipt processing can write records despite reported discrepancies. A processed flag or completed import is therefore not a universal guarantee of error-free application. These are legacy World procedures, not recommendations about accounting or behavior in EnterpriseOne or another ERP.
Oracle JD Edwards EnterpriseOne 9.2: the separately checked AR documentation describes receiving and reviewing EDI table data before transfer to Electronic Receipts Input (F03B13Z1). Successfully processed inbound receipts are then ready for automatic receipt processing. This is a specific product boundary; it neither proves bank settlement nor prescribes another system's table model. Do not substitute World's F0312 flow for EnterpriseOne's F03B13Z1 flow.
Standards dates: the D.24A INVOIC page displays revision 16, dated November 19, 2024; D.24A REMADV displays revision 13, dated November 19, 2024. These are explicitly versioned examples, not claims to the latest directory. GS1's current REMADV Syntax 4 landing page displays publication August 2022 and links the Edition 2016 updated 2021 PDF. Public X12 descriptions do not specify the partner's deployed release. Access dates below describe this editorial review, not standards publication dates.
Test the document lifecycle
Use controlled, synthetic cases under the deployed partner contract: a normal invoice/advice pair; several invoices per advice; partial advice detail; repeated invoice numbers in different companies; a missing invoice; advice before funds and funds before advice; dispute-related advice where supported; a currency or qualifier mismatch; conflicting totals; a new envelope carrying the same invoice; an explicit copy; a replacement after import; a qualified credit/debit note; rejected detail in an otherwise completed batch; and a lost response after a saved write.
For each case define the expected identity, validation result, permitted destination action, separate business/funds/application evidence, unresolved scope, owner and closure evidence. Verify that transport success and a technical acknowledgement never create implied business acceptance or settlement. A document lifecycle test validates technical controls; it supplies no legal, accounting or financial conclusion.
First-party source register
All references below were accessed on October 30, 2026. Standards definitions and named-product statements are limited to the checked pages; the workflow tables and examples are vendor-neutral educational models.
- X12: 810 Invoice
- X12: 820 Payment Order/Remittance Advice
- X12: Transaction set catalog
- X12: Finance references and reassociation overview
- X12: 997 Functional Acknowledgment
- UNECE: UN/EDIFACT D.24A INVOIC
- UNECE: UN/EDIFACT D.24A REMADV
- GS1: Current REMADV Syntax 4 standards page
- GS1: EANCOM 2002 S4 REMADV, Edition 2016 updated 2021 (official linked PDF)
- Oracle: JD Edwards World A9.3.x Financial Transactions
- Oracle: JD Edwards EnterpriseOne 9.2 — Understanding EDI for Accounts Receivable
- Oracle: JD Edwards EnterpriseOne 9.2 — Understanding EDI Receipt Transmissions
Editorial and education-only note
This is free, vendor-neutral technical research. It does not provide legal, tax, accounting, financial, credit, collections or individualized advice. Confirm current first-party documentation, partner profiles and authorized local instructions with the responsible teams. An EDI document does not itself prove completed settlement; a message status does not equal business acceptance.
Continue reading
Automation and integrations
Commerce Data Synchronization Observability: Freshness, Ownership, and Repair
Read guideAutomation and integrations
B2B Inbound EDI Advance Shipment Notices / DESADV: PO Matching and Receipt Reconciliation
Read guideAutomation and integrations
B2B EDI Purchase-Order Amendments During Fulfillment: Seller Responses and Safe Change Control
Read guidePayments operations
B2B Receivables and Credit-Control Workflows: Holds, Approvals, and AR Handoffs
Read guideFulfillment operations