Filing FBAR Late: Reasonable Cause Statements and Delinquent Submission Procedures

How Late FBAR Filing Is Handled#

Late FBAR filing can be a controls issue, not just a tax cleanup task. For teams managing cross-border accounts, it can expose gaps in ownership, recordkeeping, and escalation at the same time.

When you're handling a late FBAR case, start with facts and process, not theory. The report is the Report of Foreign Bank and Financial Accounts, filed as FinCEN Form 114. If a foreign account's maximum value, or the aggregate maximum across foreign accounts, exceeds $10,000 during the calendar year, an FBAR filing obligation applies. In practice, that means confirming which accounts existed, the highest values during the year, who had visibility, and what your timeline shows.

Do not mix procedural lanes. The delinquent FBAR submission procedures are for filers who do not need to use the Streamlined Filing Compliance Procedures or the IRS Criminal Investigation Voluntary Disclosure Practice. For the delinquent path, IRS guidance says the filer must not be under IRS civil examination or criminal investigation and must not already have IRS contact about the delinquent FBARs. If either point is unclear, pause and escalate before filing through the BSA E-Filing System.

The goal is a file that can be reviewed and defended, not just a submitted form. At minimum, keep a dated eligibility decision, the affected years, the account population used for filing, and the statement explaining why the FBARs are late. Also verify that each intended year was submitted and that the late-filing reason was selected on the electronic form cover page.

The risk profile is still real. IRS guidance says delinquent FBARs are not automatically audited, yet they may still be selected through existing audit processes. IRS also states it will not impose a delinquent FBAR filing penalty if income from the foreign financial accounts was properly reported and tax was properly paid. That is a conditional outcome, not a blanket safe harbor.

This article stays close to what official guidance clearly supports. Where the steps and checkpoints are explicit, it says so. Where judgment is required, it marks where operations should hand off to legal review.

We covered this in detail in How to Document 'Reasonable Cause' for IRS Penalty Abatement.

Start with terms and paths so teams do not mix procedures#

Before drafting any late-filing statement, confirm the filing lane first. If you classify the case incorrectly, the rest of the packet can be built on the wrong procedure.

Name the filing correctly#

The Report of Foreign Bank and Financial Accounts is the FBAR, filed as FinCEN Form 114. Older records may refer to Form TD F 90-22.1. Treat that as the legacy name for the same report.

Use one naming set consistently across the case file so reviewers can match account records, prior correspondence, and the draft filing without confusion.

Choose the lane before the narrative#

The Delinquent FBAR submission procedures are a separate path. They are not the Streamlined Filing Compliance Procedures and not the IRS Criminal Investigation Voluntary Disclosure Practice.

For the delinquent-FBAR path, IRS frames this lane for taxpayers who have not filed a required FBAR, are not under IRS civil examination or criminal investigation, and do not need those other procedures. Set the procedure first, then draft the late-filing explanation. That order matters because reasonable cause is evaluated case by case, and a narrative written for the wrong path is hard to reuse cleanly.

Once the path is set, the next question is simple: can you document that the filer actually qualifies to use it?

Confirm eligibility gates before preparing a late filing#

Confirm the eligibility gates first. If any gate is unresolved, pause and resolve it before filing.

For the Delinquent FBAR submission procedures, IRS describes three entry gates. The filer is not under IRS civil examination or criminal investigation, has not already been contacted by the IRS about the delinquent FBARs, and does not need either the IRS Criminal Investigation Voluntary Disclosure Practice or the Streamlined Filing Compliance Procedures.

Treat each gate as a documented yes-or-no decision, not a judgment call from memory. If you cannot verify a gate cleanly, treat it as unresolved until the team closes it.

This distinction matters because the delinquent route is narrow. IRS frames penalty non-imposition as conditional, including proper income reporting and tax payment tied to the foreign accounts. Procedure alone does not resolve those underlying facts.

Record the gate decision in an internal log with:

• case owner
• decision date and timestamp
• yes or no answers for exam status, prior IRS contact, and need for another disclosure path
• evidence checked for each answer
• final decision and approver

Keep that record audit-ready. Delinquent FBARs are not automatically audited, but they may still be selected for audit. Before submission, make sure the path decision is closed. The filing package includes an explanation statement and a late-filing reason selected on the electronic form cover page, so those items should reflect a settled eligibility decision.

Once eligibility is locked, the next job is to build the factual support for the statement you plan to file.

You might also find this useful: FBAR Late Filing Penalties: What to Expect and How to Minimize Them.

Before drafting a reasonable-cause statement, run a quick account-threshold check to confirm which years may require FBAR coverage with the FBAR calculator.

Build the late-filing statement evidence pack before you e-file#

Build the late-filing statement from a dated evidence memo, not from a standalone narrative draft. Your explanation is stronger when each claim ties back to records, timeline, and reviewer checks before you submit through the BSA E-Filing System.

IRS gives a filing process and conditional penalty language, but not one exhaustive bright-line definition of reasonable cause. It also describes reasonable cause as case by case and, in failure-to-file or failure-to-pay contexts, looks at ordinary care and prudence even when timely compliance was not possible. Write to that reality by showing what happened, when, and what you did next.

Start with a dated fact timeline#

Begin with a timeline of verified facts, then draft the statement from that timeline. If a point is not supported by a retrievable record, mark it unverified instead of presenting it as settled.

Use a document matrix for internal review#

Keep the filed explanation concise, but maintain an internal matrix that maps each claim to support and sign-off.

If you use other legal frameworks internally, treat them as organizing aids only, not as a definitive required checklist for delinquent FBAR statements.

Separate verified facts from open points#

Keep a clear split between verified facts and open points/assumptions. IRS states penalty non-imposition is conditional, including conditions tied to proper income reporting, tax payment, and prior IRS contact, so unresolved items should be visible before filing. Also confirm the delinquent-procedures eligibility gates are satisfied before submission. Do not imply unresolved items are closed. If a gate or condition is still open, pause final submission.

Add a short legal cross-check note#

For non-routine files, add a brief counsel note covering strong facts, missing or disputed facts, and questions for legal judgment. If counsel evaluates other penalty frameworks or case law, keep that analysis separate from the IRS procedural filing requirements. Do not present those analyses as the direct FBAR delinquent-statement standard.

Before e-filing, run one final consistency check. The explanation statement, the selected late-filing reason on the electronic cover page, and your evidence pack should all align.

If you want a deeper dive, read What to Do If You've Never Filed an FBAR (Delinquent FBAR Procedures).

Execute the IRS filing sequence in strict order#

Once your evidence pack is locked, execute the filing steps in the IRS order: review the instructions, include your late-filing explanation statement, file through the BSA E-Filing System, then select the late-filing reason on the electronic cover page.

Keep those steps aligned. The cover-page selection complements the written statement; it does not replace it.

Keep the order literal#

Use FBAR (FinCEN Form 114) for each delinquent year. If internal materials still reference Form TD F 90-22.1, update them before filing so the team is working from the current form label.

Before you submit, verify that the written explanation and the selected late-filing reason are consistent.

Add internal submission controls#

IRS does not prescribe an internal workflow here, but simple checks can reduce avoidable filing issues:

• Version check: confirm you are using the current Form 114 e-filing path. FinCEN guidance indicates submissions can be rejected when required elements are missing.
• Required-artifact check: confirm the late-filing explanation statement is included and a late-filing reason is selected on the electronic cover page.

Escalate immediately if e-filing breaks#

If you cannot complete electronic filing, do not invent a workaround. Use FinCEN Regulatory Help to inquire about possible alternatives, as directed by the IRS procedure.

Document the contact trail as it happens: inquiry date, issue details, and response. Submission alone does not guarantee penalty relief, which remains conditional.

Related reading: 1099-NEC vs 1099-K Platform Filing Starts With Settlement Path.

Apply a clear escalation rule when reasonable cause is not straightforward#

Treat this as a two-part decision: delinquent FBAR submission is an operational filing path, while reasonable cause is a separate, case-by-case penalty-relief analysis.

Use this filing lane when your facts match the IRS delinquent FBAR conditions: you do not need the IRS Criminal Investigation Voluntary Disclosure Practice or Streamlined Filing Compliance Procedures, you are not under IRS civil examination or criminal investigation, and the IRS has not already contacted you about the delinquent FBARs. Then file through FinCEN's BSA E-Filing System with both a late-filing statement and a cover-page late-filing reason.

If core facts are unclear or disputed, move to legal review before relying on generic late-filing or non-willful language. Reasonable cause is determined case by case, depends on the penalty involved, and does not apply to every penalty type.

Use a short two-lane decision note, signed by compliance and legal owners:

Related: Reasonable Cause Letter for Late FBAR Filing: Template and Examples.

Keep adjacent reporting regimes separate to avoid form confusion#

Treat FBAR and Form 8938 as separate controls from the start, because filing Form 8938 does not relieve the requirement to file FinCEN Form 114.

Use a shared reference so teams do not duplicate one filing and miss the other:

Map legacy references now. Older procedures and templates may still use "TD F 90-22.1," which can misroute work unless you map that label to FinCEN Form 114 and the BSA E-Filing channel.

Keep a separate completion check for each regime. A team can complete Form 8938 with the tax return and still miss the separate FBAR filing, or submit a late FBAR and still need a separate Form 8938 review under its own thresholds.

Scope this checklist tightly. Keep unrelated forms out unless another workstream independently requires them.

Once the forms are separated, assign who owns each decision so the case does not stall or move ahead on assumptions.

Need a separate filing-threshold workflow for contractor forms? Read 1099 Filing Threshold Calculator for Platform Contractor Decisions.

Assign ownership across compliance legal and finance before submission day#

Set ownership before anyone submits a late FBAR. For sensitive late FBAR filings, keep decision, explanation review, and submission in separate hands so one person is not making every call. That is not an IRS-mandated org chart, but it can be a defensible internal control when facts, legal risk, and filing execution all affect outcome.

A practical split is straightforward: compliance handles eligibility gating, legal or tax review checks the explanation statement, finance or platform operations confirms account population and records, and a separate filer submits. Small teams can have one person draft factual inputs, but a second reviewer can still check factual accuracy and legal exposure before filing.

Set owners by decision point, not by department label#

Assign by decision point, not by title.

This is where reporting-work separation matters. Work on other filing streams does not automatically assign ownership of the late FBAR path.

Build traceability like a case file, not an email trail#

Use IRS manual structure as a model for record discipline, not as a taxpayer workflow mandate. IRM 11.3.41 includes "Roles and Responsibilities," "Inventory Management System," and "Electronic Inventory Case Organization." IRM 8.11.6 includes "FBAR Administrative Case Files" and "FBAR Administrative File."

Treat late FBAR work the same way internally: one controlled case record with named owners and retrievable artifacts. For platform teams, link the case ID to the account population used for the Report of Foreign Bank and Financial Accounts, the approved explanation statement version, and the filing confirmation. If payout and tax-document teams use different systems, store that cross-reference in both.

Before submission, confirm:

• the approved explanation statement matches the final facts in the case record
• all intended FBAR years are listed and tied to the correct account population
• the filer is not the only person who approved the case

Treat premature handoff as a real failure mode#

Premature filing can be a control break: a late FBAR gets submitted before gate and fact review are complete. IRM 8.11.6.9.1 includes "FBAR Closing - Premature Referral," showing that premature referral is a recognized handling risk path.

Use a stop rule: if eligibility is unclear, facts are incomplete, or legal review is still open, do not submit. Keep the case open, document the blocker, and escalate instead of letting a single-role filer decide alone.

For a step-by-step walkthrough, see FBAR for a Foreign-Owned US LLC and the Filing Path That Works.

Prepare for audit selection with a retention and retrieval plan#

Treat each late FBAR case as audit-selectable and retrieval-tested. IRS says delinquent FBARs are not automatically audited, but they may still be selected through existing audit selection processes. Your file should be ready to explain what was filed, why it was late, and how you chose the delinquent path.

Build one indexed packet, not scattered proof#

Keep one case packet that can be produced quickly. At minimum, include:

• filed Form 114 record from the BSA E-Filing System
• the late-filing statement explaining why the FBARs were filed late, including the late-filing reason selected on the electronic cover page
• the eligibility-gate record showing why delinquent FBAR submission procedures were used
• any Regulatory Help inquiry and response, if used

If Regulatory Help was involved, retain the inquiry details and response trail, not just a final note. IRS says you may make an inquiry if you cannot file electronically. It does not guarantee an alternative filing method.

Use a retention table with clear ownership#

Use one internal packet format your team can run consistently in the Bank Secrecy Act reporting context.

Test retrieval before you need it#

Run a periodic control test: can your team reproduce the full submission history and rationale within your fixed turnaround window? Test for a complete chronology, including the late-filing reason, gate decision, and filing record. If key steps depend on memory or disconnected folders, the control is not ready.

Align this packet with broader compliance logs#

For global payment operations, cross-reference this FBAR case packet with broader tax, compliance, and risk records so teams are not reconciling in silos during escalation. IRS examination guidance includes an FBAR case-file assembly concept. Use that discipline to keep records coherent and retrievable.

A strong file can help reduce avoidable mistakes, especially repeatable control failures.

Avoid the failure modes that create preventable exposure#

The key control is simple: confirm eligibility and documentation before you file, because a clean packet cannot fix the wrong filing path.

• Do not file first and investigate later. Before anyone on your team uses the BSA E-Filing System, confirm the IRS gate conditions for Delinquent FBAR submission procedures: the filer is not under IRS civil examination or criminal investigation and has not already been contacted by the IRS about delinquent FBARs.
• Do not treat penalty relief as automatic. Under delinquent FBAR procedures, penalty relief is conditional, including proper reporting of foreign-account income on U.S. tax returns and payment of all related tax.
• Do not use generic "reasonable cause" text with no support. Use a consistent internal drafting framework, then tie each claim in the late-filing statement to records you can produce.
• Do not mix disclosure narratives. IRS distinguishes delinquent FBAR procedures from Streamlined Filing Compliance Procedures and other disclosure paths, so pulling language from other offshore procedure materials can make your filing internally inconsistent.
• Do not use advisor blog summaries as your filing baseline. Use IRS guidance and FBAR/Form 114 instructions for the actual steps.

Before closure, run two checks: include the late-filing explanation statement, and confirm the electronic cover page has a selected late-filing reason.

Conclusion#

For late FBAR cases with a reasonable-cause position, the practical approach is operational clarity: confirm the right filing path, execute the IRS steps in order, and make only claims you can support with records.

Start with the eligibility gates before filing Form 114. Delinquent FBAR procedures are for filers who are not under IRS civil examination or criminal investigation, have not already been contacted by the IRS about the delinquent FBARs, and do not need Streamlined Filing Compliance Procedures or IRS Criminal Investigation Voluntary Disclosure Practice. If any gate is unclear, pause and escalate.

Then execute the submission steps exactly. File all delinquent FBARs through the BSA E-Filing System, include a statement explaining why the FBARs are late, and select a late-filing reason on the electronic form cover page. Close the case only after confirming that all intended years and accounts were filed and proof of filing is saved. If e-filing fails, document the FinCEN Regulatory Help inquiry.

Treat the reasonable-cause statement as evidence-driven, not narrative-driven. Because reasonable cause is evaluated case by case, keep a clear timeline, support whether related foreign-account income was reported and tax paid, and document whether accounts exceeded the $10,000 threshold during the year. Do not assume "our tax professional did not advise filing" will carry the case. IRS penalty-relief guidance notes that reliance on a tax professional generally is not a valid reason in failure-to-file or failure-to-pay contexts.

Keep three decisions separate: procedure, which IRS path applies; legal judgment, whether the facts support the explanation; and governance, who approves submission. That separation can reduce surprise risk and make decisions easier to defend.

A practical next step is a one-page decision sheet covering eligibility, fact checks, submission controls, and escalation and sign-off for the next late FBAR case.

If you want to turn this checklist into a controlled workflow with audit-friendly status tracking, review Gruv's implementation options on the documentation hub.