In addition to webhooks, the PSB can send notifications by e-mail. An e-mail hook (also known as a mail hook or mailto hook) sends an e-mail for every event on a chosen topic. This is useful for organisations that do not have their own webhook endpoint, or as a supplement to existing webhooks.

Register a hook via the API with a mailto: action:

{
  "action": "mailto:finance@jouw-bedrijf.nl",
  "topics": ["InvoiceReceived"]
}

For every received invoice the PSB now sends a notification e-mail to the specified address. The e-mail address in the action may also contain a placeholder: [senderEmailAddress] or [receiverEmailAddress] to dynamically send to the sender's or recipient's e-mail address.

Note: when using placeholders, always include the fallbackEmail parameter. If the e-mail address is not available in the document, the PSB sends the notification to the fallback address.

E-mail hooks support extensive configuration via query parameters in the action URL. You build the URL as mailto:address@domain.com?param1=value&param2=value.

The PSB supports two versions of the e-mail template:

Tip: always use version 1.0 for new configurations. Version 0.9 sends from the old eVerbinding domain, which is no longer actively maintained.

An e-mail hook that sends an e-mail with the invoice as a PDF attachment (without the XML) for every received invoice:

mailto:finance@jouw-bedrijf.nl?includeAttachment=true&excludePrimaryAttachment=true&version=1.0

A hook that dynamically sends to the sender, with a fallback:

mailto:[senderEmailAddress]?includeAttachment=true&version=1.0&fallbackEmail=backup@jouw-bedrijf.nl

Want full control over the e-mail layout? Have eConnect configure a custom SendGrid template and use the templateId parameter. You can also link your own SendGrid account by adding an init object with your API key to the hook configuration.

If a customer finds that forwarded incoming invoices contain only the XML and not the PDF, this is caused by excludeAdditionalAttachments=true. When an e-mail connector/mail hook is created, this parameter defaults to true, meaning PDF attachments are not included.

Solution: set excludeAdditionalAttachments=false on the mail hook. The additional attachments (PDF/PNG from the XML) will then be included in the e-mail.

Execution: if the automatically created e-mail connector (Collabrr platform) is involved, only TechSupport can make this change. Do not manually modify the connector after the fix — a manual edit will overwrite the correction and suppress the PDF attachment again. If the customer manages their own PSB mail hook, they can set the parameter to false themselves.

You can specify multiple e-mail addresses by creating separate hooks, or by using the bcc parameter for additional recipients.

An e-mail hook sends notifications from a no-reply address (noreply@everbinding.nl for version 0.9, noreply@econnect.email for version 1.0). If the receiving mailbox replies automatically — for example via an out-of-office or absence assistant — that reply often bounces back with an Undeliverable or NDR message (non-delivery report), typically with error code 550 5.1.10 Recipient not found.

If you receive such an Undeliverable/NDR with a subject referencing a PSB notification such as InvoiceSent, this does not mean the invoice failed to be delivered via Peppol. The topic InvoiceSent means the outgoing invoice was successfully delivered to the receiving party (see configure webhooks: commonly used topics). The bounce occurs because the customer's mailbox automatically replied to a no-reply address — not because of a Peppol delivery failure.

How to verify:

1. Read the attachment of the NDR: does the original subject or envelope sender reference a no-reply address (noreply@everbinding.nl or noreply@econnect.email)?
2. If the notification is for a topic like InvoiceSent, the invoice has already been successfully delivered. The bounce is a reaction to the notification e-mail itself, not a delivery failure.
3. Ask the customer to disable the auto-reply or absence assistant for mail from everbinding.nl and econnect.eu, or to exclude no-reply addresses from automatic replies.

A genuine platform delivery failure appears as Delivery Failed status in the outbox, not as an NDR on a no-reply address.

See the full API specification at psb.econnect.eu for all available configurations and examples.