Missing Intercompany Billing (IV) After Delivery

Finance reports that intercompany accounts receivable and payable between the selling company code and the delivering company code do not reconcile for a given period. Controlling in the delivering plant says a delivery went out and was goods-issued weeks ago but no revenue ever posted for that plant. The order desk insists the order is closed because the customer invoice went out and was paid, so from the sales rep's point of view nothing is wrong. When someone finally checks the billing due list for the internal document type, the delivery is simply not there, or it is there but returns an error the moment anyone tries to force it through. Nobody notices for a while because the customer-facing side of the process completed cleanly; the gap only shows up when the two company codes try to close their intercompany ledgers against each other at month end.

Intercompany billing depends on a chain of configuration that is independent of the customer-facing invoice, so the customer invoice succeeding proves nothing about the intercompany side.

Work from the delivery outward rather than from the order, since intercompany billing is delivery-related, not order-related.

Pull VF04 filtered on billing type IV and the sales organization and delivering plant in question, over the period in dispute, and compare the count against goods-issued deliveries for the same plant and sales organization pulled from delivery document flow. Any delivery that appears goods-issued but has no corresponding IV entry in VBFA is a confirmed gap. Cross-check the plant's internal customer assignment for that same sales organization; a blank entry there explains the entire population of gaps at once rather than one delivery at a time.

If the internal customer number is missing on the plant, this is master data maintenance in the plant/customer assignment table and can usually be corrected directly in the target system without a transport, though many landscapes lock this table and require a change request. If the item category billing relevance indicator or the VTFL copy control entry is wrong, that is IMG configuration and must move through development and be transported; do not hand-edit it directly in production unless local policy explicitly allows it. If the cause is a missing condition record for the internal pricing condition, that is master data and can be created with the standard condition maintenance transaction without a transport. If the sales organization and plant genuinely share a company code, close the complaint as expected behavior and explain to finance why no IV document will ever appear. After any config or master data fix, rerun the billing due list for the affected delivery; do not attempt to create the IV document manually with a hardcoded amount, since that bypasses the pricing and account determination the document is supposed to carry.

The common reflex is to open VF01, type the delivery number and billing type IV directly, and try to force the document through, sometimes typing in a manual price when pricing comes back blank. This can produce an intercompany invoice, but with a wrong or default internal price, or billed to a fallback customer that does not correctly represent the delivering company code. The document then posts, closing the visible gap, but the account determination and intercompany reconciliation are wrong underneath, which surfaces later as an unexplained variance at month end that is far harder to trace than the original missing document.

SD configuration owns the plant-to-internal-customer assignment, item category billing relevance, and copy control settings, since these require change requests and transports. Sales master data or finance typically owns the intercompany pricing condition records. The handover note should state the delivery number, the sales organization and plant combination affected, whether goods issue was confirmed, and which of the two config tables (plant assignment or copy control) was found empty, since both produce the identical symptom in VF04.