Before you switch anything on in production, an e-invoice API integration needs four groups of test cases: valid documents (a plain invoice, a multi-line invoice with several VAT rates, a document-level discount or charge, a rounding edge case, buyer reference versus order reference, a prepayment invoice, full and partial credit notes), deliberately broken documents, routing tests that run all the way to a real verified recipient, and operational tests — wrong credentials, duplicate sends, retries, status polling and a daily reconciliation. Validate against the rule set that is actually in force: Peppol BIS Billing version 3.0.21 is mandatory to use from 17 August 2026. On top of that come the local checks: whether your Estonian buyer is registered in the e-Business Register as an e-invoice recipient, and whether data on Latvian transactions reaches VID — the State Revenue Service — on time.
Key facts
| Fact | Value | Valid from | Source |
|---|---|---|---|
| Peppol BIS Billing 3.0.21 becomes mandatory | Mandatory from 17 August 2026; released 20 May 2026 | 2026-08-17 | docs.peppol.eu |
| Validation artefacts (UBL and CII) | Version 1.3.16, released 10 April 2026 | 2026-04-10 | docs.peppol.eu |
| EAS code list correction and rules made stricter | 14 unusable EAS codes removed; PEPPOL-COMMON-R052 and R053 are now errors, not warnings | 2026-05-20 | docs.peppol.eu |
| Reference number rule on every invoice | An invoice must carry either a buyer reference (BT-10) or an order reference (BT-13) | as of 2026-09 | docs.peppol.eu |
| Estonia: the right to demand an e-invoice | Any accounting entity registered as an e-invoice recipient in the e-Business Register may demand an e-invoice (Accounting Act § 7¹ (7)); roughly 18,000 companies | 2025 | fin.ee |
| Latvia: reporting e-invoice data to VID | From 1 January 2026 for B2G, G2B and G2G transactions involving entities registered in Latvia; data within 5 working days; B2B postponed to 1 January 2028 | 2026-01-01 | vid.gov.lv |
Does a Green Light in the Test Environment Mean You’re Ready?
Teams call an integration finished too early, because one step out of four worked. Those four steps are independent of each other.
Four Steps That Can Fail Separately
First, your ERP or accounting software turns its own data into a document in UBL 2.1 format — Universal Business Language, the XML structure Peppol invoices are written in. Peppol BIS Billing uses the UBL 2.1 Invoice and CreditNote schemas, so a correct XML file is one that validates against the schema, not one that merely looks tidy when you open it. Second, your system hands the document to your service provider’s interface. For Finbite, the publicly documented data exchange address is app.finbite.eu/finance/erp together with a WSDL description, but the exact header fields and credentials always come from your own onboarding instructions.
Third, the provider’s Access Point looks the recipient up in the registry and passes the document to the buyer’s Access Point, which delivers it into the buyer’s software. Fourth, weeks later you can still prove what happened to a specific document.
Why “200 OK” Is Not Delivery
Steps two and three are the ones that get conflated. “The API returned 200” means the request was accepted. It does not mean the document reached the buyer, and it certainly does not mean the buyer’s accountant can use it.
Which Fixtures Belong in the Pack Before You Touch Production?
Fixtures — prepared sample documents — are the heart of the whole exercise. Without them you are testing a random sample of whatever your sales team happened to invoice last week.
The Valid Cases
Valid cases that should be in the pack:
- a plain invoice with one line and one VAT rate;
- a multi-line invoice with at least two different VAT rates and a correct VAT breakdown;
- a document-level discount and a document-level charge, each with a reason;
- a rounding edge case where the sum of the lines and the document total differ by a cent or two;
- two reference variants — one carrying only the buyer reference, the other only the purchase order reference. The specification requires an invoice to carry either a buyer reference (BT-10) or an order reference (BT-13);
- an invoice with an attachment, if attachments are part of your process;
- a prepayment invoice. For Latvia, be precise here: VID explains that a purely informative advance invoice does not have to be issued as an e-invoice and its data does not have to be reported to VID;
- a full and a partial credit note referencing the original invoice, plus a negative invoice. Peppol requires a receiving system to support both correction mechanisms, credit notes as well as negative invoices.
The Deliberately Broken Cases
The broken cases matter just as much. The minimum set: a document missing both the buyer and the order reference; a document with an invalid EAS code — the Electronic Address Scheme code that tells the network what kind of identifier the Peppol ID is built from; a document whose VAT breakdown doesn’t reconcile with its lines; and a document whose CustomizationID — the field declaring which specification version the document follows — contains a version number. That last check was tightened in the 3.0.21 release and it is a fatal error.
Write down, next to each broken fixture, the error code you expect. If expectation and result diverge, your validator is running the wrong version.
Which Version of the Rule Set Should You Validate Against?
Fix Errors in Layer Order
Peppol validation is layered: XML syntax and UBL structure first, then the semantic rules of EN 16931 (the European e-invoicing standard), then Peppol’s own CIUS rules — a narrower national-or-network profile on top of the standard — and finally country-specific rules, triggered by the seller’s country code. Fix errors in that same order. An XSD error means the structure of the document is broken. Codes starting with BR point to a substantive rule in the European standard, typically amount or VAT logic; codes prefixed PEPPOL point to an extra Peppol constraint; codes carrying a country prefix point to a local requirement. Fixing a BR error before you clear the XSD error is wasted time, because the next layer never runs.
What Changed in 3.0.21
The version matters. 3.0.21 was published on 20 May 2026 and uses the UBL and CII validation artefacts in version 1.3.16, released on 10 April 2026. The same release corrected the EAS code list by removing 14 unusable codes, and turned rules PEPPOL-COMMON-R052 and PEPPOL-COMMON-R053 from warnings into errors for all profiles. In practice: identifier fixtures that produced a yellow warning last year can reject the document today. Run the validator locally, run it in your CI pipeline, and pin the artefact version in configuration — not on one developer’s laptop.
Why Testing the XML Alone Isn’t Enough
A formally perfect invoice delivered to the wrong recipient is worse than a rejected one. Test these separately:
Identifiers, Lookup and Profile
- Recipient identifier and scheme. Are you building the Peppol ID from the right registry code or VAT number, with the right EAS scheme code? Add a negative test using one of the removed codes.
- Recipient capability lookup. Before sending, ask the registry whether the addressee accepts that document type at all. If your system skips this, your customer will report the failure for you.
- Profile choice. By default you use profile 01 (Billing). The new optional profile 02, Billing with Response, requires a separate SMP registration. The SMP (Service Metadata Publisher) is the public register that states what a recipient is able to receive. Test that profile only if both sender and receiver are registered for it.
One Real Delivery, End to End
- Delivery to a real recipient. At least one document has to travel end to end into an account you control, or to a cooperative partner who confirms the data opened readably in their own software.
Which Failures Should You Cause Yourself Before a Customer Finds Them?
Production produces errors a test environment never will. Produce them on purpose:
Credentials, Malformed Requests and Transport
- wrong or expired credentials: is the error logged in a way a human understands, and does sending stop rather than retry forever;
- a malformed request (missing mandatory field, broken XML): does your side distinguish “our error” from “the provider’s error”;
- timeout and dropped connection: is a retry safe, and does it have an upper limit.
Duplicates, Statuses and Daily Reconciliation
- duplicate prevention: sending the same invoice number twice must not produce two invoices for the buyer. How a provider handles a repeated request is that provider’s own contractual detail, so ask for it in writing instead of assuming;
- status handling: an intermediate status (“in processing”) is not a final status. Store the provider-side document identifier with every send, or you will have nothing to argue with later;
- daily reconciliation: the count of invoices marked as sent in the ERP against the provider’s log. A difference nobody looks at grows quietly.
Which Accounting Scenarios Expose a Weak Integration?
Before go-live, borrow two hours of your accountant’s time. Test numbering continuity, VAT and totals matching between the ERP and the file actually sent, visibility of the buyer reference on the buyer’s side, the link between a credit note and its original invoice, attachments arriving intact, and the human-readable form. That last one is not cosmetics: the Ministry of Finance stresses that an original document must let any reader understand the substance of the transaction, which is why a PDF often travels alongside the machine-readable e-invoice in practice.
Go Live With a Small, Watched Batch
Freeze the tested mapping and the validator version. Confirm production credentials and recipient data. On day one send a handful of real invoices you personally follow, and in the evening compare the provider’s records with the ERP. Name the person who picks up a rejected document by the next working morning.
The Estonian Line in Your Release Checklist
For Estonian customers, add one query to your release checklist: has the buyer registered as an e-invoice recipient in the e-Business Register? Since 2025, every accounting entity that has done so has the right to demand an e-invoice (Accounting Act § 7¹ (7)). The same source states plainly that Estonia follows format freedom: both the Estonian and the European standard are allowed. So don’t hard-code the assumption that Peppol is the only valid output.
The Latvian Calendar and the Five-Working-Day Window
For Latvian customers the calendar is different. Invoices from companies registered in Latvia to public sector recipients must be structured e-invoices since 1 January 2025, and from 1 January 2026 the e-invoice data for B2G, G2B and G2G transactions must also be reported to VID, within five working days of sending the invoice at the latest. A foreign company currently has no such VID reporting obligation. Mandatory structured invoicing and data reporting for B2B was postponed to 1 January 2028, rather than starting in 2026 as originally planned. A practical test case: send an invoice, store the send timestamp, and check that your system can show which Latvian invoices have been reported to VID and which are still open inside the five-working-day window.
Also available in: eesti keeles · latviski
Last reviewed:
Does an API response code 200 confirm that the e-invoice has successfully reached the buyer?
No, an API status code 200 only confirms that the service provider accepted the request. It does not guarantee that the file passed Peppol validation, reached the recipient’s Access Point, or opened correctly in the buyer’s accounting software.
Which version of the Peppol rule set should serve as the basis when testing an e-invoice API?
Validation should be based on the Peppol BIS Billing 3.0.21 rules together with validation artefacts 1.3.16, which become mandatory from 17 August 2026. In this version, the identifier rules PEPPOL-COMMON-R052 and R053, which previously functioned only as warnings, have been turned into errors.
Which broken cases must definitely be tested in an e-invoice API?
The test pack must include files with missing buyer and order references, outdated EAS codes, and faulty VAT breakdowns. In addition, you should simulate network timeouts, invalid authentication credentials, and duplicate sends using the same invoice number, to check how the system recovers.