In-depth Minnesota legal guide
Presenting a false claim to a public officer or body under Minnesota Statute § 609.465
Minnesota Statute § 609.465 addresses a specific transaction: a person presents a claim or demand for audit, allowance, or payment to a public officer or body authorized to act on it, knows the claim is false in whole or in part, and acts with intent to defraud. The statute treats that completed presentation as an attempt to commit theft of public funds and imports the attempt and theft penalty structure. For current law, that produces two amount-based felony ceilings and two different 2026 Sentencing Guidelines rankings. A reliable defense analysis therefore must identify the exact claim, what was represented, how and when it reached an authorized recipient, who knew what, the alleged fraudulent purpose, the supported amount, and the law in force on the alleged offense date.
You will work directly with me.
If you hire me, I will isolate the claim actually charged, obtain the source and transmission records, identify the legally authorized recipient, test authorship and access, separate knowledge from assumption, examine the alleged fraudulent objective, and calculate the amount and exposure under the law that applied on the alleged offense date. I will not treat an audit conclusion or spreadsheet total as a substitute for element-by-element proof.
The prosecution must prove the claim, the presentation, the recipient’s authority, knowledge, and fraudulent intent
- Claim or demand
- The prosecution must identify a request submitted for government audit, allowance, or payment—not merely an inaccurate private record that never became a claim.
- Presentation
- The accused presented the claim or is legally liable for another person’s presentation under an alleged accomplice theory.
- Authorized recipient
- The claim went to a public officer or body authorized to audit, allow, or pay it.
- Knowledge
- At presentation, the accused knew the claim was false in whole or in part.
- Intent
- The presentation was made with intent to defraud. Knowledge of an error and intent to defraud are related but analytically distinct questions.
- Amount and offense date
- The supported amount selects the current penalty ceiling and Guidelines ranking; the alleged date selects the statute, thresholds, Guidelines edition, and limitations rule.
Every phrase does work. A record may be wrong without being a claim. A draft may be created without being presented. A recipient may work for government without possessing authority to audit, allow, or pay the particular demand. A person may know a line is inaccurate without intending to deceive the government into parting with public funds. Conversely, a partly legitimate invoice does not automatically defeat the statute because it expressly covers falsity “in whole or in part.” The charging document and discovery should permit these questions to be tested transaction by transaction.
“For audit, allowance or payment” identifies three government functions
Audit
Verification or examination
- Typical material
- Cost report, grant draw, expense claim, supporting schedule, certification, audit response, source ledger, or reconciliation.
- Proof question
- Was the record submitted so an authorized public decision-maker could examine and validate a demand?
- Defense focus
- Identify the version transmitted, scope of the audit, adjustments disclosed, estimates allowed, and underlying source data.
Allowance
Approval or recognition
- Typical material
- Voucher, reimbursement request, eligibility submission, contract invoice, change order, benefits claim, or electronic certification.
- Proof question
- Was the claim placed before an officer or body empowered to approve or authorize it?
- Defense focus
- Distinguish a preliminary intake, returned draft, private discussion, or recommendation from operative presentation for allowance.
Payment
Disbursement request
- Typical material
- Invoice, billing file, payment batch, mileage log, time record, transportation log, purchase record, or electronic claim.
- Proof question
- Did the submission request payment of public funds from an officer or body authorized to release them?
- Defense focus
- Match each billed item to performance, delivery, contract terms, correction history, payment status, and the person who transmitted it.
Presentation must be proved, not assumed: the file should show what crossed from the claimant’s side to the government side, when it crossed, by what channel, in which version, and to whom. A local spreadsheet, unsent draft, bookkeeping entry, or internal email may be evidence of preparation or knowledge, but it is not automatically the statutory presentation.
The government must prove both known falsity and an intent to defraud
Knowledge asks what the accused understood about the identified false portion when the claim was presented. Intent to defraud asks the purpose of the presentation. Those questions may be proved circumstantially, but neither should be collapsed into the fact that an auditor later made an adjustment. Government programs often involve changing guidance, estimates, allocation judgments, incomplete source data, coding decisions, documentation rules, and reconciliation after submission. A civil overpayment, contract dispute, administrative disallowance, negligent entry, or good-faith interpretation does not by itself establish the criminal mental states.
The prosecution may rely on altered support, concealed credits, invented services, duplicate billing, fictitious recipients, backdated entries, undisclosed side payments, repeated warnings, false certifications, coordinated explanations, or destruction of records. The defense should test whether those inferences fit the complete chronology. Who supplied the source number? Was the person told that it was wrong? Did policy permit an estimate followed by reconciliation? Was the adjustment disclosed? Did a supervisor, accountant, vendor, billing service, or software rule generate the entry? Was a correction made before the government acted? Was the accused trying to obtain money the claimant was not entitled to receive, or resolving a genuine eligibility or accounting dispute?
“False in whole or in part” does not eliminate the need to identify the false part
A claim can include legitimate and disputed components. The statute prevents a defendant from arguing that an entire invoice is immune merely because some services were real. It does not authorize the state to label a whole claim fraudulent without specifying the false representation or amount. The source contract, benefit rule, rate methodology, delivery record, patient or client record, payroll data, mileage or time record, and contemporaneous explanation should be tied to each disputed line. That analysis also matters because value affects both the statutory ceiling and Guidelines severity level.
An unsuccessful claim can still be charged
Section 609.465 focuses on presentation and declares the offense to be an attempted theft of public funds. The government therefore need not prove that it actually paid the claim in order to allege a completed § 609.465 violation. Nonpayment, rejection, or correction may remain important to intent, amount, restitution, mitigation, and the credibility of the alleged scheme. It is simply not the same as proving that no claim was presented.
Build a claim packet for every transaction instead of arguing from a summary spreadsheet
I would reconstruct each alleged claim from the source event through submission and government action. The packet should include the governing contract or program rule; raw service, delivery, eligibility, time, cost, or expense record; every draft; edits and approvals; the transmitted version; certification; receipt or portal acknowledgment; audit inquiry; response; allowance or rejection; payment or reversal; correction; and communications. The packet should identify the person and system responsible at each step. That makes it possible to test every statutory element and exposes when a prosecution summary mixes different versions, people, dates, or monetary concepts.
| Disputed issue | Records to obtain | Question to test |
|---|---|---|
| Existence of a claim or demand | Invoice, voucher, cost report, grant draw, reimbursement request, benefits form, billing file, certification, and governing submission rules. | What payment, approval, or audit action did the document actually request? |
| Presentation | Portal receipt, email header, API log, upload history, mail record, batch manifest, audit trail, and recipient testimony. | Which exact version was transmitted, when, by whom, and through what channel? |
| Authorized public recipient | Statute, ordinance, delegation, job description, board resolution, contract, workflow map, and system permissions. | Was the recipient legally authorized to audit, allow, or pay this kind of claim? |
| False portion | Underlying time, service, delivery, patient, mileage, payroll, cost, eligibility, price, credit, rebate, and allocation records. | What exact representation was false, why was it false under the governing rule, and what part remained valid? |
| Knowledge | Training, warnings, prior corrections, messages, version history, source-data access, review notes, and contemporaneous explanation. | What did the accused know when the claim was presented rather than after an audit reconstructed it? |
| Intent to defraud | Concealment, false certification, benefit flow, side agreement, altered support, repeated pattern, disclosure, correction, and advice received. | Does the evidence prove a purpose to deceive for financial action, or is it consistent with error, ambiguity, reliance, or a genuine dispute? |
| Value | Gross request, valid portion, false portion, payment, denial, credit, reversal, reimbursement, and forensic methodology. | Which number is legally relevant to the charge, statutory ceiling, Guidelines ranking, restitution, and negotiation? |
Native electronic evidence can resolve authorship and timing
A printed claim may display a person’s name without proving who entered, edited, approved, or transmitted it. Preserve native files, database audit logs, portal records, access logs, IP and device information, email with headers, billing-system roles, batch history, and administrator changes. Identify time zones and whether timestamps record creation, modification, submission, receipt, approval, or payment. Shared credentials, delegated queues, automated imports, copied templates, third-party billers, and administrator overrides create attribution questions that a screenshot cannot answer.
Preservation must be lawful and immediate. Do not delete, alter, backdate, coordinate accounts, contact witnesses to shape testimony, or access a former employer’s system without authorization. Counsel can identify sources, send appropriate preservation requests, and use discovery or process available in the case. Minnesota Rule of Criminal Procedure 9 governs prosecution and defense disclosure in felony and gross-misdemeanor cases and includes continuing obligations; the exact request should be tied to the actual claim system and theory.
Internal, civil, administrative, and criminal investigations can overlap
A payer audit, inspector-general request, licensing inquiry, employer interview, contract dispute, civil demand, and criminal investigation may use the same records for different legal questions. Before producing a narrative or spreadsheet, determine who is asking, under what authority, what deadline applies, whether the interview is compelled, who may receive the response, and whether counsel represents the individual, organization, or both. A statement intended to preserve a contract or job may later become evidence of knowledge or intent.
Experts must show their work
Financial or program experts may be needed to explain a rate methodology, cost allocation, medical or service documentation, database extraction, contract measure, or loss calculation. Obtain the engagement scope, data set, query, assumptions, exclusions, version history, and reproducible workpapers. Test whether the expert applied the rule in force at the time, distinguished disallowed documentation from nonexistent service, credited legitimate value, and attributed each entry to the correct person. An expert’s bottom-line “overpayment” number is not itself proof of presentation, knowledge, or intent to defraud.
Section 609.465 uses attempted-public-funds-theft ceilings, but the Guidelines rank the offense directly
Section 609.465 does not print a number of years or dollars. It says the person is guilty of an attempt to commit theft of public funds and may be sentenced accordingly. Under current § 609.17, an ordinary attempt carries no more than one-half the maximum imprisonment or fine for the completed crime. Current § 609.52 authorizes up to ten years and/or $20,000 for theft over $5,000. It authorizes up to five years and/or $10,000 for theft from $1,001 through $5,000. For $1,000 or less, the ordinary value tiers would be lower, but § 609.52 expressly retains the five-year/$10,000 tier when the property consists of public funds belonging to the state or a political subdivision or agency. Applying the attempt rule therefore produces the current two § 609.465 ceilings below.
| Supported public-funds amount | Completed-theft ceiling used by the cross-reference | Current § 609.465 attempt ceiling | 2026 Guidelines ranking |
|---|---|---|---|
| More than $5,000 | Ten years and/or $20,000 under § 609.52, subd. 3(2) | Five years and/or $10,000 after § 609.17, subd. 4(2) | Severity Level 3 |
| $1,001 through $5,000 | Five years and/or $10,000 under § 609.52, subd. 3(3)(a) | Two years six months and/or $5,000 after § 609.17, subd. 4(2) | Severity Level 2 |
| $1,000 or less in public funds | Five years and/or $10,000 under § 609.52, subd. 3(3)(d)(iv) | Two years six months and/or $5,000 after § 609.17, subd. 4(2) | Severity Level 2 |
Both current alternatives are felonies because both authorize more than one year of imprisonment. Neither § 609.465 nor the cross-referenced provisions state a universal minimum custody term. Section 609.101 separately supplies a $3,000 minimum-fine starting figure for the over-$5,000 approach and a $1,500 figure for the $5,000-or-less approach, calculated from the two attempt-level maximum fines. Qualifying public-defender status, indigence, or undue hardship permits reduction to at least $50; community work service may substitute for a fine; and installments may be authorized. The ceiling is not a prediction. The offense-date Guidelines edition, supported amount, criminal-history score, custody status, grid, plea or verdict offense, and any departure govern the presumptive framework.
Do not halve the Guidelines ranking twice
The 2026 Guidelines reference table specifically ranks § 609.465 at Severity Level 3 over $5,000 and Severity Level 2 at $5,000 or less, and § 7 puts it on the Theft Offense List. Because the Commission directly ranked this statute, the correct starting point is that specific listing. It would be a mistake to take the already specified § 609.465 ranking and reduce it again simply because the offense text uses the word “attempt.” Any separate attempt charge or unusual theory requires its own analysis, but the completed presentation offense uses the listed ranking.
Amount is not necessarily the gross invoice or the check ultimately issued
The relevant amount must be supported under the charged theory. A claim may include legitimate services plus an allegedly false line, a denied component, a credit, a contractual offset, or a later reconciliation. The requested amount, false portion, amount allowed, amount paid, actual loss, restitution request, and Guidelines value can be different numbers. The parties should disclose the methodology and underlying rows instead of moving one total among all legal questions without explanation.
The filing deadline changed on August 1, 2026
Chapter 97, article 3, section 4 of the 2026 Minnesota Session Laws added § 609.465 to a seven-year limitations clause. The amendment became effective August 1, 2026. Its application provision covers crimes committed on or after that date and crimes committed earlier if the prior limitations period had not expired before August 1, 2026. That language makes a date calculation indispensable. For older alleged conduct, determine the commission date, the period previously applicable, whether it expired before August 1, 2026, the complaint or indictment date, and any statutory exclusion. A current seven-year label cannot revive a prosecution the session law says was already expired.
Restitution, employment, contracting, and licensing are separate questions
Restitution may be sought, but the recoverable amount is not automatically the gross claim or the Guidelines value. Causation, actual loss, legitimate value, payments, credits, reimbursement, and procedural rules matter. Government or health-care work may also create employment, exclusion, credentialing, contract, debarment, disclosure, or professional-discipline consequences. Those consequences depend on the position, license, program, governing authority, and disposition.
One consequence is expressly tied to this conviction. Minnesota Statute § 214.10, subdivision 2a, directs a covered health-related licensing board to initiate proceedings to suspend or revoke, or to refuse renewal of, a license after a § 609.465 conviction. That is a required proceeding under the statute; it should not be described as an automatic universal loss of every Minnesota license. A person with a regulated credential needs advice addressing the particular board and procedure before resolving the criminal case.
The role in the transaction can change the statute
| Potential statute | Primary focus | Distinction to investigate |
|---|---|---|
| § 609.465 — presenting false claims | Submitting a known false claim with intent to defraud to an authorized public officer or body. | The claimant-side presentation, recipient authority, known falsity, fraudulent intent, and amount. |
| § 609.455 — permitting false claims | A public officer or employee audits, allows, or pays a government claim while knowing it is false or fraudulent. | The government-side actor’s public status, operative role, and knowledge. Section 609.455 does not contain § 609.465’s separate intent-to-defraud phrase. |
| § 609.466 or § 609.467 — medical-assistance fraud | Specified conduct involving Minnesota medical assistance, including current tiered provisions. | The program, claim date, statutory version, representation, service, amount, and offense-specific theory may be more specific than § 609.465. |
| § 609.52 — theft | Multiple theft theories, including false representation, swindle, and public funds. | The means of obtaining property, completion, value, aggregation, and overlap or merger issues depend on the exact counts and record. |
Preserve the claim trail and stop the investigation from becoming a guessing contest
First, I would obtain the complaint, probable-cause statement, audit demand, subpoena, interview request, or charging notice and identify the specific claim, period, amount, recipient, and alleged method. I would preserve the governing rules and native source records from the same period. I would not assume that a later policy, reconstructed export, or investigator’s spreadsheet accurately reflects what the accused saw or submitted.
Second, I would create a chronology that separates creation, review, certification, presentation, receipt, allowance, payment, audit, correction, and reimbursement. I would map each person and system to those events. Then I would assess knowledge and intent without importing hindsight. Finally, I would calculate the amount, offense-date penalty law, Guidelines edition, seven-year amendment, restitution position, and any licensing or employment consequence. That sequence turns a broad accusation into legal and factual questions that can be proved or challenged.
Minnesota false-public-claim questions
What must Minnesota prove under § 609.465?
The state must prove a claim or demand was presented for audit, allowance, or payment to a public officer or body authorized to act on it; the accused knew the claim was false in whole or part; and the presentation was made with intent to defraud. Accomplice liability requires its own proof if someone else physically submitted the claim.
What is the maximum penalty for a claim over $5,000?
Under current law, theft over $5,000 carries ten years and/or $20,000, and § 609.17 limits an ordinary attempt to one-half. Because § 609.465 is sentenced as attempted theft of public funds, the current ceiling is five years and/or $10,000. The 2026 Guidelines rank this approach at Severity Level 3.
What is the maximum penalty when the amount is $5,000 or less?
Current theft from $1,001 through $5,000 carries five years and/or $10,000. At $1,000 or less, theft of public funds carries that same ceiling under the special public-funds provision. Applying the attempt rule produces a § 609.465 ceiling of two years six months and/or $5,000 throughout the lower range. The 2026 Guidelines rank it at Severity Level 2. Offense-date law still must be checked.
Must the government actually pay the false claim?
No. Section 609.465 focuses on presenting the claim and deems that offense an attempted theft. Rejection or nonpayment can still matter to intent, amount, restitution, mitigation, and factual credibility, but payment is not written as an element of the presentation offense.
Is a billing or accounting error enough?
Not by itself. The statute requires knowledge that the claim was false and intent to defraud. The evidence must distinguish deliberate deception from mistake, ambiguous rules, reasonable reliance, estimates, allocation disputes, documentation defects, and good-faith correction.
Can a person be charged if someone else submitted the claim?
Potentially, under Minnesota accomplice law, but role or association alone is not enough. Strimling illustrates liability where evidence supported intentional aid in causing false amounts to enter a cost report submitted by another. The state must prove the underlying offense and the accused’s intentional aid with the legally required mental state.
How long does Minnesota have to charge § 609.465?
A 2026 amendment created a seven-year period effective August 1, 2026. It applies to crimes on or after that date and earlier crimes only if the prior period had not expired before August 1, 2026. The exact offense date, prior expiration date, charging date, and statutory exclusions must be calculated.
Can a conviction affect a professional license?
Yes, in some fields. Section 214.10, subdivision 2a, requires a covered health-related licensing board to initiate suspension or revocation proceedings or refuse renewal after a § 609.465 conviction. Other licenses, employment, and contracting consequences depend on their own governing authority; there is no single automatic rule for every credential.
A lawyer’s file review of Presenting False Claims to Public Officer or Body in Minnesota
A useful defense analysis starts by slowing the case down. The title of the charge is not an element, and the largest number in a penalty provision is not a prediction. I read the count, the incorporated definitions, and the alleged facts side by side before I tell a client what I think.
Read the count as a set of propositions the State must prove
To understand Presenting False Claims to Public Officer or Body in Minnesota, I start with Minn. Stat. §§ 609.465, 609.17, 609.52, and 214.10; 2026 Minn. Laws ch. 97, art. 3, § 4; 2026 Minn. Sentencing Guidelines §§ 5.B and 7; State v. Scheu; State v. Strimling and the version of the law in effect on the alleged date. The offense classification sets the outer framework, but it does not tell us what happened or what the state can prove. I then identify every fact that could change the charge or sentence and look for the record, testimony, or forensic evidence that supports—or contradicts—each one.
From there, I build a proof map. For every required element, I identify the witness, recording, document, test result, or admissible inference the prosecution would rely on, then compare that source with the rest of the file. This separates a disputed fact from a search, statement, or admissibility issue and keeps the analysis focused on problems that can actually affect the case.
The evidence I would ask for first
For Presenting False Claims to Public Officer or Body in Minnesota, I would not begin with a canned list of defenses. I would begin with the source file: the charging paper, every police report, uncut recordings, witness interviews, warrants and returns, device and account records, photographs with metadata, expert or laboratory material, certified prior records, court orders, and any document the prosecution relies on to prove an element or increase the classification. A police summary can identify what an officer or witness says happened, but it cannot substitute for the recording, photograph, data, or document being summarized. The same is true of a complaint. It identifies the prosecution’s theory at the start of the case; it does not prove the theory.
I put those materials on one chronology. That lets me see what was known at each decision point, which account was contemporaneous, what appeared only after people spoke with one another, and where the record is silent. It also keeps an admissibility question separate from a factual one. A fact can be disputed even if the evidence was lawfully obtained. Evidence can also be accurate yet inadmissible for a particular purpose. Those are different arguments and should not be blurred together.
Read the charging document against the offense date
The alleged date matters because statutes, penalty thresholds, definitions, sentencing rules, and published decisions change. I save the version in force on that date and read the session-law history when the current online text is different. I also check whether a later amendment was merely clarifying or made a substantive change; that is a legal question, not an assumption. The same discipline applies to prior convictions and administrative events. A prior must fit the definition the charged statute actually uses, fall within any stated lookback period, and be proved by a reliable record.
I then compare the formal count with the probable-cause narrative and the discovery. If the prosecution’s theory shifts, I want the amended pleading and enough detail to prepare. If several factual alternatives are alleged, I identify whether they are separate elements, alternative means, enhancement facts, or merely evidentiary details. That distinction affects notice, motions, jury instructions, unanimity arguments, and how a verdict form should be read.
Separate an evidentiary weakness from a suppression issue
Not every troubling fact produces a motion to suppress. Suppression ordinarily requires a constitutional, statutory, or rule-based violation with a remedy that reaches the evidence at issue. A weak identification, an incomplete investigation, or a witness inconsistency may be powerful at trial without making evidence inadmissible. By contrast, a stop, search, interrogation, identification procedure, warrant, or test can raise a legal issue even when the resulting evidence appears incriminating. I analyze both tracks and do not promise dismissal simply because one problem exists.
For a search issue, I reconstruct what officers knew before each intrusion and what authority they claimed. For a statement, I examine custody, questioning, warnings, voluntariness, recording, and the complete context. For scientific or technical evidence, I request the method, underlying data, quality-control material, uncertainty information, and chain of custody. For hearsay or confrontation questions, I identify the actual statement, its purpose, the declarant, and the proposed foundation. Specificity matters; “the evidence is bad” is not a motion.
Prepare negotiation and trial at the same time
A plea decision should be compared with the case the State could present at trial, not with the complaint’s maximum penalty in isolation. I want to know the strongest admissible proof, the weakest required element, the realistic motion practice, the likely instructions, and the consequences of every proposed disposition. That includes custody, probation, treatment, restitution, driving, firearm restrictions, registration, employment or licensing, immigration consultation, family-court effects, and record consequences when they are actually triggered. I avoid telling a client that every collateral consequence applies to every conviction.
Trial preparation gives negotiation its credibility. Witness interviews, exhibit review, motions in limine, expert consultation, demonstrative evidence, jury instructions, and a clean theory of the case force both sides to confront what can be proved. Negotiation can continue while that work is underway. The two tracks are not opposites.
A case-law point worth keeping in its proper place
Appellate decisions matter, but a quotation should not be detached from the issue the court was deciding. In State v. Fleck, 777 N.W.2d 233, 236 (Minn. 2010), the Minnesota Supreme Court described sufficiency review as viewing the evidence “in the light most favorable to the conviction.” That is an appellate-review rule, not a reduction of the State’s trial burden. At trial, the prosecution still must prove every element beyond a reasonable doubt. I cite the case for the proposition it actually decided and then return to the charged statute, the jury instructions, and the admissible evidence in the present file.
What I would want you to understand before choosing an outcome
You should be able to identify the exact charge, the facts that set its level, the disputed elements, the evidence that matters most, the motions that have a legal basis, the realistic trial issues, and the concrete effect of each proposed resolution. If an answer depends on a missing report, recording, expert opinion, or certified record, I will say so. An honest answer about what remains unknown is more useful than a confident guess.