E-Invoicing in the USA: DBNAlliance, Peppol and Where Things Stand

Much of the world is moving to mandatory e-invoicing, but the United States is taking a different route. There is no federal requirement for businesses to exchange structured invoices, and the US has no VAT, which is the tax that drives most mandates abroad. That does not mean nothing is happening.

A voluntary national exchange network now exists, federal agencies have been moving to electronic invoicing for a decade, and US companies with customers in Europe, the UK or the Gulf already run into mandates that affect how they bill. This guide explains where things stand as of October 2026 and what US finance and IT teams should do about it.

Is E-Invoicing Mandatory in the United States?

No. As of October 2026, no federal law or Internal Revenue Service (IRS) rule requires businesses to send each other e-invoices. The US approach is market-led, and the obligation to e-invoice comes from customers and procurement rules rather than tax law.

The Vertex developer documentation puts it plainly: the United States does not operate a national e-invoicing mandate, and adoption is driven by large buyers, federal procurement platforms and private-sector initiatives. Outside federal procurement, invoices typically move as PDFs, as ANSI X12 810 EDI messages, or as XML.

The reason is structural. In VAT countries, tax authorities use e-invoicing to see each invoice and cut VAT fraud. The US relies on state and local sales taxes collected from the final consumer, so there is no equivalent invoice-level tax control to build. We found no US state with a VAT-style mandate for B2B e-invoicing.

What Is DBNAlliance?

The Digital Business Networks Alliance (DBNAlliance) is the body that governs a voluntary US network for exchanging e-invoices and other business documents. It was set up in 2023 to give the US what Peppol gives Europe: one set of rules so that any business can reach any other through its chosen provider.

According to Federal Reserve Financial Services, participants in the Business Payments Coalition's E-invoice Exchange Market Pilot formed DBNAlliance as the legal entity to oversee the new exchange network. The Business Payments Coalition is a volunteer group working on business-to-business payment efficiency, which collaborated with Federal Reserve Financial Services on the pilot. The Federal Reserve did not create a mandate; it helped convene the work.

Today DBNAlliance describes itself on its website as an open exchange network for B2B documents in the United States, and lists members including Chevron, ConocoPhillips, Microsoft, Halliburton and Weatherford. e-invoice.app reports that the first invoice was exchanged over the network in March 2024.

How Does the DBNAlliance Network Work?

It uses a four-corner model like Peppol. The supplier sends an invoice to its certified service provider, which locates the buyer's provider through network discovery and delivers the document, and the buyer's provider passes it to the buyer's system.

1. Corner 1, supplier: the ERP or billing system produces the invoice.
2. Corner 2, supplier's service provider: converts and validates it, then looks up where the buyer receives documents.
3. Corner 3, buyer's service provider: receives the document over secure AS4 transport.
4. Corner 4, buyer: receives structured data into accounts payable.

Vertex's documentation describes the framework as based on Universal Business Language (UBL 2.3), with AS4 transport and network-based participant discovery, covering B2B and B2G document exchange. There is no fifth corner: no tax authority receives the data. That is the main architectural difference from the UAE's model, explained in our five-corner model guide.

How Do DBNAlliance, Peppol and Gulf Systems Compare?

DBNAlliance and Peppol share a design but differ in governance and legal weight; the UAE and Saudi systems are tax-driven mandates. The table summarises the differences that matter to a US company trading internationally.

For a fuller explanation of Peppol's components, see what is Peppol?

How Do Federal Suppliers Invoice the US Government?

Electronically, through platforms chosen by each agency. The policy basis is an Office of Management and Budget (OMB) memo from 2015, and the best-known civilian platform is Treasury's Invoice Processing Platform.

OMB memorandum M-15-19, dated 17 July 2015, directed agencies to transition to electronic invoicing for appropriate federal procurements by the end of fiscal year 2018. It pushed agencies towards shared service providers rather than building their own systems.

The Invoice Processing Platform (IPP) is run by the Bureau of the Fiscal Service. It is a secure, web-based service that lets agencies publish purchase orders and manage approvals, while vendors submit invoices, track status and see payment details. It is free for agencies and their vendors, and supports direct file exchange with financial systems such as Oracle, SAP and Momentum. Defense contractors typically invoice through the Department of Defense's PIEE/WAWF system instead.

Why Do US Companies Use Peppol?

Because their customers abroad require it. A US company selling to public bodies or businesses in Peppol countries often has to deliver invoices over Peppol, and registering once through a Peppol service provider makes that routine.

Peppol is open to participants anywhere. The pressure is growing as mandates spread: several EU states launched domestic e-invoicing in 2026, the UK will require e-invoices for VAT invoices on B2B and B2G supplies from April 2029 using Peppol (see the UK 2029 mandate), and the UAE and Oman have built their mandates on Peppol. Mandates usually bind locally established or VAT-registered businesses, so a US parent may be outside them while its local subsidiaries are firmly in.

The common case is a US group with a UK, EU or Gulf subsidiary. Each subsidiary follows its own country's rules, and the US head office ends up running several e-invoicing connections from one ERP.

What Must US Companies Selling into the UAE or Saudi Arabia Do?

Work out which legal entity issues the invoice and where it is registered, then follow that country's system. A UAE or Saudi subsidiary is clearly in scope; a US entity invoicing from the US needs specific tax advice.

• UAE: e-invoicing applies to persons conducting business in the UAE for B2B and B2G transactions, regardless of VAT registration, according to KPMG. Businesses with revenue of AED 50 million or more go live on 1 January 2027 and others on 1 July 2027, each through an Accredited Service Provider. See our UAE e-invoicing guide.
• Saudi Arabia: ZATCA's roll-out page applies Phase 1 to all taxpayers except non-residents, and Phase 2 integration is rolled out in waves to notified taxpayer groups. A Saudi entity must issue ZATCA-compliant invoices, with standard B2B invoices cleared by ZATCA. See Saudi ZATCA vs UAE Peppol.
• As a buyer: Gulf suppliers will increasingly send you structured invoices. Ask whether your accounts payable system can receive them, rather than relying on a PDF copy.

What Should US Companies Do Now?

Even without a mandate, a short programme pays off: know your exposure abroad, get your data into a structured format and decide whether to join a network at home.

1. Map entities and invoice flows by country, noting which entities are registered for VAT or established in mandate countries.
2. Make your ERP produce structured invoices (UBL XML) from a canonical invoice model, so new country formats become mappings rather than projects.
3. Choose providers deliberately: a Peppol provider for Europe, the UK and Peppol-based Gulf countries, an Accredited Service Provider for the UAE, ZATCA integration for Saudi Arabia, and optionally a DBNAlliance provider at home.
4. Ask your largest US customers whether they plan to receive invoices through DBNAlliance; early alignment shortens payment cycles.
5. Clean customer and supplier master data, including tax identifiers for foreign trading partners.

If your ERP struggles with any of this, our comparison of custom ERP vs SAP, Odoo or Dynamics covers the trade-offs.

How VEATEX Helps

VEATEX is a Shopify, web and software development agency that also builds Peppol e-invoicing platforms for the GCC, working with clients in the US, UK and the Gulf for over 11 years. We built a Peppol platform for a client that passed OpenPeppol testing and is now on the UAE pre-approved ASP list. For US companies with Gulf or UK operations, we connect ERPs to e-invoicing providers and build the middleware between them. See our e-invoicing services and custom software development.