To start and identify an interchange of zero or more functional groups and interchange-related control segments
Core-Mark (via SPS Commerce) X12 820 Payment Order/Remittance Advice
Plan X12 820 Payment Order/Remittance Advice for Core-Mark (via SPS Commerce). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 16
- Loops
- 4
- X12 820
- Partner references ↗
Implementation guide
Core-Mark (via SPS Commerce): 820 mapping and validation
X12 820 Payment Order/Remittance Advice is used when payment instructions or allocation details are ready. Preserve payment reference, invoice references and amounts applied so the payment or remittance record in your business system stays connected to the original document.
This document is listed for Core-Mark (via SPS Commerce). Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | payment or remittance record payment reference, invoice references and amounts applied |
|
| Update the receiving system | Processing the payment or remittance record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the payment or remittance record Original document reference and matching response |
|
The document reference includes 16 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 810 Invoice
accounts-receivable or accounts-payable invoice: a bill is ready for the buyer to process.
- X12 812 Credit Debit Adjustment
credit or debit adjustment: a financial difference needs a documented adjustment.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when payment instructions or allocation details are ready. Name the operational owner of the payment or remittance record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map payment reference, invoice references and amounts applied. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Core-Mark (via SPS Commerce) guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic payment or remittance record data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful payment or remittance record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 820 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic payment or remittance record data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out payment or remittance record without processing it twice.
Transaction context
Where 820 Payment Order/Remittance Advice fits on Core-Mark (via SPS Commerce)
- Core-Mark (via SPS Commerce) channels
- 1 of 1
1 of Core-Mark (via SPS Commerce)'s 1 channel list 820
- Trading partners
- 35
partner references list 820
- Channels
- 60
channel entries list 820
Frequently listed alongside 820
The directory associates SPS Commerce and 820 with 5 channels.
Document structure
X12 820 Payment Order/Remittance Advice at the element level
The X12 820 reference contains 27 segment entries and 88 data elements; 45 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 27
- Data elements
- 88
- Mandatory elements
- 45
| Segment | Elements | Mandatory |
|---|---|---|
| BPR | 15 | 4 |
| REF | 3 | 1 |
| DTM | 2 | 1 |
| N1 | 2 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
| NM1 | 5 | 2 |
| ADX | 4 | 2 |
Key identifiers in 820
- Transaction Handling Code
- Monetary Amount
- Credit/Debit Flag Code
- Payment Method Code
- Reference Identification Qualifier
- Date/Time Qualifier
- Entity Identifier Code
- Name
Segment reference — 16 segments 4 loops · X12 820 Payment Order/Remittance Advice
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount, or to enable related transfer of funds and/or information from payer to payee to occur
To uniquely identify a transaction to an application
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
To specify identifying information
To specify pertinent dates and times
N1 Loop
To identify a party by type of organization, name, and code
To specify additional names
To specify the location of the named party
To specify the geographic place of the named party
ENT Loop
To designate the entities which are parties to a transaction and specify a reference meaningful to those entities
RMR Loop
To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail
ADX Loop
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos
Related references
Other transactions in Core-Mark (via SPS Commerce)
Other EDI documents listed on this channel.
Purchase Order X12 850 Grocery Products Purchase Order X12 875 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Invoice X12 810 Grocery Products Invoice X12 880 Product Activity Data X12 852 Credit Debit Adjustment X12 812
No references match your search.
Showing 8 of 8 references
Browse the full directoryCore-Mark (via SPS Commerce) EDI 820 questions
Common questions about 820 Payment Order/Remittance Advice on the Core-Mark (via SPS Commerce) channel.
What is X12 820 Payment Order/Remittance Advice used for?
820 is used when payment instructions or allocation details are ready. It carries information for the payment or remittance record. Match it to your business system using payment reference, invoice references and amounts applied.
Is 820 required for Core-Mark (via SPS Commerce)?
820 is listed for Core-Mark (via SPS Commerce). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 820?
Start with payment reference, invoice references and amounts applied and the target payment or remittance record. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 820 error handling?
Allocate a partial payment across several invoices and preserve the remaining balances. Keep receipt of remittance information distinct from confirmation that funds settled. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 820 relate to other EDI messages?
X12 810 Invoice; X12 812 Credit Debit Adjustment are related documents also listed on Core-Mark (via SPS Commerce). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 820 and 810?
820 is used when payment instructions or allocation details are ready. 810 is used when a bill is ready for the buyer to process. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Core-Mark (via SPS Commerce) EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
