Lesson 6 of 6
Testing payments
7 min
The payment run is one of the few SAP processes that sends money out of the company. A defect in it is not a wrong report; it is cash paid to the wrong party, twice, or late. Testing it well means covering the logic (what gets paid, when and with what discount), the controls (what must not be paid) and the output (what the bank receives). It also means doing it safely: test runs in QAS client 100 must never reach a real bank.
Build the test matrix
Start from the risks, not from the screens. Each row below is a test case with a hand-calculated expected result written before execution.
| Test case | Setup | Expected result |
|---|---|---|
| Discount on the last day | Invoice 2/10 net 30, run posting date = baseline + 10 | Paid with 2% discount |
| Discount missed by one day | Same, posting date = baseline + 11 | Paid at net amount, or left until due if next payment date allows |
| Due before next run | Net due date falls between run date and next payment date | Paid in this run |
| Not yet due | Net due date after next payment date | Not proposed |
| Blocked item | Invoice with block A | Not paid; listed as blocked or exception |
| Blocked supplier | Supplier-level block | No items paid for that supplier |
| Missing bank details | New supplier without bank account | Exception with bank details message |
| Debit balance | Credit memo larger than open invoices | Exception, no payment |
| Credit memo offset | Invoice 5,000, linked credit memo 1,000 | One payment of 4,000 clearing both |
| Foreign currency | Invoice in CAD to a Canadian supplier | Payment in CAD from the right house bank; exchange difference posted correctly |
| Entered after cutoff | Invoice entered after documents entered up to | Not selected |
A starter test matrix for the payment run.
Test the bank file, not just the posting
Many projects test that the payment documents posted and stop there. The bank file is where real errors hide: a wrong account number format, a missing remittance reference, a value date in the past, an amount with the wrong decimal separator. Compare the file with the payment list line by line for a few payments, and check the totals and record counts for the whole file. If the bank provides a test channel or validation service, use it, with explicit agreement from the bank and treasury. Otherwise keep the file inside the test environment.
- Count of payments and total amount in the file equal the payment run totals.
- Supplier name, bank account and routing data match the business partner.
- Amount and currency per payment match the payment document.
- Remittance information lists the invoices paid, so the supplier can apply cash.
- Debtor account is the house bank account chosen by bank determination.
- Requested execution or value date is the expected date.
Evidence
- BeforeExpected resultsHand-calculated due dates, discounts and amounts for each case; signed off by Dan
- ProposalProposal list and exception listExported with the run date and identification
- Payment runPayment documents and cleared itemsManage Supplier Line Items view of cleared items with clearing document
- MediumBank file content checkTotals, counts and sampled records compared with the payment list
- AfterDefects and retestsEach mismatch logged, fixed and retested with new evidence
What would you do?
During regression testing, Priya's team finds that one supplier in Canada was paid in USD from the US house bank instead of in CAD from the Canadian account. The posting looks correct and the cleared items are fine. The release is in two days. What should she do?
- Write expected due dates, discounts and amounts by hand before running tests.
- Cover boundaries, blocks, exceptions, credit memos, foreign currency and selection cutoffs.
- Check the bank file content and totals, not only the postings.
- Never let a test payment file reach a real bank.
- Evidence: proposal and exception lists, payment documents, cleared items, file comparison.
Check your understanding · not graded
Lesson check
1. Which test proves the discount boundary works?
2. What should be compared to validate the bank file?
3. A credit memo of 1,000 is linked to an invoice of 5,000. What should the run pay?
4. What must be confirmed before payment testing in QAS?