Supported X12 sets
| Transaction | Purpose | Datasync canonical object |
|---|---|---|
| 810 | Invoice | invoice |
| 820 | Payment order/remittance | payment |
| 830 | Planning schedule | forecast |
| 850 | Purchase order | purchase_order |
| 856 | Advance ship notice | shipment |
| 860 | Purchase order change | purchase_order_change |
| 940 | Warehouse shipping order | warehouse_order |
EDIFACT highlights
- ORDERS → Purchase orders
- DESADV → Ship notices
- INVOIC → Invoices
- IFTMIN → Transport instructions
Canonical payload example (850)
{
"purchase_order": {
"po_number": "PO-10045",
"order_date": "2025-02-11",
"currency": "USD",
"ship_to": {
"name": "Northwind DC",
"code": "NW-DC-12"
},
"lines": [
{
"sku": "SKU-1234",
"description": "Widget",
"quantity": 100,
"uom": "EA",
"price": 4.25
}
]
}
}Datasync ships pre-built mappings for each transaction type. You can customize:
- Field-level transforms (trim, pad, convert)
- Business rules (minimum order quantities, status calculations)
- Splitting/combining logic across multiple partners
Change management
- Store mapping versions in Git and link them to Datasync via CI/CD.
- Use Validation Suite to test new mappings against golden files before promoting.
Resources
Code snippets
- 850 → JSON canonical mapping
- EDIFACT DESADV transformation
Related integrations
ERP Monitoring