Create an invoice for United States

Where is this invoice for?

Invoice rules are set country by country. Tell us where you are billing and Stampbench asks only for the details that apply there — and produces the right file automatically. You can change it later.

Billing somewhere else? See exactly what Stampbench covers, country by country.

Or start from an example

Realistic data for fictional companies — nothing here belongs to a real business. Every example is a working invoice you can generate and validate straight away.

What Stampbench does for United States

Stampbench implements no US rules and no sales-tax logic. It is structured-invoice infrastructure: it reads and writes the XML formats European customers and their portals expect, checks a document against the European standard, and repairs what is provably wrong. If your invoicing is entirely domestic US, most of that is not yet useful to you — better to hear it now.

Validated against
EN 16931 core
en16931@2017 · 40 rules
Form adapts to
United States
ZIP code, State · routing + account number
Exports
JSON · PDF (print) · XML
Structured document first, printable view second.

Formats available here

Commercial invoiceSupported

An ordinary business invoice: the same structured model, the same exact arithmetic, a printable document and canonical JSON — but no national e-invoicing standard is claimed and no compliance verdict is given, because Stampbench has no ruleset for it. Use this where a plain invoice is what the customer wants.

Not a structured e-invoicing standard. Stampbench will check the totals arithmetic but cannot tell you whether the document satisfies any legal requirement.

EN 16931 (UBL)Supported

UBL 2.1 declaring the plain EN 16931 customization id, validated against the 40 core rules and the full VAT category families. The right choice whenever a customer or their portal asks for an EN 16931-compliant invoice and no national profile applies.

Peppol BIS Billing 3.0Not implemented

The Peppol BIS rules are a further customisation on top of EN 16931, and Stampbench does not implement them. Generated UBL carries the Peppol billing process id (BT-23) because XRechnung requires it, which is not the same thing as being Peppol BIS validated.

No Peppol BIS ruleset and no network transmission. Neither is on this page.

What else Stampbench covers for United States·API documentation·Validate an invoice you already have