Document Fraud Red Flags for Compliance Teams

Document fraud remains a persistent challenge for banks, fintechs and law firms. While technology has improved, many attempts to disguise a customer’s true financial position still rely on altered or fabricated paperwork.

This guide highlights some of the red flags that AML and compliance teams are trained to recognise when reviewing bank statements, payslips and proof-of-address documents. The goal is to support awareness and training, not to provide instructions for committing fraud.

Why Red Flags Matter in AML and KYC

Red flags are not proof that a document is forged. Instead, they indicate that something may be wrong and that further checks are warranted. When multiple red flags appear alongside other risk factors, it may be appropriate to reject the evidence or escalate the case to a financial crime specialist.

Training programmes often use simulated bank statements and other mock documents to help staff become more confident in identifying these warning signs.

Layout and Formatting Red Flags

The visual appearance of a document can reveal subtle signs of manipulation. Examples include:

• Mismatched fonts or font sizes within the same row or section.
• Logos or branding elements that do not match known genuine templates.
• Unusual spacing or alignment, particularly where numbers have been inserted or removed.
• Blurry or pixelated areas around key figures or names, suggesting local edits.
• Inconsistent margins or header styles from page to page.

During training, these kinds of issues may be exaggerated in novelty or prop-style documents so that learners can see the effect clearly before encountering more subtle variations in genuine work.

Content and Consistency Red Flags

Even when a document looks convincing at first glance, the content itself may contain contradictions. Common examples include:

• Balances that do not add up when transactions are compared to the running total.
• Overlapping or duplicated dates where two different statements claim to cover the same period.
• Salary amounts that do not match the employment details provided elsewhere.
• Addresses or account numbers that differ from other documents in the same file.
• Information that conflicts with data obtained from trusted third-party sources.

AML teams are encouraged to look beyond the surface and ask whether the document tells a coherent story that matches the customer’s overall risk profile.

Behavioural and Pattern-Based Red Flags

Many institutions combine document review with transaction monitoring. Certain patterns in a bank statement may raise questions, for example:

• Regular cash deposits of large, round amounts with no clear explanation.
• Frequent transfers between related accounts shortly after funds are received.
• Spikes in activity that only appear in the period being scrutinised.
• Activity inconsistent with the customer’s stated occupation or lifestyle.

On their own, these patterns do not prove that a statement is fake, but they may justify additional questions or supporting evidence.

Channel and Presentation Red Flags

The way a document is delivered can also reveal useful information:

• Photographs of screens instead of downloaded statements, particularly if key details are cut off.
• Files with unusual names or multiple versions where later copies appear altered.
• Reluctance to provide original PDFs from online banking or employer systems.
• Documents sent via unusual channels instead of secure upload tools.

Training that includes simulated customer interactions can help staff practise handling these scenarios while keeping a professional and fair approach.

Using Red Flags in a Risk-Based Approach

Good AML frameworks emphasise a risk-based approach. This means red flags should be considered alongside other information rather than in isolation. In practice, that may involve:

• Recording specific concerns in case notes or internal systems.
• Requesting alternative documents or direct confirmation from the issuer.
• Escalating the file to an AML or financial crime team for review.
• Documenting the rationale for any decision taken.

Training materials, such as novelty payslips and mock bank statements, can support these discussions without exposing real customer data.