Bulk Invoice Generator

The same amount, five different invoices

Take nine hundred euro of consulting work. If the client is in your own country you charge your own rate and the invoice is unremarkable. If the client is a VAT registered business one country over, you charge nothing and the invoice has to say why, citing Article 196, with the client's number on it as the evidence that the rule applies. If that same client never sent you their number, the reverse charge does not apply at all and you should be charging VAT. If they are a private person rather than a business, you charge your own rate again. And if they are outside the European Union entirely, the supply falls outside the scope and the invoice says so differently.

Five invoices, one amount, and the difference between them is not the arithmetic. It is a sentence at the bottom of the page and a tax category in the file underneath.

Which is why a single tax box on a form is the wrong shape for this job.

Most free generators give you one. You set it once and it applies to the whole invoice, and to the next one, and to the thirty after that. The moment your client list crosses a border the box is wrong for some of them and there is nothing on the page to tell you which. Here the treatment is worked out per invoice from what the row actually says, and the reason is printed next to the result in words you can check.

What is claimed, and what is not. The page applies the general rules for cross-border services and goods, the United Kingdom construction reverse charge, and the Indian place of supply split. Property, events, passenger transport, margin schemes, second hand goods and digital services sold to consumers all have their own rules that this page does not try to apply, and it says which rule it used on every invoice so you can see when none of them is the one you need.

The United Kingdom one that everyone gets half right

The domestic reverse charge for construction has applied since March 2021, and the invoice it produces is not a normal invoice with the VAT line deleted. The VAT still has to appear. You show the rate, and the amount the customer will have to account for, and then you leave that amount out of what you are asking to be paid.

Every free generator that handles the reverse charge at all handles the European one, which works the other way: the VAT is simply absent. Apply that shape to a construction invoice and you have left out something the regulations ask for. This page keeps them apart. A United Kingdom construction invoice carries the section 55A wording, the rate, and the amount in figures, with a line saying it is not in the total, and the total agrees.

There is a second trap in the same rule. The reverse charge stops applying when the customer is an end user, but only if they have told you so in writing. Silence is not a declaration. So the default here is that the reverse charge applies, and charging VAT instead is something you turn on for a customer who has actually sent you the declaration, rather than something that happens because nobody filled in a field.

India, where one rate becomes two columns

An Indian invoice does not carry a single tax figure. The same eighteen percent splits into nine percent of central tax and nine percent of state tax when the supply stays inside one state, and becomes eighteen percent of integrated tax when it crosses into another. Which of those applies is decided by the place of supply, and the place of supply is usually readable from the first two digits of the customer's own GSTIN.

So this page reads it from there, splits the tax into the right heads, and puts the place of supply on the invoice with the state named, which Rule 46 asks for. When the split is an odd number of paise the halves are not both rounded, because two rounded halves do not add back to the whole. One half takes the extra unit and the two columns sum to the figure in the total.

The GSTIN itself is checked rather than accepted. Its last character is a check character over the first fourteen, computed with Luhn in base thirty six, and a single mistyped digit fails it. The state code is checked against the published list, and the fixed Z in the fourteenth position is required, because a number that passes the eye and fails the portal is worse than one that fails both.

The invoice number, which nothing else checks

Article 226 asks for a sequential number that identifies the invoice on its own. Rule 46 asks for a consecutive serial number of no more than sixteen characters, unique within the financial year. Both are short sentences and both are broken constantly, because a number is checked by the person typing it and by nothing else in the chain.

A batch is where the breakage becomes visible. Two invoices carrying the same number is the serious one, and it happens whenever two systems both think they are allocating the next one. A number missing from the middle of a series is not automatically wrong, because that invoice may exist somewhere else, but it is always worth knowing about. And the quiet one is padding: INV-7 and INV-0007 read as the same number to a person and as two different numbers to anything that sorts them.

All three are reported across the whole batch, with the positions, before anything is downloaded.

Where the cent goes, and why there are two answers

Add the tax on each line and then total it, and you get one number. Total the lines first and work the tax out once, and you sometimes get a different number. Neither is a mistake. They are two methods and they disagree by a cent or two on invoices with several lines, which is exactly the kind of difference that a client's accounts payable system rejects an invoice over.

The European standard checks the second method: it compares each VAT category's tax amount against that category's taxable amount times the rate. So that is the method this page uses. It also works the first one out, and where the two differ it says so, with the amount, instead of quietly picking one and leaving you to discover the difference in a reconciliation.

Underneath, no amount is ever held as a decimal fraction. Every figure is an integer count of the currency's smallest unit, which is why a hundred lines of ten cents come to exactly ten euro here and not to nine ninety nine with a tail of nines. The yen, which has no smaller unit, and the dinar, which has three places rather than two, are both read and written at their own precision.

An e-invoice, and a second opinion about it

Belgium has required structured business to business e-invoicing since January 2026. Poland's system took in its largest taxpayers in February and everybody else in April. France's mandate landed on the first of September, and from that date every business there has to be able to receive one. All of them are built on the same European semantic standard, and the document underneath is either UBL or its cross industry equivalent.

So every invoice here comes with that document. What makes it worth having is the second half: the file is then read back and checked against the standard's own business rules, the ones that compare the lines to the totals and insist that a category charging no VAT gives the reason it is not charging any.

Why the checker is a separate thing. It would be easy, and useless, to check the invoice against the same code that built it. Both halves would agree, including about a mistake. So the checker shares nothing with the builder: it reads only the finished XML as text, it works the amounts out with its own arithmetic, and the rules in it were written from the published rule list rather than from the code that writes the file. When a deliberate fault is put into the builder, the checker is what notices.

Checking a tax number without asking anybody

A VAT number is not a random string. Most countries build a check digit into it, so a transposed pair or a mistyped digit can be caught by arithmetic alone, with no network call and nothing leaving the page. Eight schemes here are checked that way: the United Kingdom in both of its series, Ireland, Germany, France, Belgium, Italy, the Netherlands in both its old and its post-2020 form, and the Indian GSTIN.

The rest are checked for shape, and the page says that is what it did. Several countries publish no check digit algorithm at all, and a tool that reports all twenty seven member states as validated is reporting a regular expression as arithmetic. The difference matters most on a reverse charge, where the customer's number is the evidence that you were right not to charge VAT.

What none of this proves is that the number belongs to a registered business today. That needs a call to the European Commission's VIES service or to HMRC, which is a different kind of check and a different kind of page. This one tells you the number is arithmetically sound and leaves the registry question where it belongs.

What has actually been tested

Every figure here is a test run that has to pass before anything reaches this page. If one fails, nothing ships. A number on a page that nothing checks goes stale, so a test reads this page, pulls out every figure in it, and compares each one with the code behind it.

• 95Exact money arithmetic, every separator a spreadsheet writes, and eight tax number schemes against their own check digits money
• 70Every numeral system, every date shape, every timezone, and the invoice in each language it offers world
• 46The treatment of every kind of supply across every kind of border, each against the rule it cites treatment
• 39Every file that ships, scanned for generated copy, inline styles, off-origin loads and broken asset paths ship
• 35Whole awkward spreadsheets read and counted back out, amount for amount files
• 31The e-invoice checked against the European standard's own rules, including on invoices broken on purpose standard
• 28Every feature against every other feature, and the sizes pushed until the machine is the limit limits
• 23Numbering across a batch: duplicates, gaps, padding and the sixteen character limit numbering
• 22Layout at seven screen sizes, with the browser text enlarged, and the contrast of every line visual
• 15Every number printed on this page, checked against the code behind it figures
• 14The live page in a real browser, under the security policy it ships with e2e
• 12Every control clicked in a real browser, to prove none of them is decoration ui
• 10Every icon and image is the real brand asset, and the link preview belongs to this tool brand
• 8The writing itself: sentence rhythm, repeated openers, and the templates that give generated prose away humanise

Properties you can hold it to

• It says which rule it usedEvery invoice carries the reason for its treatment in a sentence, with the article or section it comes from, so a disagreement is one line to settle rather than a figure to reverse engineer.
• It names the difference instead of smoothing itWhere two rounding methods give two answers, both are worked out and the gap is stated. Where a number has two readings, it says so rather than choosing.
• It separates arithmetic from registrationA tax number that passes here is arithmetically sound. Whether it belongs to a registered business is a question for VIES or HMRC, and the page says which of the two it answered.
• It keeps the limit out of the totalOn a United Kingdom construction invoice the VAT appears in figures and stays out of the amount due, which is what the regulations ask and what the shape borrowed from the European rule gets wrong.
• It holds nothingNo account, no history, no storage. Close the tab and the client list you dropped in is gone from it, which is the right property for a file that lists everyone you bill and what you charge them.
• It states what it checked and what it did notEight tax number schemes are checked by their own published check digit and the rest by shape, and each result says which of the two it was. Nothing here is reported as verified that was not.
• It leaves your other columns aloneProject codes, internal references and anything else are read past, not used, not altered, and handed back beside the result.
• It works offlineEverything happens in this tab. Pull the connection out after the page has loaded and it carries on, which a test does on every run.

Questions people ask first