The US is one of the last major economies without federal e-invoicing. But state-level sales tax economic nexus, the Business Payments Coalition pilot, and DATEV/Peppol rollouts are pushing US SMBs toward structured electronic invoices — whether they're ready or not.
The US Is Behind — and That Window Is Closing
Ask a bookkeeper in Mexico, Brazil, Italy, or the Dominican Republic how they invoice: every invoice goes through a government portal that returns a signed electronic receipt (CFDI, NF-e, SDI, e-CF). The portal validates tax IDs, line-level tax math, and sequence numbers before the invoice is legally valid.
Ask a US bookkeeper: they send a PDF. Maybe from QuickBooks. Maybe from a template in Word.
This gap is not permanent. Three forces are closing it:
- State sales tax economic nexus post-Wayfair (2018) — if you ship more than $100K or 200 transactions into a state, you owe sales tax filing and remittance there. Structured invoice data is the only practical way to track this.
- Business Payments Coalition (BPC) e-invoice exchange pilot — a 2022–2023 pilot run with the Federal Reserve and major corporates tested a US e-invoicing exchange based on the Peppol framework used across the EU and Asia-Pacific.
- Buyer requirements — large enterprises (Walmart, Amazon Business, Federal contractors under WAWF) already require structured e-invoices from their suppliers. SMB vendors adapt or lose the account.
This article lays out what US small businesses should be doing now, in the absence of a federal mandate, so they're not scrambling when one arrives.
What "Structured" Means and Why It Matters
A PDF invoice is a picture of numbers. A structured e-invoice is the numbers themselves, in a machine-readable format — XML or JSON — that a buyer's system can import, validate, and pay without re-keying.
The two formats shaping the US conversation:
- UBL 2.1 / Peppol BIS 3.0 — the format used across 40+ countries, now in the BPC pilot
- EDI 810 — legacy format used by large US retailers and 3PLs (Walmart, Target, Whole Foods)
Why it matters for the sender (you):
- Faster payment: buyers that ingest structured invoices approve faster (often same-day) because line items pre-match their PO system.
- Fewer disputes: the tax math, rounding, and line-level detail are validated by the format — not by a human reading a PDF.
- Audit trail: every invoice has a canonical digital record, not a file in someone's email.
Why it matters for tax compliance:
- Sales tax accuracy: structured invoices carry the ship-to ZIP, the tax rate applied, the exemption certificate reference, and the taxable vs. non-taxable split. This is exactly what a state revenue department asks for on audit.
- 1099 reconciliation: structured invoices from your vendors feed 1099-NEC tracking directly — no year-end data entry.
- Nexus evidence: when a state comes calling about economic nexus, structured invoice data proves (or disproves) the threshold-crossing date.
The Wayfair Problem: You're Already in Multi-State Invoice Hell
The 2018 Supreme Court decision in South Dakota v. Wayfair ended the physical-presence test for sales tax. As of 2025, 45 states plus DC enforce economic nexus — typically at $100,000 in sales or 200 transactions per year into the state (thresholds vary).
If your business sells across state lines, you are almost certainly required to:
- Register for sales tax in every state where you cross the threshold
- File a state sales tax return in each of those states (monthly, quarterly, or annually depending on volume)
- Remit the collected tax on the filing schedule
- Maintain exemption certificates for B2B customers who claim exempt status
A typical e-commerce SMB with $2M in revenue is filing sales tax returns in 15–25 states. Managing this with PDF invoices and a spreadsheet is the current baseline for most SMBs — and it's unsustainable past a certain size.
Structured invoice data — even without a federal mandate — is how you scale sales tax compliance.
Three Triggers That Should Force the Change
Trigger 1: Your First Major B2B Customer
The moment you onboard a customer that requires EDI 810, UBL, or an AP automation platform (Coupa, Ariba, SAP Concur), you need structured invoice capability. Refusing to integrate loses the account.
Trigger 2: A State Audit Notice
When a state revenue department sends a notice asking for your sales detail — by ship-to, by tax rate, by transaction — you'll want structured data. Assembling it from PDFs and memory is weeks of work.
Trigger 3: The Business Payments Coalition Pilot Goes Live
The BPC/FPC pilot wasn't a one-off. It's a blueprint for how the US could roll out a federal e-invoice exchange. When that happens (most likely via voluntary adoption before any mandate), the businesses already on structured invoicing are ready on day one.
What to Do Now (Before a Mandate Forces You)
1. Get Your Invoice Data Structured
Every invoice your system produces should have:
- Unique invoice ID (sequence + date, e.g.,
INV-2026-000142) - Seller legal name, EIN, and address
- Buyer legal name, EIN (or SSN for individuals), ship-to address
- Line items with description, quantity, unit price, tax code, and tax amount
- Subtotal, total tax, total due
- Payment terms and due date
If your current invoicing tool stores these fields but only outputs them as PDF, you're 80% of the way to structured. You need an export path (UBL XML, CSV, or JSON) — that's implementation, not redesign.
2. Track Nexus by State
Every time you ship an order into a new state, log the transaction count and dollar amount against that state's nexus threshold. When you cross 80% of threshold, start preparing to register.
3. Collect Exemption Certificates Systematically
For every B2B customer claiming sales tax exempt status, store the resale or exemption certificate in the customer record. Tie it to a specific state. Set an expiration date. Audit your exemption file at least annually.
4. Separate Taxable and Non-Taxable Line Items
Services, products, shipping, and discounts have different taxability rules in different states. Your line items should tag each as taxable or non-taxable with the reason (state statute or customer exemption). Don't bury this in the description field.
5. Plan for Peppol or UBL Export
If you sell to customers in Europe, Australia, Singapore, or other Peppol-connected jurisdictions, you already need this. Even if you sell only in the US, add it to your 12-month roadmap. The cost to add later is higher than building it in now.
How Pleelo Handles E-Invoicing Readiness
Pleelo's invoicing engine is built around structured invoice data — the PDF is an output, not the source of truth.
Structured invoice storage: every invoice is stored as a typed object with buyer, seller, line items (each with tax code, tax rate, and amount), totals, and metadata. The PDF is generated from this structure; the structure is the record.
Multi-state sales tax engine: for US businesses with nexus in multiple states, Pleelo applies the correct state + local tax rate based on the ship-to address, and tracks cumulative sales by state against the nexus threshold.
Exemption certificate storage: attach a W-9 equivalent (resale or exemption certificate) to any B2B customer, tied to the states it applies to, with an expiration date. When you invoice that customer for a shipment to a covered state, tax is automatically exempted and the certificate reference appears on the invoice.
Structured export: invoices can be exported as UBL 2.1 XML (Peppol-compatible) or JSON for integration with buyer AP systems or state tax filing tools.
Sales tax reporting by state: on demand, produce a state-by-state sales summary with taxable sales, exempt sales, tax collected, and transaction count — the exact data every state revenue department asks for.
Ready for the BPC exchange: when the US federal e-invoice exchange goes from pilot to production, Pleelo's structured invoice data is already in the format the exchange requires. Submitting through a connector becomes a configuration change, not a rebuild.
The 90-Day E-Invoicing Readiness Plan
If you're a US SMB without federal pressure to move on e-invoicing, here's the minimum you should do this year:
Month 1: Audit Current State
- Export a year of invoices
- Check that every invoice has: buyer EIN, ship-to state, line-level tax codes, exemption references (if any)
- Identify missing fields — these are your data gaps
- Pull a list of every state where you've shipped — check each against its nexus threshold
Month 2: Fix the Data
- Enrich customer records with complete EIN/SSN, billing address, ship-to addresses
- Collect missing W-9s (see our guide on W-9/1099 compliance)
- Upload exemption certificates for B2B exempt customers
- Configure sales tax rates by state where you have nexus
Month 3: Enable Structured Output
- Set up UBL or JSON export from your invoicing system
- Test with one buyer that can ingest structured invoices
- Register for any state nexus thresholds you've crossed but haven't registered for yet
By the end of 90 days, you have a clean invoice database, known nexus exposure, and structured-export capability — ready for the next buyer requirement, state audit, or federal exchange.
Stop Treating Invoicing as Just a PDF Generator
The US e-invoicing shift is happening gradually, through buyer mandates and state tax complexity. Businesses that treat invoicing as a PDF generator today are going to spend the next 24–36 months retrofitting structured data under pressure.
Pleelo builds structured invoice data into the system from day one, with multi-state sales tax, exemption tracking, and structured export already in place.
See Pleelo's invoicing module →
The PDF is the output. The data is the record. The US is catching up to the rest of the world — be ready before it arrives.
