# Custom Invoicing Software Development | Tembrant

> Custom invoicing software for online sellers: gapless numbering, credit notes for refunds, exact tax math and structured e-invoices ready for Peppol.

Source: https://tembrant.com/ecommerce-invoicing-software-development
Last updated: 2026-11-21

[E-commerce operations](https://tembrant.com/ecommerce-operations) / Custom invoicing software development for online sellers

# Custom invoicing software development for online sellers

Invoices issued once, numbered without gaps, corrected by credit note, and ready for structured e-invoicing.

[Start a project](https://tembrant.com/contact)

On this page

* [Where the EU rules stand](#where-the-eu-rules-stand)
* [When custom invoicing makes sense](#when-custom-invoicing-makes-sense)
* [How we would build it](#how-we-would-build-it)
* [Proof from our own code](#proof-from-our-own-code)
* [What the first version includes](#what-the-first-version-includes)
* [How the work is run](#how-the-work-is-run)

Invoicing looks solved until you sell in several places. The store app numbers one series, the marketplace issues its own documents, wholesale orders are invoiced from the accounting package, and refunds may or may not get a credit note. When the tax return or an audit needs every invoice in order, nobody can show the series is complete.

EU e-invoicing mandates add a new requirement: for business-to-business sales, a PDF attached to an email no longer counts as an invoice in a growing number of countries.

## Where the EU rules stand

* **Belgium:** structured B2B e-invoices have been mandatory since 1 January 2026, with Peppol BIS Billing 3.0 as the default format and network.
* **Germany:** businesses have had to be able to receive e-invoices since 1 January 2025\. From 1 January 2027, businesses whose turnover in the previous year was above €800,000 must issue them, and from 1 January 2028 all businesses must. The formats in use are XRechnung and ZUGFeRD, both conforming to the European standard EN 16931.
* **France:** from 1 September 2026, every business established in France must be able to receive e-invoices through an authorized platform, and large and mid-sized businesses must issue them. Small and micro businesses must issue them from 1 September 2027.
* **EU-wide:** under the VAT in the Digital Age package, adopted in March 2025, digital reporting based on e-invoices applies to cross-border B2B transactions within the EU from 1 July 2030.
* **United Kingdom:** the government has said VAT invoices must be issued as e-invoices from April 2029, with Peppol as the framework.

None of this needs a new invoicing system on its own. It needs invoices held as structured data, not as PDFs.

## When custom invoicing makes sense

Store-platform invoice apps, accounting packages and e-invoicing services fit many sellers, and the right answer may be one of them. Custom is worth it when:

* You invoice from several channels and need one complete series.
* Your tax treatment varies by channel, country and customer type in ways the apps handle differently.
* You have B2B customers in mandate countries and your current tools only produce PDFs.

## How we would build it

### Invoices as records, not documents

Each invoice is a record: seller and buyer details, lines, tax per line, totals and the order it came from. The PDF is generated from that record. So is the EN 16931 data (UBL or CII XML) that e-invoicing needs. Seller and buyer details are copied onto the invoice when it is issued, so a later change to a customer’s address doesn’t rewrite an invoice already sent.

### Numbering without gaps

Each series has a counter. The number is assigned in the same database transaction that issues the invoice, so two orders issued at the same moment can’t share a number, and a failed issue doesn’t burn one.

### Corrections by credit note

An issued invoice is never edited. Refunds and corrections are credit notes linked to the original invoice, with their own numbers. A partial refund credits only the lines refunded.

### Exact money

Amounts are integers in the smallest currency unit. How tax is rounded, per line or per invoice, is a written rule taken from your tax adviser, tested against real invoices, and applied the same way everywhere.

### Validation before sending

Every structured invoice is checked against the EN 16931 and Peppol BIS Billing 3.0 validation rules before it leaves. A failing invoice is held with the rule it broke, and a person fixes it before it is sent. Sending would go through a certified Peppol access point provider of your choice.

## Proof from our own code

[Lekhavo](https://tembrant.com/products/lekhavo), our bookkeeping product for Indian accounting practices, issues its own tax invoices and exports them for the Indian GST sales return. That code works this way:

* An invoice number is assigned only when payment is confirmed, from a counter that keeps each financial year’s series free of gaps.
* Amounts, buyer and seller are stored as snapshots, so an issued invoice outlives later changes, even deletion of the customer’s account.
* Before export, the series is checked. If a number is missing, the export refuses and names the missing invoice. A number longer than the return’s 16-character limit stops the export too.

In the invoice registers it keeps for clients, an amendment or reversal is a new document linked to the original, and the original is marked amended or reversed rather than rewritten.

## What the first version includes

* Invoices and credit notes from your store, marketplace and wholesale orders, in series you define
* PDF output and EN 16931 structured output, validated before sending
* Integration with one Peppol access point provider
* A series-completeness report and an export to your accounting system
* Source code, a written spec and runbooks

Invoices then need to meet payouts and bank deposits in the books. That is the [accounting integration](https://tembrant.com/ecommerce-accounting-integration) and [reconciliation](https://tembrant.com/reconciliation-software-development) work. If invoices start in Shopify, part of the system can run as a [Shopify app](https://tembrant.com/services/shopify-app-development).

## How the work is run

Tembrant builds with an AI software factory: many agents work in parallel, held to fixed gates. Every change starts from a written spec, tests are written first, each change gets independent reviews, and a person signs off before it ships.

If you sell to businesses in Belgium, Germany or France and still send PDFs, [tell us how you invoice today](https://tembrant.com/contact).

## Questions

Do EU e-invoicing mandates apply to sales to consumers?

Mostly not. Belgium's mandate covers sales between VAT-registered businesses, and Germany's covers domestic business-to-business invoices. France is broader: alongside e-invoicing it requires e-reporting of some transactions that aren't e-invoiced, which can include sales to consumers. If any of your orders are wholesale or to business buyers, those invoices are in scope. Confirm your position with your tax adviser.

Will you connect us to Peppol directly?

Sending on Peppol goes through a certified access point provider. We would build your system to produce valid Peppol BIS Billing 3.0 invoices and integrate with the access point provider you choose. We are not an access point ourselves.

Can it fix an invoice that went out wrong?

Not by editing it. An issued invoice stays as it was issued. A mistake is corrected with a credit note that references the original, then a new invoice if needed, so the record shows what the customer received and how it was put right.

Have you built invoicing for an online store?

Not for an e-commerce client. We built invoicing into our own product, Lekhavo, which issues its own tax invoices and exports them for the Indian GST return. The numbering and series checks on this page come from that code. E-invoicing to EU formats would be new work for your project.

## Related

* [Shopify and Amazon accounting integration: payouts reconciled into Xero or QuickBooks](https://tembrant.com/ecommerce-accounting-integration)
* [Custom reconciliation software development](https://tembrant.com/reconciliation-software-development)
* </services/shopify-app-development>
* [E-commerce operations overview](https://tembrant.com/ecommerce-operations)

## Have financial data that has to tie out?

Tell us what you want to build. We reply with questions, a plan and an estimate.

[Start a project](https://tembrant.com/contact)

![](https://tembrant.com/emblem.webp)
