| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2708 |
| Technical Name |
peppol_health_dashboard |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2708 |
| Technical Name |
peppol_health_dashboard |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
EU Peppol Dashboard
Transmission health for e-invoicing over Peppol — delivery rates, rejection breakdown and endpoint reachability over your transport logs
Once you are live on the Peppol network you need to know whether your invoices are actually delivered, why some bounce, and whether your access point is reachable. This dashboard turns the e-Invoice Core Engine transport log into a live operational view — no new transport, no extra credentials, just analytics over the calls you already make.
Delivery KPIs & health score
Delivered, rejected, failed and pending counts with their rates, plus a weighted 0–100 operational health score over a configurable look-back window. A delivered transmission is full credit, a rejection partial, a hard failure zero.
Rejection breakdown
Every rejection is classified from its response body into stable reason codes — Schematron / EN 16931 business rules, recipient-not-registered, malformed XSD, auth / certificate, duplicate, rate-limited and payload-too-large — so you fix the right thing.
Endpoint reachability
A per access-point snapshot — up / degraded / down, sample count, error rate and average / p95 latency — with the most recent observation driving the live status so a recovered AP is not kept flagged as down.
Delivery trend
Hourly, daily or weekly time series of delivery rate and volume with a moving average and sharp-regression detection, so a sudden drop in delivery surfaces immediately.
Retry queue planner
Transient failures (network, 5xx, throttling) are separated from permanent sender-side rejections that need a payload fix. Retryable items get capped exponential backoff, and the planner warns when the resend backlog would exceed your access point's hourly rate budget.
Daily snapshots
A scheduled action freezes the KPIs per company every day, so the delivery-rate trend survives transport-log pruning and you keep a durable compliance record of your transmission health.
Read-only, private by design
The dashboard only reads your transport logs and transmits nothing anywhere. All analytics — classification, percentiles, backoff, trend bucketing, regression detection — run in plain Python services with no external calls. Works alongside any Peppol connector built on the e-Invoice Core Engine.
Compatible with Odoo 18 and Odoo 19.
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