EDI 820 Payment Processing in SAP

Every finance team knows how this works: a customer pays an invoice, but the payment doesn’t always match the invoice amount exactly.

Maybe there’s a cash discount. Maybe a credit memo is involved. Maybe three invoices got bundled into one wire transfer.

Figuring out what was actually paid, for what, and how to apply it in SAP is one of those back-office tasks that eats hours every single day - and it’s exactly the kind of manual, error-prone work EDI automation was built to reduce.

That’s what the EDI 820 transaction does, and it’s what we want to walk through here: how Arcus takes an inbound 820 Payment Order/Remittance Advice and turns it into a payment advice document in SAP that’s ready for your team to review and post - without anyone having to key in the details by hand.

What Is a Payment Advice?

A payment advice (or remittance advice) is a document a payer sends to a payee confirming a payment - and it specifies exactly which invoices that payment settles. That’s what lets your accounts receivable team match incoming cash to the right invoices quickly, instead of piecing it together from a check stub or a wire notice.

That’s the X12 820 transaction set. You receive it from the trading partner, and it gets translated and delivered into SAP as a native payment advice document - arriving automatically instead of being keyed in by hand.

What Kind of Data Actually Gets Pulled Out

Once the 820 is received, the system reads through it and pulls out the pieces that actually matter for reconciling a payment - things like:

• Who’s paying and who’s getting paid - so the payment lands against the right account.
• The total payment amount and how it was paid (check, wire, etc.), along with the date.
• Every invoice or credit memo the payment is settling - including the original invoice amount, any cash discount taken, and the actual amount applied to each one. This is the part that saves the most time: instead of an AR clerk manually piecing together “this payment covers these five invoices, minus this discount,” it’s already broken out line by line.
• Reference numbers - PO numbers, invoice numbers - so each line ties back to the exact open item sitting in SAP, with nothing left to guess at.

One nice safeguard built into the process: if a trading partner ever sends a type of adjustment or reason code the system hasn’t seen before, it deliberately stops and flags it for review rather than guessing what it means. That way, new scenarios get looked at by a human before anything posts incorrectly.

What Happens on the SAP Side

Once the payment advice document arrives, it’s created in SAP automatically and ready for review. From there, your AR team can pull up the payment advice, see exactly which invoices it’s paying and for how much, and post it against those invoices - clearing them in a fraction of the time manual entry would take, with the matching work already done for them.

The one-time setup - telling SAP which trading partners are enabled for this - happens once per partner as part of onboarding. After that, it just runs.

How This Saves You Time

Instead of an AR team spending their day transcribing remittance details off a payment stub, they’re reviewing and confirming what’s already matched. Cash gets applied faster, and discrepancies get caught automatically. The audit trail - what was paid, when, and against what - is cleaner because the numbers came straight from the trading partner’s file, not manual entry.

For most companies, automating this process with even one trading partner will save your AR team time. Multiply that across all of your customers, and you get a faster month-end close, fewer open items, and a more efficient AR team.