EDIconnect Message Flow

This page explains who sends which message, when, and what response is expected. The goal is to understand the logic behind EDI message exchange before working with individual segments.

1. Full Order-to-Cash Flow

This is the standard flow for a sales transaction from order to invoice.

Partner (Retailer/Distributor)            Azuvio / CRMconnect (Supplier)
─────────────────────────────────────────────────────────────────────
1. ORDERS ──────────────────────────────►
   Purchase Order

                                        2. [Internal order processing]
                                           Order creation in WMS/ERP

3. ◄─────────────────────────────────── DESADV
                                           Despatch Advice
                                           (sent after shipment,
                                           before the truck arrives)

4. RECADV ──────────────────────────────►
   Receiving Advice / NIR
   (confirmation of quantities received)

                                        5. [Invoice generation in ERP]

6. ◄─────────────────────────────────── INVOIC
                                           Fiscal Invoice

Important note: Large partners (e.g. Kaufland, Lidl, Metro) may impose additional rules — for example, DESADV must be sent before the truck leaves the warehouse. Check your partner's specifications before implementation.

2. Message Directions

Direction legend:

• Partner → CRMconnect = message enters the system (inbound)
• CRMconnect → Partner = message leaves the system (outbound)

3. Special Scenarios

3a. Goods Return

When a partner returns goods, the flow is initiated by the partner via a RECADV with document type R.

Partner                                  CRMconnect
────────────────────────────────────────────────────────────
RECADV (DocumentType=R) ───────────────►
Return Goods Advice
(contains quantities returned
and the reason for return)

                                        [Return order creation in WMS]
                                        [Stock update]

◄─────────────────────────────────────── INVOIC (DocumentType=R)
                                         Return invoice / credit note
                                         (negative value or credit)

What to check: In the return RECADV, the BGM segment will contain code 35 (Return Advice). Quantities are positive — the negative sign only appears in the return INVOIC.

3b. Correction Invoice

If an error is discovered in an already-sent invoice (wrong price, incorrect quantity etc.), CRMconnect issues a correction invoice without any action required from the partner.

CRMconnect
────────────────────────────────────────────────────────────
[Error discovered in original invoice]

◄─────────────────────────────────────── INVOIC (DocumentType=C)
                                         Correction Invoice
                                         (references the original invoice
                                         via RFF+IV)

What to check: The correction invoice contains the number of the original invoice it corrects in the RFF+IV segment. The value in the correction invoice represents the difference from the original.

3c. Goods Confiscation

Some partners (particularly international retailers) may confiscate non-conforming goods upon receipt. This is communicated via a RECADV with a specific function code.

Partner                                  CRMconnect
────────────────────────────────────────────────────────────
RECADV (BGM+70E) ──────────────────────►
Goods Confiscation Notification
(goods not accepted into stock,
disposed of by partner)

                                        [Goods disposal workflow]
                                        [Confiscation file creation]

◄─────────────────────────────────────── INVOIC credit
                                         (value of confiscated goods,
                                         issued as a credit note)

What to check: Code 70E in the BGM segment indicates confiscation. Check with your partner whether their process also requires an additional physical document (confiscation report).

4. Recommended Timing

Adhering to deadlines is critical — large partners may automatically reject messages received outside the allowed time window.

Caution: Some partners (e.g. Carrefour, Auchan) have very strict time windows for DESADV. A DESADV sent after the truck has arrived may be automatically rejected by their system.

5. Key Identifiers per Message

EDI messages are linked to each other through common references. If a reference is missing or incorrect, the partner cannot automatically correlate the documents.

Practical example: When the partner receives an invoice (INVOIC), their system automatically looks for RFF+ON to find the original order and RFF+DQ to find the despatch advice. If these fields are missing, the invoice will be placed on hold for manual reconciliation — which can delay payment.

Previous page: EDIconnect Architecture | Next page: Segment Quick Reference