EDIconnect Implementation Checklist

Follow the steps below for each message you implement. Check off each item before moving to production.

1. Initial Configuration (one-time)

Complete this section once, at the start of any EDI implementation with a new partner.

• Your organisation's GLN is confirmed with the partner (13 digits, string format)
• The partner's GLN is confirmed and tested
• Transport protocol chosen and configured (AS2 / SFTP / REST API)
• Test credentials received from the partner (sandbox URL, AS2 certificates or SFTP username/password)
• Test environment configured separately from production
• TestIndicator=1 set in ALL messages in the test environment
• UTF-8 encoding configured on all systems involved
• Standard version confirmed with the partner: EANCOM D.01B

2. ORDERS (Inbound — you receive orders)

• The system correctly parses the structure <Message><Documents><Order><Header>...
• The <Version> field is present and the value is read correctly
• The GLN in Seller/GLN matches your configured GLN
• OrderNumber is saved — it will be used in DESADV and INVOIC (field RFF+ON)
• DocumentType is processed correctly: O=new order, OR=response to a previous order
• All lines in <Lines> are imported (verify that <Summary><Lines> = the number of lines)
• EAN is validated: exactly 13 digits
• QuantityPieces and PackingUnit are processed correctly (ordered quantity and packaging)
• Simple ORDERS test (1 line) sent and processed without errors
• ORDERS test with 10+ lines sent and processed without errors
• Test with unknown EAN → error EDI-007 returned correctly

3. DESADV (Outbound — you send delivery notices)

• DESADV generated automatically when a shipment is created in CRMconnect
• DeliveryNumber unique per notice
• OrderNumber (RFF+ON in EDIfact) correctly references the original order
• The GLN in NAD+DP matches the partner's delivery location GLN
• QuantityDelivery reflects the physical quantity dispatched (not the ordered quantity)
• SSCC present and valid (18 digits) for each pallet — if the partner requires it
• BestBeforeDate / ExpiryDate present for food/pharmaceutical products
• BatchNo (lot) present when products have lot traceability
• UNT count verified with the EDIconnect validator
• Test DESADV sent and confirmed by the partner (or validated in sandbox)

4. RECADV (Inbound — you receive receiving advices)

• The system recognises all 3 types: NIR (632), Return (DocumentType=R), Seizure (70E)
• ReceptionNumber is saved
• QuantityReception is compared with QuantityDelivery from DESADV
• Quantity discrepancies generate a notification/credit note suggestion
• Return (DocumentType=R) creates a return order in the warehouse
• Seizure (BGM+70E) triggers the correct workflow
• NIR test with equal quantity → no additional action
• NIR test with quantity shortage → credit note suggestion generated
• Return test → return order created in the warehouse

5. INVOIC (Outbound — you send invoices)

• InvoiceSeries + InvoiceNumber ≤ 16 characters total
• Seller/RegisteredCapital filled in (legally mandatory)
• Seller/VAT (CUI) and Seller/RegNo (Commercial Register) filled in
• DeliveryNumber (RFF+DQ) references the corresponding DESADV
• TaxSummary contains one TaxLine per distinct VAT rate
• Totals are consistent: TotalPriceNoTax + TotalTax = TotalIncludingTax
• Correction invoices (DocumentType=C) reference the original invoice via ReferenceInvoiceNumber
• Reversal invoices (DocumentType=S) have BGM_1225=1
• Simple invoice test (1 VAT rate, 1 line) → validated with the XSD tool
• Multi-VAT invoice test (9% + 19%) → TaxSummary with 2 TaxLines
• Credit note test (DocumentType=C or BGM+381)

6. Go-Live

Complete this section only after all previous sections have been fully checked off.

• All scenarios above tested successfully in sandbox
• Written confirmation from the partner that tests have passed
• Production credentials received and configured
• TestIndicator=1 removed or set to 0 in production
• First real message sent and monitored manually
• Partner escalation contact identified and saved