# Incoming Invoice (e-Invoice and Paper) Approval Workflow and Tracking Cockpit

> A cockpit that brings incoming e-invoices and scanned paper invoices into SAP and routes them to the right people for approval before posting. PO invoices are held as parked invoices, non-PO invoices as approval records; the approval route is determined by cost center owner, purchasing group and amount. It offers reminder emails, mass approval, portal or mobile approval, and approval time and exception reports.

- Type: Program, Custom development, Interface
- Module: FI
- Estimated effort: XL (20–30 working days)
- Last updated: 2026-11-18
- URL: https://nekuhub.com/en/programs/incoming-invoice-approval-workflow-and-tracking-cockpit/


## Why is the standard not enough?

MIRO enters and parks an invoice, MRBR releases invoices blocked for price or quantity differences, and MIR4 shows the invoice status. But a route that decides who approves an incoming invoice by cost center, purchasing group and amount, tracking of approval waiting time, reminders and exception reports are not available out of the box; for non-PO invoices approval happens entirely outside SAP. Invoices end up circulating as email attachments and paper files, and due dates are missed.

### Closest standard alternatives

- MIRO: Enters or parks the invoice; no approval route or waiting time tracking.
- MRBR: Releases invoices blocked for price or quantity differences; not for business approval.
- MIR4: Shows invoice status; no approval history or list of waiting approvals.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| RBKP | Parked and posted invoice header | Read / write | - | ECC + S/4 |
| RSEG | Invoice items and PO reference | Read | RSEG-BELNR = RBKP-BELNR AND RSEG-GJAHR = RBKP-GJAHR | ECC + S/4 |
| EKKO | PO header: purchasing group, vendor | Read | EKKO-EBELN = RSEG-EBELN | ECC + S/4 |
| EKPO | PO item | Read | EKPO-EBELN = RSEG-EBELN AND EKPO-EBELP = RSEG-EBELP | ECC + S/4 |
| EKBE | Goods receipts and previous invoices | Read | EKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELP | ECC + S/4 |
| LFA1 | Supplier name and tax number | Read | LFA1-LIFNR = RBKP-LIFNR | ECC + S/4 |
| CSKS | Cost center owner (non-PO invoice route) | Read | - | ECC + S/4 |
| T024 | Purchasing group (PO invoice route) | Read | T024-EKGRP = EKKO-EKGRP | ECC + S/4 |
| SWWWIHEAD | Approval work items and their status | Read | - | ECC + S/4 |
| TOA01 | Archive link of the invoice image | Write | - | ECC + S/4 |
| BKPF | Accounting document of the non-PO invoice | Write | - | ECC + S/4 |

## BAPIs and functions used

- FI_DUPLICATE_INVOICE_CHECK: Checks for duplicate invoices
- BAPI_INCOMINGINVOICE_PARK: Parks the PO invoice
- SAP_WAPI_START_WORKFLOW: Starts the approval route
- SAP_WAPI_WORKITEM_COMPLETE: Completes the work item for portal or mobile approval
- BAPI_ACC_DOCUMENT_POST: Posts the approved non-PO invoice
- SO_NEW_DOCUMENT_ATT_SEND_API1: Sends notice, reminder and escalation emails

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | RBKP-BUKRS | Yes |
| S_LIFNR | Supplier | Range / multiple | RBKP-LIFNR | No |
| S_BLDAT | Invoice date | Range / multiple | RBKP-BLDAT | No |
| P_OPEN | Waiting for approval | Radio button | - | No |
| P_ALL | All invoices | Radio button | - | No |
| P_DUE | Only those due within 7 days | Checkbox | - | No |

## Result list columns

| Column | Source |
|---|---|
| Supplier | RBKP-LIFNR |
| Supplier name | LFA1-NAME1 |
| Invoice number | RBKP-XBLNR |
| Invoice date | RBKP-BLDAT |
| Gross amount | RBKP-RMWWR |
| Currency | RBKP-WAERS |
| Source | Calculated: e-Invoice or paper (scanned) |
| PO-based | Calculated: PO reference yes/no |
| Next approver | Calculated: Open level in the route |
| Waiting (days) | Calculated: Today − date entered in the cockpit |
| Status | Calculated: Waiting, approved, posted, rejected or duplicate |

## How does the program work?

1. Incoming invoices come from two sources: invoices from the e-invoice integration (supplier tax number, invoice number, date, amounts, PO reference) and paper invoices scanned and linked to the archive (TOA01). Each invoice becomes a record in the cockpit; duplicates are checked with FI_DUPLICATE_INVOICE_CHECK.
2. For PO invoices the PO is matched with EKKO/EKPO and the PO history in EKBE, and the invoice is parked with BAPI_INCOMINGINVOICE_PARK (RBKP, RSEG). For non-PO invoices a G/L account and cost center are proposed from the supplier's previous invoices.
3. The approval route is set by rules: for PO invoices the purchasing group (T024) and PO owner, for non-PO invoices the cost center owner (CSKS-VERAK_USER); extra levels are added by amount limits. The route is started with SAP_WAPI_START_WORKFLOW.
4. The approver sees the invoice and its image in the SAP inbox, a portal or a mobile app, and approves, rejects or asks a question. On the mass approval screen invoices for the same person are approved together. A reminder goes out for approvals waiting longer than a set time, and an escalation email to the manager after a longer wait.
5. After the final approval, the parked MM invoice is posted with BAPI_INCOMINGINVOICE_POST; a non-PO invoice is posted as a vendor invoice with BAPI_ACC_DOCUMENT_POST (BKPF). A rejected invoice is flagged for the return process with the supplier.
6. Reports: waiting invoices and waiting time, average approval time per approver, invoices whose due date passed while awaiting approval, and exceptions approved outside the route. In S/4HANA, if the flexible workflow for supplier invoices is used, the cockpit can be set up to feed it.

## Authorization objects

- M_RECH_BUK: Invoice verification authorization by company code
- F_BKPF_BUK: Authorization to post non-PO invoices
- S_WF_WI: Authorization to process approval work items

## Frequently asked questions

### What about e-invoices that must be rejected within the response period?

For commercial invoices the legal objection period must be tracked. The cockpit shows waiting invoices close to the end of the objection period in a separate exception list and warns the team to send a rejection through the e-invoice system; the period is set during installation according to current regulation.

### How do approvers without an SAP user approve?

Approval can be given in a portal or mobile app; the approval screen shows the invoice image and items, and the answer is recorded on the work item in SAP. User licensing is assessed against SAP license terms during installation.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=fi-incoming-invoice-approval-workflow
