Handle a repeated request without losing the audit trail
A repeated request may concern a different purpose, a rejected file or a missing receipt. Establish which before resubmitting.
The distinction that matters
Compare the exact wording and reference number with the previous message. A file can be received but not accepted, or accepted for one purpose while another check remains open. Preserve each status rather than compressing them all into 'verified'. Repeatedly opening new support tickets can make the sequence harder to follow.
A worked example
You uploaded an address statement on Monday and see another request on Wednesday. Your receipt establishes that a file was transmitted, not that it passed review. A useful response quotes the existing case number and asks whether the issue is receipt, readability, document type or another requirement.
Your next steps
- Find the previous receipt and case reference.
- Ask which stage remains incomplete.
- Send a replacement only through the confirmed channel.
- Record the new submission against the same timeline where possible.
Where this answer stops
Do not assume the second request proves misconduct or approval failure. Northline cannot see account records. A clear chronological record is more useful than public screenshots containing document numbers, addresses or banking information.
Sources & reading
Original Northline explanation. Worked examples use stated assumptions; they do not establish an operator’s policy or predict personal results. Read how we handle evidence.
An editorial review date is not a new policy effective date. Always check the current source for operator-specific conditions.
Suggest a correction