How to Choose an E-Invoicing Provider: What Comes First?

In practice the order is short: compliance is the gate, integration picks the winner, the weight you give Peppol depends on your trading partners, and price is compared last. Compliance is not a feature you pay extra for — if a provider doesn’t cover your specific invoice flows, country by country and counterparty by counterparty, there is nothing further to compare. Once two or three providers clear the gate, the difference is what happens between the purchase invoice inbox and your accounting software: capture, purchase order matching, coding and dimensions, the approval chain, exceptions. Peppol support deserves heavy weight when your partners or a government channel require it — in Latvia the Peppol BIS Billing 3.0 format is already tied to the rules, in Estonia it is not. Price only starts to say something once the technical and process scope is identical in every quote.

Start With Your Invoice Flows, Not a Feature Grid

Before you open anyone’s price list, write down how your invoices actually move. One table, one row per flow:

• the legal entity and the country where it is registered;
• whether the flow is sales or purchase;
• counterparty type: public sector, company, private individual;
• the counterparty’s country and the channel they use;
• whether the same invoice data also has to reach the tax authority;
• which accounting system the entry ends up in.

Ten or fifteen rows in, two things usually become obvious. First, only a couple of flows are genuinely tied to regulation — the rest is handwork nobody has automated yet. Second, most of the requirements you’re about to put to a provider concern one specific legal entity in one country. That map is the foundation for everything else in the comparison. Without it you’re scoring feature lists, not your own process.

Is Compliance a Competitive Advantage or Just a Gate?

“Mandate-ready” is almost empty as a sales claim, because it never says which flow, which country, which channel. Check it flow by flow.

Estonia: Does the Obligation Start on a Date or With the Buyer’s Registry Entry?

Estonia works differently from Latvia. Under the amendment to the Accounting Act that took effect on 1 July 2025, an accounting-obligated entity that has registered itself in the Business Register as an e-invoice recipient may require the seller to submit an e-invoice for payment — and the invoice counts as correctly issued if it complies with EN 16931-1, the European semantic data model for e-invoicing, unless the parties have agreed on another suitable standard. So the obligation is triggered by the buyer’s registry entry and their request, not by one general date.

On the basis of these sources, Estonia has no general obligation to issue B2B e-invoices or to report them to the tax authority. If a provider promises “readiness for the Estonian mandate” as of some date, ask for the legal basis. If there isn’t one, you’re reading marketing.

Latvia: Three Dates You Can’t Mix Up

Latvia’s timeline is staged and written into law. According to the overview published by VID, the Latvian tax administration, structured e-invoices have been mandatory since 1 January 2025 in settlements between the state and companies registered in Latvia — the G2G, B2G and G2B segments — and from 1 January 2026 the e-invoice data from those flows must also be reported to VID. Invoices between companies follow later: under the Accounting Act, from 1 January 2028 companies registered in Latvia must issue the documents they submit for payment to each other as e-invoices and report them to VID, with B2B data reporting voluntary from 1 January 2026 until 31 December 2027.

The technical side matters as much as the date. The e-invoice file format is XML, and it must comply with the Latvian national standard and with the Peppol BIS Billing 3.0 specification. VID receives data from the eAddress platform, from service providers and from taxpayers themselves; only an XML file can be uploaded to EDS, the tax authority’s electronic declaration system; and integrations run through the E-Invoice API V2. The deadline is five working days from the day the invoice was sent, once per invoice — set out in Cabinet Regulation No 749 of 9 December 2025, point 14. So ask the provider plainly: which of those three routes carries my invoice data to VID, and what happens if the transmission fails on day four?

ViDA: What Changes in 2030 and 2035?

The European frame is Council Directive (EU) 2025/516, known as ViDA — VAT in the Digital Age — adopted on 11 March 2025. From 14 April 2025 member states may impose mandatory domestic e-invoicing on the conditions the directive sets. That is permission for national steps, not a pan-European B2B obligation. Digital reporting of cross-border B2B transactions based on e-invoices applies from 1 July 2030, and national real-time reporting systems must be aligned with the EU model by 1 January 2035. A provider’s roadmap should know these dates, but today’s decision is made by Estonian and Latvian rules.

Is Peppol a Network or a Compliance Certificate?

Four separate things get mixed up here more often than anything else: the structured invoice format, the Peppol delivery network, the service provider’s access point, and national tax data reporting. OpenPeppol says it itself — Peppol is neither a portal nor a delivery service provider. Documents are sent and received through a Peppol-certified service provider of your choosing, who acts as your access point in the four-corner model, where two service providers sit between sender and receiver. So “we support Peppol” does not automatically mean tax reporting or a local mandate is covered. In Latvia the two simply sit side by side: the format comes from Peppol BIS, the data transfer from VID’s API.

Five questions that separate real capability from a sales deck:

1. Are you a certified access point yourselves, or do you use a partner’s — and whose name is on the contract?
2. In the demo, do we test both sending and receiving, or only sending?
3. How is my Peppol ID registered, and which identifier scheme do you use for our legal entities?
4. Which format versions do you support today, and who tracks country-specific validation rules?
5. What did you do during the last version upgrades?

The last one is the best evidence request, because the answer is checkable. According to OpenPeppol’s list of post-award specifications, Peppol BIS Billing 3.0 was published on 20 May 2026 and became mandatory on 17 August 2026, while PINT BIS Billing EU 1.1.1 was published on 8 June 2026 and became mandatory on 7 September 2026. Ask what the provider did on those dates, who they notified, and whether the customer had to act at all.

Automation Happens Between the Inbox and the ERP

Once the compliance gate is behind you, workflow decides the rest. Run your own real invoices through the demo — including the three that get stuck every month:

1. Capture and validation. A PDF, a scan and a machine-readable e-invoice side by side; what happens when the VAT amount on a line doesn’t match the total in the header.
2. Purchase order and receipt matching. Partial delivery, a price difference, one invoice against several orders.
3. Accounts and dimensions. Are supplier-specific rules, cost centres and projects filled in automatically — and who changes those rules later, you or the provider’s support desk?
4. The approval chain. Amount limits, stand-ins during holidays, approval from a phone, a reason for rejection.
5. Exceptions. Duplicate invoice, unknown supplier, wrong legal entity, an invoice arriving late at month-end.
6. Credit notes. Full and partial credits, and how they link to the original invoice and to an entry already posted.
7. The entry’s trip to the ERP and back. When the posting is created, and how payment status finds its way back to the invoice centre.
8. Audit trail and archive. Who saw and approved what and when, how long data is kept, and in what form you can get it out.

The sales side needs the same scrutiny in reverse: how do you find out that an invoice never arrived? Ask how a validation error is shown, who retries the delivery, how many times, and how that appears on your team’s dashboard. A failed delivery nobody notices costs more in Latvia than elsewhere — the five-working-day clock keeps ticking.

Can You Compare Price Without Identical Scope?

The monthly fee and the per-invoice price are two lines out of twelve. Make every provider calculate a 36-month total cost on the same volume and the same scope, itemised:

• onboarding and configuration;
• integration with the accounting system, including whether it is a ready-made interface or development work at an hourly rate;
• purchase invoice volume and capture;
• sales invoice volume and Peppol traffic;
• reporting to the tax authority, if it isn’t in the package;
• archiving and data export at the end of the contract;
• each additional legal entity and each country;
• users and approvers;
• resending failed or rejected invoices;
• standard and version upgrades;
• support: language, working hours, response time, whether incident resolution is billable;
• your own people’s hours during the first three months.

If one quote comes in a third cheaper, one of those lines is usually sitting on somebody else’s desk — most often your accountant’s.

One Demo Pack, One Decision Matrix

Give every provider the same pack: ten real purchase invoices (one faulty, one credit note, one without a purchase order), five sales invoices (one to the public sector, one to a Latvian partner, one to a foreign Peppol recipient) and an extract from your chart of accounts. Then score them all with the same table.

Criterion	Role in the decision	Weight	Evidence to ask for
Compliance per flow	Gate: pass or drop out	pass / fail	list of countries, formats, channels and dates for each of your flows
Inbox → ERP workflow	Where the saving is made	~40%	demo with your own invoices, integration documentation, reference from a customer on the same ERP
Peppol and the government channel	Depends on partners and country	10–30%	access point status, send and receive test, version management history
Exceptions, errors and support	Decides your month-end	~20%	validation error examples, failed delivery process, response time, support language
Price	Comparable only with scope locked	~15%	36-month total cost on the same volume and scope

The weights are a starting point, and you should move them to fit your situation. Sell a lot to the Latvian public sector or into the Nordics, and Peppol plus the government channel climbs close to integration. Keep all your volume inside Estonia on one ERP, and it drops to the bottom of the range. One thing doesn’t move: compliance isn’t weighted, it either exists or it doesn’t — and price is only looked at once every quote contains the same thing.

Also available in: eesti keeles · latviski

Last reviewed: 16 September 2026