Supplier e-invoicing requirements in the United States depend entirely on who your customer is: no federal law forces one private business to send another an electronic invoice, but if you sell to a federal agency, OMB Memorandum M-15-19 makes electronic submission effectively mandatory, and every invoice you send, paper or electronic, still has to satisfy IRS recordkeeping rules under 26 U.S.C. § 6001 and Revenue Procedure 98-25. What follows is what you actually have to do to invoice electronically, keep the records the IRS expects, and get paid on time.
When E-Invoicing Is Actually Required
Business-to-business e-invoicing in the United States is voluntary. There is no federal statute compelling private companies to exchange structured electronic invoices with each other, unlike regimes in the EU, India, and parts of Latin America. In practice, adoption is spreading because large buyers make electronic submission a condition of doing business, but that is a contract requirement, not a legal one.
The legal obligation appears when your customer is the federal government. OMB Memorandum M-15-19 directed federal agencies to manage invoices electronically for commercial goods and services, using either a Federal Shared Service Provider or an OMB-approved solution such as the Invoice Processing Platform. If you hold a federal contract, you are also required to register in the System for Award Management (SAM) and keep your electronic funds transfer information current. Under FAR clause 52.232-33, federal contract payments run through EFT using the banking data in your SAM record, so those details need to be right before your first invoice goes out.
One boundary worth naming: if you invoice a public-sector buyer inside the European Union, EU Directive 2014/55/EU requires that buyer to accept e-invoices in the European standard format, and your U.S. location does not exempt you from producing a compliant file. Purely domestic B2B work carries no equivalent obligation.
The Data Every E-Invoice Has to Carry
A structured e-invoice only works if the buyer’s system can find each piece of information in a predictable place and match it against a purchase order. Miss a field and the invoice either bounces or lands in an exception queue.
Every invoice needs a unique identification number. Sequential numbering is standard, and the buyer’s system uses that number to prevent duplicate payments, so gaps or repeats will trigger a rejection. Tax identification numbers for both parties belong on every invoice; for domestic work this is typically your Employer Identification Number, and for federal payments the identifier ties back to your SAM registration.
You also need the invoice date, a description of what you delivered, unit prices, quantities, and the total amount due. Separate the base price from any applicable sales tax, and put discounts on their own line rather than burying them in the total. State the currency explicitly. That last point matters little for domestic invoicing and becomes critical the first time you bill across a border.
Structured Formats vs. Emailed PDFs
The purpose of e-invoicing is that a machine reads your data without a human retyping it. That only happens when the file is structured, meaning every value sits in a tagged, predictable location.
Two formats dominate. XML uses descriptive tags around each data element so the receiving system knows exactly what it’s looking at, and most modern cloud-based invoicing platforms generate XML natively. EDI is the older standard and remains widespread among large enterprises with decades of high-volume B2B history. Both accomplish the same goal: parsing your invoice into the correct fields automatically.
Peppol is a standardized network that acts as a common translation layer between different accounting platforms. Originally built for European public procurement, it has expanded to countries including Australia and Singapore. If you sell into multiple buyers running different software, a certified Peppol access point can replace a stack of one-off integrations.
Emailed PDFs are not e-invoicing. The buyer’s system has to run optical character recognition to pull data off what is essentially a picture of text, and OCR is unreliable across varying layouts. Structured formats sidestep that problem.
Getting Set Up With the Buyer
Before your first e-invoice goes anywhere, you have to onboard with the buyer’s system. Specifics vary; the pattern does not.
Federal Agencies
Suppliers invoicing federal agencies typically use the Invoice Processing Platform, the government’s centralized portal for electronic invoices. IPP enrollment requires multi-factor authentication and verification of your entity information. Before you can access IPP, you need an active SAM.gov registration, which must be renewed every 365 days. SAM registration can take up to 10 business days to become active, so build that lead time in.
Private Buyers
Most private buyers run a procurement portal where you build a supplier profile with your banking information, contact details, and tax documentation. A completed Form W-9 is almost always required so the buyer can verify your taxpayer identification number and meet its own information reporting obligations. Some buyers require a digital signature certificate that authenticates your invoices and flags any alteration in transit.
Setup costs scale with volume and integration depth. A small supplier keying invoices into a web portal may pay nothing beyond staff time. Direct API or EDI integration typically involves configuration fees to the service provider and an ongoing subscription that varies with transaction volume and features.
Why Invoices Get Rejected: Three-Way Matching
Three-way matching is the single most useful concept for getting paid quickly. The buyer’s system compares three documents: the purchase order, the goods receipt confirming delivery, and your invoice. If quantities, prices, and item descriptions align across all three, the invoice moves to payment with no human involvement. If they don’t, it goes to an exception queue.
Price variances, quantity mismatches, and missing purchase order references are the usual reasons for a hold. A structured e-invoice makes matching easier because the data arrives in tagged fields the system can compare line by line. That same precision means small discrepancies a human might have waved through on paper will now trip an automatic flag.
What that means in practice: reference the exact purchase order number on the invoice, match line items to the PO descriptions precisely, and confirm delivered quantities with the buyer’s receiving department before you invoice. Clean submissions on the first try beat any amount of downstream follow-up.
Submitting Invoices and Handling Rejections
Once configured, invoices move through one of three channels: upload into the buyer’s web portal, push through an API connecting your accounting software to the buyer’s system, or transmit over an EDI network. All three deliver within seconds.
Most platforms generate automated acceptance or rejection notifications and let you track status as an invoice moves from received to matched, approved, and scheduled for payment. When an invoice is rejected, the system typically states the reason: a missing PO reference, a price mismatch, a formatting error. Fix the specific problem and resubmit through the same channel.
For substantive disputes over pricing or quantities, document the discrepancy formally and attach the purchase order, shipping receipt, and any correspondence supporting your position. Follow up on time. Many organizations set internal deadlines, often around 14 days, for raising disputes, and waiting past those windows pushes your invoice back in the queue.
IRS Recordkeeping for Your Electronic Invoices
Every business has to keep records sufficient to establish its tax liability. Under 26 U.S.C. § 6001, the IRS can require any person to keep whatever records the Secretary considers necessary, and that authority reaches electronic records exactly as it reaches paper.
The technical rules for electronic storage come from IRS Revenue Procedure 98-25. Your system has to maintain documentation evidencing the authenticity and integrity of your records, so you can prove an invoice actually came from the claimed source and that nothing was altered after creation. It also has to include internal controls that prevent unauthorized additions, changes, or deletions.
Beyond that, your electronic records must reconcile with your books and your tax return, producing a clear audit trail from the general ledger down to individual source documents. If the IRS asks for access during an examination, you must be able to retrieve and reproduce records, including paper copies on request, and provide the hardware, software, and personnel needed to read the data. Handing storage to a third-party service does not shift these obligations off you.
How Long to Keep the Records
The IRS wants you to keep records supporting a return until the statute of limitations on that return expires. The standard period is three years from the date filed. Several exceptions extend it:
- Unreported income exceeding 25% of gross income: six years.
- Bad debt deductions or worthless securities: seven years.
- Employment tax records: at least four years after the tax becomes due or is paid, whichever is later.
- Fraudulent returns or failure to file: no expiration; keep them indefinitely.
Revenue Procedure 98-25 adds a trap for anyone changing systems. If you stop maintaining the hardware or software needed to access old electronic records, the IRS treats those records as destroyed. Before decommissioning any invoicing platform, export the data in a format you can still read and produce years later.
Penalties When Information Returns Are Wrong or Late
The IRS penalizes businesses under 26 U.S.C. § 6721 for failing to file a correct information return or filing it late. The base statutory penalty is $250 per return, reduced if you correct the problem quickly. For returns due in calendar year 2026, the inflation-adjusted tiers are:
- Corrected within 30 days: $60 per return, capped at $683,000 per year for larger businesses or $239,000 for businesses with gross receipts of $5 million or less.
- Corrected after 30 days but by August 1: $130 per return, capped at $2,049,000 (or $683,000 for small businesses).
- Corrected after August 1 or not corrected: $340 per return, capped at $4,098,500 (or $1,366,000 for small businesses).
- Intentional disregard: $680 per return with no annual cap.
26 U.S.C. § 6722 imposes a parallel structure and the same inflation-adjusted amounts when you fail to furnish correct payee statements. These penalties apply to information returns, not to every invoice you send, but if invoicing errors feed incorrect 1099 reporting, the exposure adds up quickly at $340 or more per return.
Prompt Payment Protection on Federal Contracts
Suppliers to federal agencies get a counterweight to all the enrollment work. Under 31 U.S.C. § 3903, the default payment deadline is 30 days after the agency receives a proper invoice unless the contract specifies otherwise. For small business prime contractors, agencies are directed to target an accelerated 15-day payment.
Miss the deadline and the agency owes interest for every day payment is late. The Prompt Payment Act interest rate for the first half of 2026 is 4.125% per year, adjusted semiannually by Treasury.
The statute also limits how long a rejection can stall you. If the agency decides your invoice is not proper, it has to return the invoice within seven days and explain the defect. Take longer and the clock keeps running: the agency loses one day of its payment window for each day of rejection delay. This is one place where structured e-invoicing carries a real advantage, because field-level validation at submission catches most formatting problems immediately rather than after a week in someone’s queue.