Lifecycle, status and payment / Guide

Status messages and their meanings

Common status messages, what each one commits the sender and receiver to, and what to do on each one.

CreateMapValidateRouteProcessStage: Process

In brief: the direct answer

Common status messages, what each one commits the sender and receiver to, and what to do on each one. Status messages and their meanings is best approached through status as a commitment. For status messages and their meanings, the action each status requires decides the outcome. For status messages and their meanings, the action each status requires missing means rejection. For status messages and their meanings, the action each status requires wrongly mapped means wrong meaning. This guide keeps returning to one check for status messages and their meanings: act on the status, do not only record it.

The route stage for status messages and their meanings is Process. At Process, the action each status requires is what follows next. For status messages and their meanings, a Process decision cannot be repaired later. For status messages and their meanings, a Process decision cannot be repaired cheaply. Check the action each status requires for status messages and their meanings before moving on.

The record at this stage

Follow the invoice as a record through status messages and their meanings. At Process, the record for status messages and their meanings carries the action each status requires. Answer the action each status requires for status messages and their meanings with evidence. Then the rest of lifecycle, status and payment becomes easier. Then the rest of status messages and their meanings becomes easier to check.

Describe the record before the system for status messages and their meanings. Systems change, but the action each status requires for status messages and their meanings stays. Providers change, but the action each status requires for status messages and their meanings stays. Formats change, but the action each status requires for status messages and their meanings stays. For status messages and their meanings, ask what record a system produces. For status messages and their meanings, ask what record a system accepts. For status messages and their meanings, ask what status evidence it returns.

What the data must carry

The data that matters most for status messages and their meanings is the action each status requires. That is not a slogan for status messages and their meanings. It is what the next status messages and their meanings check looks at. If the action each status requires for status messages and their meanings is missing, expect rejection. If the action each status requires for status messages and their meanings is ambiguous, expect rejection. If the action each status requires for status messages and their meanings is wrongly formatted, expect rejection.

Check the action each status requires as the receiver reads status messages and their meanings. For status messages and their meanings, screen correctness is not enough. For status messages and their meanings, file correctness is not enough. For status messages and their meanings, mapping correctness matters too. Use the mapping table for status messages and their meanings first. Use the receiver test for status messages and their meanings second. Use a sample invoice for status messages and their meanings third.

Validation and evidence

For status messages and their meanings, validation has three gates. Status messages and their meanings structure comes first. Status messages and their meanings business rules come second. Status messages and their meanings receiver rules come third. Each status messages and their meanings gate has its own failure message.

A status messages and their meanings rejection should name its rule. A status messages and their meanings rejection should name its field. A status messages and their meanings rejection should name the value sent. A status messages and their meanings rejection should name the value expected. Without those facts, a status messages and their meanings rejection is a delay. Return a status messages and their meanings rejection with that request.

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

Where it breaks, and the check to make first

The common status messages and their meanings break is simple. For status messages and their meanings, act on the status, do not only record it was skipped. For status messages and their meanings, the receiver found the problem. For status messages and their meanings, the sender must now correct it. For status messages and their meanings, the sender must resend it. For status messages and their meanings, the sender must explain it.

Illustration, with round numbers only, for status messages and their meanings: A seller sends 20 invoices for status messages and their meanings. 5 fail on the action each status requires for status messages and their meanings. Checking the action each status requires first for status messages and their meanings costs minutes. A status messages and their meanings receiver rejection costs days. Sometimes a status messages and their meanings rejection costs a payment cycle. That is why status messages and their meanings repeats one check: act on the status, do not only record it.

What to verify before acting

Before acting on status messages and their meanings, verify three things. First, jurisdiction and transaction for status messages and their meanings. First, buyer and country for status messages and their meanings. Second, OpenPeppol: Billing validation rules for status messages and their meanings today. Third, the status messages and their meanings buyer requirement in writing.

A guide on status messages and their meanings organises those questions. A guide on status messages and their meanings cannot answer a specific transaction. This guide on status messages and their meanings gives general information only. This guide on status messages and their meanings is not advice for a specific invoice. For a specific invoice about status messages and their meanings, check OpenPeppol: Billing validation rules. For a specific question about status messages and their meanings, ask a qualified adviser.

Requirements, formats and obligations vary by jurisdiction and transaction type. Verify current details with the relevant official source and trading partner before acting. This guide is general information, not legal, tax, accounting or compliance advice.

How this guide is layered

Every guide on this site is read through the same twelve layers, in the order that fits its topic: evidence, direct intent, transaction, jurisdiction, obligation, data, format, network, validation, tax, accounting, lifecycle. The layers are a reading method, not a claim about any single system.

Evidence basis: Primary sources named in the sources section, checked 2026-10-27; country guides are dated research routes, not mandate calendars. Scope: General educational information only; no individual legal, tax, accounting or compliance advice; jurisdiction and transaction specific checks remain with the reader.

Back to the pillar guide: Invoice lifecycle, status and payment explained.

In this topic

Primary sources and further reading

These official resources support the standards and regulatory context. Check their current versions before implementation.