X12
Inbound

Google X12 861 Receiving Advice/Acceptance Certificate

Google
The EDI 861 Receiving Advice is sent by Google to confirm what was actually received at the dock. It includes received quantities, damaged items, and shortages — enabling suppliers to reconcile shipments and resolve discrepancies.
19segments
2loops
6mandatory

Schema Reference

19 segments · X12 861 Receiving Advice/Acceptance Certificate

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
BRA Beginning Segment for Receiving Advice or Acceptance Certificate
Mandatory Max: 1
BRA01 Reference Identification
M AN 1-30
BRA02 Date
M DT 8-8
BRA03 Transaction Set Purpose Code
M ID 2-2
BRA04 Receiving Advice or Acceptance Certificate Type Code
M ID 1-1
BRA05 Time
O TM 4-8
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
REF03 Description
C AN 1-80
DTM Date/Time Reference
Mandatory Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
DTM03 Time
C TM 4-8
DTM04 Time Code
O ID 2-2
PRF Purchase Order Reference
Optional Max: 25
PRF01 Purchase Order Number
M AN 1-22
PRF02 Release Number
O AN 1-30
PRF03 Change Order Sequence Number
O AN 1-8
PRF04 Date
O DT 8-8
TD5 Carrier Details (Routing Sequence/Transit Time)
Optional Max: 12
TD502 Identification Code Qualifier
C ID 1-2
TD503 Identification Code
C AN 2-80
TD504 Transportation Method/Type Code
C ID 1-2
TD505 Routing
C AN 1-35
TD512 Service Level Code
C ID 2-2
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
N2 Additional Name Information
Optional Max: 2
N201 Name
M AN 1-60
N202 Name
O AN 1-60
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N403 Postal Code
O ID 3-15
N404 Country Code
O ID 2-3
N405 Location Qualifier
C ID 1-2
N406 Location Identifier
O AN 1-30
PER Administrative Communications Contact
Optional Max: 3
PER01 Contact Function Code
M ID 2-2
PER02 Name
O AN 1-60
PER03 Communication Number Qualifier
C ID 2-2
PER04 Communication Number
C AN 1-80
PER05 Communication Number Qualifier
C ID 2-2
PER06 Communication Number
C AN 1-80
PER07 Communication Number Qualifier
C ID 2-2
PER08 Communication Number
C AN 1-80
RCD Loop Repeat: 200,000
RCD Receiving Conditions
Optional Max: 1
RCD01 Assigned Identification
O AN 1-20
RCD02 Quantity Units Received or Accepted
C R 1-9
RCD04 Quantity Units Returned
C R 1-9
RCD06 Quantity in Question
C R 1-9
RCD08 Receiving Condition Code
C ID 2-2
RCD21 Quantity
O R 1-15
LIN Item Identification
Optional Max: 100
LIN01 Assigned Identification
O AN 1-20
LIN02 Product/Service ID Qualifier
M ID 2-2
LIN03 Product/Service ID
M AN 1-48
LIN04 Product/Service ID Qualifier
C ID 2-2
LIN05 Product/Service ID
C AN 1-48
LIN06 Product/Service ID Qualifier
C ID 2-2
LIN07 Product/Service ID
C AN 1-48
LIN08 Product/Service ID Qualifier
C ID 2-2
LIN09 Product/Service ID
C AN 1-48
LIN10 Product/Service ID Qualifier
C ID 2-2
LIN11 Product/Service ID
C AN 1-48
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
REF03 Description
C AN 1-80
TD5 Carrier Details (Routing Sequence/Transit Time)
Optional Max: 12
TD502 Identification Code Qualifier
C ID 1-2
TD503 Identification Code
C AN 2-80
TD504 Transportation Method/Type Code
C ID 1-2
TD505 Routing
C AN 1-35
TD512 Service Level Code
C ID 2-2
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
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 Google EDI 861

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

Validate
Transform
Route
Monitor
Stacksync syncs Google 861 Receiving Advice to your system automatically — so you see exactly what was received, what was short, and what was damaged, without waiting for manual reports.

Google EDI 861 FAQ

Common questions about 861 Receiving Advice/Acceptance Certificate transactions with Google.

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

Most suppliers are fully connected and processing live Google 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 Google?

No. Stacksync handles the entire EDI transport layer. We connect directly to Google'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 Google 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 Google?

Stacksync supports all EDI document types required by Google — 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 Google 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 Google's EDI network and your system in real time.

What happens when Google updates their EDI specifications?

Stacksync monitors Google'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.