Lesson 6 of 6
Testing receivables
6 min
Receivables testing proves three things: that customer invoices from every route post to the right accounts with the right terms; that payments clear the right items with differences handled as designed; and that dunning sends the right notice to the right customer at the right time. It is a mix of integration testing with order-to-cash and focused testing of finance rules.
The scenarios
| Area | Scenario | Expected result |
|---|---|---|
| Invoices | Billing for Great Lakes Fleet Services from sales order | Customer debited, revenue and tax credited; terms from sales area data |
| Invoices | AR invoice and credit memo posted in finance | Correct accounts and tax; terms from company code data |
| Payments | Full payment | Invoice cleared; clearing document recorded |
| Payments | Partial payment | Invoice open; payment open with invoice reference |
| Payments | Residual payment with reason code | Invoice and payment cleared; residual item with reference and reason |
| Tolerances | Differences just inside and outside limits | Automatic posting inside; user decision outside |
| Dunning | Items at each level boundary | Correct level per item; notice text of the highest level |
| Dunning | Blocked item and blocked customer | Not dunned |
| Dunning | Item within grace days, amount below minimum | Not dunned |
Core receivables test scenarios.
Setting up dunning tests
Dunning depends on dates, so tests need deliberate data. Create invoices with baseline dates chosen so that, on the planned dunning date, some items are inside grace days, some just past it, and some past each level threshold. Then run two or three dunning runs in sequence, respecting the dunning interval, to prove that items move up a level and that an account is not dunned again before the interval passes. Document the dates in the test case so anyone can repeat it.
- Day -40Create test invoicesBaseline dates chosen so items are 2, 4, 16 and 31 days overdue on the first dunning date
- Day 0Run 1Expect: 2 days overdue not dunned (grace); others at levels 1, 2 and 3
- Day 7Run 2Expect: no notices, interval of 14 days not reached
- Day 14Run 3Expect: items move up one level where days in arrears allow
- AfterEvidenceProposals, notices, Display Dunning History
Test data that stays usable
Receivables tests consume their data: once an invoice is cleared or dunned, it cannot be used for the same test again. Plan a set of dedicated test customers in QAS client 100, for example one customer per tolerance group and one per dunning procedure, and create fresh invoices for each test cycle with a documented recipe. Avoid using Great Lakes Fleet Services' migrated copy for destructive tests, because other teams, such as Maria's order-to-cash testers, rely on its history. If the project uses a data refresh before each test cycle, agree with Luis which test customers are recreated and when.
Do not forget the link to bank accounting. Most incoming payments in production will be cleared by the electronic bank statement, not by hand. A manual clearing test proves the clearing logic; an end-to-end test from bank statement import to cleared invoice proves the process. Run both before go-live, and include the end-to-end case in the regression set.
Evidence
- Journal entries for invoices and payments, with document numbers.
- Manage Customer Line Items views showing open and cleared items, clearing documents and residual references.
- Tolerance test results with the difference amount and the account it posted to.
- Dunning proposal list, generated notices (or their preview), and Display Dunning History for the test customer.
- The user and tolerance group used for each test.
What would you do?
In the second dunning test run, a customer already dunned at level 1 seven days ago receives another level 1 notice. The interval in the design is 14 days. What does this suggest, and what should Priya do?
- Test both invoice routes: billing from sales and AR-posted invoices.
- Test full, partial and residual payments and tolerance boundaries with the real user group.
- Design dunning test data with dates; run several runs to test levels and intervals.
- Evidence: journal entries, line item views, dunning proposals and history.
Check your understanding · not graded
Lesson check
1. Why run several dunning runs in a test?
2. Which evidence shows dunning results over time for a customer?
3. What should be recorded with each tolerance test?
4. An item is 2 days overdue and grace days are 3. What should the first dunning run do?