Implementation

End-to-end Peppol pipeline setup. ERP integration, format mapping, test cycles, and supervised go-live. We hand over a working system, not a slide deck.

Good fit

Who this is for

  • Companies committing to a full e-invoicing rollout in a defined timeline.
  • Finance and IT teams that have scoped the programme and need execution.
  • Scale-ups with one or more ERPs that need Peppol integration across multiple entities or countries.
  • COOs and finance managers who need a predictable delivery timeline with fixed milestones.
Not a fit

Who it isn't for

  • Single-entity businesses on a cloud ERP that already supports Peppol natively.
  • Teams that have not yet scoped the programme (see Readiness Assessment first).
  • Companies looking for a self-service integration guide. Our API documentation covers that.
Deliverables

What you get

01

Programme Plan

Five-phase Gantt-style plan with week markers, milestones, dependencies, and go-live readiness gates. Your single source of truth from kickoff to production.

02

Format mapping

Field-by-field mapping from your ERP output to Peppol BIS 3.0 and applicable country profiles. Covers invoices, credit notes, self-billing, and multi-currency scenarios.

03

Test cycles and validation

Schematron validation against production invoice samples. End-to-end send/receive testing on the Peppol test network. Regression suite for credit notes and edge cases.

04

Peppol participant registration

We handle Peppol participant registration for each entity. Includes endpoint configuration, routing setup, and verification across the live network.

05

Supervised go-live

Production cutover with parallel-run window, monitoring dashboard, runbook handover, and 30-day post-launch support. Zero post-launch reissues is the target.

Anonymised customer profile. Names and figures changed. Company details available on request under NDA.

Case study

Dutch SaaS scale-up, greenfield Peppol rollout

Client profile
Type
SaaS scale-up
Headcount
~80 staff
ERP
NetSuite
Scope
HQ (NL) + DE, BE subsidiaries
Buyer: COO + finance manager|Peppol status: greenfield|Multi-currency: EUR, GBP, USD

The situation

A Dutch SaaS scale-up with approximately 80 staff is growing fast. The company runs NetSuite as its primary ERP and invoices in multiple currencies (EUR, GBP, USD). Headquarters are in the Netherlands, with subsidiaries appearing in Germany and Belgium. There is no legacy e-invoicing infrastructure. The company has never sent or received a Peppol document.

The COO and finance manager share ownership of the initiative. The Belgian e-invoicing mandate applies to the Belgian subsidiary. The Dutch entity needs Peppol for an increasing number of enterprise customers requiring structured invoices. Germany is next in line as XRechnung requirements tighten.

What an Implementation programme would cover for this profile

In an Implementation programme for this profile we would start with a discovery phase to map the NetSuite configuration, run a Peppol Readiness Scan of the customer and supplier base, and document the multi-currency invoice flows. The programme plan would lock five phases across 12 to 16 weeks.

The format mapping phase would build field-by-field mappings from NetSuite output to Peppol BIS 3.0. Credit notes and self-billing scenarios would get dedicated mapping attention. Country profiles for Belgium, the Netherlands, and Germany would be configured individually. Tax breakdown alignment against EN16931 rules (BR-CO-15, BR-S-08) is typically where the detailed work sits.

Integration would cover Peppol participant registration for each entity, API integration via NetSuite SuiteScript, webhook configuration for inbound documents, and multi-entity routing. Test cycles would run schematron validation against production invoice samples before any document touches the live network.

What commonly goes sideways

For a profile like this, the most common risks we would surface and manage during the implementation include:

NetSuite + Peppol mapping

NetSuite's default tax breakdown structure is fragile around credit notes. The mapping between NetSuite tax lines and Peppol BIS 3.0 tax categories requires careful handling to avoid BR-CO-15 violations.

Supplier reachability

Verifying supplier reachability across customers' Peppol IDs takes longer than planned. Each customer's Peppol endpoint must be verified individually, and coverage gaps surface late in the process.

BR-CO-15 violations

Test cycles commonly expose BR-CO-15 violations from NetSuite's default tax breakdown. The tax sum validation rule is strict and NetSuite's rounding behaviour does not always align.

Multi-country timeline

Three countries means three sets of schematron rules, three registration processes, and three sets of test scenarios. Timeline pressure compounds when stakeholders in different countries operate on different cadences.

The go-live

In the go-live phase we would run a parallel production window where both the old and new invoicing paths operate simultaneously. The monitoring dashboard would track delivery status, validation results, and exception rates in real time. The team would receive a runbook covering escalation paths, common failure modes, and resolution procedures. A 30-day post-launch support period starts at cutover.

Indicative outcomes
3–4 months

time-to-mandate-compliance

Cut from 9 months internal estimate to 3–4 months with structured programme delivery.

0 reissues

post-launch in the first month (typical)

Go-live with zero post-launch reissues. Test cycles and the readiness gate catch issues before production.

~50% less

internal IT effort vs. building in-house

Internal IT effort reduced approximately 50% compared to building the Peppol integration pipeline in-house.

Sample deliverable
Sample artefact

Implementation Programme Plan

Client: ████████ BV

16-week programme
5 phases · 4 gates
Week
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Discovery & scoping
Format mapping & design
Integration & build
Test cycles
Go-live & handover
Kickoff
Mapping sign-off
Go-live gate
Production live
Discovery & scoping
Format mapping & design
Integration & build
Test cycles
Go-live & handover
Gate / milestone
Phase 1: Discovery & scopingWk 1–3
  • •ERP landscape mapping (NetSuite config export)
  • •Peppol Readiness Scan of customer + supplier base
  • •Invoice format gap analysis against Peppol BIS 3.0
  • •Multi-currency flow documentation (EUR, GBP, USD)
Phase 2: Format mapping & designWk 3–7
  • •NetSuite → UBL field mapping (██ fields)
  • •Credit note and self-billing mapping
  • •Tax breakdown alignment (BR-CO-15, BR-S-08)
  • •Country profile configuration (BE, NL, DE)
Mapping sign-off
Phase 3: Integration & buildWk 6–11
  • •Peppol participant registration (██████ entity)
  • •API integration with NetSuite SuiteScript
  • •Webhook configuration for inbound documents
  • •Multi-entity routing and ██████ logic
Phase 4: Test cyclesWk 10–14
  • •Schematron validation against production samples
  • •End-to-end send/receive with Peppol test network
  • •Credit note regression suite (██ scenarios)
  • •Supplier reachability verification across ██ Peppol IDs
Go-live readiness gate
Phase 5: Go-live & handoverWk 14–16
  • •Production cutover with parallel-run window
  • •Monitoring dashboard handover
  • •Runbook and escalation path documentation
  • •30-day post-launch support period starts
Dependencies
Discovery & scoping → Format mapping & designFormat mapping & design → Integration & buildIntegration & build → Test cyclesTest cycles → Go-live & handover

Timeline assumes standard data access and stakeholder availability. Redacted fields (██) contain client-specific data available under NDA.

Process

How we run it

1

Discovery and scoping

Week 1–3

Map the ERP landscape, run a Peppol Readiness Scan on the customer and supplier base, document multi-currency flows, and lock the programme plan.

2

Format mapping and design

Week 3–7

Build field-by-field mapping from ERP output to UBL. Cover credit notes, self-billing, and tax breakdown alignment. Sign off the mapping before integration starts.

3

Integration and build

Week 6–11

Peppol participant registration, API integration with the ERP, webhook configuration for inbound documents, and multi-entity routing logic.

4

Test cycles

Week 10–14

Schematron validation against production samples, end-to-end send/receive on the Peppol test network, credit note regression suite, and supplier reachability verification.

5

Go-live and handover

Week 14–16

Production cutover with parallel-run window, monitoring dashboard handover, runbook and escalation documentation, and 30-day post-launch support period.

Investment

Format and pricing

From €35,000

Fixed price with day-rate overflow for out-of-scope work. Final price depends on ERP complexity, country mix, and scope of format mapping work. Day rate for overflow work agreed upfront in the proposal.

Related packages

Often followed by

Automation

Post go-live optimisation. Three-way matching, approval workflows, exception handling, and reconciliation. Turn the pipeline into a true automation lever.

Automation

Often comes with

UBL/XML Validation

Bring invoice output into compliance with Peppol BIS 3.0 and EN16931, including country profiles and schematron edge cases.

UBL/XML Validation
Related reading
FAQ

Frequently asked questions

What ERP systems do you integrate with?
We have delivered implementations on NetSuite, SAP, Exact Online, Odoo, Dynamics 365, and several custom-built ERPs. The integration approach depends on the ERP capabilities. Modern cloud ERPs typically expose REST APIs. Legacy systems may need a middleware layer or file-based integration.
Do we need a Readiness Assessment first?
Not always. If you already have a clear picture of your ERP landscape, entity scope, and format gaps, we can scope the implementation directly. If there is ambiguity around programme scope, a Readiness Assessment saves time and budget by locking scope before execution starts.
What does day-rate overflow mean?
The fixed price covers the agreed scope. If additional work surfaces during the programme that falls outside the original scope, it is billed at a pre-agreed day rate. The day rate is stated in the proposal before you sign. No surprises.
How long does a typical implementation take?
12 to 16 weeks from kickoff to production go-live. Timeline depends on ERP complexity, number of entities, and how quickly stakeholders can provide data access and sign off on mappings. We confirm the schedule during the discovery phase.
Can you handle multi-country rollouts?
Yes. We configure country-specific Peppol profiles (Belgian, Dutch, German, French) and handle the differences in tax reporting, schematron rules, and endpoint registration per jurisdiction. Multi-country is a common pattern in our implementations.
What happens after go-live?
The 30-day post-launch support period covers monitoring, incident response, and any production fixes. After that, many clients continue with an Automation engagement to optimise AP/AR workflows, but there is no obligation.
Discovery call

Discuss on a discovery call

30 minutes with a co-founder or senior e-invoicing expert. You leave the call with a clear next step. Tailored proposal in your inbox within 48 hours.

Vendor-neutral. No obligation to switch platforms.

E-invoicing Implementation | Peppol Rollout Programme | e-invoice.be