A date stamp changed at 19:40
It is 14 March, a Tuesday. Your team is finalising a client's quarterly regulatory return, due through the regulator's portal at 23:59 tonight. At 19:40 a junior analyst, Tom, tells you he has altered the approval date stamp on the model documentation from 12 March to 14 March, on the instruction of the client's head of finance, so the file "shows sign-off before submission". The underlying numbers were reviewed on 13 March and have not changed. The head of finance says the original delay was a printer failure, that no figure is affected, and that "nobody is misled". The engagement letter gives the client responsibility for the return but requires your firm to confirm it was "prepared from complete and accurate records". You are the manager; the partner is on a flight until 07:00 tomorrow. The portal has no extension mechanism, and a late return triggers a public notice naming the firm.
1. What do you do between 19:40 and midnight, and in what order?
Read the worked answer
First, freeze the change. Ask Tom to revert the stamp to 12 March immediately and to send you a written note of what he changed, when, and on whose instruction, with the original file preserved rather than overwritten. Preserve the email or message containing the instruction. Nothing is deleted - the audit trail is the evidence, and deleting it would be worse than the alteration.
Second, get the facts straight before deciding anything. Was the 13 March review genuine and documented? Is the 14 March date the only altered field? Ask the head of finance to confirm in writing what he instructed and why. Do not accept "cosmetic" as a conclusion until you have compared the two versions yourself.
Third, separate the two deadlines. The regulatory deadline is real and the public notice is a real consequence, but neither is a reason to certify something untrue. The return was in fact approved on 12 March - earlier than the stamp suggests - so the accurate statement can be made tonight without any loss. Put the accurate position in the submission.
Fourth, escalate. Try the partner by message; if unreachable, notify the firm's ethics or risk partner now rather than at 07:00, and record that you did.
Finally, document the sequence in the file before midnight, while memory is fresh: what you were told, what you did, and on what basis the return was submitted.
2. The client argues the change is cosmetic and that no figure is affected. Is he right, and how does your answer change if the altered date is on the sign-off page rather than in working papers?
Read the worked answer
He is wrong on both counts, but the reasoning needs care.
A date stamp is a record of when something happened. Changing it makes the record false even if every number is right. The engagement letter requires a confirmation that the return was prepared from complete and accurate records. If the file knowingly contains an inaccurate date, that confirmation cannot be given honestly - not because the figures are wrong, but because the records are. The harm is not to this quarter's numbers; it is to the reliability of the file as evidence, which is exactly what a regulator, or a later reviewer, would rely on.
There is also a practical point about incentives. Once a record has been adjusted to fit a deadline, the next adjustment looks smaller. The professional response is to stop the practice at the first instance, not to weigh each instance on its own merits.
If the altered date is on the sign-off page, the position is more serious, not less. Sign-off dates represent who approved what, and when, and go directly to accountability. A false sign-off date can misrepresent that approval was obtained before submission when it was not. That would need to be corrected before submission and reported to the partner and, if the client insists, escalated to those charged with governance. In either case the submission proceeds on the accurate record; the timing pressure is the client's problem to manage, not a reason for the firm to sign something it knows to be inaccurate.
3. What do you say to Tom, and what should the firm change so this does not recur?
Read the worked answer
To Tom: he did the right thing by telling you, and say so plainly - the instinct to escalate a partner-adjacent instruction at 19:40 is exactly what the firm wants. Then be clear about the boundary: he must not alter source records on a client's verbal instruction, however senior, without the manager's approval. If asked again, he should say "I'll need to check with the manager" and come to you. Do not let him feel that reporting created a problem; the problem was created by the instruction.
To the client: restate the position in writing - the firm will not adjust dates on records, and the return will be submitted on the accurate basis, which is achievable tonight.
Firm-level changes worth raising with the partner:
- A standing rule that no field evidencing approval, review or sign-off is edited after the fact; corrections are made by addendum, not overwrite.
- Version control on submission files, so an alteration is visible rather than silent.
- A named deputy with authority to make the call when the partner is unreachable, because "partner on a plane" will happen again and should not leave a manager exposed.
- Pre-deadline checkpoints: a T-48-hour readiness review so that late client instructions land against a completed file, not an unbuilt one.
- A short annual session for juniors on what to do when a client instructs something that changes a record, using a scenario like this one.