If you’ve seen “EDI payment” or “EDI PMT” on a bank statement, you may be wondering what it means. In simple terms, an EDI payment means electronically exchanging payment or remittance information. In a business-to-business supply chain, however, an EDI payment often involves the EDI 820, a transaction trading partners can use to communicate payment instructions, remittance details, or both. For finance and operations teams, that electronic exchange can solve a familiar problem: knowing not only that money arrived, but exactly which invoices, deductions, and adjustments go with it.
What is an EDI payment?
So, what is an EDI payment in a B2B transaction?
An EDI payment, or electronic data interchange payment, is the electronic exchange of payment-related information between businesses using EDI. Rather than sending remittance details through email, paper documents, spreadsheets, or another disconnected process, businesses can exchange that information in a standardized electronic format.
If EDI itself is new to you, the fundamentals of EDI are straightforward: EDI allows businesses to exchange documents electronically in standardized formats so information can move between systems with less manual intervention.
For payments, the key document is the EDI 820. It’s known as a Payment Order or Remittance Advice document and tells the recipient what a payment covers.
That distinction matters. The movement of money and the information explaining the payment are closely connected, but they aren’t necessarily the same thing. An electronic funds transfer moves the funds; the EDI 820 provides the remittance information a business needs to apply those funds accurately.
How EDI Payments Work: The 820 Remittance Advice
Consider what happens after you send a customer an invoice.
The payment arrives, but it may cover several invoices. One invoice may have been paid in full, another may include a deduction, and another may have an adjustment. Without structured remittance information, your accounts receivable team has to work out where everything belongs. The EDI 820 helps connect those dots.
Here is how EDI payments work in a typical transaction:
- A buyer places an order with an EDI 850 Purchase Order.
- The seller fulfills the order and sends an EDI 810 Invoice.
- The buyer processes the invoice and initiates payment.
- The buyer sends an EDI 820 with the payment or remittance information.
- The seller uses that data to match the payment against its open invoices.
You may also see EDI PMT used as shorthand for an EDI payment or payment transaction in statements and internal systems.
Instead of leaving the seller with a deposit and a reconciliation puzzle, the EDI 820 provides structured information that can tell the business what was paid and how the payment should be applied.
The usefulness of an EDI payment comes down to the information traveling with it. An EDI 820 can include details such as:
- Payer and payee identification
- Invoice numbers or other invoice references
- Amounts paid
- Deduction or short-payment reason codes
- Adjustment information
Together, those details give finance teams the context they need to reconcile payments with outstanding receivables. The specific transaction contains more technical information than most finance and operations professionals need for an introduction to EDI payments. For a deeper look at the document structure and its use, see our guide to the Payment Order or Remittance Advice document.
How EDI Payments Fit into the Order-to-Cash Cycle
Payment reconciliation doesn’t happen in isolation. It’s one step in a larger exchange of information between a buyer and seller. A simplified order-to-cash flow may include:
EDI 850 Purchase Order → EDI 810 Invoice → EDI 820 Payment/Remittance Advice → EDI 997 Functional Acknowledgment
Each transaction has a job to do. The purchase order communicates what the buyer wants to purchase. The invoice communicates what the seller expects to be paid. The EDI 820 communicates the payment and remittance details. A 997 Functional Acknowledgment reports whether an EDI transaction passed syntax checks and was accepted or rejected at the functional level..
Together, these EDI transaction codes create a digital flow of information between trading partners. When those transactions are integrated with your business systems, information can move through the order-to-cash process without your team repeatedly re-entering or tracking down data, and that becomes particularly important at the end of the cycle. Sending an invoice electronically saves time. But if your team still has to manually determine how every incoming payment should be applied, there’s manual work left to remove.
Common Challenges With Manual Payment Reconciliation
When a payment lands in the bank, someone has to figure out what it paid. For a handful of transactions, that may be manageable. Across hundreds or thousands of invoices and multiple trading partners, it becomes a drain on your team.
Matching Payments to Invoices Manually
When remittance information isn’t connected to your financial system, employees may need to search for invoice numbers, compare amounts, and enter payment information by hand. Every manual touch takes time. It also creates another opportunity for an error.
Investigating Short Payments and Deductions
A payment doesn’t always equal the original invoice amount. Customers may take deductions or make adjustments that leave your team investigating why the amount received differs from the amount expected. If the explanation arrives separately, or in a format that’s difficult to process, the investigation takes longer.
Managing Different Trading Partner Processes
One customer may provide remittance information electronically. Another may send a separate file. Another may use a different process altogether. The more disconnected those workflows become, the more work falls on your team to turn different sources of information into one consistent reconciliation process.
That can create the same problems seen elsewhere in manual supply chain processes: more employee time spent on non-value-added tasks, delayed processing, limited visibility, and slower cash application.
Connecting EDI with ERP integration helps address that disconnect by allowing transaction information to flow into the systems your team already uses.
How TrueCommerce Automates EDI Payment Processing
The goal isn’t simply to receive an EDI 820. It’s to make the information useful without adding another manual process.
With integrated EDI payment processing, remittance information can flow into your ERP and be matched with the appropriate business data rather than requiring your team to rekey it. That creates an opportunity to move from reviewing every transaction manually to managing by exception.
Instead of spending time on payments that match as expected, your team can focus on the transactions that actually require attention.
TrueCommerce combines EDI transaction processing with ERP integration so payment and remittance data can become part of the broader business workflow. Automated EDI processing can reduce manual data entry and help your team identify exceptions such as deductions or mismatched amounts that need review.
The result is a more connected process from purchase order to invoice to payment: less repetitive reconciliation work, fewer manual dependencies, and more time for your finance and operations teams to focus on the exceptions and decisions that need their expertise.
See How TrueCommerce Automates EDI 820 Reconciliation
TrueCommerce EDI matches your EDI 820 remittance data to open invoices automatically, so your team can skip manual payment matching.
See How It Works