What we do
Tools
Industries
Department
How we workLet's talk →
Home/SAP/SAP Accounts Payable Automation by SAP Release
SAP

SAP Accounts Payable Automation, From the Inbox to the Payment Run

A supplier calls about an invoice that's three weeks old. It was received, read and posted. It's sitting behind a payment block because the goods receipt never went in, and nothing told anyone. Reading invoices is the part of SAP accounts payable automation that SAP and its partners already sell well. The part that stays manual on most SAP systems is what happens between a posted invoice and the payment run.

The invoice capture route that goes with each SAP system

Your SAP system Capture route to look at first What to ask about it
SAP ECC 6.0 Invoice Management by OpenText (VIM), the long-standing add-on for ECC ECC mainstream maintenance ends in 2027. Ask how much of a new VIM project carries over when you move to S/4HANA.
S/4HANA, on-premise or private cloud Invoice Management by OpenText, or SAP Document AI (formerly Document Information Extraction) feeding supplier invoices Whether captured invoices arrive parked for review or posted, and who clears the ones that land parked.
S/4HANA Cloud, Public Edition SAP's own capture with Document AI, or the OpenText invoice processing SAP offers for this edition What your scope already licenses. Extensions here run on SAP BTP, not inside the system.
Already on Concur for expenses Concur Invoice, a separate cloud AP product that sends approved invoices to the ERP Approval then lives in Concur, while payment blocks and the payment run stay in SAP. Decide who owns an invoice that's approved in one and blocked in the other.

One invoice's path through SAP, and the stops where it waits

Transaction codes are the classic SAP GUI ones. On S/4HANA the Fiori apps (Create Supplier Invoice, Manage Supplier Invoices) do the same jobs.

  1. 1

    It arrives

    By email, EDI, a supplier portal or the post. Whatever reads it, the vendor, PO number, amounts and tax have to come off it correctly before anything else can happen.

    Watch for: the same invoice arriving twice, once as a PDF and once on paper. SAP's duplicate check depends on reference and amount matching exactly.

  2. 2

    It gets parked

    MIR7

    Capture tools and AP clerks often park an invoice when something's missing. A parked invoice isn't in the ledger and won't pay, and it isn't anyone's job by default.

  3. 3

    It posts against the PO

    MIRO

    SAP matches the invoice to the purchase order and the goods receipt itself, using the tolerances your team configured for price and quantity.

  4. 4

    It gets blocked for payment

    A price or quantity outside tolerance, or no goods receipt yet, sets a payment block. The invoice is posted and owed, and the payment run skips it.

    Watch for: the goods receipt. When receiving happens in a separate warehouse or field system, the block can't clear until someone posts it in SAP.

  5. 5

    It gets released and paid

    MRBR F110

    MRBR's automatic release clears blocks whose reason has gone away, but only when someone runs it or schedules it. The payment run then picks the invoice up on its next pass.

The follow-up work SAP leaves to email

If you run VIM, its exception workflows are the first place to look, and tuning them may be all you need. What tends to stay outside any SAP tool is the people and systems that aren't in SAP: a requester who never logs in to confirm receipt, a warehouse system that records the delivery but doesn't post the goods receipt, a buyer who needs to see a price variance next to the PO before approving it.

n-frames builds that layer around SAP accounts payable: goods receipts posted from wherever receiving really happens, price variances routed to the buyer who raised the PO, a list of parked and blocked invoices by age and value for the AP lead, and supplier status answers that don't need a clerk to look them up. Where there's no capture add-on yet, n-frames builds the capture too, and posts or parks invoices through the BAPIs or supplier invoice APIs your release exposes. The SAP API page covers which interface your system has.

Let's talk

Invoices posted, then stuck behind a payment block?

n-frames builds the follow-up around SAP AP, so a missing goods receipt or a price variance reaches the person who can fix it while there's still time to pay on terms.

Goods receipts that post on time →

SAP AP automation, from the AP desk

Does SAP have built-in AP automation?

It has several pieces, and which you have depends on your system and licenses. S/4HANA can read supplier invoices with SAP Document AI, SAP resells Invoice Management by OpenText for ECC and S/4HANA, and Concur Invoice is SAP's cloud AP product. How much of the exception follow-up each one handles depends on how it's configured.

Can you automate AP without replacing our SAP setup?

Yes. The automation works with the SAP release you're on, through the interfaces it already has, so there's no upgrade or AP add-on to buy first. Documents created through interfaces can count under SAP's digital access licensing, so confirm that with your SAP account team.

What about matching invoices to purchase orders?

SAP runs the three-way match itself when an invoice posts, comparing it with the PO and the goods receipt. What usually breaks it is a goods receipt that's late or missing, so that's where n-frames puts the work: posting receipts from the system that records deliveries, and sending real variances to the buyer.

We're happy with SAP, but AP still means a lot of manual keying. Do we need new AP software?

Usually not. If invoices are keyed by hand today, capture can post or park them in your existing SAP instance, and the follow-up around blocked invoices sits beside it rather than replacing anything.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.