Frequently Asked Questions — EDIconnect

Configuration and Setup

Which GLN should I use — the company's or the warehouse's?

It depends on the context. In the NAD+SU segment, put the company's GLN (supplier). In NAD+DP, put the GLN of the delivery location — that is, the partner's warehouse or store. The partner will confirm during onboarding which GLNs they accept for each position.

Can I use the same EDIfact file for multiple messages of the same type?

Yes. A single interchange (UNB...UNZ) can contain multiple UNH...UNT pairs. For example, you can send 50 ORDERS in the same file. Each individual message has its own UNH and UNT. The message counter in UNZ must reflect the total number of UNH/UNT pairs in the file.

What do I do if I don't have an SSCC for pallets?

SSCC is optional in DESADV (segment GIN+BJ). If the partner does not explicitly require it, you can omit the PAC, PCI and GIN segments from the message. If they do require it, generate the SSCC using the GS1 formula: company prefix (from GS1 Romania) + serial number + check digit.

Do I need to register somewhere before sending the first EDI message?

Yes. Before the first production message, the partner must register your GLN in their system. Sending a message with an unregistered GLN will generate error EDI-002 ("GLN not authorized"). Request written confirmation of registration before go-live.

Format and Structure

What is the difference between EDIfact and XML in EDIconnect?

Both transmit the same business data. EDIfact (EANCOM D.01B) is the classic text-segment-based format, used by traditional systems (large ERPs, retailers with older infrastructure). XML is the modern format, easier to read and debug. Partners specify their preferred format at onboarding — you cannot choose unilaterally.

Do I have to send UNA in every EDIfact message?

It is not mandatory. UNA is omitted when you use the standard separators (:, +, ., ?, '). If your partners use different separators (a rare situation), UNA becomes necessary to declare the alternative separators. The EDIconnect validator accepts both variants.

The `` field in XML — what value should I put?

The correct value is 2.0 — the current version of the EDIconnect schema. This value is validated by the XSD schema and the message will be rejected if it is missing or has a different value.

Can I send an invoice without a delivery note number (DeliveryNumber / RFF+DQ)?

DeliveryNumber is mandatory in INVOIC according to the Expert Supplier specification. If, exceptionally, you do not have an associated delivery note (for example, for service invoicing), discuss this with your partner — some partners accept a bilaterally agreed placeholder value. Do not omit the field without the partner's explicit agreement.

What is the maximum length of a free-text field in XML?

Refer to the XSD schema for each message — each field has its maximum length declared as maxLength. As a general rule, Name-type fields are limited to 70 characters, and Reference-type fields to 35 characters. Exceeding the maximum length will cause XSD validation to fail.

Errors and Troubleshooting

I am getting the error "GLN not authorized" (EDI-002). What does it mean?

The sender's or recipient's GLN is not registered in the partner's system. Check that you communicated the correct GLNs during onboarding and that you are using them as a string of exactly 13 digits (no spaces, no quotes). Contact the partner to confirm that registration has been completed.

I am getting "Duplicate message" (EDI-003). What should I do?

A message with the same reference number (OrderNumber, InvoiceNumber, etc.) has already been sent and accepted previously. Generate a new, unique number for the new message. Do not resend the identical message — it will generate the EDI-003 error again. If it was an error and the original message should not have been sent, contact the partner for manual cancellation.

My UNT count is always wrong. How do I calculate it correctly?

Count ALL segments from UNH through to UNT, including UNH and UNT. The UNA, UNB and UNZ segments are not counted — they belong to the interchange, not to the individual message. The simplest approach: use the EDIconnect validator, which automatically calculates and verifies the UNT count.

My invoices are rejected with "Invalid VAT rate". What should I check?

The VAT rate must be a whole number (9, 19, 0, etc.), not a formatted percentage ("9%" is incorrect). Check that TaxRate contains only digits and that the value corresponds to the VAT rates in force under Romanian tax legislation. Also check that there are no spaces or hidden characters in the field.

My messages reach the partner but are not processed. What is happening?

Check in order: (1) TestIndicator — if it is set to 1 in production, messages are treated as tests and ignored; (2) the file format — if partners were expecting EDIfact and you sent XML; (3) encoding — if your system is sending ISO-8859-1 instead of UTF-8. Ask the partner for their logs to identify the exact point of failure.

Business Logic

When do I send DESADV — before or after delivery?

Always before physical delivery. The partner processes the DESADV to prepare for the reception (ramp allocation, staff, space). If you send it after delivery, the reception was done "blind" and discrepancies that are difficult to reconcile may arise. The GS1 recommendation is to send DESADV at least 2 hours before delivery.

The partner has received the goods but is not sending RECADV. What should I do?

Contact the partner's EDI contact person. The absence of RECADV blocks automatic reconciliation in CRMconnect and prevents you from generating a credit note for any shortages. Agree in the EDI contract (or in an attached SLA) on a maximum deadline for sending RECADV — typically 24–48 hours after physical reception.

Can I send an invoice for multiple delivery notes?

Yes, a single invoice can reference multiple DESADVs. Include each DeliveryNumber as a separate reference (one RFF+DQ per delivery note) and ensure that the invoice lines correspond to the lines in all referenced DESADVs. The invoice totals must cover the sum of all included delivery notes.

How do I send a credit note (partial reversal)?

Send an INVOIC with DocumentType=C (correction/credit) or BGM+381 (credit note), referencing the original invoice via ReferenceInvoiceNumber and ReferenceInvoiceDate. Include only the affected lines, with quantities expressed as negative values. The total of the credit invoice will be negative, reflecting the amount to be refunded.

Do I have to send ORDRSP for every ORDERS received?

ORDRSP (order response) is optional if you accept the order in full. It becomes mandatory if: (a) you change the quantities or delivery dates from the order, (b) you reject the order in full or in part, or (c) the partner explicitly requests confirmation for all orders. Check the partner's specification at onboarding.

Didn't find your answer?

If your question does not appear above or you need further clarification, contact the EDIconnect support team:

• Email: support@azuvio.io
• Support portal: Open a ticket
• Technical documentation: EDIconnect Architecture | Error Codes | Field Mapping

Include in your message: the partner's name, the message type (ORDERS/DESADV/etc.), the error code received and, if possible, an anonymised example of the problematic message.