Odoo e-invoicing in United States
The United States e-invoicing picture in full: the scheme, the authority behind it, who it binds, and every requirement we map before a build is quoted.
No national scheme. DBNAlliance Exchange Framework (voluntary industry network) plus the Invoice Processing Platform (IPP) for federal procurement.
Authority: None at federal level for B2B. The DBNAlliance governs the voluntary exchange network. The US Department of the Treasury runs IPP, under OMB Memorandum M-15-19 issued 17 July 2015.
There is no US federal or nationwide B2B e-invoicing mandate as of 22 August 2026, and no VAT to drive one. The only compulsory piece is federal procurement: OMB M-15-19 directed agencies to move to electronic invoicing by the end of FY 2018, and many now require vendors to bill through Treasury's IPP.
No US business is obliged to e-invoice its private-sector customers. Suppliers selling to federal agencies must submit invoices through whatever electronic solution the agency adopted, commonly Treasury's IPP. DBNAlliance participation is by voluntary membership; current members include Microsoft, Chevron and Halliburton.
Every requirement, in full
5 requirements. Each one has to end up as a field, a document layout, a stored response, or an API call in your Odoo build. This is the list an e-invoicing project in United States gets costed against.
- 1 Nothing for domestic B2B. Adoption is market-driven, not government-mandated, because the US has no VAT and no transaction-level tax reporting requirement.
- 2 OMB M-15-19 directed agencies, by the end of FY 2018, to transition to electronic invoicing for appropriate federal procurements by one of three routes: migrating to a designated Federal Shared Service Provider and adopting its e-invoicing solution, using an OMB-approved e-invoicing solution, or ceasing investment in new e-invoicing solutions.
- 3 The same memo defines electronic invoicing as payment requests managed as structured data elements exchanged through electronic workflow, with minimal manual interaction, and directs solution providers to integrate with the Integrated Award Environment including SAM, and to expose web services or APIs.
- 4 In practice, a federal vendor keys or uploads invoices into IPP and matches on its SAM registration. There is no Odoo connector for this, so it is a parallel manual step.
- 5 DBNAlliance runs a Peppol-style four-corner exchange network for B2B e-invoices and e-documents. Joining is an onboarding process, and it recently launched a mass adoption API. Treat it as a customer-driven requirement (a large buyer asks for it) rather than a legal one.
Checked Localization notes on this page checked on 22 August 2026.
Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.
How we build e-invoicing for United States
The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.
- 1 Requirements first, code second. Each line above becomes a field, a report, or an API call on a written mapping sheet. Anything with no home in Odoo is quoted as a build before the project starts.
- 2 Numbering is settled on day one. Invoice sequences are the part that breaks quietly and costs the most to unwind after go-live, so they are signed off before the first test document.
- 3 Submission runs from a queue. Retries, idempotency keys, stored responses and an audit trail. A failed send becomes a ticket with evidence, not a missing invoice you find at month end.
- 4 Your finance team signs it off. Real documents, in a test database, checked with your accountant or tax advisor before cutover, with a rollback plan in writing.
What we need from you to quote it
Bring these to the first call and you get a scoped, priced e-invoicing plan for United States instead of a range.
- โ Your tax registration details and the entity each one belongs to.
- โ A sample of every document type you issue: invoice, credit note, debit note, self-billing if you use it.
- โ Any registration, certificate or portal credential the authority has already issued you.
Services behind this work
The rest of the United States localization detail
Each topic has its own page with the full item list, the same way this one does.
Full detail, printed as checked.
Payroll in United StatesFull detail, printed as checked.
Payments in United StatesFull detail, printed as checked.
Shipping in United StatesFull detail, printed as checked.
United States country overviewServices, modules, client work and delivery for United States.
E-invoicing in other markets we cover
Running the same rollout across borders? These pages carry the same depth for each market, so you can compare before scoping a multi-country phase.
Scope e-invoicing for your United States rollout.
Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.