# 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 code. A document that hits a rule is parked, the approver gets a workflow item and an email, and the posting is completed after approval; documents posted around the rules are reported in a separate violation list.

- Type: Program, Custom development, Enhancement
- Module: FI
- Estimated effort: L (12–18 working days)
- Last updated: 2026-11-18
- URL: https://nekuhub.com/en/programs/accounting-document-approval-and-posting-control/


## Why is the standard not enough?

The standard system offers document parking (FBV1, F-63) and posting a parked document (FBV0), and a workflow can be set up for parked documents. But which document needs approval cannot be defined flexibly with combined rules such as amount limits, document types and sensitive accounts, approvers cannot be tiered by amount, and documents a user posts directly with FB01 or FB50 are not reported as having bypassed approval. The custom solution brings the rule table, tiered approval and the violation report together.

### Closest standard alternatives

- FBV0: Posts parked documents one at a time; no rule-based approval levels or violation report.
- FBV3: Displays a parked document; approval status and waiting time are not tracked.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VBKPF | Parked document header: document type, user, status (driving table) | Read / write | - | ECC + S/4 |
| VBSEGS | Parked G/L account items: account, amount, cost center | Read | VBSEGS-BELNR = VBKPF-BELNR AND VBSEGS-BUKRS = VBKPF-BUKRS | ECC + S/4 |
| VBSEGK | Parked vendor items | Read | VBSEGK-BELNR = VBKPF-BELNR AND VBSEGK-BUKRS = VBKPF-BUKRS | ECC + S/4 |
| BKPF | Document header posted after approval; source of the violation report | Write | BKPF-BUKRS = VBKPF-BUKRS AND BKPF-BELNR = VBKPF-BELNR | ECC + S/4 |
| BSEG | Posted document items (violation check) | Read | BSEG-BUKRS = BKPF-BUKRS AND BSEG-BELNR = BKPF-BELNR AND BSEG-GJAHR = BKPF-GJAHR | ECC + S/4 |
| ACDOCA | Posted journal entry lines (S/4HANA) | Read | ACDOCA-RBUKRS = BKPF-BUKRS AND ACDOCA-BELNR = BKPF-BELNR | S/4HANA only |
| T003 | Document types (rule key) | Read | T003-BLART = VBKPF-BLART | ECC + S/4 |
| SKB1 | Company code G/L account data (sensitive account rules) | Read | SKB1-SAKNR = VBSEGS-SAKNR | ECC + S/4 |
| SWWWIHEAD | Approval work items and their status | Read | SWWWIHEAD-WI_ID = onay kaydındaki iş öğesi | ECC + S/4 |

## BAPIs and functions used

- SAP_WAPI_START_WORKFLOW: Starts the approval workflow for the parked document
- SO_DOCUMENT_SEND_API1: Sends email to the approver and the document owner
- FI_DOCUMENT_READ: Reads the document data for the approval screen

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | BKPF-BUKRS | Yes |
| S_BLART | Document type | Range / multiple | BKPF-BLART | No |
| S_BUDAT | Posting date | Range / multiple | BKPF-BUDAT | Yes |
| S_USNAM | Entered by | Range / multiple | BKPF-USNAM | No |
| P_OPEN | Documents waiting for approval | Radio button | - | No |
| P_VIOL | Documents that bypassed approval (violation report) | Radio button | - | No |

## Result list columns

| Column | Source |
|---|---|
| Company code | BKPF-BUKRS |
| Document number | BKPF-BELNR |
| Document type | BKPF-BLART |
| Posting date | BKPF-BUDAT |
| Entered by | BKPF-USNAM |
| Document amount | Calculated: Sum of debit items (VBSEGS/BSEG-WRBTR, SHKZG = S) |
| Currency | BKPF-WAERS |
| Rule | Calculated: Rule and level the document hit |
| Approver | Calculated: User at the next approval level |
| Status | Calculated: Waiting, approved, rejected or posted without approval (violation) |
| Waiting (days) | Calculated: Today − parking date |

## How does the program work?

1. A rule table is set up: company code, document type (T003), G/L account or account range (SKB1), amount range and approver or approver role. A rule can have several approval levels.
2. A check that runs when an accounting document is saved (validation or business transaction event enhancement) compares the document with the rules. For a document that hits a rule the user is warned, and the document is parked instead of posted (VBKPF, VBSEGS, VBSEGK).
3. For the parked document an approval workflow is started with SAP_WAPI_START_WORKFLOW; the approver gets a work item in the inbox and an email with the document summary through SO_DOCUMENT_SEND_API1.
4. The approver sees the document with its items in the cockpit and approves it, or rejects it with a reason. At the last approval level the document is posted with the post-parked-document function (PRELIMINARY_POSTING_POST_ALL) and written to BKPF/BSEG; a rejected document goes back to its owner.
5. The violation report compares the posted documents of the period (BKPF, BSEG) with the rules again and lists documents posted without an approval record, with the posting user and transaction code.
6. Every approval, rejection and reminder is kept with user, date and time; open approvals are tracked by waiting time. In S/4HANA posted lines can also be read from ACDOCA; if the S/4HANA journal entry verification with flexible workflow is used, the rules are designed to fit it.

## Authorization objects

- F_BKPF_BUK: Document posting and display authorization by company code
- F_BKPF_BLA: Posting authorization by document type
- F_BKPF_KOA: Posting authorization by account type
- S_WF_WI: Authorization to process approval work items

## Frequently asked questions

### What happens if a user posts the document directly with FB01?

The check at save time redirects a document that hits a rule to parking with a warning. For cases where the check did not run, mass interfaces or earlier periods, the violation report separately lists posted documents without an approval record.

### Are MM invoice verification and billing documents covered by the rules?

The rules are designed mainly for documents entered manually in FI. Documents from integrated sources such as purchasing and sales can be excluded by source transaction code and reference type (BKPF-AWTYP), or only tracked in the violation report.

### Does a document wait while the approver is on leave?

A deputy approver can be defined per rule, and the standard workflow substitution can also be used. Approvals waiting longer than a set time trigger a reminder to the next level.

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