FATF October 2026 Statements: What Crypto Accounting Teams Should Do

CryptaCount Editorial · November 3, 2026 · 5 min read

Japan's Financial Services Agency has flagged that the FATF adopted and published two fresh statements at its October 2026 plenary: one on high-risk jurisdictions subject to a call for action, and one on jurisdictions under increased monitoring. For any firm choosing or running crypto accounting software, the practical point is simple: your counterparty, wallet and exchange data has to be screened against the current lists, and the records must show that you did it.

What the FSA notice actually says

The two statements

The FSA published its notice on 2 November 2026 (Reiwa 8). It explains that the Financial Action Task Force, at its October 2026 plenary, adopted and released statements identifying jurisdictions that are not cooperating enough on anti-money laundering and counter-terrorist financing. There are two documents. The first covers "High-Risk Jurisdictions subject to a Call for Action". The second covers "Jurisdictions under Increased Monitoring". Both are dated 30 October 2026.

What the notice does not tell you

The FSA page is a pointer, not a summary. It links to the original FATF English texts and does not list which countries or territories moved on or off either list, nor does it describe any new Japanese rule or deadline. We have deliberately not guessed at names or changes. Anyone who needs the detail should read the two FATF statements directly, using the links from the FSA page, before updating controls.

Why this matters for firms and CFOs

Two lists, two levels of response

The distinction in the titles matters. A call for action is the stronger category and is the one that typically drives enhanced due diligence or countermeasures. Increased monitoring signals that a jurisdiction has committed to fixing deficiencies and is being watched. Your policy should say, in writing, how each category changes onboarding, transaction monitoring and approval levels. Check the FATF texts for the exact wording of the expected response before you set those rules.

Crypto makes geography harder to see

A bank account has a country attached. A wallet address does not. Exposure to a listed jurisdiction in a crypto business usually shows up indirectly: a customer's residence, an exchange's place of incorporation, a payment institution at the fiat on-ramp, or a counterparty's registered office. Finance teams that hold this information in separate systems tend to discover the link late.

Accounting and bookkeeping implications

For accounting firms and auditors

If you service clients with digital assets, the new statements are a trigger to refresh client risk assessments. Re-run the jurisdiction field for every client and every material counterparty against the October 2026 lists. Keep a dated record of the check, the version of the list used, and the decision taken. For audit work, this supports your understanding of the entity's compliance environment and any judgement about whether unusual flows need further inquiry.

For CFOs and finance controllers

The ledger is where compliance evidence ends up. Good crypto bookkeeping software should let you tag each wallet, venue and counterparty with a jurisdiction, then filter transactions by that tag. That turns "did we deal with anyone connected to a listed jurisdiction this quarter" from a week of spreadsheet work into a report. When evaluating digital asset accounting software, ask whether the jurisdiction data is editable, versioned and exportable with an audit trail, because lists change at every plenary.

For individual filers

Most individuals are not directly bound by FATF lists, since the obligations fall on regulated businesses. The knock-on effect is on you: the exchange you use may ask for more information, delay a transfer, or restrict dealings linked to listed jurisdictions. Keep clean records of where funds came from and where they went, including dates, amounts and the platform used, so you can answer questions quickly. Those same records are what you need for tax reporting anyway.

Practical next steps

A short checklist

Read both FATF statements from the links on the FSA page and note any changes to the lists.
Update the jurisdiction reference data in your screening and accounting tools, and record the effective date.
Re-screen existing clients, exchanges and payment partners, not only new ones.
Review policy wording so that each list category maps to a defined control.
Document who reviewed the results and what was decided, including "no match" outcomes.
Check whether your local supervisor, such as the FSA in Japan, has added its own guidance beyond the FATF text.

Where software helps and where it does not

Software can store the data, flag matches and preserve the evidence trail. It cannot decide your risk appetite or replace the judgement of a qualified reviewer. Treat the lists as an input to a documented process, not a box ticked by a tool.

FAQ

What did the FATF publish in October 2026?

According to the FSA notice, two statements were adopted and published on 30 October 2026: one on high-risk jurisdictions subject to a call for action and one on jurisdictions under increased monitoring.