EDI Document

820 Payment Remittance.
Know which invoices were paid.

When a retail partner makes a payment, they send an 820 that reconciles automatically in Fulfil. You see which invoices were paid, any deductions taken, and payment details.

See how it works

What's included in an 820.

The 820 provides complete payment and reconciliation details.

Payment Information

  • ✓ Payment amount and date
  • ✓ Check or wire transfer reference number
  • ✓ Payment method (ACH, wire, check)
  • ✓ Currency and banking details

Invoice Reconciliation

  • ✓ Invoice numbers paid
  • ✓ Amount paid per invoice
  • ✓ Deductions or adjustments applied
  • ✓ Reason codes for short payments

How 820 works in Fulfil.

Fulfil receives 820 remittances and automatically reconciles payments.

1

Retailer makes payment

When a retail partner pays your invoices via ACH or wire transfer, their AP system generates an 820 remittance advice with payment details.

2

820 arrives in Fulfil

The 820 remittance arrives via EDI, listing which invoices were paid, any deductions taken, and the payment reference number.

3

Automatic reconciliation

Fulfil automatically matches the 820 to your outstanding invoices, marks them as paid, and records any deductions or adjustments.

✓

Match to bank deposit

When the payment hits your bank account, you can match it directly to the 820 remittance, knowing exactly which invoices were paid without manual reconciliation.

Why 820 matters for your business.

Automatic payment reconciliation

The 820 tells you exactly which invoices were paid before the money hits your bank. Fulfil automatically matches payments to invoices, eliminating manual reconciliation work.

Eliminates manual bank deposit matching

Without the 820, you see a $47,329 deposit in your bank and must manually figure out which invoices it covers. The 820 provides a detailed breakdown, so you know exactly what was paid.

Know exactly which invoices were paid

Large retailers often pay multiple invoices in a single ACH transfer. The 820 breaks down the payment invoice-by-invoice, showing what was paid in full and what had deductions. Critical for accurate AR management.

Track deductions and disputes automatically

The 820 includes deduction codes when retailers take chargebacks or adjustments. Fulfil captures these automatically, so you can dispute invalid deductions or fix recurring issues without digging through paper remittance advice.

Related EDI documents.

The 820 Remittance works with other EDI documents in the payment cycle.

810

Invoice

The invoices being paid
850

Purchase Order

Original orders for the invoices
856

Advance Ship Notice

Shipment notifications for orders

FAQ

Questions? Answers.

What is an 820 and what does it become in Fulfil?
The 820 is an inbound Payment Order or Remittance Advice a trading partner sends to tell you a payment is coming and how it applies across your open invoices and adjustments. Fulfil parses the 820 and creates a Customer Payment record with a header and one allocation row per invoice payment and per adjustment. It is inbound only, so Fulfil receives the 820 rather than sending it.
What details does the 820 carry?
On the payment header it carries the total payment amount, the payment method such as check or ACH, the settlement date, and a trace or reference number used for reconciliation. Per line it lists the invoice numbers paid with amounts and any discount, plus adjustment or deduction lines that each carry a reason code.
How does Fulfil reconcile the 820 against invoices?
For each invoice line, Fulfil looks for a customer invoice in Posted state for the same customer and company whose number or reference matches the 820. Matched amounts are applied against the invoice's open balance, and each deduction line is matched to a GL account by its reason code. The reconciliation is automatic once the trading partner and its accounts are configured.
What do the deduction and adjustment codes map to?
Fulfil translates each raw reason code into an internal adjustment type, such as freight allowances, shortages, or an authorised return, and then looks up the matching GL account from the contact's account preferences. Once you map an adjustment type for a partner, Fulfil remembers it and usually matches the same code automatically next time.
Why might an 820 payment need manual review?
The Customer Payment lands in Allocated when every row has a matched invoice or account and the allocations sum to the total on the 820. If a row is missing an invoice link or a GL account, or the allocations do not equal the payment total, the payment moves to Waiting Allocation so someone can fix the offending rows and reprocess.
Which EDI documents relate to the 820?
The 820 pays down the 810 Invoices you sent for fulfilled orders, closing the order-to-cash cycle. If the trading partner is set up for 997 acknowledgements, Fulfil triggers an outbound 997 once the payment is created and the 820 is marked Accepted.

Ready to automate
your AR reconciliation?

See how it works