FI Program Custom development Enhancement

Accounting Document Approval and Posting Control

Short answer: 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.

Estimated effort
L · 12–18 working days
System
ECC and S/4HANA
Tables
9
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

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.

Who uses it? Chief accountants, finance managers, internal control and internal audit teams, general ledger users.

Closest standard alternatives

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

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
VBKPFDocument Header for Document ParkingParked document header: document type, user, status (driving table)Read / writeECC + S/4
VBSEGSParked Document Segment for G/L AccountsParked G/L account items: account, amount, cost centerReadECC + S/4
VBSEGKParked Document Segment (Vendor)Parked vendor itemsReadECC + S/4
BKPFAccounting Document HeaderDocument header posted after approval; source of the violation reportWriteECC + S/4
BSEGAccounting Document SegmentPosted document items (violation check)ReadECC + S/4
ACDOCAUniversal Journal Entry Line ItemsPosted journal entry lines (S/4HANA)ReadS/4HANA only
T003Document TypesDocument types (rule key)ReadECC + S/4
SKB1G/L Account Master (Company Code)Company code G/L account data (sensitive account rules)ReadECC + S/4
SWWWIHEADWorkflow Runtime: Work Item HeaderApproval work items and their statusReadECC + S/4

BAPIs and functions used

  • SAP_WAPI_START_WORKFLOWWorkflow: Start Workflow. Starts the approval workflow for the parked document
  • SO_DOCUMENT_SEND_API1SAPoffice: Send Document with Attachments. Sends email to the approver and the document owner
  • FI_DOCUMENT_READRead FI Document. Reads the document data for the approval screen

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_BUKRSCompany codeRange / multipleBKPF-BUKRSYes1000
S_BLARTDocument typeRange / multipleBKPF-BLARTNoSA, KR
S_BUDATPosting dateRange / multipleBKPF-BUDATYes01.11.2026 – 30.11.2026
S_USNAMEntered byRange / multipleBKPF-USNAMNoMUHASEBE01
P_OPENDocuments waiting for approvalRadio button—NoX
P_VIOLDocuments that bypassed approval (violation report)Radio button—No—

Result list columns

#ColumnSource
1Company codeBKPF-BUKRS
2Document numberBKPF-BELNR
3Document typeBKPF-BLART
4Posting dateBKPF-BUDAT
5Entered byBKPF-USNAM
6Document amountCalculated Sum of debit items (VBSEGS/BSEG-WRBTR, SHKZG = S)
7CurrencyBKPF-WAERS
8RuleCalculated Rule and level the document hit
9ApproverCalculated User at the next approval level
10StatusCalculated Waiting, approved, rejected or posted without approval (violation)
11Waiting (days)Calculated Today − parking date

Sample result list

Company codeDocument numberDocument typePosting dateEntered byDocument amountCurrencyRuleApproverStatusWaiting (days)
1000100004512SA28.11.2026MUHASEBE01420,000TRYAmount > approval limit, level 1MALIMUDURWaiting2
1000190001187KR27.11.2026MUHASEBE0286,500TRYSensitive account: consulting expensesMUHSEFIApproved0
2000100000931SA26.11.2026MUHASEBE031,250,000TRYAmount > approval limit, level 2-Posted without approval (violation)0
A view built with fictional sample data; not real system data.

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.

Performance notes

Run the rule check at save time on the document data in memory only, and buffer the rule table once per session. In the violation report read BSEG through BKPF with a date range and company code; run it in the background for long periods.

Features

  • ALV list (sort, filter, subtotals)
  • Send the result by email Notice to the approver, approval or rejection result to the document owner, and reminders for waiting approvals.
  • Line-by-line result and error log Every approval, rejection and reason is kept with user and time.
  • Runs as a background job The violation report and reminders run as periodic jobs.

Authorization objects

  • F_BKPF_BUKDocument posting and display authorization by company code
  • F_BKPF_BLAPosting authorization by document type
  • F_BKPF_KOAPosting authorization by account type
  • S_WF_WIAuthorization 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.

Related reports

FI Program Custom Mass upload

Mass G/L Journal Entry Upload from Excel

A custom program that posts multi-line G/L documents (accruals, reclassifications, allocation entries) in bulk from Excel or CSV rows. It checks every …

BKPF · BSEG · SKB1 · CSKS

FI Report Custom ALV report

Parked Documents Aging Report

A custom ALV report that lists parked accounting documents that are not yet posted by user, document type and waiting time. Before the period close it …

VBKPF · BKPF · VBSEGS · T001

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.

Related report: Accounting Document Approval and Posting Control