Desk note
Decline reasons that do not match the policy pack
· Hafiz Abdullah
Declined BNPL applications are awkward to keep. They do not become accounts. They still belong in the audit universe, because they show how the programme says no — and whether that ‘no’ is reproducible.
A common pattern: the system stores a score-threshold decline. The agent notes say ‘income insufficient.’ The customer-facing message says ‘we are unable to offer this plan at this time.’ None of these is necessarily improper. Together they are unreproducible. A second-line reviewer cannot tell which rule was applied.
Another pattern: a policy pack is updated on a Monday, and files originated on Tuesday still cite the Friday reason list. Versioning of reason codes is unglamorous work. It is also the only way a later reader can match a file to a rule.
Overrides sit next to declines. An approval that bypasses a decline needs extra evidence, a named person, and a reason that exists in the policy. ‘Customer waiting at the counter’ is not a policy reason, however true it may have been.
If you only sample approvals, you will miss this. Ask for declined and withdrawn files in the same frame, even if they are stored in a different system.