A BNPL account reaches collections. The balance is present and a field says “notice issued”. Before the receiving team relies on that status, it needs the communication history behind it.
A useful handover connects the account to six things:
- the event that triggered the notice and its date;
- the exact approved template version;
- the generation reference and timestamp;
- the historical output, where retained, and its integrity record;
- the separate sending reference and recorded outcome;
- the owner of any gap or exception.
Agree these fields between creditor and receiving team before the next transfer. They are practical handover recommendations: the point is to let someone follow the history without asking the original operator to reconstruct it.
Establish which agreement and role you are handling
“BNPL” alone does not establish the agreement's regulatory status or each party's responsibilities. Confirm those before selecting the notice process.
For regulated deferred payment credit, CONC 7.20.1R, effective from 15 July 2026, requires firms to notify the borrower as soon as possible after a missed payment. It covers unpaid sums, the agreement, adverse consequences that have arisen or are considered likely, and relevant mitigation, with the required information provided together. CONC 7.20.2G points specifically to charges and credit reference reporting. [1]
The handover needs to show what was done for the account. A generic template in a shared folder cannot establish the customer-specific history.
Preserve the historical output
Consider a fictional case. Version four is approved. A notice is generated on Tuesday using the balance then supplied by the account system. The balance is corrected on Wednesday. The account moves to the agency on Thursday.
Opening version four shows the approved wording. Generating another document on Thursday may produce a different balance. Preserve the distinction between the historical output and a later reconstruction, including the data and rendering conditions used.
If the original output is unavailable, record that gap. A hash can check whether a candidate file matches the recorded output; it cannot recreate a missing letter. This is why the handover should distinguish retained files from integrity records.
Connect replacement documents and retries
If an operator produced a replacement notice, the receiving team needs to identify which output was passed to the sender. If a sending attempt failed and was retried, preserve the sequence rather than showing only the latest status.
Use stable references across the account, generation and sending systems. Decide who investigates incomplete records and how the receiving team escalates them. A status label should not silently determine the next customer communication.
CONC 7.20.3R separately addresses notice before specified action, including certain enforcement steps and termination. [1] Identify the proposed action and the applicable requirements rather than treating every communication as the same notice type.
Make the evidence accessible to the right people
The CommsPliant Evidence Vault supports the connection between approved versions and generation evidence. By default, the evidence approach records a cryptographic hash of the rendered output; encrypted full-output retention is optional. The responsible team still assesses the wording and treatment, and generation does not establish sending, delivery, reading or understanding.
Agree access and retention with the relevant owners. A useful evidence handover does not require an unrestricted customer-document export to everyone involved.