Country deep dive
The US approach has been market-led from the start — a payments-efficiency project born out of the Federal Reserve, not a tax authority closing a VAT gap (the US doesn't have a VAT).
Federal agencies are directed to move to electronic invoicing for appropriate procurements by the end of fiscal year 2018, using a federal shared service provider or an approved solution such as the Treasury's Invoice Processing Platform.
The first wave connects around 20 businesses; by May 2022 over 75 international businesses have joined across three rollout waves, testing secure e-invoice delivery between service providers.
The BPC and Federal Reserve formalise the exchange framework's rules and technical specifications, moving from proof-of-concept toward a durable governance structure.
The Digital Business Networks Alliance — the nonprofit formed by pilot participants — takes over governing the exchange framework, covering both the US and Canada.
A genuine operational milestone — proof the network functions in production, not just in pilot testing.
There's no federally mandated format — the DBNAlliance network has its own standard, but plenty of US commerce still runs on decades-old EDI instead.
The framework deliberately mirrors Peppol's technical approach — a genuine advantage if your business already has Peppol experience from EU or Australia/NZ operations.
Don't assume "e-invoicing in the US" means DBNAlliance by default — most large-enterprise structured invoicing today still runs on bilateral EDI arrangements, not the newer network.
This is a genuinely different posture from almost every other country in this tracker — there's no tax authority driving format standardisation here at all.
A US company with meaningful international operations will encounter e-invoicing mandates abroad long before any equivalent exists domestically — plan accordingly rather than treating this as a purely domestic question.
Two genuinely separate channels exist — DBNAlliance for voluntary B2B, and a distinct federal procurement channel for anyone selling to the government.
A sender and receiver each connect once to their own service provider, and the two providers handle exchange across the network — no bilateral setup needed per trading partner, the same core value proposition Peppol offers in Europe.
DBNAlliance defines electronic delivery standards, policies, and guidelines, and helps service providers connect to the framework — but it has no regulatory or tax-collection authority whatsoever.
Don't conflate these — if you sell to a federal agency, you're dealing with IPP or an agency-approved solution, a completely distinct system from the voluntary B2B DBNAlliance network.
The exchange framework supports all major electronic payment methods — it's explicitly designed around payment efficiency, reinforcing that this is a payments-industry initiative rather than a tax-compliance one.
Nothing here is mandatory — but given the direction of travel globally, proactive readiness has real upside even without a regulatory deadline forcing it.
This is the one genuinely existing obligation here — check you're connected via the Treasury's Invoice Processing Platform or your agency's approved alternative.
Look for a member service provider or Access Point if you want to modernise B2B invoice exchange with major trading partners — participation is entirely optional.
If you already exchange structured invoices via bilateral EDI, weigh whether DBNAlliance's open framework could reduce mapping overhead over time versus maintaining point-to-point connections.
If you decide to join DBNAlliance, check whether your existing software can generate UBL-based invoices natively, or whether you'll need an Access Point provider to bridge the gap.
If you trade with the EU, Mexico, Brazil, Saudi Arabia, or any other mandating country, ensure your systems can produce their required formats — this need exists independently of anything happening in the US.
Network effects — not compliance deadlines — are what will actually drive US e-invoicing adoption forward. If a major customer or supplier asks you to connect via DBNAlliance, that's the practical trigger to act.
No penalty framework exists because there's no mandate to enforce — the entire posture here is structurally different from every clearance-model country in this tracker.