Ask Mat: “I don’t have time to form a suspicion at the counter — am I doing something wrong?”

The question:

“I work at a Schedule 2 money service business (bureau de change/FX) that’s JFSC-supervised, and I’ve been told about my suspicious reporting duties and what happens if I don’t report. What worries me is that when dealing with a customer at the counter, I don’t have enough information or time to crystallise a suspicion — it’s only when the customer has moved on that I may, on reflection, crystallise a suspicion. Am I wrong for not reporting earlier, and for having dealt with the customer at all, given I was only suspicious after the transaction?”

Mat’s answer:

No — on both counts. In fact, the law is built specifically around the sequence you’ve described: serve the customer, then realise something’s off, then report. Let me take the two halves separately, because different provisions answer each one — and then look at the reverse situation too, because it’s the natural follow-on question: what if you realise before the transaction is finished, while the customer is still standing at your counter?

Was it wrong to deal with the customer, given that the suspicion only came afterwards?

No — and there’s a specific statutory answer to this, not just a general reassurance.

Under the Proceeds of Crime (Jersey) Law 1999, “criminal property” is defined (Article 29(1)) by reference to your own state of mind at the time: property only counts as criminal property in your hands if you “know or suspect” it’s derived from or connected to criminal conduct. Before your suspicion formed, the funds you were handling weren’t criminal property as against you — so completing that transaction wasn’t capable of being an offence under Article 30 (dealing with criminal property) at the point you did it. You can’t unknowingly deal with something the law only treats as tainted once you actually know or suspect it is.

On top of that, there’s an explicit safety net for exactly this “act first, suspect after” sequence: Article 32 — protection for disclosures. The JFSC Handbook (effective 30 June 2026) restates it in paragraph 54:

“…if the report is made after the person does the act in question, it is made on the person’s own initiative and as soon as reasonably practicable after the person has done the act in question.” (Handbook, para 54, restating Article 32(4))

In other words, Jersey law anticipated that suspicion often crystallises after a transaction is already complete — particularly in a fast-moving counter environment — and built a protective measure around that, rather than requiring staff to suspect before they’ve had the chance to.

Was it wrong not to report earlier?

Also, no — provided the reflection is genuine and the report follows promptly once the suspicion actually forms. For a Schedule 2 money service business, the relevant reporting duty is Article 34D, and the Handbook is direct about the timing:

“Employees of a supervised person are required to raise an internal SAR as soon as practicable where they have knowledge or suspicion, or where there are reasonable grounds for having knowledge or suspicion…” (Handbook, para 16)

“…made as soon as is practicable after the information or other matter on which the knowledge or suspicion is based … comes to their attention.” (Handbook, para 30, restating Article 34D(4A))

The clock starts when the suspicion (or reasonable grounds for it) actually exists — not when the customer was standing in front of you. The Handbook’s own description of what “suspicion” means backs this up: it’s framed as something that can build, not something that switches on instantly.

“If someone has not yet formed a suspicion, but they have cause for concern, a supervised person may choose to ask the customer or other parties more questions… [whether someone has a suspicion] is a matter of their own judgement.” (Handbook, paras 70–71, 73)

A short walk-up counter transaction rarely gives you room for those follow-up questions in the moment — which is exactly why suspicion-forming is treated as a process that can continue after the interaction ends, not a snapshot judgement you’re expected to make on the spot.

The one thing this doesn’t excuse

None of this is a free pass for genuinely obvious red flags spotted and ignored in the moment. If the facts in front of you at the counter were glaringly suspicious — the kind of thing your training specifically flags — “I only thought about it afterwards” won’t rescue a case where you should reasonably have caught it at the time; that’s what your firm’s red-flag training exists to sharpen.

But that’s a different situation from the one you’ve described: a customer dealt with normally, where the picture only came together on reflection once they’d gone. That’s not a gap in your compliance — it’s the situation the reporting timeline was written to accommodate.

What if the suspicion forms before you’ve completed the transaction?

This is the harder situation, and it deserves separate treatment because the Handbook is explicit that it’s governed by a different rule, not a variation on the one above:

“A report should be made before doing an act where a customer instruction is received prior to an activity or transaction taking place… [but] a report should be made after doing an act where something appears suspicious only with the benefit of hindsight or following the receipt of additional information.” (Handbook, para 86)

So if the suspicion crystallises while the customer is still in front of you, the “reflect afterwards” protection covered above doesn’t apply in the same way — the expectation shifts to stopping before you complete the transaction. In practice, for a counter employee, that means:

1.          Don’t complete the transaction. Pause it, using whatever ordinary, non-alarming reason your firm’s procedures provide for (e.g. standard checks, system issue, manager sign-off) — not a reference to suspicion or reporting.

2.          Refer to your MLRO or Deputy MLRO immediately through your firm’s internal procedure. This is genuinely urgent here, unlike the reflect-afterwards scenario — the point of raising it before the act is to give your MLRO the chance to decide what happens next before anything is committed to.

3.          Leave the next decision to your MLRO. They may seek the FIU’s consent to proceed under Article 32(4) of the Proceeds of Crime Law via the SAR portal (Handbook, para 87), or they may decide not to proceed with the transaction. Either way, that call — and any conversation with the FIU — is theirs, not yours.

4.          This still applies even if the transaction is declined and never happens. The Handbook is explicit that the reporting duty covers one-off transactions and potential business relationships that don’t go ahead, not just completed ones (Handbook COP84, para 76ff — “internal SARs are to be made regardless of… whether it is thought to involve tax matters,” extending to declined transactions).

Be careful what you say to the customer. This is where tipping off becomes a real risk, not a theoretical one. The Handbook is direct about what you cannot do:

“…a supervised person or employee of a supervised person: cannot, at the time, tell a customer that a transaction or activity is being delayed because an internal SAR is about to be made or has been made to the MLRO… cannot later tell a customer that a transaction or activity was delayed because an internal or external SAR had been made.” (Handbook, para 95)

If the customer asks why the transaction isn’t proceeding, use the generic, pre-agreed wording your firm’s procedures provide — “we’re unable to complete this today,” standard checks, a systems issue — never anything that references suspicion, a report, or the real reason (Handbook, paras 88, 95).

If you’re unsure what to say in the moment, that’s exactly the kind of question to have already covered in your firm’s training, precisely because there’s no room to improvise safely once you’re standing at the counter.

Doesn’t the risk of a breach-of-contract claim change any of this?

It’s worth addressing directly because it’s a natural concern once you realise a transaction might have to be stopped: if declining or delaying a customer’s instruction could expose the firm to a claim, does that pressure the timing of the report?

The Handbook draws a clear line here, and it only moves in one specific, narrow circumstance:

“…when a transaction which gives rise to concern is already within an automated clearing or settlement system where a delay would lead to a breach of a contractual obligation or where it would breach market settlement or clearing rules, the MLRO (or Deputy MLRO) may need to let the transaction proceed and report it later.” (Handbook, para 86)

That’s a defined exception for transactions already committed within a clearing or settlement system — typically in a banking or payments context — not a general licence to let commercial pressure dictate the timing.

For a bureau de change counter transaction, that exception usually won’t apply, so it doesn’t change anything at the employee level.

Outside that narrow case, breach-of-contract risk is a downstream consequence to be managed, not a factor in deciding when to report. The Handbook is explicit that this is handled through:

“…ensuring that customers’ terms of business specifically: allow an instruction to be delayed or deferred pending investigation; exclude breaches in circumstances where following a customer instruction may lead to the supervised person committing an offence.” (Handbook, para 91)

And, if a customer does pursue a claim, by taking legal advice or seeking direction from the courts (Handbook, para 90). Both of those are firm-level responses that happen after the reporting decision, not inputs into it. What this means practically for you at the counter: the risk of upsetting a customer, or of the firm facing a contract dispute, is never a reason to delay raising an internal SAR, or to let a transaction you’re suspicious of go ahead anyway. That call belongs to your MLRO, working within the AML/CFT framework — not to a judgement about customer relations.

What to do next

Once the suspicion has genuinely formed, report it to your MLRO or Deputy MLRO through your firm’s internal procedure promptly. That fully satisfies your personal statutory obligation (Handbook, para 22) — it’s then your MLRO’s job, not yours, to decide whether it goes on to the FIU.

The short version: whether the suspicion arises before or after you’ve completed the transaction, the law has an answer for both — reflect and report promptly if it arises after; stop, refer, and let your MLRO handle the next step if it arises before. Neither situation is a failure on your part; they’re two different, well-established routes through the same underlying duty.

This article addresses the general position under the Proceeds of Crime (Jersey) Law 1999 and the JFSC AML/CFT/CPF Handbook (effective 30 June 2026). It isn’t a substitute for your firm’s own AML/CFT policies and procedures, which set out exactly how and to whom internal disclosures should be made.

Sources

Proceeds of Crime (Jersey) Law 1999 (Articles 29, 30, 31, 32, 34D) https://www.jerseylaw.je/laws/current/l_8_1999

The JFSC AML/CFT/CPF Handbook content  

 https://www.jerseyfsc.org/industry/financial-crime/amlcftcpf-handbooks/amlcftcpf-handbook/

https://www.jerseyfsc.org/media/2j0c4zoo/handbook-section-09-reporting-money-laundering.pdf

Section 9.2.1 — "Requirement to report knowledge or suspicion"

1. Para 16 (duty to raise an internal SAR "as soon as practicable")

2. Para 30 (restates Article 34D(4A) — report to whom, and the "after" timing)

Section 9.2.2 — "Protective report"

3. Para 54 (Article 32(4) protection for a report made after the act, on own initiative, "as soon as reasonably practicable")

Section 9.2.3.2 — "Suspicion" (part of 9.2.3 "What constitutes knowledge or suspicion?")

4. Para 70 (suspicion is a subjective test)

5. Para 71 (cause for concern vs. formed suspicion; asking further questions)

Section 9.4 — "FIU Consent"

6. Para 86 (the before/after protective-report split; the automated clearing/settlement carve-out)

7. Para 91 (mitigating civil/breach-of-contract risk via terms of business)

Section 9.5 — "Tipping off"

8. Para 95 (what a supervised person/employee cannot tell the customer)

All eight sit within the same run of the Handbook: Section 9 "Reporting money laundering, the financing of terrorism or proliferation, and sanctions reporting obligations" (page 200 onward in this 30 June 2026 edition) — specifically subsections 9.2 through 9.5

https://www.jerseyfsc.org/media/2j0c4zoo/handbook-section-09-reporting-money-laundering.pdf