Project Revenue vs Sales Order Billing Reconciliation Report
Short answer: A custom ALV report that shows, on one row per billing WBS element, the differences between the sales order value, the amount invoiced and the revenue posted to the project. Project control and accounting teams catch billing documents not passed to accounting, revenue that went to another WBS element and the remaining unbilled amount before month end.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 10
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
CJI3 shows the revenue line items posted to the project but does not compare them with the sales order item value and the billing documents. The VA03 document flow shows the invoices of a single order. The reason for a difference between billed amount and project revenue (billing not passed to accounting, posting to another WBS, direct FI revenue) does not appear together in any standard list. The custom report reconciles the three sources per WBS element.
Who uses it? Project control teams, project accounting, sales operations and finance managers.
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 |
|---|---|---|---|
| PRPSWBS Element Master Data | Billing WBS elements (driving table) | — | ECC + S/4 |
| PROJProject Definition | Project definition | PROJ-PSPNR = PRPS-PSPHI | ECC + S/4 |
| VBAPSales Document Item | Sales order item assigned to the WBS element and its net value | VBAP-PS_PSP_PNR = PRPS-PSPNR | ECC + S/4 |
| VBAKSales Document Header | Order header: customer and sales organization | VBAK-VBELN = VBAP-VBELN | ECC + S/4 |
| VBRPBilling Document: Item Data | Billing items created for the order item | VBRP-AUBEL = VBAP-VBELN AND VBRP-AUPOS = VBAP-POSNR | ECC + S/4 |
| VBRKBilling Document Header | Billing header: cancellation, document category and accounting transfer status | VBRK-VBELN = VBRP-VBELN | ECC + S/4 |
| COSPCO Object: Cost Totals for External Postings | Actual revenue posted to the project (revenue cost elements, WRTTP 04) | COSP-OBJNR = PRPS-OBJNR | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = VBAK-KUNNR | ECC + S/4 |
| I_SalesOrderItemSales Order Item | CDS view that can replace VBAP in S/4HANA | SalesOrder = VBAP-VBELN AND SalesOrderItem = VBAP-POSNR | S/4HANA only |
| I_BillingDocumentItemBilling Document Item | Can replace VBRP in S/4HANA | BillingDocument = VBRP-VBELN | S/4HANA only |
S/4HANA notes
- COSP → ACDOCA: In S/4HANA COSP is a view, not a table; actual totals are calculated from ACDOCA.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_PSPID | Project | Range / multiple | PROJ-PSPID | Yes | P-26015 |
| S_POSID | WBS element | Range / multiple | PRPS-POSID | No | P-26015* |
| S_PBUKR | Company code | Range / multiple | PRPS-PBUKR | Yes | 1000 |
| S_VKORG | Sales organization | Range / multiple | VBAK-VKORG | No | 1000 |
| S_KUNNR | Customer | Range / multiple | VBAK-KUNNR | No | 200150 |
| S_KSTAR | Revenue cost elements | Range / multiple | COSP-KSTAR | Yes | 800000–809999 |
| S_GJAHR | Fiscal year | Range / multiple | COSP-GJAHR | No | 2026 |
| P_DIFF | Differences only | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | WBS element | PRPS-POSID |
| 2 | Description | PRPS-POST1 |
| 3 | Sales order | VBAP-VBELN |
| 4 | Item | VBAP-POSNR |
| 5 | Customer | VBAK-KUNNR |
| 6 | Customer name | KNA1-NAME1 |
| 7 | Order value | VBAP-NETWR |
| 8 | Billed | Calculated Σ VBRP-NETWR (not cancelled; returns and credit memos negative) |
| 9 | Project revenue | Calculated −Σ COSP actual (WRTTP 04), revenue cost elements |
| 10 | Difference | Calculated Billed − project revenue |
| 11 | Remaining unbilled | Calculated VBAP-NETWR − billed |
| 12 | Currency | VBAP-WAERK |
| 13 | Invoices not posted | Calculated Number of invoices with VBRK-RFBSK ≠ C |
| 14 | Check result | Calculated Matched, invoice not posted, billed to another WBS or direct FI revenue |
Sample output
| WBS element | Description | Sales order | Item | Customer | Customer name | Order value | Billed | Project revenue | Difference | Remaining unbilled | Currency | Invoices not posted | Check result |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| P-26015-01 | Engineering service | 0000081240 | 000010 | 200150 | Anadolu Enerji | 2,400,000 | 1,600,000 | 1,600,000 | 0 | 800,000 | TRY | 0 | Matched |
| P-26015-04 | Equipment delivery | 0000081240 | 000020 | 200150 | Anadolu Enerji | 5,100,000 | 3,060,000 | 2,040,000 | 1,020,000 | 2,040,000 | TRY | 1 | Invoice not posted |
| P-26022-01 | Site services | 0000081305 | 000010 | 200218 | Trakya Altyapı | 950,000 | 475,000 | 520,000 | -45,000 | 475,000 | TRY | 0 | Direct FI revenue |
| P-26031-02 | Commissioning | 0000081377 | 000010 | 200301 | Karadeniz Tesis | 380,000 | 190,000 | 0 | 190,000 | 190,000 | EUR | 0 | Billed to another WBS |
How does the report work?
- PROJ and PRPS are read by project, WBS element and company code; only billing elements (PRPS-FAKKZ = X) are taken.
- Sales order items assigned to the WBS element are found via VBAP-PS_PSP_PNR; rejected items (ABGRU filled) are skipped. The customer comes from VBAK and KNA1.
- Billing documents are read via VBRP-AUBEL/AUPOS; cancelled documents (VBRK-FKSTO) are skipped and returns and credit memos (VBRK-VBTYP) are totalled with a negative sign. Documents not passed to accounting (VBRK-RFBSK ≠ C) are counted separately.
- Project revenue comes from the COSP actuals (WRTTP 04) of the selected revenue cost elements; the sign is reversed because revenue is a credit posting.
- Difference = billed − project revenue; remaining = order value − billed. If the billing WBS (VBRP-PS_PSP_PNR) differs from the order WBS, a “billed to another WBS” flag is set. The check result column states the likely reason for the difference.
Performance notes
Narrow the PRPS selection by project and FAKKZ. If there is no secondary index for reading VBAP via PS_PSP_PNR, read orders with a VBAK/VBAP JOIN and a sales organization filter. Restrict COSP by the revenue cost element range and fiscal year.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the order opens VA03; double-clicking the project revenue opens CJI3.
- Export to Excel
- Runs as a background job
- Send the result by email Rows with differences can be sent to project accounting before month-end close.
Authorization objects
- C_PROJ_KOKProject display authorization by controlling area
- V_VBAK_VKOSales order display authorization by sales organization
- V_VBRK_VKOBilling document display authorization by sales organization
Frequently asked questions
Why are revenue cost elements asked on the selection screen?
Both costs and revenues are posted to the project, and revenue is separated by revenue-type cost elements. Because the range depends on the chart of accounts, these elements are given on the selection screen or in a variant; the report totals only those as revenue.
What about projects with results analysis (revenue accrual)?
With results analysis, the project may carry a revenue value different from billing. In that case the report is extended to show billing revenue and the results analysis value in separate columns, so the reason for the difference stays clear.
How is this reconciliation done on S/4HANA?
In S/4HANA revenue is written to ACDOCA; COSP can be read as a compatibility view or ACDOCA can be totalled directly by WBS element and account. For orders and billing, the CDS views I_SalesOrderItem and I_BillingDocumentItem can be used.
Packages that include this solution
Project Closing Control Pack
A five-component pack for closing projects without leaving open items behind: a technical completion readiness check, reconciliation of project …
Related reports
Billing Milestones Reached but Not Invoiced Report
A custom ALV report that lists completed project milestones, those with an actual date, whose billing plan date in the sales order is still not …
Billing Documents Not Posted to Accounting Report
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 …
Sales Order Gross Margin Report by Item
A custom ALV report that compares the net value of every sales order item with the cost determined in pricing and shows the gross profit and margin …
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.