| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 313 |
| Technical Name |
account_peppol_attachment |
| License | OPL-1 |
| Website | https://www.alwinen.de |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 313 |
| Technical Name |
account_peppol_attachment |
| License | OPL-1 |
| Website | https://www.alwinen.de |
| Versions | 17.0 18.0 19.0 |
PEPPOL with Multiple Attachments
Send and Receive Supporting Documents Through PEPPOL Network
Extend PEPPOL Invoices with Supporting Documents
Extend PEPPOL invoice and debit notes with supporting documents! This module enables Odoo to send and receive multiple attachments through the PEPPOL network, allowing you to send delivery notes, certificates, product specifications, and other supporting documents directly embedded in your PEPPOL invoices and debit notes according to BIS Billing 3.0 standards.
- Outbound Attachments: Mark and upload documents to send via PEPPOL network embedded in your e-invoices
- Inbound Attachments: Enable Odoo to import attachments embedded in received e-invoices via PEPPOL network
- Standards Compliant: Fully compatible with PEPPOL BIS Billing 3.0 and UBL 2.1 standards
- Multiple Formats: Supports PDF, JPEG, PNG, XLSX, ODS, and CSV files which are allowed by PEPPOL network
- Easy Integration: Manage attachments directly in the invoice send dialog
Why Do You Need This Module?
The Challenge
Only the invoice or debit note itself as PDF attachment will be included when Odoo sends via PEPPOL. If additional documents are needed, they must be sent separately via email or other channels.
The Problem
Workflow fragmentation, manual processes across multiple channels, compliance gaps from missing documentation, and customer confusion from correlating documents from different sources.
The Solution
This module enables sending and receiving multiple attachments through PEPPOL. All supporting documents are embedded directly in the UBL XML according to BIS Billing 3.0 standards.
Key Features
Outbound Documents
- Simple Checkbox Interface: Mark and upload attachments to send via PEPPOL
- Integrated Send Wizard: Manage attachments directly in the invoice send dialog
- Automatic Embedding: Attachments are Base64-encoded into UBL XML
- File Validation: Real-time size checks with configurable maximum file size
- Multiple Files: Send multiple supporting documents as needed
Inbound Documents
- Automatic Import: Attachments from received invoices are imported automatically
- Format Support: Handles PDF, JPEG, PNG, XLSX, ODS, CSV
- Seamless Attachment: Files are automatically linked to invoice records
- Standards Compliant: Follows PEPPOL BIS Billing 3.0 specifications
Bidirectional
Not only handle sending, this module supports both sending and receiving attachments through PEPPOL network.
Standards Compliant
Fully compliant with PEPPOL BIS Billing 3.0 and UBL 2.1 standards. Works seamlessly with any PEPPOL access point.
Automatic
Just add attachments at the sending dialog. Receiving attachments is completely automatic. No complex configuration required.
Installation & Configuration
|
1
|
PrerequisitesEnsure PEPPOL is already installed and configured:
|
|
2
|
Install the ModuleGo to |
|
✔
|
Done - Start Sending Attachments!No additional configuration needed. Create an invoice, add attachments, and select them for PEPPOL transmission. |
Test Your PEPPOL Setup
After configuring PEPPOL Electronic Invoicing, you can verify the complete send/receive workflow by sending an e-invoice to your own company. This is an effective way to test both outbound transmission and inbound document reception, including the multi-attachment feature provided by this module.
|
1
|
Create a Customer Partner for Your Own Company
Navigate to |
|
2
|
Create a Customer Invoice with Attachments
Go to |
|
3
|
Send via PEPPOL with Attachments
Click |
|
4
|
Waiting
Waiting Odoo's cron job works and receiving e-invoice from PEPPOL network, by default the cron job will run every 4 hours, you can change the interval in the cron job settings
at |
|
✔
|
Test Complete - PEPPOL Workflow Verified!
Navigate to If you have any questions or need assistance, please don't hesitate to contact us at info@alwinen.de |
Business Benefits at a Glance
Requirements & Compatibility
- Odoo Version: Community or Enterprise Edition
- Required Modules: account_peppol (must be installed and configured)
- PEPPOL Standards: Compatible with BIS Billing 3.0
- Access Point: Works with any PEPPOL access point provider
- File Size Limit: 2MB per attachment (configurable in settings)
- Supported Formats: PDF, JPEG, PNG, XLSX, ODS, CSV
- Multi-Company: Fully supported
- Languages: Translation-ready
Frequently Asked Questions
Does this work with all PEPPOL access point providers?
Yes! This module follows the standard PEPPOL BIS Billing 3.0 specification and works with any compliant access point provider.
Are the attachments transferred through PEPPOL network?
Yes! This module enables Odoo to send attachments through PEPPOL network, which means all documents are transmitted via the PEPPOL infrastructure only.
Can I send multiple attachments with one invoice?
Yes, you can send as many attachments as needed in theory. All the attachments will be embedded in a single E-Invoice file. In practice, different PEPPOL access point providers have different limits. According to our experience, 10MB total is widely accepted.
What happens if my attachment is larger than the maximum file size limit?
The system will show a validation error and prevent sending until you reduce the file size or uncheck that attachment. You can configure the maximum file size in settings.
Will recipients without this module receive my attachments?
Yes! Attachments are embedded in the standard UBL XML. Any PEPPOL-compliant system can receive and process them (though they may need their own import functionality based on the PEPPOL specification).
Does this affect regular email invoice sending?
No, this only affects PEPPOL transmissions. Regular email sending in Odoo works as usual with standard attachment handling.
Can I receive multiple attachments within one invoice?
Yes! This module enables Odoo to receive multiple attachments within one invoice based on the PEPPOL specification. The attachments will be retrieved automatically and linked as attachments in Odoo.
Support & Contact
For questions, customization requests, or technical support, please contact us. We'd be happy to help you out.
Email Support:
info@alwinen.de
Developed by Alwinen GmbH
Professional Odoo Solutions
https://www.alwinen.de
Copyright © 2025 Alwinen GmbH | Licensed under Odoo Proprietary License v1.0
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