X12
Inbound

ASUSTeK Computer Inc. (dba ASUS) X12 850 Purchase Order

ASUS
The EDI 850 Purchase Order is ASUSTeK Computer Inc. (dba ASUS)'s primary document for placing orders with suppliers. It contains item details, quantities, pricing, shipping instructions, and delivery windows. Suppliers must acknowledge and fulfill these orders according to ASUSTeK Computer Inc. (dba ASUS)'s compliance requirements.
22segments
7loops
6mandatory

Schema Reference

22 segments · X12 850 Purchase Order

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 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator 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
BEG Beginning Segment for Purchase Order
Mandatory Max: 1
BEG01 Transaction Set Purpose Code
M ID 2-2
BEG02 Purchase Order Type Code
M ID 2-2
BEG03 Purchase Order Number
M AN 1-22
BEG05 Date
M DT 8-8
BEG06 Contract Number
O AN 1-30
BEG12 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
CUR04 Entity Identifier Code
O ID 2-3
CUR05 Currency Code
O ID 3-3
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
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-256
PER05 Communication Number Qualifier
C ID 2-2
PER06 Communication Number
C AN 1-256
PER07 Communication Number Qualifier
C ID 2-2
PER08 Communication Number
C AN 1-256
PER09 Contact Inquiry Reference
O AN 1-20
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
TD5 Carrier Details (Routing Sequence/Transit Time)
TD504 Transportation Method/Type Code
C ID 1-2
TD505 Routing
C AN 1-35
AMT Loop
AMT Monetary Amount
Optional Max: 1
AMT01 Amount Qualifier Code
M ID 1-3
AMT02 Monetary Amount
M R 1-18
N9 Loop Repeat: 1,000
N9 Reference Identification
Optional Max: 1
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-50
MTX Text
MTX02 Message Text
C AN 1-4096
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
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
C ID 2-3
PO1 Loop Repeat: 100,000
PO1 Baseline Item Data
Mandatory Max: 1
PO101 Assigned Identification
O AN 1-20
PO102 Quantity Ordered
C R 1-15
PO103 Unit or Basis for Measurement Code
O ID 2-2
PO104 Unit Price
C R 1-17
PO106 Product/Service ID Qualifier
C ID 2-2
PO107 Product/Service ID
C AN 1-48
PO108 Product/Service ID Qualifier
C ID 2-2
PO109 Product/Service ID
C AN 1-48
PO110 Product/Service ID Qualifier
C ID 2-2
PO111 Product/Service ID
C AN 1-48
PO112 Product/Service ID Qualifier
C ID 2-2
PO113 Product/Service ID
C AN 1-48
PID Loop Repeat: 1,000
PID Product/Item Description
Optional Max: 1
PID01 Item Description Type
M ID 1-1
PID05 Description
C AN 1-80
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
N9 Loop Repeat: 1,000
N9 Reference Identification
Optional Max: 1
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-50
MTX Text
MTX02 Message Text
C AN 1-4096
CTT Loop Repeat: 1
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 ASUSTeK Computer Inc. (dba ASUS) EDI 850

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

Validate
Transform
Route
Monitor
Stacksync automatically syncs incoming ASUSTeK Computer Inc. (dba ASUS) 850 Purchase Orders directly to your ERP or database. New orders appear in your system within seconds — no manual data entry, no CSV imports. Field mappings are configured once and every future PO flows through automatically.

ASUSTeK Computer Inc. (dba ASUS) EDI 850 FAQ

Common questions about 850 Purchase Order transactions with ASUSTeK Computer Inc. (dba ASUS).

What information does ASUSTeK Computer Inc. (dba ASUS) include in an EDI 850 Purchase Order?

ASUSTeK Computer Inc. (dba ASUS) EDI 850 Purchase Orders contain item-level detail including UPCs or GTINs, ordered quantities, unit pricing, ship-to addresses, and requested delivery dates. Key segments like BEG (beginning of the PO), PO1 (line items), N1 (party identification), and CTT (transaction totals) structure the document. ASUSTeK Computer Inc. (dba ASUS) sends 850s electronically through their EDI network, and each PO must be acknowledged with an 855 to confirm receipt. Stacksync parses these fields and maps them directly to your ERP or database so orders appear automatically without manual data entry or CSV imports.

What information does ASUSTeK Computer Inc. (dba ASUS) include in an EDI 850 Purchase Order?

ASUSTeK Computer Inc. (dba ASUS) EDI 850 Purchase Orders contain item-level detail including UPCs or GTINs, ordered quantities, unit pricing, ship-to addresses, and requested delivery dates. Key segments like BEG (beginning of the PO), PO1 (line items), N1 (party identification), and CTT (transaction totals) structure the document. ASUSTeK Computer Inc. (dba ASUS) sends 850s electronically through their EDI network, and each PO must be acknowledged with an 855 to confirm receipt. Stacksync parses these fields and maps them directly to your ERP or database so orders appear automatically without manual data entry or CSV imports.

How quickly does Stacksync process ASUSTeK Computer Inc. (dba ASUS) EDI 850 Purchase Orders?

Stacksync processes incoming ASUSTeK Computer Inc. (dba ASUS) 850 Purchase Orders in real time, typically within seconds of receipt. The platform validates the X12 envelope, parses all segments, maps fields to your system's schema, and inserts the order record automatically. Unlike batch-processing EDI providers that run on scheduled intervals, Stacksync's event-driven architecture means your team sees new ASUSTeK Computer Inc. (dba ASUS) POs immediately. This speed is critical for meeting ASUSTeK Computer Inc. (dba ASUS)'s tight fulfillment windows and maintaining high on-time in-full compliance scores.

How quickly does Stacksync process ASUSTeK Computer Inc. (dba ASUS) EDI 850 Purchase Orders?

Stacksync processes incoming ASUSTeK Computer Inc. (dba ASUS) 850 Purchase Orders in real time, typically within seconds of receipt. The platform validates the X12 envelope, parses all segments, maps fields to your system's schema, and inserts the order record automatically. Unlike batch-processing EDI providers that run on scheduled intervals, Stacksync's event-driven architecture means your team sees new ASUSTeK Computer Inc. (dba ASUS) POs immediately. This speed is critical for meeting ASUSTeK Computer Inc. (dba ASUS)'s tight fulfillment windows and maintaining high on-time in-full compliance scores.

What are common reasons a ASUSTeK Computer Inc. (dba ASUS) EDI 850 Purchase Order gets rejected?

The most frequent rejection causes for ASUSTeK Computer Inc. (dba ASUS) 850s include invalid UPC or GTIN codes, incorrect ship-to location identifiers, quantities that don't match ASUSTeK Computer Inc. (dba ASUS)'s rounding requirements, and missing mandatory segments. Formatting issues like incorrect date formats in the DTM segment or invalid N1 qualifier codes also trigger rejections. Stacksync validates every incoming ASUSTeK Computer Inc. (dba ASUS) 850 against known compliance requirements before syncing to your system, flagging anomalies immediately rather than silently dropping the transaction.

What are common reasons a ASUSTeK Computer Inc. (dba ASUS) EDI 850 Purchase Order gets rejected?

The most frequent rejection causes for ASUSTeK Computer Inc. (dba ASUS) 850s include invalid UPC or GTIN codes, incorrect ship-to location identifiers, quantities that don't match ASUSTeK Computer Inc. (dba ASUS)'s rounding requirements, and missing mandatory segments. Formatting issues like incorrect date formats in the DTM segment or invalid N1 qualifier codes also trigger rejections. Stacksync validates every incoming ASUSTeK Computer Inc. (dba ASUS) 850 against known compliance requirements before syncing to your system, flagging anomalies immediately rather than silently dropping the transaction.

Do I need to send an EDI 855 after receiving a ASUSTeK Computer Inc. (dba ASUS) 850 Purchase Order?

ASUSTeK Computer Inc. (dba ASUS) typically requires an EDI 855 Purchase Order Acknowledgment for every 850 received. The 855 confirms that you received the PO and indicates whether you can fulfill it as ordered, need to modify quantities, or must reject specific line items. Most ASUSTeK Computer Inc. (dba ASUS) compliance programs expect the 855 within 24 to 48 hours of PO receipt. Stacksync can generate and send 855 acknowledgments automatically based on your acceptance rules, ensuring you never miss a compliance deadline. A 997 Functional Acknowledgment may also be required as a separate technical receipt.

Do I need to send an EDI 855 after receiving a ASUSTeK Computer Inc. (dba ASUS) 850 Purchase Order?

ASUSTeK Computer Inc. (dba ASUS) typically requires an EDI 855 Purchase Order Acknowledgment for every 850 received. The 855 confirms that you received the PO and indicates whether you can fulfill it as ordered, need to modify quantities, or must reject specific line items. Most ASUSTeK Computer Inc. (dba ASUS) compliance programs expect the 855 within 24 to 48 hours of PO receipt. Stacksync can generate and send 855 acknowledgments automatically based on your acceptance rules, ensuring you never miss a compliance deadline. A 997 Functional Acknowledgment may also be required as a separate technical receipt.

How does Stacksync map ASUSTeK Computer Inc. (dba ASUS) EDI 850 fields to my ERP system?

Stacksync uses a visual field mapping interface to connect ASUSTeK Computer Inc. (dba ASUS) 850 segments — such as BEG for PO header data, PO1 for line items, and N1 for party identification — to the corresponding fields in your ERP, WMS, or database. You configure the mapping once, and Stacksync applies it to every subsequent ASUSTeK Computer Inc. (dba ASUS) 850 automatically. The platform handles data type conversions, conditional logic for optional fields, and ASUSTeK Computer Inc. (dba ASUS)-specific formatting requirements. If ASUSTeK Computer Inc. (dba ASUS) changes their 850 specification, Stacksync alerts you and suggests mapping updates.

How does Stacksync map ASUSTeK Computer Inc. (dba ASUS) EDI 850 fields to my ERP system?

Stacksync uses a visual field mapping interface to connect ASUSTeK Computer Inc. (dba ASUS) 850 segments — such as BEG for PO header data, PO1 for line items, and N1 for party identification — to the corresponding fields in your ERP, WMS, or database. You configure the mapping once, and Stacksync applies it to every subsequent ASUSTeK Computer Inc. (dba ASUS) 850 automatically. The platform handles data type conversions, conditional logic for optional fields, and ASUSTeK Computer Inc. (dba ASUS)-specific formatting requirements. If ASUSTeK Computer Inc. (dba ASUS) changes their 850 specification, Stacksync alerts you and suggests mapping updates.

Ready to automate ASUSTeK Computer Inc. (dba ASUS) EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding