Lesson 5 of 6
FI-CA testing
9 min
Listen to this lesson
Bills become money in FI-CA (Contract Accounts Receivable and Payable), the high-volume subledger that utilities, telecoms and insurers use instead of classic accounts receivable. FI-CA posts open items on contract accounts, clears them with payments, runs dunning and collections, handles installment plans and security deposits, and summarizes its postings into the general ledger. In a conversion, its logic largely continues, which makes regression and reconciliation the main tests.
FI-CA in the meter-to-cash flow
| Process | Transaction (examples) | What to test |
|---|---|---|
| Account balance display | FPL9 | Bills, payments and balances match the comparison expectations |
| Payment lot (incoming payments) | FP05 | Payments clear the right items; unassigned payments go to clarification |
| Payment run (refunds, direct debits) | FPY1 | Direct debits collected on due date; credits refunded |
| Dunning proposal and activity | FPVA, FPVB | Dunning levels, charges, letters, and exclusions |
| Transfer to the general ledger | FPG1 | FI-CA summary records reach the general ledger and reconcile |
FI-CA processes and transactions to test. Check apps and transactions for your release.
Main and subtransactions
Every FI-CA line item carries a main transaction and subtransaction, which decide its meaning (consumption billing, budget billing request, dunning charge, security deposit) and, through account determination, its G/L accounts. Utilities often add their own. A conversion keeps them, but any change in account determination or G/L account structure shows up here first. A single test per main and subtransaction combination in use, posting and then transferring to the general ledger, catches most problems.
Worked example: Contoso's account
| Step (illustrative) | Contoso contract account | Expected result |
|---|---|---|
| June electricity invoice | Open item USD 193,730.00 plus taxes, due in 21 days | Open item with consumption billing main transaction |
| Contoso pays by bank transfer | Payment arrives in a payment lot | Item cleared in full |
| July invoice unpaid at due date | Dunning proposal selects the account | First dunning level letter, no charge for industrial customers (policy) |
| Payment received after reminder | Cleared after dunning | Dunning history kept; no further levels |
An FI-CA test path through Contoso's account at Northwind.
Reconciliation after conversion
Three reconciliations prove FI-CA after a mock: open items per contract account before and after conversion (counts and amounts), FI-CA totals against the general ledger reconciliation accounts after the transfer, and the comparison's expected bills against the open items they created. Northwind's illustrative Mock 2 figures: 640,212 contract accounts, 1,118,904 open items totaling USD 96,402,117.36 before and after conversion, with zero differences.
What would you do?
After Mock 2, FI-CA open items match exactly, but the general ledger receivables account is USD 412,880.15 lower than FI-CA. What do you check first?
What goes wrong in testing
- Payment tests use only perfect payments, never partial, overpaid, unassigned or returned ones.
- Dunning is tested on new data only, so converted dunning histories and locks are never exercised.
- Direct debit mandates and bank details are masked in test, so the payment run cannot be tested realistically.
- The transfer to the general ledger is not run in the test cycle, so reconciliation is never proven.
Security deposits, installment plans and returns
Three FI-CA features cause most post-conversion complaints when they are not tested. Security deposits, requested from new or risky customers, must keep their status and interest rules across the conversion. Installment plans agreed in ECC must continue to schedule and track installments in SAP S/4HANA without re-dunning the original items. Payment returns, such as a bounced direct debit, must reopen the cleared items, add return charges per policy and feed dunning. Each needs at least one converted case in the test set.
| Feature | Converted test case | Expected result |
|---|---|---|
| Security deposit | Deposit requested in ECC, paid, still held | Held deposit visible; release rule unchanged |
| Installment plan | Plan created in ECC with two of six installments paid | Remaining four installments due on schedule; original items not dunned |
| Payment return | Direct debit returned after conversion | Items reopened; return charge posted; dunning next run |
Converted FI-CA cases that belong in every mock.
Finally, check what customers see. A contract account statement or online account view after conversion must show the same history, balances and payment status as before, because customers compare. Pick ten converted accounts with long histories, including Contoso's, and compare the customer-facing views before and after the mock line by line.
- FI-CA is the utility's receivables subledger: open items, payments, dunning, collections.
- Main and subtransactions drive meaning and G/L accounts; test each pair in use.
- Reconcile open items before and after conversion, and FI-CA to the general ledger.
- Test imperfect payments and converted dunning histories, not only clean cases.
Check your understanding · not graded
Lesson check
1. What do main and subtransactions determine for an FI-CA line?
2. Which transaction transfers FI-CA summary records to the general ledger?
3. FI-CA open items match after a mock, but the G/L does not. What is the usual cause?
4. Which payment cases should FI-CA tests include?