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
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| VBRKBilling Document Header | Billing header, posting status, amount and company code (driving table) | — | ECC + S/4 |
| VBRPBilling Document: Item Data | Billing items and reference sales order | VBRP-VBELN = VBRK-VBELN | ECC + S/4 |
| BKPFAccounting Document Header | Check whether an accounting document exists | BKPF-AWTYP = 'VBRK' AND BKPF-AWKEY = VBRK-VBELN AND BKPF-BUKRS = VBRK-BUKRS | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = VBRK-KUNAG | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBRK-VKORG | Yes | 1000 |
| S_BUKRS | Company code | Range / multiple | VBRK-BUKRS | No | 1000 |
| S_FKART | Billing type | Range / multiple | VBRK-FKART | No | F2 |
| S_FKDAT | Billing date range | Range / multiple | VBRK-FKDAT | Yes | 01.10.2026 – 31.10.2026 |
| S_KUNAG | Sold-to party | Range / multiple | VBRK-KUNAG | No | 200100 |
| S_RFBSK | Posting status | Range / multiple | VBRK-RFBSK | No | A, B |
| P_CANC | Exclude cancelled invoices | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Billing document | VBRK-VBELN |
| 2 | Billing type | VBRK-FKART |
| 3 | Billing date | VBRK-FKDAT |
| 4 | Company code | VBRK-BUKRS |
| 5 | Sold-to | VBRK-KUNAG |
| 6 | Customer name | KNA1-NAME1 |
| 7 | Reference order | VBRP-AUBEL |
| 8 | Net value | VBRK-NETWR |
| 9 | Tax | VBRK-MWSBK |
| 10 | Currency | VBRK-WAERK |
| 11 | Posting status | VBRK-RFBSK |
| 12 | Reason group | Calculated From RFBSK: A blocked, B account determination, F pricing, G foreign trade, H FI/CO inconsistency; RFBSK = C but no BKPF gives "document missing" |
| 13 | Waiting (days) | Calculated Today − VBRK-FKDAT |
| 14 | Created by | VBRK-ERNAM |
Sample output
| Billing document | Billing type | Billing date | Company code | Sold-to | Customer name | Reference order | Net value | Tax | Currency | Posting status | Reason group | Waiting (days) | Created by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 90008812 | F2 | 10/28/2026 | 1000 | 200100 | Marmara Gıda | 12088 | 84,500 | 16,900 | TRY | B | Account determination | 20 | FATURA01 |
| 90008830 | F2 | 10/30/2026 | 1000 | 200245 | Karadeniz Market | 12102 | 12,750 | 2,550 | TRY | A | Blocked for posting | 18 | FATURA02 |
| 90008907 | F8 | 11/03/2026 | 2000 | 300410 | Ege Tekstil Dış Ticaret | 12131 | 41,200 | 0 | EUR | G | Foreign trade data missing | 14 | FATURA01 |
| 90008944 | F2 | 11/05/2026 | 1000 | 200388 | Toros Yapı Market | 12150 | 6,380 | 1,276 | TRY | F | Pricing error | 12 | FATURA03 |
How does the report work?
- 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.
- 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.
- 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.
- 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).
- 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
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 …
Related reports
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 …
Scheduled Billing Job with Pre-Billing Checks and Hold List
A custom background job that bills goods-issued, unbilled deliveries at set times and runs customer-specific checks before billing. Deliveries that …
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.