ERPClimb logoERPClimb

SAP SD / O2C Billing Interview Questions

Interviewers use billing to test depth rather than coverage: the follow-up question is almost always "why does the system behave that way?", and that is where prepared answers usually run out.

Billing is the SD process step that converts confirmed deliveries or sales order services into customer-facing financial documents (invoices, credit/debit memos, pro forma invoices), triggering revenue recognition, FI/CO posting, and downstream accounts receivable processing. This topic covers billing document types, creation methods, copy control, pricing redetermination, output, and integration with FI, CO, and S/4HANA innovations.

This page carries 27 reviewed SAP SD / O2C billing interview questions, each with a complete written answer and no sign-in required. The set breaks down into 5 foundational, 16 mid-level and 6 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

If you can handle every question here without hesitating, billing is unlikely to be what costs you an SAP SD / O2C interview — and the same reasoning pattern transfers to the neighbouring topics linked at the bottom of this page.

27 Billing questions with answers

easyBilling

1. How does SD billing integrate with FI-AR to trigger revenue posting, and what is the role of the account determination procedure in this flow?

When a billing document is released to accounting, SD calls the revenue account determination procedure (typically KOFI/KOFI00) via VKOA condition records to derive G/L accounts for revenue, discounts, and tax. The system creates an accounting document (BKPF/BSEG, and ACDOCA in S/4HANA) posting to customer reconciliation account and revenue accounts based on condition type, account key, chart of accounts, sales org, and account assignment group of customer/material.
easyBilling

2. What is the difference between periodic billing plans and milestone billing plans in SD, and when would you use each?

Periodic billing plans generate repeated invoices at fixed intervals for the same full or partial value, typically used for rentals, maintenance contracts, or subscriptions. Milestone billing plans split a total order value across specific project milestones (e.g., down payment, delivery, completion), each billed independently based on completion status. Periodic plans use date-based determination; milestone plans link billing dates to project/network activities or manual milestone confirmation, common in project-based sales (make-to-order, plant engineering).
easyBilling

3. What is the business purpose of an invoice list in SD, and which condition type is typically used to calculate the factoring discount on it?

An invoice list (VF21) consolidates multiple individual invoices for one payer into a single summarized document, usually for retail chains or distributors with central billing. It reduces payment processing overhead and often triggers a factoring discount, calculated using condition type RL00, which credits the payer for early or consolidated settlement. The invoice list references the original invoices without reversing them.
easyBilling

4. What is the business purpose of a pro forma invoice in SD, and why does it not create an entry in FI-AR?

A pro forma invoice is a non-FI-relevant billing document used to give customers pricing, quantity, and value information ahead of actual delivery or billing, typically for customs clearance, letters of credit, or advance payment arrangements. It is configured with billing type F5/F8 (or copies) that have the 'no accounting document' setting active, so no revenue posting, no update to the customer's open item balance, and no credit exposure change occurs.
easyBilling

5. What is the difference between a debit memo billing type and a credit memo billing type in SD, and how does the system determine which one to use?

Debit memo (e.g., F2/DR) increases the customer's receivable, typically issued for underbilling or additional charges via a debit memo request; credit memo (e.g., G2/CR) reduces the receivable, issued for price corrections, returns, or overbilling via a credit memo request. The billing type is derived from the sales document type of the preceding request document (copy control), and posts with reversed +/- sign in FI-AR compared to standard invoices.
mediumBilling

6. Billing documents created from a specific delivery type are posting revenue to an unexpected GL account compared to other delivery types using the same sales order type. What VKOA-related root causes would you investigate?

Since VKOA determination keys typically use account assignment group of customer/material, account key, chart of accounts, and sales organization—not delivery type directly—I'd check whether the delivery type drives a different billing type or item category via copy control, which in turn changes the account key assigned in the pricing procedure. I'd also verify if the delivery-specific billing document uses a different document pricing procedure or if item category determination differs, altering which condition types (and thus account keys) are active.
mediumBilling

7. 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?

I would check VKOA access sequence: typically account determination uses combination of application (V), condition type (KOFI), chart of accounts, sales org, account assignment group of customer and material, and account key. Since material reclassification changed the account assignment group of material, existing condition records under the old combination no longer match; I'd verify material master Sales: Gen/Plant data or Accounting view for the assigned group, then create/correct VKOA entries for the new combination, and reprocess future invoices - correcting already-posted documents requires FI adjustment, not VKOA change.
mediumBilling

8. In configuring a periodic billing plan for a rental contract, what are the key configuration elements you must set up, and how does the system generate billing due dates?

You configure a billing plan type in customizing (date category, horizon, start/end rules) and assign it to the item category via the billing plan determination. Date rules define the periodicity (monthly, quarterly) and offset from contract start. Billing plan lines are generated in the sales document (VBEP/FPLA) based on horizon settings, and each due date triggers a billing block release for VF01 processing when the date is reached, either individually or via collective billing.
mediumBilling

9. 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?

I would check that the new material's account assignment group is maintained in the material master and matches an existing VKOA condition table entry combined with chart of accounts, sales organization, account assignment group of customer, and account key (ERL/ERS/ERF). I would also confirm the access sequence for that condition table is assigned to the account determination procedure linked to the billing type, and validate GL accounts exist and are not blocked for posting in that company code.
mediumBilling

10. A customer complains that revenue postings for a billing document went to the wrong G/L account after a new material was launched. How would you investigate and resolve this?

First check the billing document's account determination analysis (VF02, Environment > Account determination analysis) to see which VKOA entry was hit. Verify the new material's account assignment group in the material master matches expectations, and confirm VKOA has a specific entry for that combination rather than falling back to a generic default. Also check if a new sales org/distribution channel combination was introduced without corresponding VKOA maintenance. Correct by adding the missing VKOA entry and, if postings already occurred, coordinate an FI reclassification.
mediumBilling

11. After Post Goods Issue (PGI), the cost of goods sold posting hits the wrong GL account for a specific material/plant combination, but revenue account determination via VKOA appears correctly configured. What would you investigate?

Since PGI-triggered COGS postings come from MM/inventory valuation (material master accounting view, valuation class, and OBYC account assignment) rather than VKOA which governs SD revenue/receivable accounts, I would check the material's valuation class and the OBYC GBB/BSX account assignment for that valuation class and plant/valuation area, not VKOA. VKOA correctness for revenue doesn't affect COGS posting since these are two separate account determination paths—one SD-driven for billing, one MM/FI-driven for goods movement.
mediumBilling

12. A construction equipment company sells long-term service contracts and wants milestone-based invoicing tied to project completion percentages, with output triggering only after each milestone billing document is created. How would you configure this?

Configure a milestone billing plan (billing plan type in the sales document item) linked to project milestones, storing planned dates and percentages in table FPLA/FPLT. Each milestone generates a billing due item that is released for VF01 processing once the milestone is confirmed complete (often via project system status or manual release). Output determination is configured at billing type level so the invoice output (e.g., print/EDI) triggers only after successful billing document creation, not at billing plan creation.
mediumBilling

13. What key configuration settings on a billing document type control how it behaves during invoice creation and posting to FI, and how would you configure a credit memo billing type to differ from a standard invoice?

Billing type configuration (VOFA) controls the SD document category, negative posting indicator, account determination procedure, cancellation billing type link, output determination procedure, and whether it is relevant for rebates or intercompany. For a credit memo type, you set the SD document category to credit memo and typically enable negative posting so amounts reduce receivables correctly, while keeping pricing procedure determination consistent with the originating request.
mediumBilling

14. A customer expects a consolidated invoice list combining multiple individual invoices, but the invoice list is not picking up all eligible billing documents. What are the common configuration and master data causes?

Invoice lists (RD/RD or LR document types) require that the payer's customer master has invoice list scheduling maintained (factory calendar for invoice list dates), and the individual billing documents must share the same payer and be within the same invoice list date. Also check that the invoice list type (billing type) is assigned correctly to the sales area, and that the billing documents haven't already been included in a prior list. Missing invoice list condition records for rebate/factoring surcharge (if used) can also cause exclusion of documents from the run (VF21/VF24).
mediumBilling

15. What configuration steps are required to enable invoice lists in SD, and how does this feature interact with FI-AR customer statements?

Invoice lists are configured via output determination for invoice list type (LR) and customer master factory calendar for invoice list dates, plus condition type RL00 for invoice list surcharge. Payer must be flagged for invoice list processing in customer master (Billing tab), and billing documents are grouped by invoice list date using VF21/VF24. FI-AR receives one net invoice list document referencing individual billing docs, simplifying dunning and payment matching, though it does not replace standard AR open item processing.
mediumBilling

16. A customer requests a pro forma invoice before goods delivery so they can arrange import financing. Walk through how this is handled in SD and clarify what does and does not happen in FI-AR.

Create a pro forma invoice using billing type F5/F8 with reference to the sales order or delivery. Pro forma documents are billing-relevant for document flow and pricing display purposes but are configured as not relevant for accounting document creation, so no posting occurs in FI-AR, no accounting document number is generated, and it does not affect customer credit exposure calculation for open AR. Once actual goods issue and standard billing occur later, the real invoice posts normally.
mediumBilling

17. A billing document posts revenue to an unexpected G/L account even though the pricing procedure and condition values appear correct. Where would you investigate first, and why?

I would check VKOA account determination first, since pricing procedure correctness does not guarantee correct G/L posting — that depends on the account determination procedure's key combination (chart of accounts, sales org, account assignment group for customer/material, and account key from the condition type). A mismatch in account assignment groups on the customer or material master, or an incorrect account key mapping in the pricing procedure, is the most common root cause.
mediumBilling

18. A new billing type configured as a copy of F2 is posting revenue to the wrong revenue account for a specific customer group, while other billing types post correctly. What would you investigate in the billing type and account determination configuration?

I'd first confirm the billing type's account determination procedure assignment is correctly copied and linked, then check VKOA entries for the account determination procedure, specifically whether account assignment group for the customer group in question is missing or mapped to a wrong G/L account. I'd also review whether the new billing type uses a different document pricing procedure that changes which condition types feed revenue account determination, and check copy control settings from delivery/order to this new billing type for pricing type overrides.
mediumBilling

19. After warehouse staff complete packing, billing documents post to an incorrect revenue GL account only for deliveries with partially picked/packed quantities, while fully packed deliveries post correctly through the same billing type. How would you use VKOA account determination analysis to diagnose this discrepancy?

Run account determination analysis on the billing document to see which condition table and access were used for the affected line items, and compare the account assignment group for the material and customer used in the partial delivery scenario versus the full quantity scenario. Check if partial quantity confirmation changes item category (e.g., triggers a different pricing type or account assignment group due to split items), since VKOA derives GL accounts using account assignment group, chart of accounts, and condition table fields that could differ between full and partial deliveries.
mediumBilling

20. A billing document posts revenue to an incorrect GL account for one specific material, while all other materials in the same order post correctly. How do you investigate and resolve this using account determination analysis?

I would run account determination analysis from the billing document (Environment/Account Determination Analysis) to see which condition table and access sequence matched for the account assignment group of that material. Likely the material's account assignment group in the material master is set incorrectly, or a specific condition record combination (chart of accounts, sales org, account assignment group of customer/material) points to a different GL account than expected. Correct the material master field or maintain the proper VKOA condition record.
mediumBilling

21. Walk through how account determination (VKOA) resolves the G/L account for a billing document line item, including the key condition table fields typically used.

During billing, the account determination procedure (e.g., KOFI00) executes access sequences against condition tables using fields like application (V), chart of accounts, sales organization, account assignment group for customer and material, and account key from the pricing procedure. SAP searches tables from most specific to most general until a match is found in VKOA, returning a G/L account. If no entry matches, the billing document errors with an account determination failure requiring master data or VKOA maintenance.
hardBilling

22. In a complex export scenario requiring pro forma invoices for customs clearance ahead of actual delivery, how should the pro forma billing type be configured to avoid unintended interference with credit management and revenue recognition?

Pro forma billing types (F5/F8) should be configured with no accounting document transfer (billing relevance blank or transaction flow indicator suppressing FI posting) and excluded from credit exposure calculation by ensuring the item category/billing type combination does not update open credit value via S066. Copy control from order/delivery to pro forma must block relevance for delivery-related billing quantity updates and revenue recognition (RR) processing to prevent duplicate revenue triggers when the real invoice is later created.
hardBilling

23. Describe the end-to-end process of invoice list generation in SD and explain how it interacts with customer credit management and FI-AR posting.

Invoice lists (VF21/VF23) consolidate multiple individual billing documents for a payer into one collective list, typically for factoring or centralized payer scenarios, using its own pricing procedure for a factoring discount. The invoice list itself does not create new FI postings for the underlying invoices, which were already posted individually; it generates a separate FI document only for the factoring discount condition. Credit checks occur at order/delivery level for underlying documents, not at invoice-list creation.
hardBilling

24. Walk through how account determination (VKOA) resolves the correct G/L account during billing, including the condition technique fields used.

Account determination uses a condition technique similar to pricing: an account determination procedure (assigned to billing type) contains condition types like KOFI, evaluated against access sequences using fields such as chart of accounts, sales organization, account assignment group of customer, account assignment group of material, and account key from the pricing procedure. The system finds the most specific matching entry in VKOA, and posts the derived G/L account during billing document release to accounting, subject to standard GL master validations.
hardBilling

25. Explain how milestone billing plans and periodic billing plans differ in configuration and processing, and describe a scenario requiring a combination of both within a single project-based sales order.

Milestone billing splits a fixed contract value across dates/milestones (billing plan type 01/04 configured with billing rule and date category), each line invoiced independently once released, often tied to project system milestones. Periodic billing generates recurring invoices for a fixed amount over a validity period, common for rentals or maintenance. A large equipment sale with installation services might use milestone billing for the equipment value and periodic billing on a separate item for ongoing maintenance charges, requiring item category and billing plan assignment at the item level.
hardBilling

26. Revenue is posting to an incorrect G/L account only for a specific material group after a recent VKOA change, while other materials post correctly. How would you diagnose and resolve this?

Start by checking the material master's account assignment group (in Sales: General/Plant data) for the affected material group, since it's a key VKOA access field alongside customer account assignment group and account key. Compare VKOA entries across access sequence levels to see if a new entry with a more specific combination was inserted incorrectly, overriding the intended generic entry. Trace a test billing document via account determination analysis (in the billing document, Environment > Account Determination Analysis) to confirm which access was hit, then correct the VKOA entry or material account assignment group mapping.
hardBilling

27. In a global template rollout, how do you design billing type strategy to correctly handle standard invoices, credit memos, debit memos, and cancellations while preserving clean FI-AR postings and audit traceability?

Design distinct billing types (F2 for invoice, G2 for credit memo, L2 for debit memo, S1/S2 for cancellations) each with dedicated number ranges and copy control (VTFL/VTFA) to the originating sales/returns document, ensuring correct sign logic and account determination. Cancellation billing types must reference the original document for full audit trail, and credit/debit memo requests should route through approval workflow before billing to prevent unauthorized revenue reversals reaching FI-AR.

Related lesson

Architecting Enterprise Billing Landscapes: Scale, Governance, and Migration Strategy

Related topics

Advanced SD Scenarios, Integration and Production SupportS/4HANA SD Transformation, Migration, Public Cloud and ArchitecturePricingEnterprise StructureCustomer and Business PartnerOutput ManagementSchedule Line CategoriesItem CategoriesCopy ControlCredit ManagementAvailability CheckSales Documents

Next practice step

Practice with Interview AITake a mock test