1. Trading partner profile
Who the partner is and how the connection is made.
| Identity | Trading partner name; partner EDI ID and qualifier; Framework EDI ID and qualifier |
|---|
| Communication method | AS2, SFTP, HTTPS, VAN or API |
|---|
| EDI file format | Flat, XML or JSON |
|---|
| Endpoints | Test endpoint; production endpoint |
|---|
| Contacts | Technical contact name, email and phone |
|---|
| Acknowledgements | 997, 999 or none |
|---|
| Schedule | Test window; planned go-live date |
|---|
2. General EDI configuration
| Data source | File, API or queue |
|---|
| Integration direction | Inbound, outbound or both |
|---|
| File naming convention | As agreed with the partner |
|---|
| Character set | ASCII or UTF-8 |
|---|
| Delimiters | Segment terminator (~), element separator (*), sub-element separator (:) |
|---|
| Envelope standards | X12 or EDIFACT; ISA and GS setup (ISA06, ISA08, GS02, GS03) |
|---|
| Acknowledgement timing | Immediate, delayed or batch |
|---|
| Error notifications | Recipient name and email |
|---|
| AI Advisor exception monitoring | Enabled or disabled |
|---|
3. Transaction details
Each transaction set in scope gets its own block: direction, purpose, trigger in Dynamics 365, required and optional segments, business rules, Advisor validation and the test files required. The template ships with the five most common transactions and a general block for any other.
EDI 850, purchase order (inbound)
| Purpose | Import customer purchase orders to create sales orders in Dynamics 365 |
|---|
| Trigger in D365 | Creates sales records |
|---|
| Required segments | ISA, GS, ST, BEG, REF, N1, N3, N4, PO1, CTT, SE |
|---|
| Optional segments | SAC (allowances and charges), TD5, FOB |
|---|
| Business rules | Validate PO duplicates before creation; default the customer account from the N1 loop; map partner item to internal item number |
|---|
| Advisor validation | Detect mismatched quantities; alert if price is below cost; flag unknown SKUs |
|---|
| Test files required | Three minimum: new, change, cancel |
|---|
EDI 810, invoice (outbound)
| Purpose | Send invoices for posted customer invoices |
|---|
| Trigger in D365 | Event or batch |
|---|
| Business rules | Match invoice to originating PO; include freight and tax details if provided; one invoice per PO unless the partner allows multiple |
|---|
| Advisor validation | Cross-validate invoice amount against PO total; detect missing tax or freight values |
|---|
EDI 856, advance ship notice (outbound)
| Purpose | Notify the trading partner of shipment details |
|---|
| Trigger in D365 | Packing slip posting or shipment confirmation |
|---|
| Hierarchical structure | Shipment, order, pack, item |
|---|
| Business rules | Validate shipped quantity equals invoiced quantity; include SSCC and GS1 labels if required |
|---|
| Advisor validation | Detect missing tracking numbers; warn on ASN timing delays |
|---|
EDI 940, warehouse shipping order (outbound)
| Purpose | Send a shipment request from Dynamics 365 to a 3PL warehouse |
|---|
| Trigger in D365 | Transfer order or sales order release to warehouse |
|---|
| Business rules | Include ship-from and ship-to locations; map the Dynamics 365 warehouse to the partner warehouse code |
|---|
| Advisor validation | Flag missing warehouse codes; check for incomplete address data |
|---|
EDI 945, warehouse shipping advice (inbound)
| Purpose | Receive confirmation from the warehouse for completed shipments |
|---|
| Trigger in D365 | Update shipment status to Confirmed |
|---|
| Business rules | Match against the 940; update quantities and confirm shipment; create the ASN automatically if configured |
|---|
| Advisor validation | Identify missing or duplicate shipment confirmations; alert if quantities do not match the 940 |
|---|
Other transactions
The general block covers any other transaction set, for example the 820 payment, 855 PO acknowledgement or 846 inventory advice: direction, trigger in Dynamics 365, business rules, Advisor validation and the number and type of test files.
4. Testing and validation plan
| Phase | Objective | Responsible |
|---|
| Connectivity test | Validate the AS2 or SFTP connection | Framework Systems and partner |
|---|
| Data structure test | Confirm envelope, delimiters and schema | Framework Systems and partner |
|---|
| Functional test | Validate business logic (PO to invoice to ASN) | Framework Systems and partner |
|---|
| User acceptance test | Confirm Dynamics 365 integration and document posting | Customer |
|---|
| Production cutover | Enable production endpoints | Framework Systems |
|---|
5. Error handling and notifications
| Event type | Method | Description |
|---|
| Transmission failure | Email or Framework portal | Failed AS2 or SFTP delivery |
|---|
| Validation error | Framework Advisor or email | Schema or mapping failure |
|---|
| Business rule exception | Framework Advisor | Price, quantity or item mismatch |
|---|
| AI Advisor alert | Portal | Pattern-based or predictive warning |
|---|
6. Compliance, documentation and sign-off
- Attach partner EDI specifications (X12 or EDIFACT PDFs), test results and partner sign-off sheets.
- Document Framework EDI entity mappings and any transformation or mapping extensions (custom X++ class references).
- Approval is signed by Framework Systems, Inc., the customer and the trading partner.
