E-invoicing cost: what the self-hosted access point really costs against a provider
The cost of running your own Peppol access point and SMP against buying the capability from a service provider or an ERP vendor's network depends on four things: how many documents you send and receive, how many countries and invoice formats you must support, how much in-house staff time you can commit, and how long the accreditation and certificate path takes in your situation. No figures in our research cover Oxalis-NG, phoss SMP, accreditation fees or provider per-document pricing, so treat any comparison you read, including ours, as a framework rather than a price. Ask each candidate for a written quote that states its fees for setup, certificates, hosting, support and each document, and confirm current costs directly with the software maintainers and the providers you shortlist.
Split the cost into what is paid once and what recurs. On the self-hosted side, the one-time items are the accreditation work, the initial integration of your ERP with the access point, testing with trading partners and the design of monitoring. The recurring items are infrastructure, certificate renewals, security patching and upgrades, on-call operations, and the staff who keep participant registration and error handling running. On the provider side, the setup fee and per-document or per-participant charges are the main lines, and you should ask whether format changes, new country rules and archiving are included or billed separately. Be explicit about who carries the work when a mandate changes, because that is usually where the largest unplanned cost appears.
Volume is the variable that most often decides the outcome, but it is not the only one. A provider usually wins at low volume or where you need only a few countries, because you avoid running a service that must stay available. Self-hosting becomes more attractive when you already operate the surrounding infrastructure, need data to stay in your own environment, or handle many countries and formats, provided you can staff operations at the required level. Before you decide, confirm the accreditation path and expected lead time with the relevant authority and the software vendors, price your internal staff hours honestly, and model at least two document volumes so you see where the lines cross.
Which cost components apply to in-house, partner and SaaS options
This table compares the main cost components of running Oxalis-NG and phoss SMP yourself, engaging an implementation partner to run them, and buying a Peppol service provider or ERP vendor network. Each cell shows whether the cost is one-time, recurring or variable, and who receives the money. The main takeaway is that self-hosting shifts most spend to internal staff and infrastructure, so volume and internal capacity decide which option is cheaper.
| Cost component | In-house (self-hosted) | Partner-run self-hosted | Service provider or ERP network |
|---|---|---|---|
| Peppol accreditation and certificates | One-time setup, recurring renewal. Paid to the accreditation authority and certificate issuer. Confirm current fees directly with them. | One-time setup, recurring renewal. Paid to the accreditation authority, with the partner billing its own setup work. | Usually included in the provider's fee. Ask whether the provider carries accreditation and certificate renewal risk. |
| Infrastructure (hosting, network, storage) | Recurring. Paid to your cloud or data center provider and internal platform staff. | Recurring. Paid to your cloud provider; partner charges for build and run support. | Usually none for you, or minimal. Hosting is inside the provider's price. |
| Integration with Odoo or ERPNext | One-time build and recurring upkeep. Paid to internal developers or the ERP team. | One-time build by partner, then recurring upkeep under a support agreement. | Connector setup by the provider or ERP vendor, often with recurring fees for maintenance. |
| Software licensing | Open-source Oxalis-NG and phoss SMP carry no license fee. Confirm any commercial add-ons with their maintainers. | Same as in-house, plus partner fees for implementation. | Recurring subscription, often tied to the ERP plan or network membership. |
| Monitoring and operations | Recurring. Paid to internal staff on call and to any monitoring tooling you add. | Recurring. Paid to the partner under a retainer or scoped support plan. | Included in the service fee. Ask about incident response times in writing. |
| Change handling as mandates evolve | Recurring. Internal staff track format and network changes and redeploy. | Recurring. Partner implements changes under a support scope, usually as separate work. | Provider absorbs most format changes, but may pass through extra charges for some updates. |
| Per-document fees | Variable. Mainly internal effort per invoice; network transport is typically free to the sender. | Variable. Partner effort may scale with volume if support is billed by usage. | Variable. Typically charged per document or per tier. Ask for the rate card and overage rules. |
| Support and upgrades | Recurring. Paid to internal staff for patching and version moves. | Recurring. Paid to partner under a retainer for patching, upgrades and testing. | Included in the subscription. Confirm support hours and escalation paths. |
What moves the cost up or down
Most of the cost difference between running your own access point and buying a provider service comes from a handful of drivers. Each one shifts effort, recurring spend or risk, so ask for each to be priced separately in any written scope.
Document volume and per-document fees
A provider usually charges per transaction or per document, so cost grows with every invoice sent or received. A self-hosted access point turns that variable fee into largely fixed infrastructure, monitoring and staff time, which only pays off at higher volumes. Ask each provider for its fee schedule, minimum commitments and how inbound and outbound documents are counted. Model your own monthly volume against both before comparing totals.
Number of countries and mandates
Each country adds its own clearance or reporting network, format rules, identifiers and onboarding steps. A self-hosted setup covering Peppol alone is simpler than one that also needs national portals such as those for Germany, France or Poland. Confirm with each provider which countries are covered directly and which require a separate integration you would build and maintain.
Formats and national variants
Peppol BIS Billing 3.0 is the common baseline, but national extensions, CIUS rules and attachment handling add validation work that differs by partner. Every format you must issue or accept needs its own mapping, test cases and error handling. Ask whether the provider validates against the current rule sets and how it handles changes when a national specification is updated.
ERP version and upgrade cadence
Your ERP determines how much e-invoicing logic you own. Odoo's standard support runs for three years after a major release on Odoo Online, Odoo.sh and on-premise, and Odoo 20.0 standard support is planned until September 2029. Major version upgrades are mandatory every two years on Odoo Online and Odoo.sh, and each upgrade can break a custom connector. Budget for re-testing the access point integration on every ERP upgrade.
Odoo edition and hosting choice
Odoo's pricing page lists Custom as the only plan that can be hosted on Odoo.sh or on-premise, and only Custom includes external API access and custom modules. A connector to your own access point generally needs that API access, so the edition choice sets the integration path before any infrastructure cost appears. Confirm which plan includes the API and hosting you need, and whether upgrades on your chosen hosting require an Enterprise subscription.
Data location, retention and audit needs
Where documents are stored and how long they are kept determine storage size, backup scope and the evidence you must produce on request. Self-hosting keeps data in your own accounts, but it also makes you responsible for retention, encryption and access logs. For example, the SEC's Rule 17a-4(b) requires broker-dealers to keep certain business records for at least three years, and similar tax retention periods apply in many countries. Confirm retention periods with your tax and legal advisers before setting storage terms.
Monitoring and on-call expectations
A live access point must be watched around the clock if trading partners expect same-day delivery of invoices. Self-hosting means you staff alerting, certificate expiry tracking, patching and incident response, and those costs recur every month. Provider contracts usually bundle these functions, but the response times and service levels differ. Ask each option for its uptime commitment, incident escalation path and who is on call outside business hours.
How each option changes the bill at low, medium and high volume
Running your own access point and SMP means you pay for the platform team that operates it, the infrastructure it runs on, the Peppol certificates and accreditation, and the monitoring that keeps it available. Most of that load is fixed. It does not shrink much when volume falls, so the per-document cost is high at low volume and falls as volume grows. The fixed load also includes the work of keeping pace with changes to the network and to the open-source components you depend on.
- Fixed operating load: Hosting, backups, patching, certificate renewal and on-call coverage recur whatever the document count.
- Staffing: Someone must own AS4 connectivity, SMP records and incident response, which is a skill set that is scarce and must be kept current.
- One-time work: Accreditation, integration with your ERP, and testing with trading partners are largely one-time costs, though they are paid again when you change platforms.
- Per-document exposure: Low, mainly compute and storage, so the unit cost is most favorable at high volume.
- Upgrade effort: You carry the cost of moving off frozen components and tracking standard changes yourself.
Before you commit, ask your team to estimate the hours per month for operations and confirm the accreditation steps with the Peppol authority in your country.
A partner runs a self-hosted stack for you, often in your own cloud account or data center, and you pay for the setup plus a recurring service. The partner spreads its operations staff across several clients, so your staffing cost is lower than in-house, but you still pay for infrastructure you control and for the integration work that connects it to your ERP. Pricing is usually a mix of fixed and per-document components, and the split depends on the partner's contract.
- Setup as a one-time cost: Scoping, deployment, ERP connection and partner testing are typically quoted as a fixed project.
- Recurring service fee: Support, monitoring, patching and upgrades are typically a retainer, so the fixed load is shared rather than eliminated.
- Infrastructure: You may pay your cloud provider or data center directly, which makes that cost visible and separate from the service fee.
- Per-document exposure: Depends on the contract. Ask whether volume tiers apply and whether they include inbound documents.
- Exit terms: Confirm who owns the certificates and configuration if you move later, because that affects the cost of switching.
Ask the partner for a written quote that separates one-time, recurring and volume-based charges at your expected volumes.
A Peppol service provider or your ERP vendor's network lets you send and receive through their access point. You pay a subscription, a per-document fee, or both, and the provider carries accreditation, certificates, infrastructure and most of the operations. Your cost is mostly variable, which makes this option cheapest at low volumes and increasingly costly as volume grows. The bill also depends on which countries and document types the provider covers, and on what happens when a mandate changes.
- Low fixed cost: Onboarding and a base subscription are usually the main fixed items, which keeps early costs small.
- Per-document exposure: Charges scale with each invoice, so high-volume senders should model the bill at their actual counts.
- Staffing: Your internal load is mostly integration and exception handling, not network operations.
- Lock-in: Moving later means re-registering participants and re-testing with trading partners, which is a cost to plan for.
- Coverage charges: Some providers price additional countries or formats separately, so check the full price list against your trading partners.
Ask for every charge in writing, including fees for inbound documents, archiving and support, and confirm what the provider's terms say about data location.
Which costs are one-time and which recur every year
The one-time costs of a self-hosted access point come from building the service before the first invoice moves. Scoping comes first: you decide which document flows (outbound sales invoices, inbound supplier invoices, credit notes) run through Peppol, which countries and trading partners are in scope, and whether you act as your own access point or only as a sender through an external one. Accreditation with the Peppol authority is the next block of work, followed by obtaining and installing the Peppol certificates and configuring the AS4 endpoint and SMP entries that Oxalis-NG and phoss SMP expose. The ERP integration is usually the largest one-time line: mapping tax IDs, Peppol participant IDs and BIS Billing 3.0 fields from Odoo or ERPNext, handling validation errors, and building the inbound path. Testing with each trading partner, and designing archiving so that outgoing and incoming invoices are retained in a form your auditors and tax authorities accept, complete the initial bill. Ask any partner to price each of these steps separately so you can see which ones you are paying for once.
The recurring costs are where self-hosting differs most from paying a provider per document. Certificates expire and must be renewed on a fixed schedule, so someone must own the renewal calendar and the rollover procedure. Infrastructure, databases, backups and network paths for the access point run every month whether or not volume is high. Patching and upgrades of the Java runtime, Oxalis-NG, phoss SMP and the ERP connector are continuous, and each change to a Peppol specification or national rule may need a test cycle with trading partners. Monitoring and on-call support for message failures are also permanent. If you are a covered financial institution under the FTC Safeguards Rule, 16 CFR 314.4(d)(2) requires annual penetration testing and vulnerability assessments at least every six months, unless continuous monitoring is in place. Budget that testing for the access point as a recurring line, and confirm with your compliance lead whether the scope of your existing program already covers it.
How to build your own e-invoicing cost estimate
This sequence turns a general question about access points into a comparable, written estimate for self-hosting, a service provider, and an ERP vendor network over the same period and volume.
Define countries, formats and networks
List every country where you issue or receive invoices, the format each one requires (for example, Peppol BIS Billing 3.0 or a national format), and the network or platform each mandate routes through. Assign an owner from finance operations and one from tax to confirm the list. Done means a single table exists that both internal teams have signed off, with no country left as a placeholder. Confirm each mandate's current dates with the relevant tax authority before you rely on them.
Count inbound and outbound documents by month
Pull the last twelve months of sales and purchase invoice volumes from your ERP, split by country, by document type (invoice, credit note) and by trading partner count. Add expected growth and seasonal peaks as separate lines. The output is a monthly volume model that every provider will price against. Flag any document type you expect to send outside Peppol, because that traffic affects the network choice.
Map each cost component to an owner
Build a register with one row per cost component: Peppol accreditation, certificates, infrastructure hosting, integration work in the ERP, monitoring, per-document fees, and support. For each row, name the internal owner or the external vendor that pays and performs it, and mark it one-time or recurring. Done means no row lacks an owner. This register becomes the skeleton for every quote you request.
Request written quotes for accreditation, certificates and fees
Ask each candidate, including your own team's infrastructure and staff time, for a written breakdown. Request accreditation and certificate costs separately from per-document fees, and ask which items recur annually. Ask the ERP vendor whether its network charges apply on top of any access point fee, and whether any AI or add-on credits are billed separately. Done means each quote shows one-time, recurring and variable amounts in its own column.
Add staffing for operations and change handling
Estimate the people needed to run the access point or manage the provider relationship: patching, certificate renewal, monitoring response, partner onboarding, and handling mandate changes that alter formats or validation rules. Record the skills required and whether they exist in-house or must be hired, contracted or retained. Done means each option has a named staffing line, including the effort for change handling, which often drives recurring cost more than hosting does.
Issue one identical scope to every provider
Send every provider, and your internal team, the same written scope: the country and format table, the monthly volume model, the integrations with your ERP, the archiving period you must meet, the monitoring expectations and the support hours you need. Ask each to answer in the same structure. Done means all responses cover the same scope, so differences in price reflect real differences in service rather than in what was assumed.
Model the three options over the same period
Build one spreadsheet that places self-hosted access point, external service provider and ERP vendor network side by side across the same number of months, using the same volume model and staffing assumptions. Show one-time costs separately from recurring ones, and show the break-even volume where each option becomes cheaper. Done means a reviewer can change one input, such as volume or staffing hours, and see every option update.
Questions buyers ask before comparing e-invoicing costs
Is a self-hosted Peppol access point cheaper than a provider at high volume?
It can be, but no list price settles the question, because the answer depends on your document volume, your internal staff time and what your provider charges per document. A self-hosted setup has one-time costs (setup, integration, accreditation work, certificates) and recurring costs (infrastructure, monitoring, patching, staff time, certificate renewals). A provider usually turns most of this into a per-document or subscription fee that rises with volume. Build a break-even model with both sides in it, and confirm accreditation fees, certificate costs and any Peppol authority charges directly with the authority and the software vendors, since they are not covered in this comparison.
How long does it take to set up a self-hosted Peppol access point?
The timeline depends mainly on scope: how many ERP systems connect, which document formats and countries apply, how many trading partners you must test with, how long accreditation and certificate steps take in your case, and how quickly your infrastructure and security teams can approve the environment. No fixed duration applies to every company, so ask for a timeline built from named milestones. DeployOpen works on fixed-scope engagements, and scope, deliverables and timelines are agreed in writing before work starts, so the quote should show each milestone and what each one depends on.
What does running an access point need from our internal team?
Four groups of people are involved. An accountable owner sets priorities and signs off changes. The ERP team maintains master data such as tax IDs and Peppol participant IDs and handles mapping changes. Network and security staff manage firewall rules, certificates and key handling. Finance operations (accounts payable and receivable) works through validation rejections and inbound exceptions. Someone must also cover monitoring alerts and failed transmissions outside business hours. Ask the partner to list these roles in the quote, with the hours each one is expected to spend during setup and during steady operation.
Can a small team run a Peppol access point on its own?
A small team can run one if it has at least two people able to handle operations, and it must cover patching, monitoring, certificate renewal and change handling as mandates evolve. A single administrator becomes a single point of failure, and a missed certificate renewal or failed inbound queue can stop invoices from reaching customers. Many organizations split the work: the partner handles setup, documentation and testing, and the internal team keeps daily operation, with a retainer for ongoing support, upgrades and continuous testing. Decide which parts you will own before you sign.
How do ERP upgrades change the cost of e-invoicing?
ERP upgrades add recurring cost to any e-invoicing setup, because each upgrade can change the connector, the mappings and the test results. Odoo's documentation shows how the timing varies by deployment: standard support covers the first three years after a major release on Odoo Online, Odoo.sh and on-premise, and Odoo 20.0 has standard support planned until September 2029. Major upgrades are mandatory every two years on Odoo Online and Odoo.sh, and on-premise upgrades need an Enterprise subscription, since Community has no access to the upgrade service. Budget for a retest of the e-invoicing flow after every upgrade, and confirm the upgrade path in the Odoo upgrade documentation.
What should a quote for self-hosted e-invoicing include?
A useful quote states its scope in writing, so that two offers can be compared line by line. It should list the ERP systems and versions covered, the countries, formats and networks in scope, the access point and SMP software and versions, who obtains and pays for accreditation and certificates, where the infrastructure runs and how it is sized, and how monitoring, backup and documentation are handled. Ask for the testing plan with trading partners, the change process for mandate updates, the support terms and any retainer, and the assumptions behind volume bands. Exclusions matter as much as inclusions, so ask for them explicitly. DeployOpen does not publish a price list, and a quote follows from the written scope.
How ERP licensing and support terms change the integration cost
The Odoo edition and support path you pick sets a recurring cost floor before any Peppol component is built. Odoo Community is licensed under LGPL-3.0, so the core code is free to run, but the upgrade service, on-premise use and several features sit in the paid Enterprise edition, which requires a subscription. Odoo's pricing page places on-premise hosting, Odoo.sh, multi-company, Odoo Studio, external API access and custom modules in the Custom plan. If your e-invoicing design relies on an API connection from the ERP to an access point, confirm in writing that the edition and plan you buy include external API access, because that single feature changes whether a self-hosted or provider model is practical.
Support windows are a second cost input. Odoo's standard support covers Odoo 20.0 (released September 2026, standard support planned until September 2029), Odoo 19.0 (until September 2028) and Odoo 18.0 (until September 2027). Standard support includes security patches, and those patches stop when the window closes. Paid extended support is limited to Odoo.sh for select versions and to on-premise deployments, and Odoo SaaS versions cannot use it. Odoo SaaS versions also ship every two to three months, and on Odoo Online and Odoo.sh major upgrades are mandatory every two years. Each upgrade can break a connector to an access point, so budget for regression testing of the e-invoicing flow at every version change.
Ask your ERP partner and Odoo or ERPNext contact to confirm four things before you compare quotes: the edition and plan that includes the features your Peppol connector needs, the support end date for the version you will run during the planned go-live, whether extended support is available for that hosting model, and who pays for the upgrade test database and regression cycle. Those answers determine whether a self-hosted access point, which adds its own upgrade and patch cycle, or a provider connection, which shifts that work to a vendor, carries the lower total cost over the contract term.
How DeployOpen scopes a fixed-price e-invoicing implementation
DeployOpen plans, implements, integrates, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For e-invoicing cost decisions, we start with a written scope that compares the self-hosted access point path against a provider path using your own volumes, countries and integrations.
How we scope
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
- The written scope lists which cost components are in and out: accreditation, certificates, hosting, integration, monitoring and per-document fees.
- We confirm current document volumes, trading partners and target countries so the cost comparison reflects your own invoice flows.
How we build
- We deploy Oxalis-NG and phoss SMP in your cloud account, data center or air-gapped network, if the scoped option is self-hosting.
- We connect the access point to your ERP or accounting system and test validation, error handling and archiving paths.
- We set up monitoring and alerting for AS4 transport, capability lookup and certificate expiry before go-live.
How we hand over
- You receive architecture diagrams, configuration records, runbooks and a cost model that maps each component to its owner.
- Test results with trading partners are documented, including the invoice samples and error cases used.
- Ownership of certificates, accreditation contacts, renewal dates and upgrade responsibilities is recorded before handover.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped separately from the build.
- Retainer scope can cover monitoring response, patching and changes as national mandates and Peppol requirements evolve.
- Support terms and response expectations are written into the agreement, so you know what recurring cost you carry.
