Data in motion: why the invoice is a record, not a file

The thesis of this guide: an invoice travels as data through systems, and every stage can change what the next system can do. Data in motion is best approached through the record travelling, not the document travelling. For data in motion, the status trail beside the invoice data decides the outcome. For data in motion, the status trail beside the invoice data missing means rejection. For data in motion, the status trail beside the invoice data wrongly mapped means wrong meaning. This guide keeps returning to one check for data in motion: follow the status, not only the document.

The route stage for data in motion is Create. At Create, the status trail beside the invoice data is what follows next. For data in motion, a Create decision cannot be repaired later. For data in motion, a Create decision cannot be repaired cheaply. Check the status trail beside the invoice data for data in motion before moving on.

Follow the invoice as a record through data in motion. At Create, the record for data in motion carries the status trail beside the invoice data. Answer the status trail beside the invoice data for data in motion with evidence. Then the rest of fundamentals becomes easier. Then the rest of data in motion becomes easier to check.

Describe the record before the system for data in motion. Systems change, but the status trail beside the invoice data for data in motion stays. Providers change, but the status trail beside the invoice data for data in motion stays. Formats change, but the status trail beside the invoice data for data in motion stays. For data in motion, ask what record a system produces. For data in motion, ask what record a system accepts. For data in motion, ask what status evidence it returns.

The data that matters most for data in motion is the status trail beside the invoice data. That is not a slogan for data in motion. It is what the next data in motion check looks at. If the status trail beside the invoice data for data in motion is missing, expect rejection. If the status trail beside the invoice data for data in motion is ambiguous, expect rejection. If the status trail beside the invoice data for data in motion is wrongly formatted, expect rejection.

Check the status trail beside the invoice data as the receiver reads data in motion. For data in motion, screen correctness is not enough. For data in motion, file correctness is not enough. For data in motion, mapping correctness matters too. Use the mapping table for data in motion first. Use the receiver test for data in motion second. Use a sample invoice for data in motion third.

For data in motion, validation has three gates. Data in motion structure comes first. Data in motion business rules come second. Data in motion receiver rules come third. Each data in motion gate has its own failure message.

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

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

The common data in motion break is simple. For data in motion, follow the status, not only the document was skipped. For data in motion, the receiver found the problem. For data in motion, the sender must now correct it. For data in motion, the sender must resend it. For data in motion, the sender must explain it.

Illustration, with round numbers only, for data in motion: A seller sends 10 invoices for data in motion. 2 fail on the status trail beside the invoice data for data in motion. Checking the status trail beside the invoice data first for data in motion costs minutes. A data in motion receiver rejection costs days. Sometimes a data in motion rejection costs a payment cycle. That is why data in motion repeats one check: follow the status, not only the document.

Before acting on data in motion, verify three things. First, jurisdiction and transaction for data in motion. First, buyer and country for data in motion. Second, European Commission: What is eInvoicing? for data in motion today. Third, the data in motion buyer requirement in writing.

A guide on data in motion organises those questions. A guide on data in motion cannot answer a specific transaction. This guide on data in motion gives general information only. This guide on data in motion is not advice for a specific invoice. For a specific invoice about data in motion, check European Commission: What is eInvoicing?. For a specific question about data in motion, ask a qualified adviser.