In brief: the direct answer
How a sender learns what a receiver can accept, before the first invoice is sent. Service metadata and capability lookup is best approached through capability before sending. For service metadata and capability lookup, the capability lookup result decides the outcome. For service metadata and capability lookup, the capability lookup result missing means rejection. For service metadata and capability lookup, the capability lookup result wrongly mapped means wrong meaning. This guide keeps returning to one check for service metadata and capability lookup: look up capability before the first invoice.
The route stage for service metadata and capability lookup is Route. At Route, the capability lookup result is what follows next. For service metadata and capability lookup, a Route decision cannot be repaired later. For service metadata and capability lookup, a Route decision cannot be repaired cheaply. Check the capability lookup result for service metadata and capability lookup before moving on.
The record at this stage
Follow the invoice as a record through service metadata and capability lookup. At Route, the record for service metadata and capability lookup carries the capability lookup result. Answer the capability lookup result for service metadata and capability lookup with evidence. Then the rest of networks, access points and peppol becomes easier. Then the rest of service metadata and capability lookup becomes easier to check.
Describe the record before the system for service metadata and capability lookup. Systems change, but the capability lookup result for service metadata and capability lookup stays. Providers change, but the capability lookup result for service metadata and capability lookup stays. Formats change, but the capability lookup result for service metadata and capability lookup stays. For service metadata and capability lookup, ask what record a system produces. For service metadata and capability lookup, ask what record a system accepts. For service metadata and capability lookup, ask what status evidence it returns.
What the data must carry
The data that matters most for service metadata and capability lookup is the capability lookup result. That is not a slogan for service metadata and capability lookup. It is what the next service metadata and capability lookup check looks at. If the capability lookup result for service metadata and capability lookup is missing, expect rejection. If the capability lookup result for service metadata and capability lookup is ambiguous, expect rejection. If the capability lookup result for service metadata and capability lookup is wrongly formatted, expect rejection.
Check the capability lookup result as the receiver reads service metadata and capability lookup. For service metadata and capability lookup, screen correctness is not enough. For service metadata and capability lookup, file correctness is not enough. For service metadata and capability lookup, mapping correctness matters too. Use the mapping table for service metadata and capability lookup first. Use the receiver test for service metadata and capability lookup second. Use a sample invoice for service metadata and capability lookup third.
Validation and evidence
For service metadata and capability lookup, validation has three gates. Service metadata and capability lookup structure comes first. Service metadata and capability lookup business rules come second. Service metadata and capability lookup receiver rules come third. Each service metadata and capability lookup gate has its own failure message.
A service metadata and capability lookup rejection should name its rule. A service metadata and capability lookup rejection should name its field. A service metadata and capability lookup rejection should name the value sent. A service metadata and capability lookup rejection should name the value expected. Without those facts, a service metadata and capability lookup rejection is a delay. Return a service metadata and capability lookup rejection with that request.
Evidence for service metadata and capability lookup is what remains afterwards. Keep the service metadata and capability lookup invoice as exchanged. Keep service metadata and capability lookup status messages with it. Keep any service metadata and capability lookup correction linked to it. An auditor for service metadata and capability lookup asks for that set.
Where it breaks, and the check to make first
The common service metadata and capability lookup break is simple. For service metadata and capability lookup, look up capability before the first invoice was skipped. For service metadata and capability lookup, the receiver found the problem. For service metadata and capability lookup, the sender must now correct it. For service metadata and capability lookup, the sender must resend it. For service metadata and capability lookup, the sender must explain it.
Illustration, with round numbers only, for service metadata and capability lookup: A seller sends 50 invoices for service metadata and capability lookup. 2 fail on the capability lookup result for service metadata and capability lookup. Checking the capability lookup result first for service metadata and capability lookup costs minutes. A service metadata and capability lookup receiver rejection costs days. Sometimes a service metadata and capability lookup rejection costs a payment cycle. That is why service metadata and capability lookup repeats one check: look up capability before the first invoice.
What to verify before acting
Before acting on service metadata and capability lookup, verify three things. First, jurisdiction and transaction for service metadata and capability lookup. First, buyer and country for service metadata and capability lookup. Second, OpenPeppol: Peppol BIS Billing 3.0 for service metadata and capability lookup today. Third, the service metadata and capability lookup buyer requirement in writing.
A guide on service metadata and capability lookup organises those questions. A guide on service metadata and capability lookup cannot answer a specific transaction. This guide on service metadata and capability lookup gives general information only. This guide on service metadata and capability lookup is not advice for a specific invoice. For a specific invoice about service metadata and capability lookup, check OpenPeppol: Peppol BIS Billing 3.0. For a specific question about service metadata and capability lookup, 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: network, validation, tax, accounting, lifecycle, evidence, direct intent, transaction, jurisdiction, obligation, data, format. 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
- Networks and access points explained: how an invoice is routed - Direct exchange, providers, platforms and the Peppol network, compared by addressing, acknowledgement and responsibility.
- Message status and acknowledgements across a network - Transport acknowledgement, delivery and business acceptance are three different statuses, and confusing them hides failures.
- Direct exchange vs network exchange - When a direct interface is simpler, when a network is safer, and what each choice costs in onboarding.
Back to the pillar guide: Networks and access points explained: how an invoice is routed.
In this topic
- Networks and access points explained: how an invoice is routed
- Access points: choosing a provider without losing control
- Direct exchange vs network exchange
- Government platforms and portals as routes
- Message status and acknowledgements across a network
- Multi-network strategy for sellers with many buyers
- Network costs and contracts to check
- Network failures and retries: a safe retry rule
- Peppol ids and addressing: getting the recipient right
- Peppol network: how it works, in plain terms
Primary sources and further reading
These official resources support the standards and regulatory context. Check their current versions before implementation.
- OpenPeppol: Peppol BIS Billing 3.0 - Billing profile, information elements and validation
- OpenPeppol: Billing validation rules - Technical and business rule examples