SD Report Custom development ALV report

Billing Documents Not Posted to Accounting Report

Short answer: A custom ALV report that lists billing documents which exist in SD but have no accounting document yet, with the reason code, age and amount. At month-end close, invoices missing from revenue are totalled by company code and error type, and every line drills down to the correction screen.

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

Why is the standard not enough?

VFX3 lists billing documents not passed to accounting per sales organization and lets you release them one by one, but it does not calculate how long they have been waiting, does not total account determination, pricing and foreign trade errors separately and does not give the tax-inclusive total per company code. It also does not check on the accounting side whether an FI document really exists (BKPF). Answering "which revenue is missing from the books and why" at the closing meeting needs a report that combines this information.

Who uses it? Billing teams, general ledger accounting and finance teams responsible for month-end close.

Closest standard alternatives

  • VFX3 List Blocked Billing Documents. Lists and releases invoices not passed to accounting; no waiting time, no totals by reason and no check against the FI document.
  • VF05 List Billing Documents. Lists invoices by customer and date; does not filter by posting status.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
VBRKBilling Document HeaderBilling header, posting status, amount and company code (driving table)—ECC + S/4
VBRPBilling Document: Item DataBilling items and reference sales orderVBRP-VBELN = VBRK-VBELNECC + S/4
BKPFAccounting Document HeaderCheck whether an accounting document existsBKPF-AWTYP = 'VBRK' AND BKPF-AWKEY = VBRK-VBELN AND BKPF-BUKRS = VBRK-BUKRSECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = VBRK-KUNAGECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_VKORGSales organizationRange / multipleVBRK-VKORGYes1000
S_BUKRSCompany codeRange / multipleVBRK-BUKRSNo1000
S_FKARTBilling typeRange / multipleVBRK-FKARTNoF2
S_FKDATBilling date rangeRange / multipleVBRK-FKDATYes01.10.2026 – 31.10.2026
S_KUNAGSold-to partyRange / multipleVBRK-KUNAGNo200100
S_RFBSKPosting statusRange / multipleVBRK-RFBSKNoA, B
P_CANCExclude cancelled invoicesCheckbox—NoX

Output columns

#ColumnSource
1Billing documentVBRK-VBELN
2Billing typeVBRK-FKART
3Billing dateVBRK-FKDAT
4Company codeVBRK-BUKRS
5Sold-toVBRK-KUNAG
6Customer nameKNA1-NAME1
7Reference orderVBRP-AUBEL
8Net valueVBRK-NETWR
9TaxVBRK-MWSBK
10CurrencyVBRK-WAERK
11Posting statusVBRK-RFBSK
12Reason groupCalculated From RFBSK: A blocked, B account determination, F pricing, G foreign trade, H FI/CO inconsistency; RFBSK = C but no BKPF gives "document missing"
13Waiting (days)Calculated Today − VBRK-FKDAT
14Created byVBRK-ERNAM

Sample output

Billing documentBilling typeBilling dateCompany codeSold-toCustomer nameReference orderNet valueTaxCurrencyPosting statusReason groupWaiting (days)Created by
90008812F210/28/20261000200100Marmara Gıda1208884,50016,900TRYBAccount determination20FATURA01
90008830F210/30/20261000200245Karadeniz Market1210212,7502,550TRYABlocked for posting18FATURA02
90008907F811/03/20262000300410Ege Tekstil Dış Ticaret1213141,2000EURGForeign trade data missing14FATURA01
90008944F211/05/20261000200388Toros Yapı Market121506,3801,276TRYFPricing error12FATURA03
A view built with fictional sample data; not real system data.

How does the report work?

  1. VBRK is read with the selection criteria; invoices whose posting status (RFBSK) is not C (accounting document created) or D (not relevant for accounting) are selected. Cancelled invoices (FKSTO = X) and cancellation documents can be excluded.
  2. For each invoice an accounting document is searched in BKPF with AWTYP = VBRK and AWKEY = billing number; invoices with RFBSK = C but no document found are also listed as inconsistencies.
  3. The RFBSK value is translated into a reason group: A blocked for posting, B account determination error, F pricing error, G foreign trade data missing, H inconsistency with FI/CO; other values are added as text from the domain values.
  4. The amount comes from VBRK-NETWR and the tax from VBRK-MWSBK; the waiting time is the number of days between today and the billing date (FKDAT).
  5. The reference sales order and the number of items are added from the billing items (VBRP); the customer name is read from KNA1. The ALV gives subtotals per company code and reason group.

Performance notes

Read VBRK with the billing date range and sales organization; the RFBSK filter keeps the selection small. Check BKPF in bulk (FOR ALL ENTRIES) with AWTYP + AWKEY instead of reading it once per invoice.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document Double-clicking the invoice opens VF03; clicking the status column opens VFX3 for the same invoice.
  • Export to Excel
  • Runs as a background job
  • Send the result by email Can be sent to the billing and accounting teams every morning during the last three days of the month.

Authorization objects

  • V_VBRK_VKOBilling document authorization by sales organization
  • V_VBRK_FKAAuthorization by billing type

Frequently asked questions

Why does an invoice stay unposted?

The most common reasons are missing account determination (no revenue account found), a posting block defined on the billing type, a pricing error and missing foreign trade data on export invoices. The report puts every invoice into one of these groups.

Can the report post the invoices to accounting itself?

The standard version only reads. A button that releases the selected lines in bulk, the way VFX3 does, can be added once the error is fixed; change authorization is then checked separately.

Does this report work on S/4HANA?

Yes. VBRK-RFBSK and the link to BKPF are the same on S/4HANA; the accounting line items live in ACDOCA, but the document header check can still be done with BKPF.

Packages that include this solution

SD Package Custom

Pricing and Billing Accuracy Pack

A five-component pack that catches pricing and billing errors from loading the price list to posting the invoice: mass price condition upload from …

5 components · v1.0

Related reports

SD Report Custom ALV report

Sales Order – Delivery – Invoice Status Report

A custom ALV report that shows every sales order item on the same line as its delivery and invoice documents. You see in one list which orders have …

VBAK · VBAP · VBFA · LIKP

Let us build this report 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: Billing Documents Not Posted to Accounting Report