Peppol has become the main way to send e invoices across Europe, and new rules in Belgium and Germany are speeding up the shift. Belgium will require Peppol for all B2B invoices starting in 2026, and Germany will follow with a full B2B mandate by 2028. Many companies already use Salesforce to manage sales and billing, which creates a clear need for a direct way to send Peppol invoices without manual steps or external uploads.
Salesforce cannot send Peppol invoices on its own. The Peppol network requires specific file formats, strict validation, and delivery through a certified access point. Third party tools fill this gap. Apps like Avalara, JustOn, Certinia, and PDF Butler, along with access point providers and middleware platforms, handle the full Peppol process while Salesforce provides the data.
In this article, we explain how these tools connect to Salesforce, how the integration works in practice, and what companies should prepare before the new EU deadlines take effect.
What is Peppol?
Peppol is a network that allows companies and public bodies to exchange structured e invoices in a secure and unified way. It was created to replace PDF and paper invoices with a standard digital process that follows the EN 16931 rules. A Peppol access point connects a company to the network and handles the delivery of each e-invoice Peppol file.
The system uses a shared Peppol format, including the Peppol BIS Billing 3.0 specification, which defines how invoice data must be structured. Peppol is supported by many tools and service providers, making it easier for companies to achieve Peppol compliance across EU markets.
When companies talk about Peppol e-invoicing, they refer to sending invoices through this network rather than by email. The core idea is simple: one standard format, one delivery channel, and clear rules for connecting.
Why Salesforce uses third-party tools for Peppol integration
Salesforce cannot create or send a Peppol e-invoice on its own because the platform does not support the required Peppol format or the transport rules defined by the Peppol BIS Billing 3.0 specification. A Peppol access point is needed to send and receive files, and only certified providers can operate these services.
Third-party apps act as the link between Salesforce and the Peppol network. They collect invoice data from Salesforce, build a valid UBL file, run all checks needed for Peppol compliance, and send it through an access point Peppol provider. Most tools also return delivery results so teams can track Peppol invoicing status in real time.
Using these Peppol solutions keeps the setup simple. Salesforce handles customer, order, or billing data, while the external Peppol provider manages connecting to Peppol and sending the e-invoice.
How Salesforce connects to Peppol through third-party tools
A Salesforce org creates invoice data, but a certified Peppol access point must deliver it. Third-party tools fill this gap by handling the technical parts of Peppol e invoicing while Salesforce remains the source of customer, order, and billing information. The integration follows a clear flow that keeps the process stable and compliant.
1. Creating invoice data inside Salesforce
Invoice records can come from Salesforce Billing, Revenue Cloud, Certinia, JustOn, or a custom object. Each record must contain the fields required by the Peppol format, including customer identifiers, tax details, payment terms, and line items. Clean data is important because the Peppol BIS Billing 3.0 specification rejects invoices with missing or inconsistent entries.
2. Sending data to a Peppol service provider
Salesforce sends invoice data to the chosen Peppol access point provider through Apex callouts, Flow actions, or middleware. The provider then prepares a UBL file, applies validation rules, and checks that it meets Peppol compliance requirements. Some tools also run country-specific checks, such as VAT rounding rules for Belgium.
3. Converting the invoice into a valid Peppol format
The provider transforms the data into the correct structure for e-invoice Peppol delivery. This includes building XML, applying tax rules, and assigning unique invoice IDs. Many providers offer extra checks to prevent failures during delivery.
4. Connecting to Peppol and sending the invoice
Once the file is ready, the Peppol provider uses its access point Peppol connection to deliver the invoice to the receiver’s access point. Both sides rely on the shared rules of the network, which keeps the delivery flow consistent. This is the core of how does Peppol work in practice.
5. Returning status updates to Salesforce
After sending, the provider sends status updates back to Salesforce. The most common statuses include:
- Sent;
- Delivered;
- Accepted;
- Rejected, with a clear error message
Teams use these updates to track Peppol invoicing, follow up with customers, or fix issues before resending.
6. Storing logs and files in Salesforce
Many companies keep the UBL file, PDF version, and delivery history inside Salesforce for audit needs. This way finance, sales, and support teams get one place to view the full e-invoicing Peppol record.
This structure creates a steady workflow where Salesforce manages the data, and the external Peppol provider manages connecting to Peppol and delivering invoices safely.
Key third-party tools for Peppol Salesforce integration
A stable Peppol integration depends on the tool that takes invoice data from Salesforce and sends it through a certified Peppol access point. Each option below supports e-invoicing Peppol in a different way, depending on how your billing process is built and which Peppol solutions you already use.
1. Avalara
Avalara supports Peppol e invoicing by handling tax logic, UBL formatting, and invoice delivery.
- Tax rules help prepare invoices for markets where local VAT rules apply, including Belgium and Germany.
- UBL generation ensures every e invoice Peppol file meets the Peppol format and follows the Peppol BIS Billing 3.0 specification.
- Peppol sending uses Avalara’s connection to a certified access point Peppol provider, which removes the need for a custom transport layer.
- Status updates back to Salesforce give clear insight into whether an invoice was sent, delivered, accepted, or rejected.
- Avalara works well for companies operating in several EU markets or those that already rely on Avalara for tax automation.
2. JustOn
JustOn is a Salesforce-native billing tool that supports Peppol invoicing from inside the CRM.
- Salesforce-native billing means all invoice data is already structured for Peppol integration and is easy to export.
- XML invoice generation creates the required UBL file for e-invoicing Peppol based on invoice records stored in Salesforce.
- Peppol delivery is handled through a connected Peppol service provider, which manages validation and routing.
- Full invoice history stored on records keeps UBL files, PDFs, logs, and results directly on the invoice record.
- JustOn is useful if you want clean billing, no external databases, and a straightforward way to begin connecting to Peppol.
3. Certinia
Certinia provides finance and billing modules that run on Salesforce, making it easier to prepare data for Peppol compliance.
- Finance and billing modules on Salesforce give structured data for tax, billing, and revenue treatment.
- Smooth mapping for Peppol handoff reduces the risk of failed validation because fields already follow standard finance models.
- Works with external Peppol gateways for UBL generation and delivery through a certified Peppol access point provider.
- Certinia fits teams that want a full financial process inside Salesforce and plan to add Peppol integration through a gateway rather than a built-in tool.
4. PDF Butler
PDF Butler provides a managed package designed for simple, fast Peppol e-invoicing setup.
- Managed package for Peppol handles requirements for Peppol invoicing without extra custom development.
- UBL creation inside Salesforce builds the structured XML file from invoice data stored in the org.
- Option to send both XML and PDF gives customers a human-readable file alongside the e-invoice Peppol file when needed.
- Works with Flow and Apex so teams can send invoices automatically at key billing steps.
- PDF Butler is a good fit for companies that want to keep all invoice creation inside Salesforce and prefer a native approach.
5. Middleware tools used as Peppol connectors
Middleware tools connect Salesforce to an external Peppol provider without adding billing logic inside the CRM. Mulesoft, Boomi, and Workato are the most common options.
- These platforms take invoice data from Salesforce and pass it to a Peppol provider for UBL creation and delivery.
- They support field mapping, custom routing, and integration with ERPs or accounting systems.
- They help when Salesforce is not the only system involved in invoicing, or when several countries use different billing flows.
- Middleware is the right choice when you have a complex system architecture, multiple invoice sources, or need a single route for connecting to people across several business units.
How to choose the right tool or combination for your Peppol integration
Integration steps for a Salesforce project
A Salesforce Peppol integration follows a clear sequence. Each step prepares your invoice data for the Peppol format and connects it to a Peppol access point provider that handles sending and validation.
Step 1: Select the third-party tool
Choose the Peppol provider or app that will manage UBL creation and delivery. Options include Avalara, JustOn, Certinia, PDF Butler, middleware platforms, or a standalone Peppol access point. The choice depends on where the billing data lives and how many countries you support.
Step 2: Prepare invoice data in Salesforce
Invoice records must contain all fields needed for Peppol e-invoicing. Required fields vary by country but usually include buyer identifiers, seller identifiers, VAT details, item lines, and payment terms. Clean data helps prevent failed delivery during Peppol invoicing.
Step 3: Map Salesforce fields to UBL fields
Each tool needs a clear mapping between Salesforce objects and the Peppol BIS Billing 3.0 specification. Mapping covers header fields, tax rules, totals, and line items. Correct mapping ensures full Peppol compliance when generating the e invoice Peppol file.
Step 4: Build the handoff from Salesforce
Salesforce sends invoice data to the Peppol service provider using Apex callouts, Flow actions, middleware, or API events. The provider then creates the UBL XML and prepares the file for e invoicing Peppol delivery.
Step 5: Add validation and error handling
Validation rules catch missing fields, incorrect VAT treatment, or mismatched totals. Clear error messages help teams fix issues quickly. Many companies add alerts, list views, or dashboards to track failed invoices.
Step 6: Connect to Peppol and send the invoice
Once validated, the provider delivers the UBL file through a certified access point Peppol connection. The receiver’s access point collects the file, checks it, and returns the delivery status.
Step 7: Capture status updates in Salesforce
Delivery results appear on the invoice record: sent, delivered, accepted, or rejected. Teams use these updates to follow up with customers, review problems, or resend corrected files.
Step 8: Store files and logs
Many companies save the UBL file, the PDF, and the audit log in Salesforce. This keeps all details of Peppol integration in one place and supports finance, support, and audit teams.
These steps create a steady workflow where Salesforce manages customer and billing data, and the external Peppol provider manages connecting to Peppol and delivering the invoice.
Wrapping up
Peppol e-invoicing is becoming a core requirement across Europe, and the deadlines in Belgium and Germany make early planning important. Preparing now helps avoid last-minute changes, reduces the risk of non-compliant invoices, and gives your team enough time to test the full flow for each market.
Noltic can guide you through the process. Our team has delivered more than 140 Salesforce projects, holds 400+ certifications, and has deep experience with billing, finance, and integrations. We help you select the right tool, set up the mapping, build the handoff from Salesforce, and confirm that your invoices meet all Peppol compliance rules.
.webp)
together