If you sell to a big-box retailer, a distributor, or a large corporate customer, you've probably already lived through this: you email a clean, professional PDF invoice, and it bounces back. Not because the numbers are wrong, but because your customer's system can't read a PDF at all. It needs a structured, machine-readable document — and if you can't produce one, you don't get paid on schedule, or you don't get to keep the account.
This isn't a hypothetical for 2026. It's the daily reality for tens of thousands of small suppliers who sell into Walmart, into large distributors, or into any enterprise buyer that has standardized its accounts payable around electronic data interchange (EDI). And a newer, cheaper alternative — a nonprofit-run network called the DBNAlliance — is quietly changing what small businesses have to spend to comply.
Here's what's actually happening, why it matters for your bottom line, and what to do about it before your next big customer hands you a compliance deadline instead of a purchase order.
The Old Way: EDI, and Why It's Expensive for Small Sellers
Large retailers didn't wait for a government mandate to demand electronic invoices — they built their own requirements decades ago, and they enforce them strictly. Walmart is the clearest example: every supplier is expected to be EDI-capable, with no manual fallback for ongoing business. A Walmart supplier routinely has to handle:
- EDI 850 — the purchase order Walmart sends you
- EDI 855 — your acknowledgment of that order
- EDI 856 — the advance ship notice, due within a tight window after you ship
- EDI 810 — the actual invoice, typically required within 24 hours of shipment
- EDI 997 — the functional acknowledgment confirming the exchange went through
Suppliers processing more than roughly 5,500 transactions a year are pushed onto the AS2 communication protocol; smaller suppliers get a browser-based portal instead, but the underlying format requirements don't relax. Miss a deadline or send a malformed 810, and the penalty isn't a warning — it's a delayed payment or an outright chargeback.
The problem for a small business is cost. Traditional EDI setup — software, mapping, a value-added network subscription, integration with your accounting system — commonly runs $10,000 to $100,000+ to get started, plus $1 to $5 per transaction afterward. For a supplier doing a few hundred invoices a month, that per-transaction fee alone can erase a meaningful slice of margin, and the upfront cost is often more than the account is worth in year one.
That math is exactly why a lot of small suppliers have historically avoided big retail and enterprise accounts altogether — not because they couldn't win the business, but because they couldn't afford to invoice for it.
Enter DBNAlliance: A Cheaper On-Ramp
In January 2024, a nonprofit called the Digital Business Networks Alliance (DBNAlliance) launched to operate a U.S. electronic invoice exchange network, grown out of the Federal Reserve-backed Business Payments Coalition. Its founding board included names like Chevron, Microsoft, Halliburton, SAP, and Avalara — companies with obvious reasons to want cheaper, standardized B2B invoicing across the country.
The technical model is the same "four-corner" architecture used by Europe's Peppol network: your business connects to a certified access point provider, your customer connects to their own (or the same) access point, and structured invoices — in the UBL 2.x format, over AS2/AS4 protocols — move between the two automatically. Neither side has to build a direct integration with the other; you each just need one connection to the network, and it can reach every other participant. The tagline the network uses is "connect once, connect to all."
The economics are the part that matters most for a small seller: transacting through a DBNAlliance access point typically costs $0.05 to $0.25 per transaction — a 90%+ reduction versus traditional EDI per-invoice fees — and several providers, including Avalara, now offer free U.S. domestic e-invoicing through their certified access point with no transaction cost at all, provided you're connecting through a supported accounting or ERP system.
The savings compound past the transaction fee. Industry data on e-invoicing consistently shows:
- Roughly $15.16 saved per invoice received and $8.93 per invoice sent, versus paper or PDF handling
- Payment arriving 1.4 to 2 days faster on average
- A 27% reduction in tax-related penalties and 30% less invoice fraud among businesses using structured e-invoicing
- Paper and PDF invoices are nearly twice as likely to be paid late as structured e-invoices
For a supplier running on thin retail margins, "paid two days faster and half as likely to be late" isn't a nice-to-have — it's working capital you get to keep.
Is Amazon Requiring This Too?
Amazon Business publishes guidance encouraging its own enterprise buying customers to modernize accounts-payable with e-invoicing, and large enterprise buyers broadly — Amazon included — are moving in that direction as a matter of AP efficiency. That's a different thing from Amazon Business itself issuing a blanket mandate that every third-party seller must submit structured e-invoices today. The accurate takeaway for a small seller is: large buyers, across retail and distribution, are converging on structured electronic invoicing as the default expectation, whether that arrives as a hard EDI mandate (as with Walmart) or a strong preference that increasingly becomes a condition of doing business. Either way, the direction of travel is the same, and it's not reversing.
What Small B2B Sellers Should Actually Do
You don't need to solve this the week a big customer's compliance team emails you. A little preparation now avoids a scramble later.
- Check what your specific customer requires. Walmart's published supplier requirements are public and specific. Other large buyers post similar EDI or e-invoicing specs on their supplier portals — read the actual document before assuming your PDF process will pass.
- Ask your accounting software or ERP whether it has a certified DBNAlliance access point. If you're already on a supported platform, you may be able to turn on e-invoicing at little or no additional cost rather than buying a separate EDI package.
- Don't over-invest in legacy EDI if you don't have to. If a customer doesn't specifically require AS2/EDI 810 (a Walmart-style mandate), a DBNAlliance-connected access point can satisfy "structured electronic invoice" requirements at a fraction of the cost.
- Pilot with one account before rolling out everywhere. Test the format, the acknowledgment cycle, and the payment timing with a single customer before assuming it'll behave identically for every buyer.
- Plan for multiple formats. Bigger sellers end up supporting UBL, EDI, and PDF simultaneously for different customers for years. Choose a workflow flexible enough to not force a rebuild every time you land a new enterprise account.
Why Your Books Need to Keep Up Too
Structured e-invoicing changes more than how the document leaves your business — it changes how fast and how precisely the payment comes back in. When remittances start arriving two days sooner and through a different channel than before, sloppy bookkeeping turns into reconciliation headaches fast: payments that don't obviously match an invoice number, partial payments against a batch of electronic invoices, or a customer's access point taking short pay for a disputed line item you never flagged in your own records.
This is exactly the kind of moment where clear, auditable financial records earn their keep. If every invoice, payment, and adjustment is tracked in a system you can query and reconcile line by line, matching an incoming ACH deposit to the right EDI 810 (or DBNAlliance transaction) takes minutes instead of a Friday-afternoon guessing game.
Keep Your Books Ready for Whatever Format Your Customer Demands
As big buyers standardize around electronic invoicing, the businesses that adapt fastest are the ones whose underlying records were already in order. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in, and records you can reconcile against any invoice format a customer throws at you. Get started for free and see why developers and finance-minded business owners are switching to plain-text accounting.