X12
Outbound

Rehlko X12 810 Invoice

Rehlko Generator
The EDI 810 Invoice is submitted to Rehlko for payment processing. It must pass three-way matching against the original PO and ASN — mismatches in quantity, price, or item data can cause rejection and payment delays.
15segments
2loops
6mandatory

Schema Reference

15 segments · X12 810 Invoice

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BIG Beginning Segment for Invoice
Mandatory Max: 1
BIG01 Date
M DT 8-8
BIG02 Invoice Number
M AN 1-22
BIG03 Date
O DT 8-8
BIG04 Purchase Order Number
O AN 1-22
BIG07 Transaction Type Code
O ID 2-2
CUR Currency
Optional Max: 1
CUR01 Entity Identifier Code
M ID 2-3
CUR02 Currency Code
M ID 3-3
REF Reference Identification
Optional Max: 12
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
N1 Loop Repeat: 200
N1 Name
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
ITD Terms of Sale/Deferred Terms of Sale
ITD01 Terms Type Code
O ID 2-2
ITD02 Terms Basis Date Code
O ID 1-2
ITD03 Terms Discount Percent
O R 1-6
ITD05 Terms Discount Days Due
C N0 1-3
ITD07 Terms Net Days
O N0 1-3
ITD08 Terms Discount Amount
O N2 1-10
ITD12 Description
O AN 1-80
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
IT1 Loop Repeat: 200,000
IT1 Baseline Item Data (Invoice)
Optional Max: 1
IT101 Assigned Identification
O AN 1-20
IT102 Quantity Invoiced
C R 1-10
IT103 Unit or Basis for Measurement Code
C ID 2-2
IT104 Unit Price
C R 1-17
IT106 Product/Service ID Qualifier
C ID 2-2
IT107 Product/Service ID
C AN 1-48
IT108 Product/Service ID Qualifier
C ID 2-2
IT109 Product/Service ID
C AN 1-48
IT110 Product/Service ID Qualifier
C ID 2-2
IT111 Product/Service ID
C AN 1-48
CTP Pricing Information
Optional Max: 25
CTP02 Price Identifier Code
C ID 3-3
CTP03 Unit Price
C R 1-17
CTP10 Condition Value
O AN 1-10
TDS Total Monetary Value Summary
Mandatory Max: 1
TDS01 Amount
M N2 1-15
TXI Tax Information
Optional Max: 10
TXI01 Tax Type Code
M ID 2-2
TXI02 Monetary Amount
C R 1-18
TXI03 Percent
C R 1-10
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
CTT02 Hash Total
O R 1-10
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Rehlko EDI 810

Stacksync validates, transforms, and delivers your 810 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync auto-generates 810 Invoices from your billing system, pre-validated against the original PO and ASN. Three-way match discrepancies are flagged before submission — reducing rejections and accelerating payment cycles.

Rehlko EDI 810 FAQ

Common questions about 810 Invoice transactions with Rehlko.

How long does it take to set up Rehlko EDI with Stacksync?

Most suppliers are fully connected and processing live Rehlko EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Rehlko?

No. Stacksync handles the entire EDI transport layer. We connect directly to Rehlko's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Rehlko compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Rehlko?

Stacksync supports all EDI document types required by Rehlko — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Rehlko EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Rehlko's EDI network and your system in real time.

What happens when Rehlko updates their EDI specifications?

Stacksync monitors Rehlko's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.