Price and Quantity Differences Between Sales Order and Invoice Report
Short answer: A custom ALV report that compares the invoiced unit price with the net price on the sales order, and the invoiced quantity with the delivered or ordered quantity, and lists the items outside the tolerance together with their value effect. Billing and sales teams find wrongly priced or under- and over-billed items before the customer disputes them.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
VF05 shows invoices and VF03 the items of a single invoice; neither compares the invoiced price with the order price or the invoiced quantity with the delivered quantity. When the pricing date changes on the invoice, copy control triggers new pricing or someone changes the invoice manually, the difference is only noticed when the customer disputes it. The custom report matches every invoice item with its source and shows the amount of the difference.
Who uses it? Billing teams, sales operations, receivables management and internal audit.
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 | Invoice header: type, date, sold-to, currency, cancellation status (driving table) | — | ECC + S/4 |
| VBRPBilling Document: Item Data | Invoice item: billed quantity, net value, reference delivery and order | VBRP-VBELN = VBRK-VBELN | ECC + S/4 |
| VBAPSales Document Item | Order net price, price unit and order quantity | VBAP-VBELN = VBRP-AUBEL AND VBAP-POSNR = VBRP-AUPOS | ECC + S/4 |
| LIPSDelivery Item Data | Delivered quantity (reference for delivery-related billing) | LIPS-VBELN = VBRP-VGBEL AND LIPS-POSNR = VBRP-VGPOS | ECC + S/4 |
| KNA1Customer Master (General Section) | Customer name | KNA1-KUNNR = VBRK-KUNAG | ECC + S/4 |
| I_BillingDocumentItemBilling Document Item | In S/4HANA it can replace VBRP with a clean core approach | BillingDocument = VBRK-VBELN | S/4HANA only |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBRK-VKORG | Yes | 1000 |
| S_FKDAT | Billing date range | Range / multiple | VBRK-FKDAT | Yes | 01.11.2026 – 17.11.2026 |
| S_FKART | Billing type | Range / multiple | VBRK-FKART | No | F2 |
| S_KUNAG | Sold-to party | Range / multiple | VBRK-KUNAG | No | 200100 |
| S_MATNR | Material | Range / multiple | VBRP-MATNR | No | FG-1001 |
| P_TOLP | Price tolerance (%) | Single value | — | Yes | 0.5 |
| P_QTY | Also show quantity differences | Checkbox | — | No | X |
| P_STORN | Exclude cancelled invoices | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Invoice | VBRK-VBELN |
| 2 | Item | VBRP-POSNR |
| 3 | Billing date | VBRK-FKDAT |
| 4 | Sold-to | VBRK-KUNAG |
| 5 | Customer name | KNA1-NAME1 |
| 6 | Sales order | VBRP-AUBEL |
| 7 | Material | VBRP-MATNR |
| 8 | Reference qty | Calculated LIPS-LFIMG for delivery-related, VBAP-KWMENG for order-related billing |
| 9 | Billed qty | VBRP-FKIMG |
| 10 | Qty difference | Calculated VBRP-FKIMG − reference qty |
| 11 | Order unit price | Calculated VBAP-NETPR ÷ VBAP-KPEIN |
| 12 | Invoice unit price | Calculated VBRP-NETWR ÷ VBRP-FKIMG |
| 13 | Price difference % | Calculated (Invoice unit price − order unit price) ÷ order unit price × 100 |
| 14 | Value effect | Calculated VBRP-NETWR − reference qty × order unit price |
| 15 | Currency | VBRK-WAERK |
| 16 | Difference type | Calculated Price, quantity or price and quantity |
Sample output
| Invoice | Item | Billing date | Sold-to | Customer name | Sales order | Material | Reference qty | Billed qty | Qty difference | Order unit price | Invoice unit price | Price difference % | Value effect | Currency | Difference type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 90009120 | 000010 | 11/04/2026 | 200100 | Marmara Gıda | 0000012388 | FG-1001 | 1,000 | 1,000 | 0 | 42.50 | 40.80 | -4 | -1,700 | TRY | Price |
| 90009133 | 000020 | 11/06/2026 | 200388 | Toros Yapı Market | 0000012402 | FG-2050 | 500 | 540 | 40 | 55 | 55 | 0 | 2,200 | TRY | Quantity |
| 90009141 | 000010 | 11/10/2026 | 200512 | Anadolu Toptan Gıda | 0000012430 | FG-1120 | 300 | 280 | -20 | 62 | 66 | 6.50 | -120 | TRY | Price and quantity |
| 90009158 | 000030 | 11/12/2026 | 200245 | Karadeniz Market Zinciri | 0000012455 | FG-3300 | 120 | 120 | 0 | 310 | 279 | -10 | -3,720 | TRY | Price |
How does the report work?
- VBRK is read by sales organization, billing date and billing type; with “Exclude cancellations” selected, cancelled invoices (VBRK-FKSTO = X) and cancellation documents (VBRK-SFAKN filled) are skipped.
- The source of each VBRP item is found: for delivery-related billing the reference quantity is LIPS-LFIMG through VBRP-VGBEL/VGPOS, for order-related billing it is VBAP-KWMENG through VBRP-AUBEL/AUPOS. If the sales units differ, a conversion is applied.
- Order unit price = VBAP-NETPR ÷ VBAP-KPEIN; invoice unit price = VBRP-NETWR ÷ VBRP-FKIMG.
- Price difference % = (invoice unit price − order unit price) ÷ order unit price × 100; items whose absolute value is below the tolerance are skipped. Quantity difference = VBRP-FKIMG − reference quantity.
- Value effect = VBRP-NETWR − reference quantity × order unit price. The difference type is set to price, quantity or both; if the pricing date (VBRP-PRSDT) differs from the order, this is shown in the message column.
- The result is listed with subtotals per customer.
Performance notes
Narrow VBRK by billing date and sales organization. Read LIPS and VBAP once by item key with FOR ALL ENTRIES. For the monthly check, run the report in the background before month-end closing.
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 order opens VA03.
- Export to Excel
- Runs as a background job
- Send the result by email Items outside the tolerance can be emailed to the billing team every day.
Authorization objects
- V_VBRK_VKOBilling document display authorization by sales organization
- V_VBRK_FKAAuthorization by billing type
Frequently asked questions
Why would the order price and the invoice price differ?
The most common causes are a pricing date taken from the billing date with a new price condition starting in between, a pricing type in copy control that re-prices, and manual condition changes on the invoice. The report shows a pricing date difference separately.
What does the value effect show?
The difference between the invoiced net value and the reference quantity multiplied by the order price. A positive value means the customer was over-billed, a negative value means under-billed; price and quantity differences act together on the same line.
Does the report work on S/4HANA?
Yes. VBRK, VBRP, VBAP and LIPS keep the same structure in S/4HANA; if pricing details are needed, PRCD_ELEMENTS is read instead of KONV. For clean core, I_BillingDocumentItem can be used.
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
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 …
Customer and Material Price Conditions with Validity Dates Report
A custom ALV report that lists customer-specific price conditions in one list with their validity dates, the difference to the list price and the …
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.