HUNDREDS

of people served

★★★★★

rated by clients

24/7

available to help

Author Avatar
CURATED BY Luke W.

Officer Not Filing Security

Minnesota § 609.435: Attorney on Officer Not Filing Security Charges & Defenses

Minnesota Statute § 609.435 addresses a specific administrative requirement tied to holding certain public offices: the filing of legally required security, often an official bond. This statute makes it a misdemeanor offense for an individual designated as a public officer to intentionally begin performing the duties associated with their office before they have properly executed and filed this required security. The law underscores the importance of these prerequisites, which typically serve to protect the public and government entities from potential financial losses resulting from the officer’s negligence or misconduct while performing their duties. Failure to comply with this requirement before exercising official functions can lead to criminal charges.

The core of this offense is the intentional performance of official duties without having the necessary security in place as mandated by law for that specific office. It is not about the quality of the officer’s performance but about fulfilling a legal condition precedent to lawfully exercising the powers of the office. Different public offices may have different security or bonding requirements set by statute or charter. This law provides a general penalty for public officers who deliberately disregard such requirements and begin acting in their official capacity prematurely. An attorney can help determine if security was required and if the elements of this misdemeanor offense are met.

What the Statute Says: Officer Not Filing Security Laws in Minnesota

Minnesota Statute § 609.435 establishes the misdemeanor offense committed when a public officer intentionally performs official functions without first having executed and filed security mandated by law for their position. This statute emphasizes compliance with prerequisite bonding or security requirements designed to ensure accountability and protect public interests before an individual assumes the powers of their office.

609.435 OFFICER NOT FILING SECURITY.

Whoever intentionally performs the functions of a public officer without having executed and duly filed the required security is guilty of a misdemeanor.

What are the Elements of Officer Not Filing Security in Minnesota?

To secure a conviction under Minnesota Statute § 609.435, the prosecution must prove several distinct elements beyond a reasonable doubt. The case hinges on the defendant’s status as a public officer, the legal requirement for security associated with that office, the failure to meet that requirement, and the intentional performance of official duties despite that failure. Each component must be established for a conviction to stand under this specific misdemeanor statute.

  • Status as Public Officer: The individual charged must legally qualify as a “public officer.” While § 609.435 doesn’t explicitly reference § 609.415 (the general definition statute), the context strongly implies that the definition of “public officer” found there would apply. The prosecution needs to establish that the defendant held a position recognized under Minnesota law as a public office, carrying specific duties and authorities conferred by law, at the time the alleged functions were performed. This distinguishes public officers from general public employees or private citizens.
  • Required Security: The prosecution must demonstrate that a specific law, regulation, charter provision, or ordinance pertaining to the particular public office held by the defendant mandates the execution (obtaining and signing) and filing of some form of security as a condition of holding or performing the functions of that office. This security is typically an official bond (surety bond) guaranteeing the faithful performance of duties and protecting against financial loss caused by the officer. The specific requirement must be identified.
  • Failure to Execute and Duly File Security: It must be proven that the defendant had not completed the required process before performing the official functions. This involves showing that the necessary security document (e.g., the bond) was neither properly executed by the officer nor “duly filed” with the legally designated recipient (which could be the county auditor, secretary of state, or another specified office, depending on the position). Evidence of non-filing or incomplete execution is crucial.
  • Intentional Performance of Functions: The defendant must have intentionally performed actions that constitute the official “functions of a public officer.” This means they deliberately carried out duties or exercised powers associated with their office, knowing (or under circumstances where they should have known) that the prerequisite security was not yet properly filed. Accidental actions, preliminary administrative tasks unrelated to core official functions, or actions taken before realizing the security wasn’t filed might negate this element.

What are the Penalties for Officer Not Filing Security in Minnesota?

Violating Minnesota Statute § 609.435 by intentionally performing the functions of a public officer without having filed the required security is classified as a misdemeanor. This penalty level is less severe than gross misdemeanors or felonies but still carries potential legal sanctions and results in a criminal record for the convicted public officer, which can have significant professional implications.

Misdemeanor Penalties

Under Minnesota law (Minn. Stat. § 609.02, subd. 3), a misdemeanor offense is punishable by:

  • Imprisonment for not more than 90 days; or
  • Payment of a fine of not more than $1,000; or
  • Both imprisonment and a fine.

A judge would determine the specific sentence within these maximums based on the circumstances of the offense and the officer’s background. While jail time might be less common for this type of administrative violation compared to other crimes, the potential exists, along with fines and the creation of a public criminal record.

Understanding Officer Not Filing Security in Minnesota: Examples

Minnesota Statute § 609.435 highlights the importance the state places on procedural requirements designed to ensure accountability and protect public resources before individuals exercise the powers of public office. Many positions, particularly those involving handling public funds or making critical decisions, require the officeholder to secure a bond. This bond acts as a form of insurance, guaranteeing that the officer will perform their duties faithfully and providing a source of recovery if they cause financial loss through negligence or intentional misconduct.

This law targets the specific act of assuming official duties before this safeguard is properly in place. It’s not about whether the officer performs well or poorly later, but whether they intentionally bypassed a required administrative step meant to protect the public from the outset. It emphasizes that holding public office comes with responsibilities that begin even before the first official act, including fulfilling prerequisites like filing required security.

Newly Elected County Treasurer Begins Handling Funds Before Filing Bond

An individual is newly elected as County Treasurer, an office that, by state statute, requires the treasurer to execute and file a substantial official bond with the county auditor before handling any public funds. Eager to start, the treasurer-elect accesses the county accounts and begins processing payments a few days before their bond application is approved and officially filed with the auditor. By intentionally performing key functions of the office (handling funds) before the required security was duly filed, they have violated § 609.435.

Appointed Notary Public Starts Notarizing Documents Before Bond is Filed

A person applies for and receives an appointment as a Notary Public in Minnesota. State law requires notaries to file a surety bond with the Secretary of State as part of their commissioning process before they can legally perform notarial acts. Believing the commission approval was the final step, the individual purchases a notary stamp and begins notarizing documents for clients before their bond has been processed and officially filed. Intentionally performing the functions of this public office without the required security being filed constitutes a misdemeanor under § 609.435.

Township Supervisor Votes at Board Meeting Knowing Bond Lapsed/Wasn’t Renewed

A township supervisor was required to maintain an official bond throughout their term. Their bond expires, and they are notified but intentionally neglect to renew it and file the new bond certificate with the town clerk as required. Despite knowing their required security is no longer validly filed, they continue to attend township board meetings and cast votes on official matters. By intentionally performing official functions (voting at board meetings) while the required security was not duly filed, the supervisor violates § 609.435.

Conservation District Officer Issues Permits Before Required Security is Approved/Filed

An officer of a local Soil and Water Conservation District is required by district policy or statute to file a bond before assuming duties that include issuing permits impacting land use. The officer is appointed but, due to administrative delays, their bond hasn’t been formally approved and filed. Knowing this, but facing pressure to process applications, the officer intentionally begins reviewing and issuing official permits. Performing these official functions prior to the required security being duly filed violates § 609.435.

Defenses Against Officer Not Filing Security in Minnesota

Defending against a charge under Minnesota Statute § 609.435, Officer Not Filing Security, typically involves challenging one of the core elements the prosecution must prove. Since it’s a misdemeanor focusing on a specific administrative prerequisite, defenses often center on whether the security was legally required, whether it was actually filed or reasonably attempted, the defendant’s intent in performing official functions, or whether the actions taken truly constituted exercising the “functions of a public officer.”

An effective defense requires a careful review of the specific laws or rules governing the public office in question, documentation related to the security filing process, and the nature of the actions performed by the defendant before the security was allegedly filed. Demonstrating a lack of intent, factual compliance, or that the requirement didn’t apply can lead to dismissal or acquittal of this misdemeanor charge. An attorney can help investigate these factual and legal avenues.

Security Not Required or Invalid Requirement

This defense argues that the premise of the charge is flawed because there was no valid legal requirement for the defendant to file security for their specific office.

  • No Statutory Requirement: Research the statutes, charters, ordinances, or rules governing the specific public office and argue that they contain no provision mandating the execution or filing of a bond or other security for that position.
  • Requirement Misinterpreted: Argue that while some security might be required generally for the governmental entity, the specific requirement cited by the prosecution does not apply to the defendant’s particular role or level of authority within that office.
  • Invalid Local Rule: If the requirement stems from a local policy or rule rather than state statute, challenge the validity or enforceability of that local rule, arguing it was improperly adopted or exceeds local authority.

Security Was Filed or Attempted Filing

This defense asserts that the defendant complied with the requirement or made reasonable efforts to do so.

  • Proof of Filing: Provide documentation (e.g., dated bond certificate, filing receipt from the receiving office, cancelled check for bond premium) demonstrating that the required security was, in fact, executed and duly filed before the alleged performance of official functions.
  • Filing Error by Receiving Office: Argue the defendant properly executed and submitted the required security to the correct office (e.g., county auditor, clerk), but the receiving office lost, misplaced, or failed to process the filing promptly, and the defendant reasonably believed it was filed.
  • Good Faith Attempt: Show the defendant took all reasonable steps to execute and file the security promptly but was prevented by administrative delays or errors outside their control, demonstrating a good faith effort to comply before performing functions.

Lack of Intent

This defense challenges the element that the defendant intentionally performed official functions knowing the security was not filed.

  • Unaware of Requirement: Argue the defendant genuinely did not know that filing security was a prerequisite before performing any official duties. This might involve lack of proper orientation, unclear instructions, or complexity of rules.
  • Mistaken Belief Filed: Present evidence showing the defendant had a reasonable basis to believe the security had been duly filed, perhaps based on misinformation from staff, confirmation from the bonding agency, or misunderstanding the filing process timeline.
  • Accidental/Inadvertent Action: Argue the specific function performed was minor, perhaps done accidentally or inadvertently (e.g., answering a simple constituent question) before the defendant realized the security filing wasn’t complete, lacking intent to perform core official functions prematurely.

Actions Were Not “Functions of a Public Officer”

This defense argues that the specific activities the defendant engaged in did not rise to the level of performing the “functions of a public officer” that would trigger the statute.

  • Preparatory Steps Only: Contend the actions were merely administrative or preparatory tasks necessary to assume office (e.g., setting up an office, attending orientation meetings, preliminary non-binding discussions) rather than exercising the actual powers or duties of the office.
  • Ministerial Acts Not Requiring Bond: Argue the specific minor tasks performed were purely ministerial and unrelated to the purpose of the bond (like handling funds or making binding decisions), and thus not the “functions” contemplated by the statute’s requirement.
  • Actions in Private Capacity: Demonstrate the defendant’s actions were taken in a personal or private capacity, completely separate from their role as a public officer, even if occurring near the time of assuming office.

FAQs About Officer Not Filing Security in Minnesota

What kind of “security” is usually required for public officers?

The most common type of security required is an official surety bond. This is a three-party contract where a surety company guarantees to the government entity (the obligee) that the public officer (the principal) will faithfully perform their duties and honestly handle public funds. If the officer causes a loss through misconduct or negligence, the surety company pays the loss up to the bond amount.

Which public officers in Minnesota typically need to file security?

Requirements vary widely. Often, officers who handle public money (like treasurers, certain clerks, financial officers), those whose duties involve potential liability (like law enforcement or notaries public), and certain key elected positions (as specified by statute or charter) are required to be bonded. The specific law governing the office must be checked.

What is the purpose of requiring a bond or security?

The primary purposes are to protect the public and the government entity from financial losses caused by the officer’s failure to perform duties faithfully or honestly, and to ensure a source of recovery for such losses. It also serves as a screening mechanism and emphasizes the accountability associated with the office.

Is simply forgetting to file the bond a valid defense?

Forgetting might support a defense based on lack of intent if the performance of duties was inadvertent before realizing the oversight. However, if an officer knows security is required and consciously decides to perform duties before filing it, simply “forgetting” the prerequisite likely wouldn’t negate the intentional performance element required by § 609.435.

What if the county clerk’s office lost the bond I submitted?

If you can provide credible evidence that you properly executed the bond and submitted it to the correct filing office before performing duties, but the office mishandled or lost it, that would be a strong defense. You fulfilled your obligation; the failure was with the receiving office, not you.

Does § 609.435 apply to all public employees, or just officers?

The statute specifically says “public officer.” It does not explicitly include “public employee.” Therefore, based on the plain language, it applies only to those meeting the definition of a public officer, not general public employees who typically aren’t required to file individual official bonds for their positions.

What are considered “functions of a public officer”?

This refers to the official powers, duties, and responsibilities conferred upon the specific public office by law, charter, or ordinance. It includes actions taken under the authority of the office, such as voting on official matters, handling public funds, issuing licenses or permits, making binding decisions, or enforcing laws, depending on the specific office.

How serious is this misdemeanor charge for a public officer?

While legally classified as a misdemeanor with relatively low maximum penalties, a conviction under § 609.435 can be very serious professionally for a public officer. It reflects poorly on their diligence and compliance with legal requirements and could potentially lead to removal from office through separate administrative or political processes, or damage future prospects for public service.

Can I lose my office automatically if convicted under § 609.435?

Unlike the bribery statute (§ 609.42) which mandates forfeiture, § 609.435 does not contain an automatic forfeiture provision. However, a misdemeanor conviction might provide grounds for removal under other laws or rules governing that specific office, or could lead to political pressure (like recall efforts) resulting in loss of office.

What if I file the required security late, after already performing some duties?

Filing late does not undo a violation that already occurred. If you intentionally performed official functions before filing, the crime was committed at that time. Filing later might be considered a mitigating factor at sentencing but doesn’t erase the initial violation if all elements were met.

Does this Minnesota law apply to federal officers working in the state?

No. Minnesota Statute § 609.435 applies to Minnesota state and local “public officers.” Federal officers are subject to federal laws and regulations regarding prerequisites for holding office, including any bonding requirements set by federal statute.

Where is the required security typically filed?

This depends entirely on the specific office and the law governing it. Bonds for state-level officers might be filed with the Secretary of State or Department of Management and Budget. Bonds for county officers are often filed with the County Auditor or court administrator. Municipal or township officer bonds are usually filed with the respective clerk.

Is there a time limit (statute of limitations) for this charge?

Yes. As a misdemeanor, the general statute of limitations under Minn. Stat. § 628.26 would typically be three years from the date the offense (intentional performance of duties before filing) was committed.

Can I be charged if I didn’t know security was required for my office?

Lack of knowledge about the requirement itself could potentially support a defense negating the element of intentional performance without having filed. If you genuinely and reasonably did not know security was a prerequisite before starting duties, you might argue you did not intentionally violate the statute when you began performing functions.

Does performing only minor administrative tasks count as “functions”?

It’s debatable and fact-specific. Purely preparatory actions like setting up an office might not count. However, if the tasks involve exercising official authority, even if seemingly minor (like signing an official document), they could potentially be considered “functions of a public officer.” The nature of the act matters.

The Long-Term Impact of Officer Not Filing Security Charges

While Officer Not Filing Security (Minn. Stat. § 609.435) is a misdemeanor offense, a conviction can still carry notable long-term consequences, particularly for an individual serving in or aspiring to public office. The conviction reflects a failure to comply with basic legal prerequisites for holding a position of public trust.

Misdemeanor Criminal Record

A conviction under § 609.435 results in a permanent misdemeanor criminal record. While less impactful than a felony or gross misdemeanor, this record can still surface during background checks for employment, housing, or volunteer positions. It may require explanation and could potentially raise concerns about an individual’s attention to detail, compliance history, and fitness for positions requiring careful adherence to rules and procedures.

Potential Job Consequences / Removal from Office

Although the statute doesn’t mandate forfeiture of office like some other misconduct laws, a conviction could certainly jeopardize the officer’s position. It might constitute grounds for removal under specific state statutes, local charters, or organizational bylaws governing that office. Even if not formally removed, the conviction could lead to votes of no confidence, recall efforts, or decisions not to reappoint, effectively ending their tenure in that office due to the perceived negligence or intentional disregard for requirements.

Damage to Reputation for Responsibility/Compliance

Public officers are expected to understand and meticulously follow the laws governing their positions. A conviction for intentionally performing duties before meeting a basic requirement like filing security suggests a lack of responsibility or respect for procedural safeguards. This can damage the officer’s reputation among colleagues, constituents, and the public, portraying them as careless or untrustworthy regarding administrative and legal obligations, which can hinder their effectiveness and future political or professional advancement.

Potential Barrier to Future Public Office or Positions of Trust

Having a criminal conviction, even a misdemeanor related to official duties, can be a significant obstacle to obtaining future positions in public office or roles requiring public trust. Screening committees, voters, or appointing authorities may view the prior conviction under § 609.435 as evidence of unsuitability for positions demanding high levels of diligence and compliance. It creates a negative mark that can be difficult to overcome when competing for positions where integrity and adherence to procedure are paramount.

Officer Not Filing Security Attorney in Minnesota

Verifying Security Requirements for Specific Offices

The threshold question in any § 609.435 case is whether the filing of security was legally required for the specific public office held by the defendant. Requirements vary greatly depending on the office (e.g., treasurer vs. park board member). An attorney will conduct thorough legal research into the state statutes, local charters, ordinances, and relevant rules governing that particular position to confirm if a bond or other security was mandated. If no such legal requirement exists, or if the requirement was misinterpreted by authorities, this forms a complete defense, and the attorney can move for dismissal based on the lack of a required element.

Investigating Filing Procedures and Potential Errors

Even if security was required, the defense involves investigating the actual process of execution and filing. An attorney can subpoena records from the designated filing office (e.g., County Auditor, Secretary of State) to determine if the security was, in fact, received but perhaps mishandled, misplaced, or improperly rejected. They can gather evidence from the defendant and potentially the bonding agency regarding the steps taken to execute and submit the bond. Demonstrating that the defendant made a good faith effort to comply, or that the failure to file was due to administrative error by others, can negate the defendant’s culpability.

Challenging the Element of Intentional Performance

Section 609.435 requires that the defendant intentionally performed official functions before filing security. This mental state (mens rea) can be a key point of defense. An attorney works to challenge the prosecution’s evidence of intent. This might involve presenting evidence that the defendant was reasonably unaware of the filing prerequisite prior to starting duties, that they mistakenly believed the filing was complete, or that the specific actions undertaken were inadvertent or so minor they didn’t constitute an intentional performance of core official “functions.” Raising reasonable doubt about whether the defendant deliberately disregarded the filing requirement is crucial.

Negotiating Resolutions to Minimize Professional Harm

Given that a conviction under § 609.435, even as a misdemeanor, can severely impact a public officer’s career and reputation, seeking a resolution that avoids a conviction or minimizes harm is often a primary goal. An attorney can negotiate with the prosecutor, highlighting weaknesses in the case (e.g., lack of intent, questionable requirement) or mitigating factors (e.g., immediate compliance once notified). Potential negotiated outcomes might include dismissal upon late filing, a continuance for dismissal (where the charge is dropped after a period of compliance), or a plea to a lesser non-criminal ordinance violation, thereby avoiding a state criminal record and lessening the professional consequences for the public officer.