/
Unit Test Protocol (Prime Overdue)

Unit Test Protocol (Prime Overdue)

Unit Test Protocol (Prime Overdue)

Actionable acceptance checks for Prime Overdue on a tenant. Run after Billing settlement is available. Cross-ref: UAT processes.

Access & config

Overdue menu visible for a collections role; config page opens
Confirmed mode is sta or csv as agreed for this tenant
Return-debit fee, payment period, and at least one dunning charge/text saved
Internet-block thresholds saved (or explicitly left empty if unused)

Debt list

Debt list / result shows open debts with contract name/number and missing amount
Internet-blocked and valid-SEPA columns filter correctly (yes/no)
Breadcrumb from a debt reaches the contract Billing tab

Import (mode-specific)

MT940: Upload a sample .sta; import finishes; Logs show matches and any unmatched lines
MT940: A return debit / transfer with invoice number clears or creates the expected debt
CSV: Upload a valid sample; debts appear; test mode previews blocks without applying them
Second import while first runs shows the wait / create-disabled behaviour

Clearing & settlement

Manual clear: create payment (negative amount) linked to parent debt; missing amount updates; cleared when zero
After a settlement run with Overdue enabled, debts exist for billed contracts (MT940 mode)
Optional: clear-credit-balance and debt-per-cost-center behave as configured

Internet block

Import that exceeds amount or count threshold blocks internet for that contract’s modems
Debt list shows internet-blocked = yes for that contract

Sign-off

Billing + collections owners accept the chosen mode and transfer-reason rule
Failures logged with contract id, import id, and timestamp

Parent hub: Prime Overdue