SD Report Custom development ALV report

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

  • VF05 List Billing Documents. Lists invoices by customer and date; does not compare with the order price or the delivered quantity.
  • VF03 Display Billing Document. Shows the items and pricing of a single invoice; does not check many invoices at once.

Tables used

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

TableRoleJoinSystem
VBRKBilling Document HeaderInvoice header: type, date, sold-to, currency, cancellation status (driving table)—ECC + S/4
VBRPBilling Document: Item DataInvoice item: billed quantity, net value, reference delivery and orderVBRP-VBELN = VBRK-VBELNECC + S/4
VBAPSales Document ItemOrder net price, price unit and order quantityVBAP-VBELN = VBRP-AUBEL AND VBAP-POSNR = VBRP-AUPOSECC + S/4
LIPSDelivery Item DataDelivered quantity (reference for delivery-related billing)LIPS-VBELN = VBRP-VGBEL AND LIPS-POSNR = VBRP-VGPOSECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = VBRK-KUNAGECC + S/4
I_BillingDocumentItemBilling Document ItemIn S/4HANA it can replace VBRP with a clean core approachBillingDocument = VBRK-VBELNS/4HANA only

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_VKORGSales organizationRange / multipleVBRK-VKORGYes1000
S_FKDATBilling date rangeRange / multipleVBRK-FKDATYes01.11.2026 – 17.11.2026
S_FKARTBilling typeRange / multipleVBRK-FKARTNoF2
S_KUNAGSold-to partyRange / multipleVBRK-KUNAGNo200100
S_MATNRMaterialRange / multipleVBRP-MATNRNoFG-1001
P_TOLPPrice tolerance (%)Single value—Yes0.5
P_QTYAlso show quantity differencesCheckbox—NoX
P_STORNExclude cancelled invoicesCheckbox—NoX

Output columns

#ColumnSource
1InvoiceVBRK-VBELN
2ItemVBRP-POSNR
3Billing dateVBRK-FKDAT
4Sold-toVBRK-KUNAG
5Customer nameKNA1-NAME1
6Sales orderVBRP-AUBEL
7MaterialVBRP-MATNR
8Reference qtyCalculated LIPS-LFIMG for delivery-related, VBAP-KWMENG for order-related billing
9Billed qtyVBRP-FKIMG
10Qty differenceCalculated VBRP-FKIMG − reference qty
11Order unit priceCalculated VBAP-NETPR ÷ VBAP-KPEIN
12Invoice unit priceCalculated VBRP-NETWR ÷ VBRP-FKIMG
13Price difference %Calculated (Invoice unit price − order unit price) ÷ order unit price × 100
14Value effectCalculated VBRP-NETWR − reference qty × order unit price
15CurrencyVBRK-WAERK
16Difference typeCalculated Price, quantity or price and quantity

Sample output

InvoiceItemBilling dateSold-toCustomer nameSales orderMaterialReference qtyBilled qtyQty differenceOrder unit priceInvoice unit pricePrice difference %Value effectCurrencyDifference type
9000912000001011/04/2026200100Marmara Gıda0000012388FG-10011,0001,000042.5040.80-4-1,700TRYPrice
9000913300002011/06/2026200388Toros Yapı Market0000012402FG-205050054040555502,200TRYQuantity
9000914100001011/10/2026200512Anadolu Toptan Gıda0000012430FG-1120300280-2062666.50-120TRYPrice and quantity
9000915800003011/12/2026200245Karadeniz Market Zinciri0000012455FG-33001201200310279-10-3,720TRYPrice
A view built with fictional sample data; not real system data.

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.

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

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

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 …

VBRK · VBRP · BKPF · KNA1

SD Report Custom ALV report

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 …

VBAK · VBAP · KNA1 · KONV

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: Price and Quantity Differences Between Sales Order and Invoice Report