IRS Title 31 Examination for MSBs: What to Expect and How to Prepare

An IRS Title 31 examination is the government's way of testing whether a money services business (MSB) is actually complying with the Bank Secrecy Act (BSA), not whether it owes additional income tax. The IRS is not the agency that writes the BSA's rules; it is one of the agencies FinCEN has authorized to check compliance with them. Understanding that distinction, and the steps the examination actually follows, is the difference between a straightforward examination and one that goes sideways from confusion alone.

This guide walks through a Title 31 examination in the order an MSB experiences it: selection, the appointment letter, the Information Document Request, the initial interview, the AML program review, transaction testing, potential deficiencies, the closing conference, and the range of outcomes. It is not a checklist for how to conduct your own independent BSA/AML audit; ComplyFactor covers that separately in its Independent BSA/AML Audit Checklist for U.S. MSBs, which this article references rather than repeats.

What Is an IRS Title 31 Examination?

"Title 31" refers to the title of the U.S. Code where the Bank Secrecy Act's core reporting and recordkeeping provisions sit, alongside the regulations FinCEN has issued under it at 31 CFR Chapter X. An IRS Title 31 examination is a government review of an MSB's compliance with those requirements: its written AML program, its recordkeeping, and its Currency Transaction Report (CTR) and Suspicious Activity Report (SAR) filings, among other obligations. The IRS's own manual describes the purpose plainly: a risk-based examination that evaluates whether the AML program's policies, procedures, and internal controls are adequate, tests whether the program is actually implemented through transaction testing, identifies noncompliance, and confirms corrective action is taken where deficiencies are found.

Businesses commonly search for "IRS BSA audit" or "MSB audit" when this happens to them; the IRS's own materials use "BSA examination" and "Title 31 examination," and this article uses that terminology throughout.

Why the IRS Examines MSBs for BSA Compliance

FinCEN, the Financial Crimes Enforcement Network, administers the Bank Secrecy Act. The Secretary of the Treasury delegated that administrative authority to FinCEN's Director, and FinCEN in turn redelegated the responsibility to examine certain financial institutions, including MSBs, to the IRS. The delegation is set out at 31 CFR § 1010.810(b)(8), which gives the Commissioner of Internal Revenue authority to examine financial institutions not otherwise examined by a federal bank supervisory agency, including non-bank financial institutions such as check cashers and other MSB categories: dealers in foreign exchange, check cashers, issuers or sellers of traveler's checks or money orders, providers and sellers of prepaid access, and money transmitters.

This delegation is limited to examining for compliance. FinCEN retains civil penalty authority over BSA violations, with one exception: the IRS itself holds authority to assess civil penalties for Report of Foreign Bank and Financial Accounts (FBAR) violations, under a separate delegation at 31 CFR § 1010.810(g). For an ordinary MSB Title 31 examination that does not involve FBAR issues, the practical division is: the IRS examines and documents findings, and FinCEN (not the IRS) holds the civil penalty authority over the underlying BSA violations it identifies.

This also means an IRS Title 31 examination is not the same thing as every FinCEN enforcement action. FinCEN can act on information from many sources, and not every FinCEN enforcement matter begins with an IRS field examination. Equally, MSBs are not examined on a fixed, universal schedule; case selection is risk-based, as discussed below.

An IRS Title 31 Examination Is Not an Income-Tax Audit

This distinction is worth stating directly because the same agency conducts both, and the confusion is common.

The IRS's own examiner manual instructs that examiners are prohibited from using the Integrated Data Retrieval System (IDRS) or other Title 26 (income tax) information during pre-planning or while conducting a BSA examination, including for something as basic as verifying an address or an EIN. The manual further states that examiners are prohibited from accessing tax or tax-related information during a BSA examination because of the disclosure restrictions in IRC § 6103, which governs confidentiality of tax return information. In practical terms, the examiner assigned to your Title 31 case is walled off from your income-tax file by internal policy and by a separate statutory disclosure regime for the purpose of the BSA examination itself; a BSA examiner does not have that file open in the next window.

This separation does not mean information developed during a BSA examination can never lawfully reach the income-tax side of the IRS under any circumstance. Current procedure describes a distinct, documented referral path (a Form 5346, Examination Information Report, approved by the BSA group manager and routed through IRS Case Selection) for a BSA examiner who uncovers information with a potential material impact on income-tax or employment-tax compliance. The BSA examiner does not simply reclassify the case as a tax audit, does not access the taxpayer's Title 26 file to make that referral, and any related-statute determination that would allow tax-return information into a Title 31 matter follows its own separate, documented procedure. Title 31 and Title 26 remain two separate legal frameworks with two separate processes throughout; the referral path exists precisely because the two are kept apart by default.

How MSBs Are Selected for BSA Examination

Selection and scope are two different questions, and it is worth keeping them separate. Case selection is the decision to examine a particular entity at all; scope and depth, covered later in this article, is how deeply an already-selected examination goes once it starts.

The IRS's BSA Case Selection function identifies entities and builds cases using a risk-based approach. Current IRS guidance identifies the following as factors that may be used in the Title 31 case-selection process:

• referrals from IRS Criminal Investigation, FinCEN, or other BSA examinations;
• location in a High Intensity Drug Trafficking Area (HIDTA) or High Intensity Financial Crime Area (HIFCA);
• the entity's compliance history;
• unusual CTR or SAR filing patterns, or non-filing patterns;
• anomalies in CTRs or SARs filed on the entity by other financial institutions, indicating cash activity inconsistent with what would be expected;
• appearing to operate as an MSB without being registered as one;
• being registered as an MSB but not having renewed that registration, or being a newly registered MSB;
• a history of filing forms late or with errors;
• an appearance of facilitating structuring; and
• referrals from federal, state, or local law enforcement or regulatory agencies.

This is a risk-based list, not a formula, and the IRS does not publish a precise weighting or trigger threshold. It is inaccurate to say that filing a particular number of SARs, by itself, causes an examination, or that filing more SARs automatically increases examination risk; unusual filing patterns are one listed factor among many, and can point in either direction. Do not treat any single factor above as a guaranteed trigger, and do not assume the absence of any one factor makes examination impossible. Separately, once a case is selected and assigned, a different set of considerations, discussed under "IRS Examination Phases" below, governs how wide and how deep that specific examination actually goes; those scope-and-depth factors (such as prior examination results or filing-volume trends) inform the conduct of an examination already underway, not the initial decision to select the entity.

How an IRS Title 31 Examination Begins

Initial contact must be made in writing, using an approved form letter; current IRS procedure does not permit initiating a BSA examination by unsolicited phone call. For MSBs, the relevant document is:

Letter 4313 — Bank Secrecy Act Money Services Business Examination Appointment

Other letters exist for other BSA-covered industries and case types (for example, Letter 3494 for casinos, Letter 4155 for insurance companies, Letter 4479 for precious metals, stones, and jewels dealers, and Letter 5946 for large cases such as MSB principals, credit unions, or headquarters examinations). Not every MSB receives the identical letter, and which one is used depends on the entity type and case size.

The letter may be sent by registered or certified mail. If the examiner does not receive confirmation of receipt within 14 calendar days, current procedure directs the examiner to follow up by phone with the compliance officer, general manager, or other appropriate contact to confirm receipt.

The appointment letter is typically accompanied by the initial Information Document Request, discussed next, so that records can be assembled before the first meeting.

What Is Form 4564, the Information Document Request?

Form 4564, Information Document Request (IDR), is the standard tool IRS examiners use to formally request records and information during a BSA examination, and it is typically sent together with the appointment letter. Current IRS guidance is explicit that sample IDRs published in the agency's own examination-technique materials are examples only, and that examiners must expand or contract them based on the facts and circumstances of the specific examination. The IDR is meant to document what the examiner needs to verify BSA compliance for that particular MSB, not to serve as a universal checklist applied identically to every case. There is no single, mandatory IDR that every MSB should expect to receive in the same form.

How Much Time Does an MSB Have to Produce Records?

Current IRS examiner guidance states that the initial interview, or any requirement to produce records ahead of that interview, should generally be set for a date at least 30 days after the appointment letter is made available to the financial institution, so the business has adequate time to gather what has been requested. This is internal IRS scheduling guidance for examiners, not a statutory deadline imposed on the MSB, and it is not the only timing standard in play:

• Separately, IRS quality standards call for the initial appointment itself to be conducted within 45 calendar days of "first action" on the case (generally, when the appointment letter is mailed), with an internal target of holding it within 28 to 35 days where possible. This is an examiner performance benchmark, not a right the MSB can enforce or a deadline that shortens the 30-day preparation guidance above.
• A separate, later concept, the Mutual Commitment Date, addresses the target date for closing the examination, not the initial records deadline; it is discussed below.
• If records are not produced voluntarily, the IRS retains summons authority as a legal enforcement mechanism (discussed in the FAQ below), which operates on its own separate legal process and is not the first step the IRS takes.

Do not treat any of these figures as a single, universal "30-day answer" to every deadline question in the examination; they address different stages and different questions, and the specific date that applies to a given IDR is the one the examiner actually sets, in writing, for that request.

What Records May the IRS Request?

What follows are categories of records commonly requested; the applicable list for any specific MSB depends on its activities, and not every MSB maintains every category below.

Corporate and business information: legal entity details, ownership and organizational structure, business locations, products and services offered, and the transaction channels and systems used to deliver them.

FinCEN registration: current MSB registration (FinCEN Form 107) and evidence of timely renewal, and the agent list where the MSB operates through agents.

AML compliance program: the written AML program, the MSB's risk assessment or other documented risk-analysis materials (if maintained; a standalone written risk assessment is not itself a separate express requirement under current § 1022.210, though examiners will still evaluate whether the program is genuinely risk-based), policies and procedures, evidence identifying the designated compliance officer, training materials and attendance records, and independent review reports along with any documented remediation of prior findings.

BSA reporting: records supporting filed CTRs and SARs, and the procedures used to identify reportable activity. SAR confidentiality is a legal requirement, and it works in a specific direction: an authorized IRS BSA examiner conducting the examination may review the MSB's own SAR filings and related records as part of the authorized examination itself; that access is not restricted. What is restricted is disclosure. An MSB, and the IRS, must not disclose the existence or content of a SAR to the subject of that SAR or to any other person or entity outside the authorized examination process. Where the IRS holds a SAR filed by a different financial institution (for example, referencing the MSB under examination), that SAR cannot be revealed to the examined MSB. In practice, this means an MSB should be prepared to produce its own SAR-related records to the examiner in the ordinary course of the examination, while still not discussing the existence or content of any SAR with anyone outside that authorized process, including its own customers, vendors, or unrelated third parties.

Transaction records: transaction-level data relevant to the MSB's specific activities, which may include wire or funds-transfer records, money order or check-cashing records, currency-exchange records, prepaid access records, or virtual-currency transaction data, depending on what the business actually does.

Agent and network information: for MSBs that operate through agents, the agent list, agent agreements, evidence of agent monitoring, and records of agent training, where applicable. This category applies specifically to MSBs with agent networks; it does not apply uniformly to every MSB structure.

System and data information: data extracts, transaction-monitoring configuration and output, and explanations of the fields, filters, and logic used to generate reports from underlying systems.

None of the above is a claim that every MSB must maintain every document listed; the actual scope of any IDR is set by the examiner for the specific facts of that examination.

Expect the IRS to Look Beyond PDFs and Written Policies

Current IRS examiner guidance directs examiners to inquire specifically about computerized records and systems, including point-of-sale systems, and whether a download of transaction data is available. A written policy that describes a control is not, by itself, evidence that the control operated; the examiner's job includes testing actual transaction data against the policy's stated rules.

Practical preparation, as a matter of ComplyFactor recommendation rather than IRS-prescribed requirement, includes:

• preserving native, unmodified source data rather than only summary reports;
• confirming the exact date range a request covers before extracting data;
• validating that transaction counts in an extract reconcile to the underlying system of record;
• documenting any filters or transformations applied to produce an export;
• retaining clear field definitions so an examiner (or your own reviewer) can interpret the data without guesswork; and
• making agent or location coverage explicit, so a data set is not silently missing a location or agent's activity.

IRS Examination Phases

The IRS's risk-based examination process broadly moves through: pre-planning, determining scope and depth, the initial interview and business walkthrough, evaluating the AML program, examining books and records, transaction testing, and developing conclusions to close the case. Two aspects of scope and depth are worth understanding precisely, because they are often misstated.

Initial examination scope is typically the most recent six-month period, though IRS guidance notes this can be narrower for high-volume principal remitters (where a smaller window, such as one month, may still be sufficient to assess compliance given transaction volume) and can vary based on the volume and nature of the specific business. This is the overall period the examination covers.

Initial transaction testing typically starts with the most recent three months, inside that already-established scope period. Two different things can then happen, and they are not the same:

• If nothing significant turns up, testing may simply stay within the initial three-month window, and the examination can close on that basis without ever testing the remaining months in the six-month scope.
• If large, unusual, or questionable items are identified, or the examiner finds significant program deficiencies, testing can extend through the remainder of the already-established six-month scope period. Current IRS guidance is explicit that reviewing transactions for the full, already-approved six-month scope period does not itself require the examiner to complete a formal scope-expansion request or obtain separate group-manager sign-off for that specific step, because it stays within the period the case was already opened to cover.

Formal scope expansion is a different, further step: extending the examination beyond its original period, or into new issues or related entities, does require the examiner's group manager to approve the expansion using the IRS's own scope-expansion documentation. So the correct way to think about it is: moving from a three-month sample to the full six-month period the case was already opened for is a normal, unremarkable part of transaction testing; going beyond that original six-month period, or picking up an issue or entity outside it, is what triggers the formal approval step.

There is no fixed, universal sample size or lookback period that applies to every MSB examination. IRS guidance explicitly ties scope and depth to the specific facts of the case, including the entity's size, the volume and nature of its transactions, and what earlier stages of the examination have found. A previous MSB examination that found only minor issues may result in a narrower-scope follow-up; a first-time examination or one uncovering significant gaps may expand further, subject to the approval step described above where it goes beyond the original period.

What Happens at the Initial Interview?

The examiner will typically want to speak with the people actually responsible for BSA compliance: the designated compliance officer, relevant owners or managers, and operations staff who process the transactions with reporting or recordkeeping implications. Current guidance describes the interview's objectives as establishing how much BSA knowledge management and staff actually have, understanding how the business genuinely operates (as distinct from what the written policy says), tracing how a transaction moves from initiation to settlement, and understanding how the systems and records that support compliance actually function, often including a live system demonstration.

IRS guidance lists specific areas examiners are directed to cover at minimum, including: the presence of an AML program with all required elements; which employees handle cash transactions and file CTRs; the volume of BSA-relevant transactions; internal controls over cash and approval authority; the type of computer system in use; procedures for verifying the completeness and accuracy of records and reports; controls around suspicious-activity identification and reporting; and staff training on BSA requirements.

Useful preparation means employees genuinely understand their actual day-to-day responsibilities and can accurately describe the real process, not a rehearsed or idealized version of it. Do not coach staff to give scripted or misleading answers; inconsistencies between what different employees describe, or between what is described and what the records show, are themselves a red flag an examiner is trained to notice, and a rehearsed inaccuracy is worse for the business than an honest description of an imperfect but real process.

Business Walkthroughs and Tours

Where the IRS's guidance supports it, examiners may conduct a tour of business locations, generally including the headquarters for a principal remitter or issuer, to see how transactions actually move through the operation and how records are created in practice, including live test transactions run against the system's own dollar-threshold controls. Tours are typically planned after the initial interview, so the examiner has a frame of reference for interpreting what was described.

For an online or remote fintech or virtual-currency MSB without a traditional retail storefront, a physical tour in the conventional sense may simply not reflect how the business operates; the underlying objective, understanding how a transaction actually flows and how records are created, still applies, but the IRS adapts its techniques to the operating model rather than imposing a fixed physical-tour requirement on every digital business.

How IRS Evaluates the MSB's AML Program

Under 31 CFR § 1022.210, every MSB must develop, implement, and maintain a written AML program reasonably designed to prevent the business from being used to facilitate money laundering and terrorist financing, commensurate with the location, size, nature, and volume of the services it provides. As of this writing, the current, operative version of that regulation requires four elements: (1) policies, procedures, and internal controls reasonably designed to assure compliance; (2) designation of a person responsible for day-to-day compliance; (3) ongoing training of appropriate personnel; and (4) independent review to monitor and maintain an adequate program, with scope and frequency commensurate with the risk of the services provided.

The examiner's evaluation generally tests whether each element is not just written down but genuinely implemented: whether policies match actual practice, whether the designated compliance officer's role functions in reality, whether training actually reaches the relevant staff, and whether independent review occurred, and if so, its scope, frequency, findings, and whether the MSB acted on them. This article does not restate the full independent-review testing framework here; ComplyFactor's Independent BSA/AML Audit Checklist for U.S. MSBs covers what an independent reviewer should test under § 1022.210(d)(4) in detail.

A significant and important current-law note applies here. On April 7, 2026, FinCEN issued a Notice of Proposed Rulemaking (Docket FinCEN-2026-0034) proposing to fundamentally restructure AML/CFT program requirements across all BSA-covered financial institution categories, including MSBs under § 1022.210, shifting toward an outcomes-based "effectiveness" standard. That proposal superseded an earlier, separate 2024 proposal on the same subject. As of this writing, the April 2026 proposal remains a proposed rule: its comment period closed June 9, 2026, no final rule has been issued, and any final rule would take effect 12 months after issuance if adopted as proposed. An IRS Title 31 examination today tests compliance against the current, operative § 1022.210 as it exists now, not against the 2026 proposal; do not treat proposed language as binding, and confirm the rule's status directly with FinCEN before relying on any account of it, including this one, since the status can change.

One additional nuance from the IRS's own examiner guidance is worth noting for accuracy: FinCEN issues interpretive guidance to clarify open questions under the regulations, but an examiner cannot cite an MSB for failing to follow FinCEN guidance as such, since guidance is not itself binding law. Where an MSB disregards relevant guidance and that choice increases its risk in a way that makes the AML program itself unreasonable or ineffective, a violation for failing to maintain an effective program can still result, but the violation is grounded in the program's inadequacy, not in non-adherence to the guidance document itself.

How IRS Transaction Testing Works

Transaction testing is where the examination moves from reading documents to checking whether real transactions were handled the way the written program says they should be. Depending on the MSB's activities, testing may cover CTR compliance and same-day aggregation, SAR decision-making on flagged activity, structuring indicators, funds-transfer recordkeeping, customer identification and information requirements, MSB registration status, agent-level activity, and whether monitoring controls actually caught what they were designed to catch.

IRS guidance describes this work as risk-based rather than governed by a fixed rule: statistical sampling can be useful for larger institutions with high transaction volumes, but may not be meaningful where there are too few transactions to sample statistically, in which case a more targeted, judgment-based selection is used instead. There is no universal sample size, no fixed percentage, and no guaranteed lookback period that applies to every MSB. As explained above, testing generally moves through the already-established scope period as findings warrant, and only extends beyond that original period through a separate, approved scope expansion.

Agent Networks, Branches, and Third-Party Data

For MSBs that operate as principals through a network of agents, examination techniques specifically address how the headquarters identifies its higher-risk agents and branches, whether it applies enhanced monitoring and training to them, and whether it has a documented basis for discontinuing agents whose risk becomes unacceptable. A headquarters-level examination typically includes review of a sample of agents and branches, generally weighted toward those the headquarters' own risk profile identifies as higher risk, alongside a broader sample of the remainder.

This agent-monitoring dimension applies specifically to MSBs with agent structures; a single-location MSB with no agents does not carry the same set of obligations, and this article does not suggest otherwise.

What About Crypto and CVC MSBs?

A business that acts as an administrator or exchanger of convertible virtual currency (CVC) can qualify as a money transmitter, and therefore an MSB, under FinCEN's existing guidance, depending on the specific activity involved; not every business that touches virtual currency meets that definition, and the analysis is activity-specific rather than automatic. Where a CVC business does qualify as an MSB, it is subject to the same Title 31 examination framework as any other MSB, and evidence an examiner may request can include wallet and transaction records, both fiat and virtual-currency transaction data, identification records where required, evidence of transaction monitoring calibrated to virtual-currency risk, and SAR decision-making specific to virtual-currency activity.

Where a business relies on blockchain analytics tooling as part of its actual monitoring practice, an examiner may look at what that tooling produced and how the business acted on it. Blockchain analytics is a common risk-management practice for CVC businesses, not a universal regulatory mandate; describe it accordingly rather than as an independently required control.

Follow-Up IDRs and Expanding Examination Scope

The first Form 4564 is often not the last. Additional IDRs can arise because the examiner needs to resolve an open question, validate a data set that did not reconcile, or continue testing within the case's already-established scope period. A follow-up request, on its own, is not evidence of a serious problem; it can simply reflect the examiner working through the case methodically. Formally expanding the examination beyond its original scope, into new issues, or to related entities is a further step that requires the examiner's group manager to approve, using the IRS's own scope-expansion documentation; it is a genuine escalation, distinct from continuing to test within the period the case already covers.

The Mutual Commitment Date

Current IRS procedure uses a Mutual Commitment Date (MCD), a tool to promote cooperation and a timely, orderly examination. The MCD is established with input from the MSB (or its representative) at the end of the initial appointment, and represents the target date by which the examiner expects to issue the closing letter. It is not a statutory deadline and does not guarantee the examination will actually close by that date. IRS guidance is explicit that the MCD can be extended if the examination expands to new issues, picks up related entities, uncovers new information, or the MSB becomes uncooperative; an extension beyond 30 calendar days requires the examiner to notify their own group manager and document the reasons. Treat the MCD as a planning and communication tool, not a guarantee, and expect the examiner to communicate proactively if it needs to move.

What Happens If IRS Identifies Deficiencies?

An examination observation is not automatically an established violation, and it is worth keeping several distinct concepts separate as the process moves forward: an examination observation, a documented deficiency, an apparent BSA violation, an IRS decision to refer the matter, and, ultimately, any FinCEN civil enforcement determination or criminal referral. These are sequential and conditional, not interchangeable labels for the same thing.

Not every deficiency leads to the same outcome, and the IRS does not have unilateral authority to impose a BSA civil monetary penalty on its own; that authority sits with FinCEN, except for FBAR matters. When an examiner identifies reporting, registration, recordkeeping, or AML-program deficiencies, current procedure requires discussing them with the MSB and documenting them, typically on Letter 1112, Title 31 Violation Notification Letter. Recommendations to correct the AML program appear on Form 13726, Summary of Examination Findings and Recommendations, and the MSB acknowledges the recommendations and commits to correcting the identified issues by signing Form 13727, Acceptance Statement; both forms travel together with the Letter 1112 package.

Where the examiner believes an apparent violation is significant or repeated enough to warrant it, the case can be referred for further action along one of two separate tracks:

• Civil referral to FinCEN, using Form 5104, Report of Apparent Violation of Financial Recordkeeping and Reporting Regulations. This is the mechanism by which the IRS passes a case to the agency that actually holds BSA civil penalty authority. FinCEN's own role, once it receives a referral, is to evaluate the matter independently and decide among its own range of responses: closing the case without contacting the subject, issuing a letter of warning or caution, or assessing a civil monetary penalty. The dollar amount of any penalty FinCEN ultimately assesses depends on factors it weighs itself, including severity, volume, willfulness, and the institution's overall compliance program; an IRS referral does not fix or predetermine that outcome.
• Criminal referral to IRS Criminal Investigation (CI), using Form 2797, Referral Report of Potential Criminal Fraud Cases, reserved for cases showing firm indications of willfulness, developed with the involvement of a Fraud Enforcement Advisor before any referral is made.

The IRS's own internal referral standards distinguish, in general terms, between apparent violations that typically warrant a FinCEN referral and those that typically do not, when deciding whether to refer a matter, which is a separate question from what penalty, if any, FinCEN ultimately imposes. A systemic or pervasive compliance-program deficiency, a pattern of repeated failures to file required reports, or a situation where an institution simply fails to respond to identified concerns are treated as significant for referral purposes. By contrast, current IRS guidance states that technical, minor, infrequent, isolated, and non-substantive violations are generally not referred to FinCEN, and that isolated first incidents of noncompliance are, by the IRS's own stated approach, normally not escalated to a referral. This is a statement about the IRS's own referral practice, not a guarantee that FinCEN could not still act on a technical issue through some other channel, or that no penalty could ever follow a first-time issue depending on its severity and circumstances; FinCEN retains its own independent enforcement discretion once any matter reaches it. Willfulness or reckless disregard, where they matter for a particular referral or penalty consideration, are generally established through circumstantial evidence such as a pattern of disregard for known requirements, repeated violations after the institution was already aware of them, concealment, or a documented failure to correct previously identified deficiencies.

Do not treat any single deficiency as automatically resulting in a monetary penalty or a referral, and do not treat "generally not referred" as "cannot be penalized" in every conceivable circumstance; the IRS's own framework is explicitly calibrated by severity, frequency, and whether the institution took corrective action, and FinCEN's own enforcement discretion sits on top of, and separate from, the IRS's referral decision.

What Happens at the Closing Conference?

The closing conference is where the examiner presents identified findings so the MSB can review them and, where appropriate, offer evidence or context before the case is finalized; good-practice guidance specifically directs examiners to keep the MSB apprised of issues as they arise during the examination, so that violations should not be raised for the first time at the closing conference. At the conference, the examiner discusses any deficiencies (whether related to the AML program, recordkeeping, or reporting), the MSB has the opportunity to respond, and remediation and future compliance expectations are typically discussed. The closing conference and its accompanying Letter 1112 package document the IRS examination's findings and the MSB's commitment to corrective action; they are a separate step from whatever action, if any, FinCEN or CI later takes on a referral, and reaching this stage does not itself mean a referral will follow. The opportunity to provide relevant evidence at or before the closing conference is not an unlimited, open-ended invitation to reopen the entire examination.

Possible Outcomes After a Title 31 Examination

Outcomes generally fall into a small number of categories, and the applicable label depends on what the examination actually found:

• No violations identified. Where the examiner reviews the MSB's records and finds no issues, the case can close as a "no-change" outcome. Where the examiner determines, without reviewing records, that the entity is not actually subject to BSA requirements or the case should be closed without further work, a different closing procedure applies, and the specific closing letter used depends on which of these scenarios actually occurred.
• Deficiencies documented, with corrective action. The MSB receives Letter 1112 and the accompanying forms, commits to remediation, and the matter can close on that basis without further escalation.
• Referral for further action. Where the apparent violations meet the IRS's own referral standards, the case moves to FinCEN (civil) or CI (criminal), as described above, and any penalty or enforcement decision from that point is made by that agency, not the IRS examiner.

Not every "no issue" case receives identical treatment or documentation; the specific closing letter and procedure depend on the facts, including whether records were actually reviewed.

Re-Examination and Follow-Up

IRS guidance recognizes that some cases warrant a follow-up examination, generally based on risk, such as where a prior examination found significant deficiencies or the MSB's risk profile has otherwise changed. There is no promise, express or implied, that closing an examination means the IRS cannot return; nor is there a fixed, universal interval (one year, two years, or otherwise) that applies to every MSB regardless of its facts. Where an MSB's own compliance program materially improves, or its risk profile is otherwise well-managed, a subsequent examination can reasonably be narrower in scope than the first, consistent with the risk-based approach described throughout this article.

What an MSB Should Do in the First 72 Hours After Notification

1. Confirm the letter and the examiner's contact details are genuine and consistent with current IRS procedure (written notice, not an unsolicited phone call).
2. Confirm this is a Title 31/BSA examination specifically, as distinct from any other IRS contact.
3. Record every date mentioned, including the appointment date and any IDR production deadlines, and calendar them immediately.
4. Assign a single internal examination coordinator to own the process and be the examiner's point of contact.
5. Read Form 4564 line by line, and resolve any ambiguity about what is actually being requested before assuming you understand it.
6. Map each IDR item to a specific system and a specific internal owner responsible for producing it.
7. Preserve records and existing versions of compliance documents exactly as they exist; do not edit or "clean up" historical policies or logs in response to the notice.
8. Identify data owners, vendors, and agents whose cooperation will be needed to produce complete records.
9. Compare source-system data to the requested population before submitting anything, to catch date-range or filter errors early.
10. Identify known gaps honestly, without concealing or backdating them, and determine the correct path for addressing any discovered filing gap under current FinCEN procedures (see the FAQ below on missed filings).
11. Determine whether legal counsel or specialized compliance support is warranted, given the scope, complexity, or potential exposure involved, particularly where a discovered gap may be significant or raise willfulness concerns.
12. Prepare staff for truthful, process-based interviews that describe how things actually work, not a rehearsed version of how they should work.

IRS IDR Response Matrix

ComplyFactor practical tool — not an IRS-prescribed template.

A structured response matrix helps coordinate a multi-department response to Form 4564 and reduces the risk of a missed item:

Using a matrix like this helps prevent missed IDR line items, coordinates departments that each hold a piece of the requested information, documents the scope actually agreed with the examiner, tracks document versions as they are produced, and surfaces open questions early enough to raise with the examiner before a deadline rather than after. The IRS does not require this or any similar tool; it is offered here as a practical aid.

Common Title 31 Examination-Response Failures

Based on the kinds of issues examiners are trained to look for, common self-inflicted problems in an examination response include:

• producing data for the wrong date range;
• omitting a location or agent from a production, whether accidentally or through an unclear scope understanding;
• an inconsistent transaction population between different data sets that should reconcile but don't;
• unexplained filters applied to an extract without documentation of what was excluded and why;
• reporting-system output that does not reconcile to the underlying source system;
• a policy document with no visible effective date or version history;
• missing evidence of the required independent review, or of remediation for its prior findings;
• incomplete training records;
• manually reconstructed data presented as though it were an original source extract;
• data held by a vendor or agent that was not identified or requested in time;
• inconsistent answers from different staff describing the same process;
• no version control across multiple document productions; and
• failing to disclose a known data limitation to the examiner rather than letting it surface unexplained.

Not every production error is itself a BSA violation. An operational failure in how the MSB responded to the examination is a different problem from an underlying regulatory non-compliance issue, and the two should be kept conceptually distinct when assessing what actually went wrong and what it means.

Independent Review Before the IRS Exam

An outside readiness review, conducted after an MSB learns it has been selected for examination, can genuinely help: it can surface missing evidence, inconsistent data, open remediation items, and unclear internal roles, and it can help organize the response before the examiner's clock starts running in earnest. What it cannot do is retroactively create a historical compliance record that did not previously exist. If the § 1022.210(d)(4) independent review requirement itself was not satisfied during the period now under examination, commissioning one now does not establish that it existed at the relevant time; it only demonstrates current diligence going forward.

How ComplyFactor Can Support Examination Readiness

ComplyFactor supports U.S. MSBs preparing for and responding to a Title 31 examination, including BSA/AML examination readiness assessments, independent AML program review, document-request mapping and coordination, transaction and data testing, and remediation planning following an examination or an internal readiness review, along with fractional BSA/AML officer support where appropriate.

ComplyFactor does not represent clients before the IRS as legal counsel, does not prevent or guarantee the outcome of an examination, does not guarantee that no penalty or referral will result, and cannot retroactively cure a period of historical non-compliance. Where a matter involves legal privilege, a summons dispute, potential criminal exposure, or FinCEN or CI enforcement, qualified U.S. legal counsel should be engaged.

Frequently Asked Questions

Can an MSB have an authorized representative during an IRS Title 31 examination?

Yes. An MSB may authorize a representative for a Title 31 examination using Form 2848, Power of Attorney and Declaration of Representative, completed with "Title 31 BSA Examination" entered as the description of the matter, and checking the box confirming it is a specific use not recorded on the IRS's Centralized Authorization File, since that file is reserved for Title 26 (income-tax) matters. The representative must be eligible to practice before the IRS under the categories listed on the form. Current IRS procedure also permits a general power of attorney valid under state law, provided it contains the elements the IRS requires (the MSB's name and address, identifying number, the representative's name and address, a description of the matter, and a clear statement of the scope of authority granted); a defect in a state-law POA can generally be cured by executing a Form 2848 that supplies the missing information. Having a representative does not exempt the MSB from producing records or making relevant personnel available; it changes who communicates with the examiner on the MSB's behalf, and current procedure requires the examiner to stop an interview if the MSB asks to consult its representative.

Does selection for a Title 31 examination mean IRS suspects money laundering?

No. Selection reflects a risk-based case-selection decision, drawing on factors such as filing patterns, referrals, or registration status; it is not itself a finding or formal accusation of wrongdoing. Whether the examination ultimately identifies a deficiency is a separate question from why the case was selected, and the two should not be conflated.

What happens if an MSB does not voluntarily provide requested records?

Current IRS procedure requires the examiner to first make every effort to obtain the requested information voluntarily through the ordinary IDR process. Where records genuinely cannot be obtained that way, the IRS can use its BSA summons authority, issued on FinCEN Form 113, Bank Secrecy Act Summons, a distinct instrument from the income-tax summons (Form 2039) and one that cannot be used in a Title 31 examination in place of Form 113. A BSA summons must be reviewed and signed by a territory manager (or higher) before it can be served, and it can compel production of records or testimony from the MSB, its officers or employees, or a third party holding relevant BSA records. A single missed or delayed IDR response does not automatically produce a summons; it is a formal step the IRS turns to only where voluntary production has genuinely broken down, and it carries its own separate legal process, including notice requirements to certain customers under the Right to Financial Privacy Act in some circumstances.

Can an MSB challenge or rebut findings before the examination closes?

Yes, within limits. Current guidance directs examiners to discuss issues with the MSB as they arise during the examination, rather than saving them for the closing conference, and the closing conference itself is where the MSB can review documented findings and provide relevant evidence or context. This is an opportunity to respond to specific findings as they are raised, not an open-ended right to relitigate the entire examination at will or to demand unlimited additional time once the closing conference has been reached.

What if requested records are held by an agent or a vendor, not by the MSB directly?

Using a vendor or agent does not, by itself, relieve the MSB of its own applicable BSA recordkeeping and compliance obligations. Identify these dependencies early (see the first-72-hours checklist above) so a third party's response time does not create an unexpected delay against an IDR deadline. Where an agent has separate BSA obligations, those obligations remain distinct from the principal MSB's own responsibilities.

What should an MSB do if it discovers a missed CTR, SAR, or other required filing during the examination?

Do not conceal the gap, backdate records, or rewrite history to make the file appear clean. Preserve the facts as they actually are. Where an examiner identifies an unfiled BSA form and no criminal referral is being contemplated, current IRS procedure directs the examiner to request that the delinquent or amended form be filed electronically with FinCEN, with confirmation of the filing provided to the examiner; this is the ordinary path for an honestly disclosed gap. Where the gap is significant, recurring, or could raise a question of willfulness, involve qualified legal counsel or compliance support before taking remedial steps, since how the issue is characterized and addressed can matter to how it is ultimately treated. An honestly disclosed, promptly corrected gap and a concealed or backdated one are treated very differently, and only the first is a defensible position to be in.

This article provides general information about the IRS Title 31 examination process for U.S. money services businesses. It is not legal advice. MSBs facing an active Title 31 examination, a referral to FinCEN, or potential criminal exposure should consult qualified U.S. legal counsel.