Incoming Invoice (e-Invoice and Paper) Approval Workflow and Tracking Cockpit
Short answer: 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.
- Estimated effort
- XL · 20–30 working days
- System
- ECC and S/4HANA
- Tables
- 11
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Accounts payable teams, purchasing, budget owners and unit managers, finance managers.
Closest standard alternatives
- MIRO Enter Incoming Invoice. Enters or parks the invoice; no approval route or waiting time tracking.
- MRBR Release Blocked Invoices. Releases invoices blocked for price or quantity differences; not for business approval.
- MIR4 Display Invoice Document / Change Status. Shows invoice status; no approval history or list of waiting approvals.
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| RBKPDocument Header: Incoming Invoice | Parked and posted invoice header | Read / write | ECC + S/4 |
| RSEGDocument Item: Incoming Invoice | Invoice items and PO reference | Read | ECC + S/4 |
| EKKOPurchasing Document Header | PO header: purchasing group, vendor | Read | ECC + S/4 |
| EKPOPurchasing Document Item | PO item | Read | ECC + S/4 |
| EKBEPurchasing Document History | Goods receipts and previous invoices | Read | ECC + S/4 |
| LFA1Vendor Master (General Section) | Supplier name and tax number | Read | ECC + S/4 |
| CSKSCost Center Master Record | Cost center owner (non-PO invoice route) | Read | ECC + S/4 |
| T024Purchasing Groups | Purchasing group (PO invoice route) | Read | ECC + S/4 |
| SWWWIHEADWorkflow Runtime: Work Item Header | Approval work items and their status | Read | ECC + S/4 |
| TOA01ArchiveLink Link Table 1 | Archive link of the invoice image | Write | ECC + S/4 |
| BKPFAccounting Document Header | Accounting document of the non-PO invoice | Write | ECC + S/4 |
BAPIs and functions used
- FI_DUPLICATE_INVOICE_CHECKDuplicate Invoice Check for Vendor Invoices. Checks for duplicate invoices
- BAPI_INCOMINGINVOICE_PARKPark Incoming Invoice. Parks the PO invoice
- SAP_WAPI_START_WORKFLOWWorkflow: Start Workflow. Starts the approval route
- SAP_WAPI_WORKITEM_COMPLETEComplete Work Item. Completes the work item for portal or mobile approval
- BAPI_ACC_DOCUMENT_POSTAccounting: Post Document. Posts the approved non-PO invoice
- SO_NEW_DOCUMENT_ATT_SEND_API1SAPoffice: Send New Document with Attachments. Sends notice, reminder and escalation emails
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | RBKP-BUKRS | Yes | 1000 |
| S_LIFNR | Supplier | Range / multiple | RBKP-LIFNR | No | — |
| S_BLDAT | Invoice date | Range / multiple | RBKP-BLDAT | No | 01.11.2026 – 30.11.2026 |
| P_OPEN | Waiting for approval | Radio button | — | No | X |
| P_ALL | All invoices | Radio button | — | No | — |
| P_DUE | Only those due within 7 days | Checkbox | — | No | — |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Supplier | RBKP-LIFNR |
| 2 | Supplier name | LFA1-NAME1 |
| 3 | Invoice number | RBKP-XBLNR |
| 4 | Invoice date | RBKP-BLDAT |
| 5 | Gross amount | RBKP-RMWWR |
| 6 | Currency | RBKP-WAERS |
| 7 | Source | Calculated e-Invoice or paper (scanned) |
| 8 | PO-based | Calculated PO reference yes/no |
| 9 | Next approver | Calculated Open level in the route |
| 10 | Waiting (days) | Calculated Today − date entered in the cockpit |
| 11 | Status | Calculated Waiting, approved, posted, rejected or duplicate |
Sample result list
| Supplier | Supplier name | Invoice number | Invoice date | Gross amount | Currency | Source | PO-based | Next approver | Waiting (days) | Status |
|---|---|---|---|---|---|---|---|---|---|---|
| 700021 | Örnek Bilişim Ltd. | OBL2026000004812 | 20.11.2026 | 218,400 | TRY | e-Invoice | Yes | SATINALMA02 | 6 | Waiting |
| 700145 | Demo Danışmanlık A.Ş. | DDA2026000000377 | 18.11.2026 | 96,000 | TRY | e-Invoice | No | BUTCE-IK | 9 | Waiting (reminder sent) |
| 700310 | Örnek Temizlik Hizm. Ltd. | A-004512 | 12.11.2026 | 31,200 | TRY | Paper | No | - | 0 | Posted |
How does the program work?
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Performance notes
Read the cockpit list from the custom invoice register table with status and date indexes; add RBKP and workflow status only for listed records with FOR ALL ENTRIES. Run the reminder job daily, not hourly.
Features
- ALV list (sort, filter, subtotals)
- Send the result by email Notice to the approver, reminders for waiting approvals and escalation to the manager after a long wait.
- Line-by-line result and error log Every approval, rejection and question is kept with user and time.
- Runs as a background job Receiving incoming invoices and reminders run as scheduled jobs.
- Double-click drill-down to the document
Authorization objects
- M_RECH_BUKInvoice verification authorization by company code
- F_BKPF_BUKAuthorization to post non-PO invoices
- S_WF_WIAuthorization 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.
Related reports
Duplicate Vendor Invoice Check Report
A custom ALV report that compares posted vendor invoices by reference number, amount and document date and lists possible duplicates in groups. …
Accounting Document Approval and Posting Control
A control program that sends accounting documents for approval before final posting, based on rules by document type, amount, G/L account and company …
Türkiye e-Invoice, e-Archive and e-Waybill Outbound and Inbound Cockpit
A custom interface cockpit that sends billing documents and deliveries from SAP to the integrator as e-Invoice, e-Archive or e-Waybill, and receives …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.