When finance or support teams need to know what happened after submission and whether a retry, correction or recipient follow-up is required.
Peppol invoice status Problem guide
Track Peppol invoice status: reconcile provider events, delivery evidence and business responses
Turn provider callbacks and technical codes into one traceable submission timeline. Dynafis separates queued, sent, delivered, technically rejected and business-response events instead of reducing everything to a single ambiguous status.
- Reconcile internal submission, provider and network identifiers
- Store ordered status events with timestamps and source
- Separate transport status, technical validation response and buyer-side invoice response
- Show retry eligibility without overwriting the previous attempt
- Provide evidence for support, audit and downstream webhooks
- Open the invoice or submission record
- Synchronize provider callbacks and controlled status queries
- Interpret technical and business events separately
- Retry, correct or follow up based on the documented state
Trust note
Dynafis supports teams with AI, rules and validation. The guidance does not replace tax advice or a legally binding review.
FAQ
Does sent mean accepted by the buyer?
No. Sent or delivered is a transport state. Technical validation and buyer-side processing may produce separate later responses.
What is an Invoice Response?
It is a Peppol business message through which the buyer can communicate processing states or actions for an invoice or credit note.
Can status polling replace webhooks?
Polling can reconcile missing events, but provider webhooks should normally deliver updates. Both paths must remain idempotent.