To start and identify an interchange of zero or more functional groups and interchange-related control segments
Granite City Electric X12 810 Invoice
Plan X12 810 Invoice for Granite City Electric (via Epicor Eclipse). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 19
- Loops
- 4
- X12 810
- Partner references ↗
Implementation guide
Granite City Electric (via Epicor Eclipse): 810 mapping and validation
X12 810 Invoice is used when a bill is ready for the buyer to process. Preserve invoice number, purchase order and invoice line so the accounts-receivable or accounts-payable invoice in your business system stays connected to the original document.
This document is listed for Granite City Electric (via Epicor Eclipse). 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 | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
| Update the receiving system | Processing the accounts-receivable or accounts-payable invoice ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the accounts-receivable or accounts-payable invoice Original document reference and matching response |
|
The document reference includes 19 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 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 856 Ship Notice Manifest
shipment notice (ASN): shipment contents are known before the agreed notification deadline.
- X12 820 Payment Order Remittance Advice
payment or remittance record: payment instructions or allocation details are ready.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a bill is ready for the buyer to process. Name the operational owner of the accounts-receivable or accounts-payable invoice and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map invoice number, purchase order and invoice line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Granite City Electric guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic accounts-receivable or accounts-payable invoice 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 accounts-receivable or accounts-payable invoice processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 810 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic accounts-receivable or accounts-payable invoice 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 accounts-receivable or accounts-payable invoice without processing it twice.
Transaction context
Where 810 Invoice fits on Granite City Electric (via Epicor Eclipse)
On Granite City Electric (via Epicor Eclipse), the X12 810 Invoice can follow the 850 Purchase Order, 855 Purchase Order Acknowledgment and 856 Ship Notice Manifest in an example Order-to-cash cycle. Confirm the required sequence for your trading agreement.
- Granite City Electric channels
- 1 of 1
1 of Granite City Electric's 1 channel list 810
- Trading partners
- 360
partner references list 810
- Channels
- 473
channel entries list 810
Frequently listed alongside 810
The directory associates Epicor Eclipse and 810 with 44 channels.
Document structure
X12 810 Invoice at the element level
The X12 810 reference contains 46 segment entries and 209 data elements; 60 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 46
- Data elements
- 209
- Mandatory elements
- 60
| Segment | Elements | Mandatory |
|---|---|---|
| BIG | 7 | 2 |
| NTE | 2 | 1 |
| CUR | 4 | 2 |
| REF | 3 | 1 |
| N1 | 4 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| PER | 8 | 1 |
| DTM | 4 | 1 |
| N9 | 3 | 1 |
| MSG | 2 | 1 |
Key identifiers in 810
- Date
- Invoice Number
- Description
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Name
- Address Information
Segment reference — 19 segments 4 loops · X12 810 Invoice
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 an invoice transaction set and transmit identifying numbers and dates
To transmit information in a free-form format, if necessary, for comment or special instruction
To specify identifying information
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To specify terms of sale
To specify pertinent dates and times
IT1 Loop Repeat: 200,000
To specify the basic and most frequently used line item data for the invoice and related transactions
PID Loop Repeat: 1,000
To describe a product or process in coded or free-form format
SAC Loop Repeat: 25
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
To specify the total invoice discounts and amounts
To specify tax information
To specify transportation details for the transaction
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Related references
Other transactions in Granite City Electric (via Epicor Eclipse)
Other EDI documents listed on this channel.
Payment Order Remittance Advice X12 820 Product Transfer Account Adjustment X12 844 Price Authorization Acknowledgment Status X12 845 Response To Product Transfer Account Adjustment X12 849 Purchase Order X12 850 Product Activity Data X12 852 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Product Transfer And Resale Report X12 867
No references match your search.
Showing 9 of 9 references
Browse the full directoryGranite City Electric (via Epicor Eclipse) EDI 810 questions
Common questions about 810 Invoice on the Granite City Electric (via Epicor Eclipse) channel.
What is X12 810 Invoice used for?
810 is used when a bill is ready for the buyer to process. It carries information for the accounts-receivable or accounts-payable invoice. Match it to your business system using invoice number, purchase order and invoice line.
Is 810 required for Granite City Electric (via Epicor Eclipse)?
810 is listed for Granite City Electric (via Epicor Eclipse). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 810?
Start with invoice number, purchase order and invoice line and the target accounts-receivable or accounts-payable invoice. 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 810 error handling?
Reconcile line amounts, allowances, charges and tax to the invoice total. Submit the same invoice twice and verify that it cannot create a second payable. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 810 relate to other EDI messages?
X12 850 Purchase Order; X12 856 Ship Notice Manifest; X12 820 Payment Order Remittance Advice are related documents also listed on Granite City Electric (via Epicor Eclipse). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 810 and 850?
810 is used when a bill is ready for the buyer to process. 850 is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
What is the difference between 810 and 856?
810 is used when a bill is ready for the buyer to process. 856 is used when shipment contents are known before the agreed notification deadline. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Granite City Electric 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.
