DBNAlliance and AS4: US E-Invoicing Guide for EDI Teams

The DBNAlliance (Digital Business Networks Alliance) is the non-profit that governs the new US B2B e-invoicing exchange network. Modeled on Europe’s Peppol, it uses a four-corner model in which certified access points exchange structured UBL invoices over the AS4 protocol. There is no US B2B e-invoicing mandate today, but voluntary adoption is accelerating ahead of the 2026 and 2027 global deadlines.

In the United States, paper-based invoices and unstructured digital documents, such as emails containing static PDF attachments, have long dominated the corporate financial landscape. Research indicates that while approximately one-third of US invoices are classified as electronic, very few contain true, machine-readable data. The Business Payments Coalition (BPC) estimates that only 25% of the total volume of invoices in the US market contains structured data. This means that the remaining 75% of billing documents require manual downloading, printing, or keying of transaction information into enterprise systems. To eliminate these costly, manual processes and modernize the B2B payments market, the Federal Reserve Bank of Minneapolis and the Business Payments Coalition initiated a highly coordinated modernization effort.

The Business Payments Coalition, representing a voluntary network of over six hundred organizations, launched a comprehensive, countrywide pilot project in 2022 to establish a standardized electronic exchange framework. In total, 73 organizations joined the Business Payments Coalition E-invoice Exchange Market Pilot to design and test the technical delivery network, while another 42 organizations formed the Remittance Delivery Assessment Work Group to evaluate secure transmission methods for remittance data across various payment types. This joint effort led to the formal creation of the Digital Business Networks Alliance (DBNAlliance) in late 2023, establishing the legal and administrative framework to oversee a national B2B exchange network.

What is DBNAlliance?

The DBNAlliance is a centralized, not-for-profit governing organization designed to standardize and secure B2B electronic document exchanges across North America. Rather than acting as a software application or a private document network, it defines the uniform standards, rules, and technical policies that allow different business platforms to communicate seamlessly. Individual companies do not need to obtain direct membership in the alliance to utilize the network; they simply connect to a certified service provider that is an active, enrolled member. This model operates on the “connect once, connect with everyone” principle, meaning that a single connection to an approved access point allows a business to transact with any other registered vendor or buyer on the system without setting up separate point-to-point connections.

Importantly, the framework is designed to support the entire B2B payment lifecycle. Beyond simple e-invoices, the network enables the secure transfer of e-remittance information, credit notes, and associated financial documents. To simplify onboarding, the alliance recently launched its Mass Adoption API, which allows certified service providers to quickly register and connect new business participants.

Why Does It Resemble Peppol?

Conceptually and structurally, the DBNAlliance network is designed to mirror the highly successful Pan-European Public Procurement Online (Peppol) network. Both frameworks employ a decentralized four-corner model that separates the end-users from the complex formatting and transport requirements of the network.

The Four-Corner Model, Step by Step

In this four-corner architecture, the sender (Corner 1) transmits an invoice to their chosen service provider or access point (Corner 2). The sender’s access point then locates the receiver’s access point (Corner 3) through a decentralized registry lookup. Once the document reaches Corner 3, that access point translates the structured file into a format compatible with the receiver’s internal system, allowing the document receiver (Corner 4) to automatically process the transaction.

How an AS4 Transmission Is Built: SML, SMP, and Certificates

To initiate an invoice transmission, the Corner 2 access point queries the central Service Metadata Locator (SML) registry using the recipient’s unique business identifier to locate the corresponding Naming Authority Pointer (NAPTR) domain record. The locator then resolves this query to the specific web address of the Service Metadata Publisher server that manages the recipient’s unique capabilities. Once the sending access point calls this publisher URL, it retrieves the essential technical metadata needed to build a secure AS4 transmission, which includes the recipient’s active endpoint URL, supported document type IDs, and digital encryption certificates. Using this retrieved metadata, the sending access point builds a secure, encrypted AS4 transmission and routes it directly to the receiver’s access point.

X12 over AS2 vs. the DBNAlliance E-Invoicing Model: What are the Differences?

Traditional North American electronic data interchange (EDI) relies heavily on ANSI ASC X12 standards, using transaction sets such as the X12 810 for invoices, the X12 850 for purchase orders, the X12 856 for advance ship notices, and the X12 997 for functional acknowledgments. These transaction sets are typically transmitted over the Applicability Statement 2 (AS2) protocol, which has served as the backbone of logistics and retail integrations since the early 2000s.

However, the legacy AS2 over X12 model requires direct, bilateral connections that are complex to establish and maintain. Each connection represents a stateful link where both trading partners must manually coordinate security certificates, IP addresses, and custom data-mapping scripts. This highly coupled approach is being replaced by the DBNAlliance e-invoicing model, which decouples messaging layers through XML web services, ebMS 3.0, and the AS4 protocol.

By utilizing SOAP messages and the WS-Security standard, AS4 provides a more secure and robust environment. While AS2 forces direct connections through firewalls, AS4 supports asynchronous message pulling. This allows receiving systems that do not have a permanent IP address, or those located behind strict enterprise firewalls, to pull documents securely from their access points on demand.

Furthermore, AS4 handles message ordering and correlation natively using Conversation IDs, which ensures that out-of-order transmissions are managed correctly by the messaging service handler without manual intervention. This positions AS4 as an ideal bridge to transition legacy EDI environments toward modern, cloud-native API architectures.

Is There a US E-Invoicing Mandate?

There is currently no mandatory nationwide B2B e-invoicing mandate in the United States, and there are no immediate plans to implement one. The key driver for e-invoicing mandates globally is the enforcement of tax collection and the mitigation of value-added tax (VAT) fraud. Because the US federal government operates a post-audit tax system without a national VAT, there is very little regulatory incentive to force private businesses into a centralized clearance network.

At the business-to-government (B2G) level, however, structured electronic invoicing has been active for several years. Since the release of Memorandum M-15-19 by the Office of Management and Budget (OMB) in 2015, federal agencies have been directed to process appropriate federal procurement invoices electronically. Federal suppliers must submit their transactions using OMB-approved solutions such as the Department of the Treasury’s Invoice Processing Platform (IPP) or other Federal Shared Service Providers. This mandate is highly fragmented, as it does not enforce a single XML format, resulting in a wide range of accepted methods from manual web-portal inputs to automated EDI connections.

Although a national B2B mandate is not expected in the short term, voluntary adoption is accelerating as US enterprises prepare for global compliance deadlines. In 2026 and 2027, several major international mandates will go live, creating immediate ripple effects for US companies trading across borders.

Even without immediate B2B mandates in North America, the operational benefits of a modernized billing architecture are driving market expectations. Organizations implementing standardized e-invoicing capture significant administrative savings. Studies from the Centre for Economics and Business Research estimate that full adoption of e-invoicing could unlock $116 billion in annual economic gains in the US, saving businesses an average of $15.16 per invoice and reducing processing errors and tax reconciliation delays.

How US EDI Teams Should Prepare for 2026

Rather than waiting for regulatory mandates or pressure from major trading partners, US enterprise integration and EDI teams should take deliberate steps to prepare their technology stacks in 2026.

Execute an ERP Data Structure and Formats Audit

EDI leaders must verify if their ERP systems (such as SAP, Oracle, or Microsoft Dynamics) are equipped to generate, receive, and validate structured XML data, specifically the OASIS UBL 2.3 format used by the DBNAlliance. The audit should confirm that essential fields (such as purchase order references, item descriptions, and tax structures) are stored natively and can be mapped automatically to avoid manual data-reconciliation issues.

Evaluate Certified DBNAlliance Access Points

Organizations should avoid building custom, direct AS4 connectivity internally, as managing distributed SMP/SML directory lookups can introduce heavy operational overhead. Evaluating and onboarding with a certified access point provider allows an enterprise to establish a single, secure gateway to route transactions to any recipient on the federated network.

Implement Outbound Data Pre-Validation Rules

Middleware systems must be configured to validate document structures and content before they leave enterprise boundaries. Standard schema checks should verify that purchase order numbers, line items, mathematical calculations, and mandatory tax identifiers conform to network requirements, thereby minimizing rejections and payment cycle delays.

Deploy a Compliant Seven-Year Archiving Structure

Under US federal tax and accounting rules, businesses must preserve and archive financial transaction records for at least seven years starting from the date of the tax return filing. Enterprise systems must support secure, tamper-evident archiving that preserves the original XML document, visual rendering, electronic signatures, and delivery acknowledgments to ensure audit readiness.

Frequently Asked Questions

What is the DBNAlliance?

The Digital Business Networks Alliance is a not-for-profit body formed in 2023 by participants of the Business Payments Coalition’s E-invoice Exchange Market Pilot, supported by the Federal Reserve. It sets the standards, rules, and policies for the US B2B e-invoicing exchange network. Businesses join by connecting through a certified access point rather than becoming members themselves.

Is e-invoicing mandatory in the United States?

No. There is no nationwide B2B e-invoicing mandate and none is planned, because the US post-audit tax system has no national VAT to enforce. Business-to-government invoicing has been directed toward electronic processing since OMB Memorandum M-15-19 in 2015. Voluntary B2B adoption is accelerating as US firms prepare for 2026 and 2027 mandates abroad.

How is DBNAlliance different from Peppol?

Structurally, very little: both run a four-corner model where access points exchange documents over the AS4 protocol using registry lookups. Peppol grew out of EU public procurement and now anchors European e-invoicing mandates. DBNAlliance is its North American counterpart, built for the US market’s voluntary, business-led adoption rather than tax-authority clearance.

Does the DBNAlliance network replace X12 EDI over AS2?

Not immediately. X12 transaction sets over AS2 remain the backbone of US retail and logistics EDI. The DBNAlliance model removes the bilateral connection burden by decoupling the messaging layer with AS4 and ebMS 3.0. Most EDI teams will run both side by side for years, which is why access-point strategy matters now.

What invoice format does the DBNAlliance network use?

The network exchanges structured XML documents based on OASIS UBL 2.3, transmitted as encrypted AS4 messages between certified access points. Beyond invoices, the framework supports e-remittance data, credit notes, and related financial documents, so ERP teams should confirm UBL field mapping, not just invoice generation.

Your first AS4 request from a trading partner will not come with a grace period. Aayu AS4 Server runs SaaS, container, or on-prem, and SaaS can be live in hours. Book a 30-minute technical demo and leave with your access-point checklist scored against your actual partner list, or start the free 30-day trial and send a live AS4 message this week.

Contact our team today to learn more about scalable and secure AS4 integration platforms.