SD / O2Cintermediate

SD Billing Part 3: Revenue Account Determination (VKOA)

Key takeaway

How billing finds G/L accounts: account keys from the pricing procedure, the KOFI condition type and access sequence, account assignment groups for customer and material, VKOA tables, posting errors when accounts are missing, and how to design account determination with finance.

Explanation

📌 KEY POINTS
✅ Each revenue-relevant pricing line has an account key (ERL revenue, ERS deductions, ERF freight, MWS tax…).
✅ Revenue account determination uses condition technique: procedure KOFI00, condition type KOFI (KOFK with CO), access sequence, tables.
✅ Typical key: chart of accounts + sales org + customer account assignment group + material account assignment group + account key → G/L.
✅ Customer account assignment group comes from customer sales data (billing tab), material's from sales org 2 view.
⚠️ A missing VKOA entry blocks the invoice from posting ("account determination error").

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured billing types. Now the accounts behind the postings.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ACCOUNT KEYS

Assigned per line in the pricing procedure (V/08).
Group conditions to revenue streams: revenue, deductions, freight, tax, accruals.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DETERMINATION PROCEDURE

Billing type → account determination procedure (KOFI00).
Condition type KOFI with access sequence (e.g. KOFI: most specific tables first).

━━━━━━━━━━━━━━━━━━━━
▶ 3. TABLES (VKOA)

001: customer group / material group / account key.
002: customer group / account key.
003: material group / account key.
004: general / account key.
005: account key only.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MASTER DATA INPUTS

Customer account assignment group (e.g. 01 domestic, 02 foreign, 03 affiliated).
Material account assignment group (e.g. 01 trading goods, 02 services).
Missing groups → most specific table not found → fallback or error.

━━━━━━━━━━━━━━━━━━━━
▶ 5. ERRORS AND RELEASE

Missing entry → billing document saved with posting status "account determination error".
Fix VKOA/master data, then release (VFX3 / VF02).

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Define account assignment groups with finance.
Maintain VKOA entries for all combinations in use.
Check account keys in the pricing procedure.
Post invoices for each combination and review.

✅ CHECKPOINT: domestic, export and affiliated customers post to the agreed revenue accounts.

Code example

ABAP Code

===== STEP 1: account keys (V/08) =====ERL revenue | ERS sales deductions | ERF freight revenue | MWS output tax | ERU rebate accruals ===== STEP 2: VKOA entries (table 001: CustGrp/MatGrp/AcctKey) =====ChAc | SOrg | AcctAsgGrCust | AcctAsgGrMat | ActKey | G/LYCOA | 1000 | 01 domestic   | 01 goods     | ERL    | 41000000YCOA | 1000 | 02 export     | 01 goods     | ERL    | 41100000YCOA | 1000 | 03 affiliated | 01 goods     | ERL    | 41200000YCOA | 1000 | 01            | 01           | ERS    | 44000000 ===== STEP 3: master data =====BP > sales area > Billing > Account assignment group (KNVV-KTGRD)MM02 > Sales: Sales Org 2 > Account assignment group (MVKE-KTGRM) ===== STEP 4: errors =====VFX3 billing documents blocked for accounting → fix VKOA → release

Real project scenario

After launching a new product line, the nightly billing run produced 900 invoices with "account determination error". The new materials had no account assignment group in the sales org 2 view, so VKOA's material-dependent table was not found and no fallback entry existed. The team maintained the group (mass change), released the invoices via VFX3, and added the field as mandatory in material creation for sellable materials.

Common mistakes

Missing account assignment groups on customers or materials.
New account keys without VKOA entries.
No fallback table in the access sequence.
Designing accounts without finance.
Releasing blocked invoices without fixing the cause.

Best practices

Agree revenue account structure with finance.
Make account assignment groups mandatory in master data processes.
Maintain VKOA for all combinations and account keys.
Monitor VFX3 daily.
Test postings for each customer/material group.

Interview angle

Questions: "How does revenue account determination work?", "Where do account assignment groups come from?", "What happens if VKOA is missing?"
Strong answer: account keys in pricing procedure; KOFI00/KOFI condition technique; VKOA tables with chart of accounts, sales org, customer and material account assignment groups and account key; master data sources; missing entries block posting, fix and release via VFX3.

Practice this lesson

Quick check

1. Invoices for a new product line stop with "account determination error". What is a typical cause?

2. Which inputs typically determine the revenue G/L account in VKOA?

3. In revenue account determination for billing documents, which combination of elements ultimately determines the G/L account posted to?

Interview questions

1. A customer complains that their invoice posted revenue to the wrong G/L account after a material was reclassified into a new account assignment group. How would you use the condition technique in VKOA to diagnose and correct this?

Answer it in your own words first, then compare.

2. During a billing run, invoices for a new product line are failing revenue account determination with an error indicating no valid condition record found in VKOA. What integration points would you check to resolve this systematically?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.