References: orders, contracts and delivery notes

How references tie an invoice to the transaction that created it, and why a missing reference blocks matching. References is best approached through references as the thread to the transaction. For references, the order or contract reference decides the outcome. For references, the order or contract reference missing means rejection. For references, the order or contract reference wrongly mapped means wrong meaning. This guide keeps returning to one check for references: confirm which reference the buyer matches on.

The route stage for references is Create. At Create, the order or contract reference is what follows next. For references, a Create decision cannot be repaired later. For references, a Create decision cannot be repaired cheaply. Check the order or contract reference for references before moving on.

Follow the invoice as a record through references. At Create, the record for references carries the order or contract reference. Answer the order or contract reference for references with evidence. Then the rest of invoice data fields and master data becomes easier. Then the rest of references becomes easier to check.

Describe the record before the system for references. Systems change, but the order or contract reference for references stays. Providers change, but the order or contract reference for references stays. Formats change, but the order or contract reference for references stays. For references, ask what record a system produces. For references, ask what record a system accepts. For references, ask what status evidence it returns.

The data that matters most for references is the order or contract reference. That is not a slogan for references. It is what the next references check looks at. If the order or contract reference for references is missing, expect rejection. If the order or contract reference for references is ambiguous, expect rejection. If the order or contract reference for references is wrongly formatted, expect rejection.

Check the order or contract reference as the receiver reads references. For references, screen correctness is not enough. For references, file correctness is not enough. For references, mapping correctness matters too. Use the mapping table for references first. Use the receiver test for references second. Use a sample invoice for references third.

For references, validation has three gates. References structure comes first. References business rules come second. References receiver rules come third. Each references gate has its own failure message.

A references rejection should name its rule. A references rejection should name its field. A references rejection should name the value sent. A references rejection should name the value expected. Without those facts, a references rejection is a delay. Return a references rejection with that request.

Evidence for references is what remains afterwards. Keep the references invoice as exchanged. Keep references status messages with it. Keep any references correction linked to it. An auditor for references asks for that set.

The common references break is simple. For references, confirm which reference the buyer matches on was skipped. For references, the receiver found the problem. For references, the sender must now correct it. For references, the sender must resend it. For references, the sender must explain it.

Illustration, with round numbers only, for references: A seller sends 10 invoices for references. 1 fail on the order or contract reference for references. Checking the order or contract reference first for references costs minutes. A references receiver rejection costs days. Sometimes a references rejection costs a payment cycle. That is why references repeats one check: confirm which reference the buyer matches on.

Before acting on references, verify three things. First, jurisdiction and transaction for references. First, buyer and country for references. Second, European Commission: Compliance with the eInvoicing standard for references today. Third, the references buyer requirement in writing.

A guide on references organises those questions. A guide on references cannot answer a specific transaction. This guide on references gives general information only. This guide on references is not advice for a specific invoice. For a specific invoice about references, check European Commission: Compliance with the eInvoicing standard. For a specific question about references, ask a qualified adviser.