In brief: the direct answer
A delivered invoice may not be accepted, and an accepted invoice may not yet be approved for payment. Delivery vs acceptance vs approval is best approached through three statuses, three meanings. For delivery vs acceptance vs approval, the status that the buyer actually sent decides the outcome. For delivery vs acceptance vs approval, the status that the buyer actually sent missing means rejection. For delivery vs acceptance vs approval, the status that the buyer actually sent wrongly mapped means wrong meaning. This guide keeps returning to one check for delivery vs acceptance vs approval: ask which status the buyer sent.
The route stage for delivery vs acceptance vs approval is Process. At Process, the status that the buyer actually sent is what follows next. For delivery vs acceptance vs approval, a Process decision cannot be repaired later. For delivery vs acceptance vs approval, a Process decision cannot be repaired cheaply. Check the status that the buyer actually sent for delivery vs acceptance vs approval before moving on.
The record at this stage
Follow the invoice as a record through delivery vs acceptance vs approval. At Process, the record for delivery vs acceptance vs approval carries the status that the buyer actually sent. Answer the status that the buyer actually sent for delivery vs acceptance vs approval with evidence. Then the rest of lifecycle, status and payment becomes easier. Then the rest of delivery vs acceptance vs approval becomes easier to check.
Describe the record before the system for delivery vs acceptance vs approval. Systems change, but the status that the buyer actually sent for delivery vs acceptance vs approval stays. Providers change, but the status that the buyer actually sent for delivery vs acceptance vs approval stays. Formats change, but the status that the buyer actually sent for delivery vs acceptance vs approval stays. For delivery vs acceptance vs approval, ask what record a system produces. For delivery vs acceptance vs approval, ask what record a system accepts. For delivery vs acceptance vs approval, ask what status evidence it returns.
What the data must carry
The data that matters most for delivery vs acceptance vs approval is the status that the buyer actually sent. That is not a slogan for delivery vs acceptance vs approval. It is what the next delivery vs acceptance vs approval check looks at. If the status that the buyer actually sent for delivery vs acceptance vs approval is missing, expect rejection. If the status that the buyer actually sent for delivery vs acceptance vs approval is ambiguous, expect rejection. If the status that the buyer actually sent for delivery vs acceptance vs approval is wrongly formatted, expect rejection.
Check the status that the buyer actually sent as the receiver reads delivery vs acceptance vs approval. For delivery vs acceptance vs approval, screen correctness is not enough. For delivery vs acceptance vs approval, file correctness is not enough. For delivery vs acceptance vs approval, mapping correctness matters too. Use the mapping table for delivery vs acceptance vs approval first. Use the receiver test for delivery vs acceptance vs approval second. Use a sample invoice for delivery vs acceptance vs approval third.
Validation and evidence
For delivery vs acceptance vs approval, validation has three gates. Delivery vs acceptance vs approval structure comes first. Delivery vs acceptance vs approval business rules come second. Delivery vs acceptance vs approval receiver rules come third. Each delivery vs acceptance vs approval gate has its own failure message.
A delivery vs acceptance vs approval rejection should name its rule. A delivery vs acceptance vs approval rejection should name its field. A delivery vs acceptance vs approval rejection should name the value sent. A delivery vs acceptance vs approval rejection should name the value expected. Without those facts, a delivery vs acceptance vs approval rejection is a delay. Return a delivery vs acceptance vs approval rejection with that request.
Evidence for delivery vs acceptance vs approval is what remains afterwards. Keep the delivery vs acceptance vs approval invoice as exchanged. Keep delivery vs acceptance vs approval status messages with it. Keep any delivery vs acceptance vs approval correction linked to it. An auditor for delivery vs acceptance vs approval asks for that set.
Where it breaks, and the check to make first
The common delivery vs acceptance vs approval break is simple. For delivery vs acceptance vs approval, ask which status the buyer sent was skipped. For delivery vs acceptance vs approval, the receiver found the problem. For delivery vs acceptance vs approval, the sender must now correct it. For delivery vs acceptance vs approval, the sender must resend it. For delivery vs acceptance vs approval, the sender must explain it.
Illustration, with round numbers only, for delivery vs acceptance vs approval: A seller sends 50 invoices for delivery vs acceptance vs approval. 2 fail on the status that the buyer actually sent for delivery vs acceptance vs approval. Checking the status that the buyer actually sent first for delivery vs acceptance vs approval costs minutes. A delivery vs acceptance vs approval receiver rejection costs days. Sometimes a delivery vs acceptance vs approval rejection costs a payment cycle. That is why delivery vs acceptance vs approval repeats one check: ask which status the buyer sent.
What to verify before acting
Before acting on delivery vs acceptance vs approval, verify three things. First, jurisdiction and transaction for delivery vs acceptance vs approval. First, buyer and country for delivery vs acceptance vs approval. Second, OpenPeppol: Billing validation rules for delivery vs acceptance vs approval today. Third, the delivery vs acceptance vs approval buyer requirement in writing.
A guide on delivery vs acceptance vs approval organises those questions. A guide on delivery vs acceptance vs approval cannot answer a specific transaction. This guide on delivery vs acceptance vs approval gives general information only. This guide on delivery vs acceptance vs approval is not advice for a specific invoice. For a specific invoice about delivery vs acceptance vs approval, check OpenPeppol: Billing validation rules. For a specific question about delivery vs acceptance vs approval, ask a qualified adviser.
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.
Related guides
- Invoice lifecycle, status and payment explained - Issue, delivery, acceptance, correction, payment and closure, and the status messages that mark each step.
- Status messages and their meanings - Common status messages, what each one commits the sender and receiver to, and what to do on each one.
- Payment status and reconciliation - Paid, partially paid, disputed and written off, reconciled against bank and ledger, invoice by invoice.
Back to the pillar guide: Invoice lifecycle, status and payment explained.
In this topic
- Invoice lifecycle, status and payment explained
- Closing an invoice and its evidence
- Invoice exchange flow: states and hand-offs
- Lifecycle for credit notes
- Lifecycle for recurring invoices
- Lifecycle gaps when status is missing
- Lifecycle monitoring dashboards that help
- Payment status and reconciliation
- Reminders and dunning without breaking the record
- Status messages and their meanings
Primary sources and further reading
These official resources support the standards and regulatory context. Check their current versions before implementation.
- OpenPeppol: Billing validation rules - Technical and business rule examples
- European Commission: eInvoicing implementation checklist - B2G implementation considerations