# Price and Quantity Differences Between Sales Order and Invoice Report

> 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.

- Type: Report, Custom development, ALV report
- Module: SD
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/sales-order-vs-invoice-price-quantity-differences-report/


## 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.

### Closest standard alternatives

- VF05: Lists invoices by customer and date; does not compare with the order price or the delivered quantity.
- VF03: Shows the items and pricing of a single invoice; does not check many invoices at once.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| VBRK | Invoice header: type, date, sold-to, currency, cancellation status (driving table) | Read | - | ECC + S/4 |
| VBRP | Invoice item: billed quantity, net value, reference delivery and order | Read | VBRP-VBELN = VBRK-VBELN | ECC + S/4 |
| VBAP | Order net price, price unit and order quantity | Read | VBAP-VBELN = VBRP-AUBEL AND VBAP-POSNR = VBRP-AUPOS | ECC + S/4 |
| LIPS | Delivered quantity (reference for delivery-related billing) | Read | LIPS-VBELN = VBRP-VGBEL AND LIPS-POSNR = VBRP-VGPOS | ECC + S/4 |
| KNA1 | Customer name | Read | KNA1-KUNNR = VBRK-KUNAG | ECC + S/4 |
| I_BillingDocumentItem | In S/4HANA it can replace VBRP with a clean core approach | Read | BillingDocument = VBRK-VBELN | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_VKORG | Sales organization | Range / multiple | VBRK-VKORG | Yes |
| S_FKDAT | Billing date range | Range / multiple | VBRK-FKDAT | Yes |
| S_FKART | Billing type | Range / multiple | VBRK-FKART | No |
| S_KUNAG | Sold-to party | Range / multiple | VBRK-KUNAG | No |
| S_MATNR | Material | Range / multiple | VBRP-MATNR | No |
| P_TOLP | Price tolerance (%) | Single value | - | Yes |
| P_QTY | Also show quantity differences | Checkbox | - | No |
| P_STORN | Exclude cancelled invoices | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Invoice | VBRK-VBELN |
| Item | VBRP-POSNR |
| Billing date | VBRK-FKDAT |
| Sold-to | VBRK-KUNAG |
| Customer name | KNA1-NAME1 |
| Sales order | VBRP-AUBEL |
| Material | VBRP-MATNR |
| Reference qty | Calculated: LIPS-LFIMG for delivery-related, VBAP-KWMENG for order-related billing |
| Billed qty | VBRP-FKIMG |
| Qty difference | Calculated: VBRP-FKIMG − reference qty |
| Order unit price | Calculated: VBAP-NETPR ÷ VBAP-KPEIN |
| Invoice unit price | Calculated: VBRP-NETWR ÷ VBRP-FKIMG |
| Price difference % | Calculated: (Invoice unit price − order unit price) ÷ order unit price × 100 |
| Value effect | Calculated: VBRP-NETWR − reference qty × order unit price |
| Currency | VBRK-WAERK |
| Difference type | Calculated: Price, quantity or price and quantity |

## How does the report work?

1. 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.
2. 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.
3. Order unit price = VBAP-NETPR ÷ VBAP-KPEIN; invoice unit price = VBRP-NETWR ÷ VBRP-FKIMG.
4. 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.
5. 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.
6. The result is listed with subtotals per customer.

## Authorization objects

- V_VBRK_VKO: Billing document display authorization by sales organization
- V_VBRK_FKA: Authorization 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=sd-invoice-vs-order-price-qty-differences
