SAP SD Partial Delivery and Billing: Reconcile Quantities Step by Step

A sales order can be partly delivered, partly billed and still open. When a user says “the invoice quantity is wrong,” the first task is to identify which quantity they expected: ordered, confirmed, picked, goods-issued or invoiced. Each describes a different point in the order-to-cash process.

This SAP SD exercise reconciles one fictional standard, delivery-based billing item. It excludes returns, free goods, third-party sales, service billing and order-related billing. Those processes need their own rules. Use a training system and confirm the item category, billing relevance and copy-control settings before expecting this example to match your landscape.

Start with a single item and unit

Imagine a customer orders 100 pumps, all recorded in pieces. Stock arrives in two batches. The first outbound delivery contains 60 pieces and has completed post goods issue. A second delivery contains 25 pieces and also has completed goods issue. The remaining 15 pieces have not been delivered.

The first delivery has an active invoice for 60 pieces. The second has no invoice yet. Capture the order item, each delivery item and each billing item separately. Matching only the customer or material is unsafe because they may appear on many unrelated orders.

Fictional order item reconciliation, quantities in pieces
MeasureQuantityMeaning
Ordered100Total customer requirement
Goods-issued deliveries8560 plus 25
Active billed quantity60First delivery invoiced
Delivered, not billed2585 minus 60
Still undelivered15100 minus 85

The system records goods issue for 85 pieces, but the current invoice covers 60. That difference can be correct: delivery and billing are separate business events. In this simplified example, 15 pieces remain to be goods-issued, while the outstanding billing quantity for the goods-issued deliveries is 25. Calling both “pending quantity” hides the actual issue.

Trace document flow before changing anything

  1. Display the sales order item and note its quantity, unit, rejection reason and delivery and billing statuses.
  2. Follow document flow to the two outbound deliveries. Confirm the item reference, actual delivery quantity and goods-issue status.
  3. Follow each delivery to its billing documents. Record quantities, units, document types and cancellation references.
  4. Check the billing due list or equivalent application for the second delivery and read its processing log.
  5. Compare the result with a working item that uses the same relevant business configuration.

A delivery existing in document flow does not prove that goods issue is complete. Likewise, an invoice number does not by itself prove that the invoice remains active or has reached accounting. Record the status that supports each statement.

Investigate the 25 pieces awaiting billing

If the second delivery is eligible but absent from the billing selection, check selection dates and organisational filters before assuming a configuration defect. If processing fails, inspect blocks, incompletion, pricing and copy-control requirements. A billing block may be intentional and should follow the business release procedure.

If billing succeeds but no accounting document is available, investigate the accounting transfer separately. Quantity reconciliation and financial posting are connected, but a missing accounting document does not automatically mean that the delivery should be invoiced again.

Handle cancellation and unit conversion carefully

Suppose the 60-piece invoice is cancelled and replaced by another 60-piece invoice. Adding the two invoice quantities would incorrectly report 120 billed pieces. Identify the cancellation pair and count the valid economic outcome once. If a credit memo or return appears, expand the reconciliation to include its purpose rather than treating every negative document as an invoice cancellation.

Check units before subtracting quantities. If an invoice shows 6 boxes and each box contains 10 pieces, the comparable quantity is 60 pieces. Use the maintained conversion and document context; do not infer conversion from a material description.

Partial delivery and partial billing are different questions

Our example bills one complete 60-piece delivery while leaving another 25-piece delivery unbilled. That is different from asking SAP to invoice only 20 pieces out of a single 60-piece delivery item. SAP documents billing relevance K for supported delivery-related partial-quantity billing. Do not assume every delivery-related item permits arbitrary quantity changes during invoice creation.

Before practising the second scenario, ask the trainer to confirm the item’s billing relevance and the supported billing application. Batch-split items introduce further rules and are outside this simple exercise. Changing configuration to make an isolated test succeed can affect other orders, so establish the intended business process first.

Build a reconciliation that another person can verify

Use a fixed reporting cutoff, such as the end of the previous business day. Otherwise, one person may read delivery quantities before a posting while another reads billing quantities after it. Record when the comparison was made, which document dates were selected, and whether any later postings are excluded.

Create one worksheet row for each relevant document item. Include the preceding document and item, transaction quantity, original unit, converted quantity in pieces, goods-issue status, billing cancellation reference and accounting status. Retain the original unit alongside the converted number so the calculation remains traceable.

For this fictional case, a simple control is 100 ordered pieces = 85 goods-issued pieces + 15 still to be goods-issued. A second control is 85 goods-issued pieces = 60 actively billed pieces + 25 awaiting billing. These identities apply to the stated clean example. They are not a substitute for SAP’s open-quantity calculation when rejection, tolerances, reversals, additional deliveries or other special processes are involved.

Three variations to test your diagnosis

A delivery exists, but goods issue is not posted

If the 25-piece delivery is only prepared, the confirmed goods-issued total in this example is 60 pieces. Keep the prepared quantity in its own column. Describing all 85 pieces as goods-issued would overstate the completed logistics step. Check the process prerequisites before treating the unposted delivery as a billing failure.

The invoice exists, but accounting transfer failed

Record the invoice as an existing billing document and investigate its posting status. Save the exact accounting error and the responsible follow-up action. Creating another invoice merely to obtain an accounting document can produce additional reconciliation problems; first establish the state of the original billing document and its references.

The first invoice was cancelled yesterday

SAP’s cancellation process creates a linked cancellation document and can reopen the reference for billing. For an invoice already transferred to accounting, the corresponding cancellation also needs the appropriate accounting posting. Check both the billing chain and financial status before declaring the correction complete. In your worksheet, show the original, cancellation and replacement explicitly, while counting the valid outcome only once.

Questions to ask before closing the ticket

Does goods issue prove that the customer received the goods?

No. This exercise measures the goods-issue event in the system. Customer receipt or proof of delivery is a separate piece of evidence where the business process uses it. Use “goods-issued quantity” in your report unless receipt has independently been confirmed.

Does the final invoice have to match the original order quantity?

Not necessarily at every stage. In this example, deliveries occur in parts and billing follows eligible delivery quantities. The final commercial outcome also depends on what was ultimately supplied, rejected, returned or otherwise agreed. Explain the current stage and open follow-up instead of forcing every document to show 100 pieces.

Official SAP references

Review SAP’s billing-quantity explanation, Create Billing Documents guidance and billing cancellation documentation. Product editions and interfaces differ; match the reference to your training system.

Turn the example into a practice deliverable

Create a worksheet with document and item references, quantity, unit, status, reference document, selection date and evidence. Add one explanation for each difference. Try a cancelled invoice, an unposted delivery and a different billing selection date, then document the expected reconciliation before running the scenario.

Use the SAP SD billing types and copying-control guide to study document copying, and the SAP support ticket lifecycle project to structure investigation and closure evidence. Learners who want to connect these checks with the wider sales process can review SAP SD training in Vizag at Softenant. Ask about the available training-system version when planning this exercise.

Leave a Comment

Your email address will not be published. Required fields are marked *