Navigating the FATF Blacklist and Greylist as a Freelancer

Check the Payment Route Before Committing Scope#

A FATF listing can affect bank review and access to cross-border payments, but it does not decide whether your particular project is legal or whether a provider will accept it. Check the parties, applicable law and actual payment route before setting delivery dates. Then ask whether your reserves can cover the agreed work if a lawful payment is delayed.

A risk signal is a public warning about jurisdiction-level AML/CFT risk, not proof that your specific transaction is improper. Payment friction is the delay caused by holds, pauses, extra checks, or blocked transfers before funds are usable. Cash runway is how long your business can operate before reserves run out if no new cash comes in.

Use this order every time#

Use these checks before committing to a route or delivery dates. You can draft a conditional proposal and gather information in parallel; resolve material legal and eligibility questions before kickoff.

Identify the contracting party and actual payer. Verify the legal entities behind the brand and finance contact. A parent company or agency can sometimes pay legitimately: record its relationship, authorization, invoice allocation and effect on the client’s payment obligation, and check that the provider permits it. Unexplained differences remain unresolved.

Check law, provider eligibility and the dated FATF statement. Applicable sanctions can prohibit a project or payment unless a specific authorization or exemption applies. Check the legal scope first, then the exact product and route. As checked on 5 October 2026, the latest two FATF statements are dated 19 June 2026. Increased monitoring alone does not call for blanket enhanced due diligence; the high-risk statement distinguishes countermeasures for DPRK and Iran from proportionate enhanced due diligence for Myanmar.

Adjust terms before work starts. If the route or jurisdiction suggests more review, tighten terms early: more upfront coverage, shorter billing intervals, and less unsecured delivery.

Check reserves against likely delay. An invoice collected in full is not necessarily bank-available cash. Under PayPal’s U.S. agreement, ordinary risk-based payment holds generally last up to 21 days, with other holds subject to different provisions. Stripe Express says a successful required W-8/W-9 submission should unpause payouts within two business days when no other requirements remain. That is a tax-form pause example, not a FATF hold-release deadline.

Log evidence before proceeding. Keep a short record of what you checked, when you checked it, and what terms changed.

Make the go or no-go call early#

Use case-specific checks rather than rejecting every customer from a listed country. FATF’s increased-monitoring statement rejects blanket cutoffs. Legal prohibitions and provider restrictions still control the affected activity: smaller milestones, a different app or advance payment cannot make prohibited work permissible.

Keep an evidence log you can actually use#

Once you know the deal is workable, keep a record you can use later if the route is reviewed. For each client or invoice path, capture:

• client trading name and legal payer name
• expected payment route and receiving account or provider profile
• FATF document checked, jurisdiction signal, and check date
• identity-verification documents or data reviewed
• term changes made because of the signal or route
• reviewer name and next recheck trigger

Recheck at the points where friction can appear: before proposal, at contract signature, before major invoices, when payer entity or bank details change, when your provider requests more verification, and whenever FATF issues list updates. Wise notes verification can expand over time, for example identity first and address later. A clean intake does not guarantee a smooth payout path later.

If inconsistencies repeat, pause scope expansion until payer, route, and terms align again. If delays are already showing up as margin drag, read The Silent Profit Killer: How to Stop Margin Erosion in Your Freelance Business.

For rate-setting pressure rather than payment-route restrictions, see How Global Inflation Changes Freelancer Rates and Real Earnings.

Understand the FATF Terms Before You Change Your Process#

Use precise terms before you tighten payment terms, pause work, or change invoice flow. In practice, FATF labels, provider labels, and legal conclusions are different signals. Mixing them creates avoidable payment friction.

FATF is a standards-setting and assessment body for money laundering, terrorist financing, and proliferation financing. AML/CFT means Anti-Money Laundering / Countering the Financing of Terrorism. Keep this distinction explicit in your file. A FATF listing is a risk signal about a jurisdiction, not a legal determination about your client or invoice. FATF does not handle individual cases or seize funds.

Use one terminology map per client file#

Map shorthand to the exact source and timestamp it. The latest FATF statements checked for this article on 5 October 2026 are dated 19 June 2026. June’s increased-monitoring update added Bosnia and Herzegovina and Iraq and removed Algeria and Namibia; Kuwait and Papua New Guinea remain listed after their February addition. Verify the current publication again before using these examples.

Keep one term end to end#

Keep FATF status, legal conclusions and provider notices in separate fields. “Increased monitoring,” “high-risk,” and “unsupported region” describe different things and may all appear in one file. Do not collapse them into a single label.

Reuse each exact label when discussing that particular finding. Keep a dated internal log; include a FATF label in an invoice or client message only when it helps explain an actual requirement. Ordinary invoices do not need country-risk commentary.

Let wording trigger action, not emotion#

Use this decision rule:

• No change when the label is only a signal and payer, route, and provider support are clear.
• Tighten terms when the label points to higher review risk or possible slower payout access.
• Pause pending verification when provider wording indicates restriction, unsupported geography, or payer details do not align.

Keep client updates neutral and process-first. Reusable lines:

• "We're adjusting payment terms to match current verification requirements for this payment route."
• "Before we proceed, we need to confirm the legal payer entity and receiving details."
• "This is a payment-process check, not a judgment about your business."

Compare Blacklist and Greylist by Payment Risk and Friction#

Do not price or accept a deal based on the label alone. Before you assume payment behavior, verify three layers: the current FATF label, the local legal rules for your route, and your payment provider's program rules.

Each layer answers a different question. FATF publishes risk signals and standards. Local law determines legal obligations. Provider rules determine whether your route is supported, restricted, or subject to extra review. A FATF label is a risk signal, not a legal conclusion about a specific client or invoice.

Know which layer is driving the decision#

The 19 June 2026 high-risk statement names DPRK, Iran and Myanmar. It calls for countermeasures for DPRK and Iran, and proportionate enhanced due diligence, not countermeasures, for Myanmar. It says countermeasures may be considered for Myanmar if progress is insufficient by October 2026; that possible future action is not current status. The Myanmar statement also protects humanitarian assistance, legitimate nonprofit activity and remittances from disruption or discouragement. These distinctions do not override applicable sanctions.

For increased monitoring, FATF's framing is different. Jurisdictions have committed to address deficiencies within agreed timeframes and are under monitoring. That is not an automatic prohibition. The practical question is narrower: can this payer, on this route, pay with predictable settlement and usable funds?

Recheck at the moments that change your exposure#

Country treatment is not static. FATF listing documents are issued three times a year, and FATF Recommendations are updated over time. Use a recheck cadence that matches your exposure: at proposal, contract signing, and before major invoices.

Log a compact record each time: check date, exact FATF label, provider rule or support reply, payer legal name, and payout method. If payer entity or bank details change after initial checks, rerun the same checks before continuing.

Use a simple commercial decision path#

If the route is supported, the payer is clear, and no live issue appears in local law or provider rules, proceed with standard terms. If support exists but payout predictability is weaker, proceed with tighter upfront protections and shorter billing intervals. If you cannot confirm route support or legal payer identity, decline or redesign the payment path before more work.

This is a commercial tradeoff. Stricter upfront controls may slow kickoff, but they can protect the margin you already won. For the margin logic, see The Silent Profit Killer: How to Stop Margin Erosion in Your Freelance Business.

Related: Best Way for a German Agency to Pay a US-Based Freelancer.

Run a Client Acceptance Check Before You Send a Proposal#

Decide one thing before you quote: proceed, proceed with tighter protections, or pause. If payer identity, route fit, or your delay tolerance is unclear, pause before you send a proposal that assumes normal payment behavior.

Verify in this order#

Legal payer identity#

Confirm the contracting entity and actual payer using reliable records. A documented parent, agency or other authorized payer does not necessarily require changing the contracting party. Explain the relationship and payment allocation, agree when the payment discharges the client’s debt, and verify provider acceptance. Do not disguise the sender or amend names merely to pass a check.

Current jurisdiction risk signal#

Check the payer jurisdiction against the live FATF statements, and also identify beneficiary and intermediary-country issues relevant to the route. The latest statements checked on 5 October 2026 are dated 19 June 2026. Check applicable sanctions and authorizations separately; a FATF label is not a sanctions-screening result.

Provider program eligibility#

Confirm your specific provider path, not just country-level support. Eligibility can vary by product, country, currency, and account setup, including connected-account differences.

Transaction-path fit#

Confirm rail, presentment currency, settlement currency, and beneficiary details before pricing. A supported country can still fail on a specific currency path, and missing originator or beneficiary information can trigger additional checks or review.

You can gather these facts in parallel, but resolve material legal, identity and eligibility questions before work begins. FATF does not investigate your invoice. Your own commercial decision still requires a lawful supported route and terms you can fund.

Tie acceptance terms to explicit conditions#

Keep negotiation simple: less upfront protection means narrower scope. Broader scope requires stronger payment protection. For the margin impact, see The Silent Profit Killer: How to Stop Margin Erosion in Your Freelance Business.

Keep an evidence log someone else can run with#

For continuity, log fields such as: check date, verifier, payer legal name, payer jurisdiction, FATF label at check time, provider or product reviewed, rail, presentment currency, settlement currency, beneficiary details, source page or support-reply date, outcome color, term changes, and next recheck trigger. Refresh this log at two handoff points: contract signing and before each major invoice.

Record your own invoice-size or exposure limit and the evidence supporting it. A yellow classification permits only a lawful supported route with agreed protections, not kickoff while required checks remain unresolved. Recheck unexplained entity changes, bank details and missing transfer information. Drafting terms does not settle those questions.

Write Contract Terms That Price in Compliance Friction#

If your intake result is anything other than clean green, price payment uncertainty into the contract from the start. The goal is to reduce unsecured exposure, define clear pause rights, and treat cash as usable only when it is actually available.

Define the terms before you set timing#

Compliance friction is operational delay or extra documentation across the payment path. Review delay is time when a payment is submitted or collected but provider, bank or intermediary checks remain. Bank-available cash, called settled cash here, is money actually accessible in your business bank account, excluding known holds. Available provider balance may still require payout. Bank receipt does not eliminate later refund, dispute or reversal risk.

Use FATF findings alongside applicable law and actual provider rules. The latest high-risk and increased-monitoring statements checked here are dated 19 June 2026. FATF cannot release your held funds. Increased monitoring alone does not call for blanket enhanced due diligence, while high-risk treatment depends on the named country. Neither advance payment nor a small phase cures a legal prohibition.

Clause patterns with clear "use this when" triggers#

Milestones + upfront coverage#

Use this when a lawful supported route has delay risk that you need to allocate explicitly. Illustrative wording: The advance for each specified phase is due before that phase starts. For these advances, work starts when funds reach the designated account and are bank-available, subject to the agreed deadline and hold procedure.

Verification-linked timing#

Use this when required checks or advance availability affect the agreed start date. Illustrative wording: If an identified required check or agreed advance remains incomplete, we will notify each other and use the specified start-date adjustment process. This does not alter unrelated delivery or payment obligations.

Payer accuracy#

Use this when a parent, agency or other third party may pay. Illustrative wording: We will identify the contracting party and any authorized payer, document their relationship and invoice allocation, and confirm provider acceptance. Payment discharges the client’s obligation as specified in this agreement.

Screening cooperation#

Use this when a provider may request supporting records. Illustrative wording: Each party will provide the relevant records reasonably required for a lawful payment review through the approved secure channel, with the stated response deadline and privacy protections.

Status-shift protection#

Use this when legal or provider treatment can change during the project. Illustrative wording: If a material legal or provider restriction affects this route, we will notify each other and follow the agreed suspension, review and termination procedure. Changes to milestones, price or a permitted payment route require the agreed written approval.

These are negotiating patterns, not ready-made enforceable clauses. Specify the phase, advance, deadline, notice, permitted suspension scope and remedy; get local review where needed. Net-payment terms may require delivery before collection. A client’s completed payment is not unpaid merely because your chosen provider holds it. Allocate that risk expressly rather than unilaterally stopping owed work.

Decision criteria at signing and before new scope#

Recheck material payer, beneficiary and route changes. Resolve required legal and provider checks before affected activity. For existing lawful work, use the contract’s notice and suspension procedure; a provider payout hold alone does not create a stop-work right. You can decline unaccepted expansion or negotiate new milestones and funding without relabeling a collected invoice unpaid.

Start with a small paid phase, then expand scope#

Start small when the route is workable but not fully proven, then expand only after the payment behavior matches the paperwork.

• Phase 1 (commit small): limited scope, paid phase, complete document set (signed contract, scope, invoice, legal payer details, beneficiary details).
• Phase 2 (expand): only after Phase 1 payment behavior is normal and records stay consistent.
• If status shifts: reopen terms before accepting additional unsecured work.

Use this negotiation script: For this new scope, I can offer a smaller phase with an agreed advance and start condition, or a broader phase with the documented route and funding in place. Existing delivery and payment obligations continue under our current agreement; any revised dates need approval.

Related reading: A Canadian Freelancer's Guide to Setting Up a US Stripe Account.

Before kickoff, draft terms that match your risk tier so milestone timing, verification dependencies, and scope limits are explicit in writing. Use the Freelance Contract Generator.

Set Up Invoicing and Collection to Prevent Avoidable Holds#

Use one stable payment path per client and count cash as usable only when it is settled in your business bank account. Avoidable holds and returns can happen when identity or destination records drift mid-cycle, or when you act on a paid invoice before payout settlement is complete.

Lock the payment path before the first invoice#

Keep rails, payer details, and payout destination stable through each invoice cycle unless you are correcting a verified error. Late changes can increase return and hold risk, especially on routes already likely to get extra review.

Use this order every time:

1. Confirm legal payer name, payer contact, collection route, and your beneficiary details.
2. Issue the invoice with matching legal names, a consistent invoice ID format, and a service description aligned to scope.
3. Collect on the agreed route only.
4. Confirm payment success before moving to payout.
5. Initiate payout only to prechecked destination details tied to that client record.
6. Count funds as available only when they are settled cash in your business bank account.

Because FATF public jurisdiction statements are updated on a recurring cycle, recheck route risk at signing and again before major invoices, especially if client, sender, or path details changed since intake.

Use payment states that mean one thing#

Track invoice collection, payment processing and payout separately. These labels can coexist: a paid invoice may have a successful payment while its payout remains pending.

Paid invoice describes collection against the client’s debt. Payment confirmed describes the processor or rail’s actual result. Payout initiated describes movement from provider to bank. Settled cash here means bank-available money. Record each separately with timestamps, owners and the next check; do not force one label to replace the others.

Do not treat these states as interchangeable. Paid invoice is not settled cash, and payout initiated is not final availability. Even a posted payout does not guarantee bank-available cash. At each state change, log the timestamp, owner, pass or fail result, action taken, and next review time.

A paid invoice can still leave a cash shortfall#

Suppose the client fully pays a $2,000 invoice into your provider account, but payout is held. With a $60 processing fee borne by you, the invoice remains fully collected and the expected net payout is $1,940. The fee is your cost, not another $60 the client owes. None of the held $1,940 belongs in accessible cash yet.

If accessible bank cash is $800, contractor obligations are $500 and a tax reserve is $200, only $100 remains. Another $300 bill creates a $200 shortfall despite the paid invoice. Resolve that with legitimate available funding or agreed creditor arrangements. Do not silently miss owed payments, bill the client twice or suspend promised work without a valid right.

Run checkpoints and contain failures fast#

Check the same fields before invoice issue, after payment confirmation, and before you treat funds as available for the next unsecured milestone. Review the legal payer name, sender identity if visible, invoice amount and ID, service description, and payout destination details.

Make pause triggers binary#

Write clear triggers with the permitted response and notice, rather than inventing new contract rights after a problem:

• If required legal or payer checks are unresolved, stop affected prohibited or unsupported activity; do not disguise party details.
• If records change, investigate the actual discrepancy. Document authorized third-party payment and legitimate beneficiary changes rather than demanding every name match literally.
• If the invoice is collected but payout is unsettled, keep its paid status, exclude held funds from cash and follow any agreed advance or suspension condition.
• If a payment is pending and cannot be cancelled, confirm its outcome before requesting a replacement. Do not charge again merely because bank cash has not arrived.

This is stricter, but cheaper than resolving mismatches after more unsecured work has shipped.

Send a process-first client update#

When a checkpoint fails, send one short update with the required fields:

Invoice ID: Amount: Current invoice state: Current payment state: Current payout state: Pending verification item: Action underway now: Who owns the next step: Next review time: Effect on the next unsecured milestone:

Keep the message factual and state-based. If this friction repeats across clients or rails, tighten billing intervals and review margin impact. See The Silent Profit Killer: How to Stop Margin Erosion in Your Freelance Business.

A fallback, including crypto, must be lawful and permitted for the parties and transaction; it cannot evade sanctions, a provider restriction or a held-payment review. For currency, custody and compliance tradeoffs, see How to Get Paid in Crypto as a Freelancer.

Build a Small Evidence Pack for Enhanced Due Diligence Events#

Keep an invoice-linked evidence pack so you can answer a specific provider request without reconstructing the project. Ordinary freelancers are not automatically required by FATF to conduct financial-institution due diligence on every client. Your own obligations depend on applicable law, business activity and provider terms. Collect only necessary records, store sensitive data securely and use the provider’s approved channel.

An enhanced due diligence event is a situation in which the responsible institution applies additional checks. FATF’s June 2026 country-specific high-risk statement and increased-monitoring statement have different treatment. Counterparty identity means identifying the actual parties with reliable records; legitimate business purpose connects the payment to real contracted services. A list entry is not evidence that an individual client is illicit.

Keep one trail per invoice cycle: the legal payer, scope, invoice, payment trail, and delivery proof should all point to the same real business activity.

Use these binary pause triggers as an internal risk-control policy before each new invoice cycle:

• Resolve identity or legal eligibility information that is actually required before the affected transaction; record who requests it.
• Fix errors in invoice amount, customer, scope or payment allocation. Do not postpone an otherwise valid invoice solely because an optional internal record is missing.
• Keep delivery proof for completed work. An agreed advance invoice can be valid before delivery: record its contractual basis and attach delivery evidence later.

Run this maintenance checklist at the end of each billing cycle:

1. Add the final invoice, payment confirmation, and delivery proof to the invoice-cycle folder.
2. Confirm legal names, invoice ID, and project reference match across files.
3. Version superseded files clearly, for example v2026-03-26, and archive older copies instead of overwriting.
4. Check access controls so only current staff or advisers can access full-detail documents.
5. Log the last review date and next review date.

If you want this upkeep to stay lightweight, fold it into your recurring finance process using How to Automate Your Freelance Tax Preparation.

If your issue is a specific payment corridor rather than a FATF listing, The Best Way for a UK Freelancer to Get Paid by an Australian Client compares practical options.

Handle Mid-Project List Changes Without Blowing Up Cashflow#

When a mid-project list alert appears, verify it first, then adjust delivery and billing in a fixed order. Do not treat rumors as facts, and do not keep expanding unpaid scope while status is unclear.

A risk signal is a dated jurisdiction-level FATF finding. An unverified signal is a claim not yet matched to an official source. A verified change is an update explicitly stated in a dated FATF publication, such as the 19 June 2026 statements or June plenary outcomes. A cashflow-control event is an actual provider or bank restriction, such as a payout pause or transfer review. These are different events and require different responses.

Use these checkpoint rules before each major milestone or near-term invoice:

• Use a compliance or payment-risk clause only when its actual trigger is met, with the required notice and scope. A social-media alert is not automatically such a trigger.
• Resolve material legal, invoice or route errors before affected activity. Do not withhold valid billing merely because optional record housekeeping remains.
• If an invoice is collected but withdrawals are paused, leave it paid and show the held amount separately in the cash forecast.
• Do not accept additional uncommitted exposure you cannot fund. Existing lawful delivery and creditor-payment obligations remain unless validly changed or suspended.

That controlled pause can be cheaper than hidden margin erosion.

Use this client update: “We are verifying [dated source or provider notice] for [affected route]. The invoice/payment status is [actual status], and [person] is checking [specific requirement] by [date]. Existing obligations continue under our agreement. If its notice or suspension provision applies, I will identify the affected scope and propose the permitted revised timing.”

Anchor checks to official FATF publications, which are issued three times a year, usually in February, June, and October, instead of relying on social chatter.

Recover Faster From Holds Returns and Rejections#

Treat this as a sorting problem first. If you label the case correctly on day one, your recovery actions get faster and cleaner.

In this workflow, a hold is a temporary restriction where funds are not fully available during review or dispute checks. A return means funds were sent back after the payment did not complete under that rail or program. A rejection means the payment could not be processed and was tagged with a failure reason or code. A prolonged pending review means the provider is still reviewing the transaction. It is not the same as a failed payment.

Use these decision criteria every time:

• Confirm the exact failure reason and original outcome before retrying.
• Correct genuine identity, account-detail or invoice-allocation errors, including documenting legitimate third-party payment.
• Exclude held funds from cash; negotiate future exposure and use existing lawful suspension rights for owed work.
• Reassess repeated failures and choose a lawful permitted alternative for future or confirmed-returned payments.
• Track time, fees and delivery effects as margin erosion, while keeping client collection and provider liquidity distinct.

FATF’s current country statements explain jurisdiction treatment, not provider case-resolution deadlines. Confirm legal permissions, actual account notices and the transaction’s original status before promising recovery or switching routes. Apply case-specific checks rather than a blanket country cutoff. A paid invoice, provider hold and legally blocked transfer require different actions.

Confirm What Varies by Country and Program Before You Commit#

Treat this as a pre-commit control: a risk signal is not a legal verdict, and not proof that your payment route will clear.

Keep these three checks separate every time:

• Your country legal position: the current local requirement that applies to your transaction type in the relevant jurisdiction.
• Your provider program rules: the current terms and compliance criteria for the exact payment product you plan to use.
• Your transaction path: the actual money route, including payer country, beneficiary country, currency pair, payout method, and intermediary or bank steps.

If any point is not verified, do not guess. Mark the item as unresolved and hold commitment until you confirm the requirement.

Run this check at signature and again before any major invoice. Save dated evidence each time.

Use a written commitment policy, adapted to your legal advice and risk tolerance:

• When legal, provider and route checks are current and consistent, consider the scope your reserves can fund.
• When a lawful supported route has timing uncertainty, negotiate smaller phases and payment conditions.
• When legality or required authorization remains unresolved, pause affected activity or decline; prepaid work is not an exception.

That discipline can reduce the chance that uncertainty turns into delays, fees, and rework that compound into margin erosion.

If screening raises a PEP flag alongside country-risk checks, What Is a Politically Exposed Person and How to Decide Next Steps explains what that means and how to handle it.

Put This Into Practice on Your Next Client#

Use one repeatable checkpoint before you send a proposal or invoice, and force a branch decision before you commit more unsecured work. Do not rely on static country lists. FATF updates these public documents three times a year, and status can change between cycles.

Run this checklist pre-proposal, at signature, before major invoices, and any time the payer, route, country, or provider program changes.

If you work solo, still keep the ownership split as separate passes: verification, document consistency, then status log or follow-up. If you work with a teammate, assign those three owners explicitly.

Save the FATF statement date, provider program, and fallback route in the client file so you can rerun decisions cleanly when timing or risk signals change. For execution detail, use Set Up Invoicing and Collection to Prevent Avoidable Holds. If review friction is already hurting profitability, read The Silent Profit Killer: How to Stop Margin Erosion in Your Freelance Business.

Save the exact requirements and follow-up date in the client file. If the route remains legally or operationally unresolved, obtain the relevant adviser or provider confirmation before committing affected work.