Invocit

INVOCIT INSIGHTS

Why hasn’t my Peppol invoice reached the recipient?

If a Peppol invoice has not reached the recipient, check the recipient’s Peppol identifier, the invoice validation result and the latest Peppol delivery-history entry. In Invocit, the document’s summary badge and its channel-specific delivery history describe different parts of the workflow. A summary badge saying Sent alone is not enough to establish that the recipient has received the invoice.

Start with the latest Peppol delivery attempt

  1. Open the invoice and its delivery history. Select the attempt whose channel is Peppol, rather than relying on an email or other-channel result.
  2. Read the latest status and, if present, its error message. Check the attempt time so that you do not mistake an older failure for the latest result.
  3. Use the checks below to decide whether you need to confirm the recipient, correct invoice data or investigate delivery.

1. Check the recipient’s Peppol registration

Confirm the recipient’s exact Peppol participant identifier and its identifier scheme with the recipient or their service provider. A company name, an email address and a Peppol participant identifier are different things. Ask whether that identifier can receive the invoice document type you are sending.

The Peppol Directory can help you find a receiver. However, absence from the Directory does not prove that the business is not registered: OpenPeppol states that Directory publication is not mandatory. Where needed, ask your provider to check the participant’s published receiving capabilities through the Peppol lookup infrastructure.

Next step: if the identifier, scheme or receiving capability is uncertain, confirm it before trying again. If the recipient cannot receive this document through Peppol, ask the Invocit team which supported workflow is appropriate for that transaction.

2. Read the validation error before resending

A failure can result from the structured invoice data. Read the complete error message and its rule identifier. Correct the underlying data through the workflow supported by Invocit, then check that the corrected data is present in the document being sent.

Real error example: BR-61 and a missing payment account

An Invocit outbox example showed a Peppol attempt with status Failed and rule BR-61. The message identified the missing field as the Payment account identifier (BT-84). Personal, company, document and integration identifiers are omitted here.

Under Peppol BIS Billing rule BR-61, an invoice using the relevant credit-transfer payment means must include the payment account identifier. In the UBL rule, payment means codes 30 and 58 trigger this check. For a SEPA credit transfer, check the intended payee bank account, normally identified by its IBAN.

This is the account to which the invoice should be paid. It is separate from the customer’s Peppol receiving identifier. Changing the customer’s Peppol ID does not supply a missing payment account.

  1. Check whether the selected payment method correctly describes how this invoice will be paid.
  2. Check the intended payee account and make sure its identifier is included in the structured invoice, not only printed in a PDF or stored in company settings.
  3. If the approved invoice is locked, or you cannot tell whether the corrected account is included in the outgoing document, ask support how to correct or regenerate it through the supported workflow.
  4. Check the new validation result before retrying. Do not change the payment method merely to bypass a rule.

Next step: resolve the reported validation problem before using Resend. Do not assume that resending automatically rebuilds the invoice from recently edited settings. A scheduled retry is not evidence that a validation error has been corrected.

3. Separate the document badge from delivery history

Invocit shows a combined document status in the list and detail heading. That badge can reflect document lifecycle, payment information or a sending result. Use the channel-specific history to investigate whether a particular Peppol attempt succeeded.

Scroll horizontally to read the status tables on a small screen.

Document summary: what the badge tells you
BadgeHow to use it in a delivery investigation
DraftDo not assume an invoice in preparation has been sent. Check for a delivery-history entry.
ApprovedApproval is a document lifecycle state; inspect the delivery history for a Peppol attempt.
SentCheck the latest Peppol history entry before treating the invoice as delivered.
SendingThe summary indicates a sending process; inspect its channel, latest attempt and error details.
Peppol failedRead the Peppol attempt’s error. A different channel’s failure should be investigated in that channel.
Paid / Partial / OverdueThese describe payment or due-date information. They do not replace channel-specific delivery evidence.
Delivery history: the channel-specific result
Visible messageWhat to check next
This invoice has not been sent yet.No send attempt is shown. Check the intended channel and the supported sending workflow.
Invoice createdThe record shows creation; look for subsequent sending and delivery entries.
SendingPending, queued and sending states use this label. Check for a later result and any retry information.
SentThe history records a sent state. Look for Delivered or a later failure; Sent and Delivered are distinct labels.
DeliveredThe attempt is marked delivered. If the recipient cannot find it, ask them to check their receiving software or provider with the relevant document reference.
Delivery failedThe UI groups failed and rejected results under this label. Read the error details to understand the reason; the label alone does not identify a business rejection by the buyer.

Delivery, business acceptance and payment are separate questions. A delivered status should not be interpreted as proof that a person has read the invoice, that the buyer has approved its contents, or that payment has been made. Peppol’s Invoice Response specification distinguishes business-process responses from transport acknowledgements.

When should you use Resend?

The outbox includes a Resend action and may show a retry count and next retry time. Check the latest attempt before retrying. A validation failure needs a data correction; an unclear or still-pending result needs investigation. If a retry is already scheduled, ask support how the pending attempt should be handled before starting another one.

If the attempt is already marked Delivered, investigate with the recipient instead of assuming a duplicate send is needed. No fixed retry schedule, retry limit or delivery-time guarantee is implied by the example.

What to send to Invocit support

Use Invocit support to share the invoice reference, attempt date and time with time zone, channel, latest delivery status, rule identifier and error message. Include whether a retry is scheduled. If the problem concerns the recipient, provide their confirmed Peppol identifier and scheme through the appropriate support channel.

For a public screenshot, hide names, account numbers and internal identifiers. Support can request the specific diagnostic information needed through a suitable channel.

Frequently asked questions

Does Sent mean my customer received the invoice?

Invocit displays Sent and Delivered as separate delivery-history states. Check the latest Peppol entry rather than relying on the combined summary badge.

My customer is not in the Peppol Directory. Does that mean they cannot receive invoices?

No. Directory publication is not mandatory. Confirm the participant identifier, scheme and supported document type with the recipient or their provider.

Will Resend fix BR-61?

Resend alone does not establish that the missing payment account has been supplied. Check the payment method, correct the required account data through the supported workflow, and verify the outgoing structured document.

The invoice says Delivered, but the recipient cannot find it. What now?

Confirm the reference and recipient identifier, then ask the recipient to investigate their receiving software or provider. A delivery label does not prove that a user has opened or approved the invoice.

Related Invocit resources

Which plan is right for me?

See Invocit in action.

Find out how Invocit can simplify your invoicing workflow.

Book a demo ↗