| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1991 |
| Technical Name |
peppol_outbound_queue_pro |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
Peppol Outbound Queue
Batch, rate-limit and track every outbound Peppol transmission â feeding your own access point (BYOK)
Peppol Outbound Queue turns ad-hoc e-invoice sending into a controlled, observable pipeline. Posted invoices and credit notes are enqueued, validated against the Peppol participant addressing rules, then dispatched in rate-limited batches to your own access point with full per-document status, automatic retries and exponential backoff. Nothing is sent without your credentials: this is a BYOK (bring-your-own-key) orchestration layer, not an access point.
Why an outbound queue?
Access points and recipient SMPs enforce request ceilings. Sending hundreds of invoices in a burst gets you throttled or dropped. A queue smooths the flow, retries transient failures politely, never re-sends a document twice, and gives finance a single screen showing exactly what has been transmitted, what is waiting, and what failed and why.
Rate-limited batch dispatch
A dual ceiling â a token bucket (steady rate + burst) combined with a rolling-window limit â decides how many documents leave per run. Configure the rate per minute, burst capacity, window and batch size per company.
Per-document status tracking
Each queued document has an explicit lifecycle: Draft → Ready → Sending → Sent, with Error and Cancelled branches. Stored status flags drive instant filters: dispatchable, sent, error, retries-exhausted, still-open.
Automatic retries with backoff
Transient failures (timeouts, 5xx) are retried with capped exponential backoff and a configurable retry budget. Permanent failures (malformed document, unroutable recipient, validation errors) are flagged immediately and never waste retries.
BYOK access point
In prepare-only mode the queue builds the Standard Business Document Header (SBDH) and transmission request for your access point to collect â nothing leaves your database. Configure your own endpoint URL and bearer token to push over HTTP using your credentials.
Peppol addressing done right
Participant identifiers are validated against the official ISO 6523 / Peppol EAS scheme code list (Belgian CBE 0208, German VAT 9930, Norwegian Org 0192, GLN 0088, LEI 0199 and the full 99xx VAT range). The recipient identifier is resolved from an explicit per-partner Peppol id or derived from the partner's VAT + country. Documents are wrapped in a spec-shaped SBDH carrying the Peppol BIS Billing 3.0 document type and process identifiers.
Feature overview
| Capability | Detail |
|---|---|
| Queue model | One item per document with routing metadata, transmission request JSON and idempotency key |
| Idempotency | Deterministic transmission id (SHA-256 of sender + receiver + doctype + document) prevents duplicate sends |
| Dispatch batch | Plan and run rate-limited batches; audit log of eligible / allowed / sent / failed / pending |
| Scheduler | Cron dispatches ready documents every few minutes, one rate-limited batch per company |
| UBL builder | Generates a BIS 3.0 UBL Invoice / CreditNote when the invoice has no UBL attachment yet |
| Bulk enqueue | Select many invoices in the list and queue them in one action with shared priority |
| Multi-company | Per-company rate config, sender identity, access point and record-rule isolation |
How it works
- Set your company's Peppol sender identifier and rate limits in Accounting → Peppol Queue → Settings.
- Post an invoice and click Queue for Peppol, or bulk-queue from the invoice list.
- The scheduler (or a manual run) dispatches ready documents in rate-limited batches to your access point.
- Track every document's status, retries and errors on the Outbound Queue and Dispatch Batches screens.
Disclosure
This module prepares and (optionally) transmits documents to the access point you configure, using your credentials. We are not an accredited Peppol access point and no third-party transmission occurs. Your credentials are stored only in your own database.
We deliver the software only (BYOK — it runs under your own Peppol access point and credentials). We are not a Peppol access point, SMP or integrator and do not transmit on the network on your behalf. Support is provided and your purchase is refundable.
Keywords: Peppol, outbound queue, e-invoicing, BIS Billing 3.0, access point, BYOK, SBDH, rate limiting, batch dispatch, EN 16931, EAS, ISO 6523, UBL invoice, credit note, retry backoff.
Screenshots
Dispatch Batches
Outbound Queue
Run Dispatch Now
Settings
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1991 |
| Technical Name |
peppol_outbound_queue_pro |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module