← All SAP articles

A billing document can be commercially correct and still post to the wrong revenue account. That means the quantity, price and customer may be right while the FI derivation selected an unintended key combination.

SAP SD Account Determination: VKOA Configuration

Confirm which line is wrong

Separate revenue, discount, freight, tax and COGS. They do not all use the same determination logic. Identify the exact accounting line and the pricing condition that created it.

Trace the account key

Inspect the pricing procedure and condition record. Confirm the account key assigned to the relevant condition. If the wrong key is attached to the condition, VKOA may be working exactly as configured.

Verify the master-data groups

Check the customer account-assignment group and material account-assignment group used at billing time. A missing specific record can cause SAP to fall back to a more general VKOA access.

Use account-determination analysis

Record the access sequence SAP followed, the rows it rejected and the row it selected. Then compare chart of accounts, sales organization, customer group, material group and account key to the intended design.

Retest the complete flow

After correction, retest sales order, delivery, PGI, billing, cancellation and credit memo. Confirm both revenue and COGS and verify that another customer or product group was not affected.

The right fix changes the decision that was wrong. It does not simply force one invoice into a preferred G/L account.

Study the complete SD account-determination path