What to do after receiving a false-claim subpoena or investigator contact

Preserve the exact submission and every attachment. Keep invoices, cost reports, time records, reimbursement forms, bids, contracts, amendments, purchase orders, grant documents, rate applications, portal confirmations, certifications, emails, accounting files, and source records. Do not rely on the government’s later printout as the only version.

Stop automatic deletion of email, texts, cloud records, accounting data, and device logs. Do not edit an old invoice or create a replacement receipt without preserving the original. A transparent correction can be lawful; silent alteration or backdating can create new problems.

Identify each person’s role before anyone gives an account. Sales staff, project managers, payroll personnel, billers, accountants, owners, and outside consultants may supply different fields. A corporate signature or portal credential does not answer who knew a particular representation was false.

Do not contact coworkers or public employees to align stories. Preserve ordinary business communications, but avoid asking a witness to change a record or description. Counsel can collect documents and conduct interviews without creating a suggestion of influence.

Respond to deadlines deliberately. A subpoena, audit request, suspension notice, repayment demand, and criminal interview involve different obligations. A person should not lie to investigators, but may obtain counsel and decline a voluntary interview where lawful. Civil cooperation should be coordinated with the criminal defense.

Section 609.465 is a specific public-claim fraud offense

The law punishes the act of presenting a false claim to government with both knowledge and intent to defraud. It does not require the claimant to be a public employee. A vendor, contractor, grantee, employee, benefit applicant, professional, company officer, or any other person can fall within “whoever.”

The statute is distinct from section 609.455, which applies to the public officer or employee who knowingly audits, allows, or pays a false government claim. One transaction can lead to an outside-presenter charge, an insider-permitting charge, or accomplice allegations, but the elements must remain separate.

The text calls the offense “an attempt to commit theft of public funds.” That is not a casual label. It connects punishment to Minnesota’s theft and attempt statutes and makes the value of the claim important even if government never pays.

The crime includes claims false “in whole or in part.” A legitimate contract does not immunize an inflated line item, duplicate bill, false hour, personal charge, or fabricated eligibility fact. At the same time, the State must identify the false component and prove the claimant knew of it.

Two mental states appear expressly: knowledge of falsity and intent to defraud. A billing error can be material and expensive while still lacking both. Civil overpayment and criminal fraud should not be treated as synonyms.

What prosecutors must prove beyond a reasonable doubt

A useful element formulation is: the accused presented a claim or demand; the recipient was a public officer or body authorized to audit, allow, or pay it; the claim was presented for one of those purposes; it was false in whole or in part; the accused knew it was false; the accused acted with intent to defraud; and the act occurred at the charged time and place.

When value affects punishment, the amount should be proved and found through the procedure required by Minnesota law. A gross invoice total is not automatically the amount of the false claim. Legitimate work, credits, offsets, and only-partly-false lines must be examined.

Identity can be disputed. Electronic submissions may use shared office credentials or a provider number while staff members prepare the underlying data. The State must prove the defendant’s own presentation or legally sufficient accomplice role.

The prosecution can rely on circumstantial evidence: impossible hours, duplicate billing, altered records, concealed ownership, side agreements, warnings, inconsistent explanations, personal benefit, or repeated claims after denials. The defense should analyze whether the circumstances also reasonably support mistake, ambiguity, delegation, or good-faith contract interpretation.

The jury should not be invited to convict merely because public money is involved. The court’s instructions must require the exact statutory act, recipient authority, falsity, knowledge, and fraudulent intent.

What it means to present a false claim

Presentation ordinarily occurs when a person submits, delivers, files, tenders, or causes the claim to reach the authorized government decision-maker for audit, allowance, or payment. Paper, email, electronic portals, data interchange, and an agent’s submission can all be relevant.

Drafting an invoice that is never sent may not complete section 609.465, although general attempt or conspiracy law could require separate analysis. The government should identify the transmission, recipient, date, and evidence of receipt.

A claim routed through an intermediary can still be presented to the public body if the process is designed to deliver it there. The defense should trace whether the first recipient was a private prime contractor, third-party administrator, managed-care organization, fiscal intermediary, or public entity—and what authority that recipient exercised.

Resubmissions and corrected claims require count-specific analysis. A rejected claim, appeal, supplemental invoice, and final payment request can contain different representations. The State should not combine them in a way that obscures which submission was knowingly false.

Corporate presentation raises attribution questions. A company acts through people, but criminal liability is not established simply by an officer’s title. Signatures, instructions, delegated duties, review, certifications, and knowledge must be linked to the accused.

What counts as a claim or demand

The ordinary examples are invoices and reimbursement requests. Other examples include cost reports, rate applications, payroll submissions, travel vouchers, grant draws, benefit claims, change orders, progress-payment requests, refund demands, and certifications that trigger release of public money.

The document need not use the word “claim.” The question is whether it requests or supports audit, allowance, or payment from public funds. A certification can be part of the demand when government relies on it to determine entitlement.

Preliminary negotiations are not necessarily claims. A proposal, estimate, bid, eligibility inquiry, or unsigned draft may precede any demand for payment. The contract and agency process show when financial liability was actually asserted.

A claim may seek payment for future or estimated work if the governing arrangement permits advance payment. Falsity cannot be inferred merely because the service was not completed on the submission date; the payment terms and representations control.

Where the government already owes money, a dispute over amount can still involve a claim. But aggressive negotiation, a debatable interpretation, or an unaccepted change order is not automatically fraudulent. The State must prove a knowingly false factual or entitlement premise and fraudulent purpose.

The recipient must be authorized to audit, allow, or pay

Section 609.465 identifies a public officer or body with authority over the claim. That language excludes a purely private audience with no governmental payment function, although other fraud statutes may apply.

Authority can come from statute, ordinance, resolution, contract, delegation, job duties, or established governmental structure. The public recipient need not be the final check signer if authorized to audit or allow the demand.

The defense should obtain organizational charts, delegations, program manuals, contract provisions, and payment workflow. A document copied to a government employee for information may differ from a claim submitted to that person for decision.

Claims involving joint powers bodies, public corporations, grant administrators, managed-care entities, and private fiscal agents require careful analysis. Public funding alone does not resolve whether the named recipient was a “public officer or body” authorized as the statute requires.

Federal, tribal, and out-of-state recipients raise jurisdiction and statutory-scope questions. Minnesota section 609.465 should not be assumed to govern every government claim with a Minnesota connection.

A claim may be false in whole or only in part

A wholly fictitious claim—billing for a nonexistent employee, patient, delivery, or project—is the clearest example. Partial falsity includes inflated quantities, duplicate units, incorrect rates, ineligible costs, personal items, unworked hours, concealed credits, or a material false certification attached to otherwise real work.

Real goods or services do not automatically make the claim true. The official Minnesota Court of Appeals explained in the related insider case that actual personal purchases billed to a city under a false public-purpose premise could be false claims. State v. Norman, No. A11-1721, slip op. at 8–10 (Minn. Ct. App. Sept. 17, 2012) (unpublished).

A contractual disagreement is different. Whether labor was within scope, a cost was reimbursable, a change order was approved, or a deliverable satisfied specifications may turn on technical language and course of performance. Reasonable ambiguity can defeat falsity or knowledge.

An estimate can be accurate as an estimate even if later facts differ. Examine what the claim represented, what forecasting method the program allowed, whether reconciliation was required, and whether uncertainty was disclosed.

The allegedly false matter should be stated precisely. “Overbilling” may hide a rate dispute, coding error, rejected cost allocation, incomplete documentation, or factually fabricated service. Only the last category is self-evidently false; the others need legal and factual proof.

The defendant must know the claim is false

Knowledge requires actual belief in the specified fact, not merely that a careful claimant should have discovered the error. A poorly designed billing system, mistaken employee entry, misunderstood rule, or negligent review can produce an overpayment without satisfying this element.

Direct proof can include an admission, instruction to falsify, warning, concealed correction, or message acknowledging ineligibility. Circumstantial proof can include impossible service volumes, repeated submission after notice, two sets of records, altered timestamps, kickbacks, fabricated signatures, or destruction of support.

The relevant point is presentation. Later learning that the claim was incorrect does not prove earlier knowledge. Subsequent conduct may be evidence, but the jury must not substitute hindsight for contemporaneous belief.

In organizations, knowledge can be fragmented. A field employee knows what service occurred; billing knows the code; management knows the contract; accounting knows the amount. The State must connect the accused to the particular false fact rather than aggregate everyone’s knowledge automatically.

Warnings must be evaluated for specificity. A general audit concern, evolving agency guidance, or unrelated prior denial is different from written notice that the precise claim category is ineligible. Continued billing after a clear, final instruction can be more probative.

Intent to defraud is more than knowledge of an error

The statute requires intent to defraud in addition to knowledge of falsity. The State must show a purpose to use the false claim to deceive the authorized public decision-maker and obtain allowance or payment not lawfully due.

Motive can be relevant but does not replace intent. Financial distress, pressure to meet a budget, a performance bonus, or desire to keep a contract may explain why a person acted. The question remains whether the person deliberately used a known false claim.

Prompt disclosure and correction can support good faith, especially before any audit or inquiry. Concealing the error, creating backup after the fact, shifting dates, or giving incompatible explanations can support the State. Timing and context matter.

A claimant may knowingly submit a disputed amount while openly identifying the dispute and asking the public body to decide it. That is materially different from representing a disputed entitlement as an undisclosed fact. Reservation language, correspondence, and negotiation history should be preserved.

There is no need to invent an extra permanent-loss element. Fraudulent intent can exist even if the public body detects the claim and refuses payment. The absence of loss remains important evidence and sentencing mitigation.

The crime can be complete even when government refuses to pay

Section 609.465 criminalizes presentation for audit, allowance, or payment and labels the offense attempted theft. Its design addresses the false demand before public money necessarily leaves the treasury.

A rejection therefore does not automatically defeat the charge. The State must still prove a completed presentation, falsity, knowledge, fraudulent intent, and authorized recipient.

Payment affects value, restitution, and factual inference. A claim caught immediately may produce no actual loss. A paid claim later recouped can generate a different restitution calculation from an unpaid demand.

Voluntary withdrawal before discovery may support abandonment or lack of intent, but section 609.465’s own completed act is presentation. Minnesota’s general attempt defense in section 609.17 concerns voluntary, good-faith abandonment before the intended crime is completed; its fit with a completed statutory false-claim presentation requires careful legal analysis.

An administrative reversal is not the same as a criminal acquittal. Agencies may deny or recoup under broad program rules. The criminal court separately determines statutory guilt under the beyond-a-reasonable-doubt standard.

How claim value controls the maximum and Guidelines rank

Minn. Stat. § 609.52, subd. 3 (2026) supplies theft maximums. Theft over $5,000 carries up to ten years and a $20,000 fine. Theft of public funds at $5,000 or less falls within the five-year and $10,000 felony provision, regardless of value.

Minn. Stat. § 609.17, subd. 4 (2026) ordinarily caps an attempt at one-half the completed crime’s maximum imprisonment and fine. Applied to section 609.465, a claim over $5,000 therefore has a five-year/$10,000 ceiling, while a claim of $5,000 or less has a two-and-one-half-year/$5,000 ceiling.

The official Sentencing Guidelines offense-severity table ranks presenting false claims over $5,000 at level 3 and claims of $5,000 or less at level 2. The presumptive sentence also depends on criminal-history score and the Guidelines effective on the offense date.

Value should reflect the false claim, not automatically the whole contract. If a $100,000 invoice contains a disputed $2,000 line, the State must justify the amount used for the conviction and sentence. Legitimate value, credits, corrections, and duplicate-count issues matter.

Multiple claims create aggregation questions. Minnesota’s theft statute authorizes six-month aggregation for specified theft forms, but counsel should not assume that every separate section 609.465 demand can be grouped without satisfying the applicable language, notice, venue, and unanimity requirements.

Vendor invoices, construction claims, procurement, and grants

Vendor cases often concern quantity, delivery, price, labor, subcontractors, rebates, change orders, warranties, or certification. Gather the solicitation, proposal, executed contract, amendments, specifications, inspection records, delivery proofs, meeting minutes, and payment history.

Construction billing can be provisional. Retainage, percentage completion, stored materials, allowances, unit pricing, disputed extras, and architect certification should be understood before calling a pay application false.

Procurement representations may affect eligibility rather than price: small-business status, conflict disclosures, debarment, prevailing wage, domestic sourcing, insurance, licensing, and subcontractor participation. A false eligibility certification can be central even if the physical work was adequate.

Grant claims may involve indirect costs, matching funds, program eligibility, budget categories, subrecipient monitoring, and time allocation. A questioned cost in a civil audit is not automatically proof of known falsity and intent to defraud.

When a private prime contractor submits a subcontractor’s data, trace who knew what. The prime may reasonably rely on certifications, or may knowingly pass through false material. The government cannot establish the owner’s knowledge simply by showing the company benefited.

Expense reports, time sheets, payroll, and public benefits

Expense cases can involve mileage, meals, lodging, moving costs, equipment, card purchases, or per diem. Policies, employment agreements, prior approvals, receipts, business purpose, reimbursement history, and consistent agency practice matter.

Time-sheet claims require more than a comparison of clock entries. On-call work, remote duties, travel, rounding, leave, schedule swaps, minimum-call provisions, and collective-bargaining terms can explain apparent overlap. Impossible hours, fabricated clients, or pay claimed for known absences present a different record.

Payroll submissions can be false even when the employee performed some work. Inflated hours, unauthorized rate, ghost employee, false classification, or concealed related-party payment may create a partly false demand.

Public benefit applications may be governed by specialized fraud statutes with different elements and penalties. Section 609.465 should not be assumed to displace a more specific program law, and the complaint must identify the selected offense.

Repayment after discovery does not necessarily undo presentation. It can reduce loss and support mitigation. A prompt correction before any inquiry may also bear on fraudulent intent, but the full timeline must be documented.

Accountants, billing staff, consultants, and delegated submissions

Professional preparation can support good faith when the client fully discloses relevant facts and follows competent advice. It does not protect a client who hides personal expenses, supplies false source data, or directs the professional to use an ineligible treatment.

Published Minnesota false-claim decisions have treated full disclosure as central to professional reliance. A requested instruction is incomplete if it suggests reliance without requiring that the claimant fairly provide the professional all material information.

Preserve engagement letters, data requests, upload logs, workpapers, questions, drafts, advice, and corrections. These show whether the professional made the disputed classification or merely transferred numbers from the client’s ledger.

Billing staff can face direct or accomplice allegations when they knowingly enter false claims. Routine data entry based on apparently valid source records is different from changing codes, fabricating notes, or billing after being told service was not provided.

Privilege is limited and fact-specific. Accountant communications are not automatically protected like attorney-client advice. Counsel should assess privilege and work-product issues before producing a professional’s complete file voluntarily.

Medical-assistance fraud changed significantly in 2026

Older resources point to section 609.466 for Medical Assistance fraud. In 2026, the Legislature repealed that provision and enacted Minn. Stat. § 609.467 (2026). Current advice must use the law in effect on the alleged offense date.

The new statute is broader and more detailed. It covers schemes to obtain Medical Assistance money through false pretenses or concealment, knowingly or with reason to know presenting ineligible claims, false enrollment information, excluded-provider control, falsified service records, specified personal-care and community-support claims, and intentional destruction of required records.

The base felony maximum is ten years and $20,000. Loss over $100,000 through $1,000,000 permits up to 20 years and $100,000; loss over $1,000,000 permits up to 30 years and $1,000,000. Failure to maintain required Medical Assistance records is a separate gross misdemeanor.

Section 609.467 also contains continuing-offense, venue, and expanded restitution provisions. The official Guidelines table ranks fraud at level 2 up to $100,000, level 6 from $100,001 through $1,000,000, and level 8 above $1,000,000.

General section 609.465 cases and old section 609.466 cases remain historically useful, but they do not erase the new language. Medical Assistance allegations require claim-by-claim analysis under section 609.467 and the program rules governing eligibility, documentation, supervision, and service delivery.

Related offenses and Minnesota’s civil False Claims Act

Minn. Stat. § 609.455 (2026) applies to the public officer or employee who knowingly audits, allows, or pays a false claim. Section 609.465 applies to the person presenting it with intent to defraud.

Theft by false representation, theft by swindle, forgery, identity theft, computer offenses, tax crimes, bribery, kickbacks, money laundering, conspiracy, and aiding-and-abetting may be charged when their distinct elements are supported.

Minnesota Statutes chapter 15C creates civil false-claims liability and permits certain private actions filed under seal. Civil multipliers, penalties, attorney fees, government intervention, and retaliation remedies are separate from criminal guilt.

Federal money can trigger the federal False Claims Act, health-care-fraud statutes, program bribery, mail fraud, wire fraud, or other federal provisions. Jurisdiction and charging must be evaluated from the actual program and conduct.

Parallel matters can produce inconsistent demands: preserve documents, cooperate with a regulator, protect privilege, answer a civil complaint, and avoid criminal admissions. Coordinated counsel is important when state, federal, civil, administrative, and licensing authorities are involved.

Evidence that commonly determines the result

Build a claim ledger listing the submission date, recipient, amount, allegedly false component, source record, preparer, signer, government action, payment, recovery, and charged count. This prevents a large investigation from becoming an undifferentiated accusation.

Source evidence includes contracts, amendments, purchase orders, service notes, time records, schedules, delivery proofs, inspection records, bank data, payroll, invoices, receipts, general ledgers, cost allocation, coding manuals, program authorizations, and eligibility records.

Electronic evidence includes portal audit trails, login history, device and IP data, batch files, claim edits, rejection messages, resubmissions, billing software settings, metadata, email, and internal chat. Native exports often reveal more than printed claim forms.

Mental-state evidence includes disclosures, questions, advice, prior audits, denials, corrective action, training, warnings, concealed records, fabricated backup, bonuses, conflicts, and personal benefit. Tie each item to the date of the charged presentation.

Experts may explain accounting, coding, construction, procurement, valuation, data systems, or program rules. An expert should use complete records and explain the method rather than simply endorse one side’s conclusion about intent.

What Minnesota appellate cases add to the statutory text

In State v. Ruud, 259 N.W.2d 567 (Minn. 1977), the Minnesota Supreme Court affirmed convictions arising from nursing-home cost reports that included personal expenses. The court addressed search scope, summary charts, professional reliance, and the defendants’ theories about offsets and accounting treatment.

Ruud explained that reliance on an accountant requires full and fair disclosure of relevant information. The requested defense instruction was not warranted where the defendants did not tell the accountants that personal expenses had been mixed into nursing-home books.

In State v. Strimling, 265 N.W.2d 423, 429–30 (Minn. 1978), the Supreme Court upheld false-claim accomplice convictions involving inflated nursing-home costs and kickbacks. The individuals had not personally signed or filed the report; liability rested on intentional assistance under section 609.05.

An official later opinion quotes Strimling’s rule that accomplice liability does not depend on an employer or principal relationship and instead reaches a person who, with the required intent, contributes meaningfully to another’s crime. State v. Jackson, No. A13-0346, slip op. at 14 (Minn. Ct. App. Mar. 10, 2014) (unpublished).

Norman concerns section 609.455 rather than the presenter statute, but its official opinion is persuasive on why an actual transaction can be false when billed to government under an untrue public-purpose premise. Each decision’s statute and procedural posture should remain explicit.

Investigation, discovery, motions, and trial

Investigations can begin with a routine audit, data match, whistleblower, competitor, public employee, payer review, inspector general, State Auditor, Legislative Auditor, Medicaid Fraud Control Unit, or search warrant. The initial referral may overstate or understate the ultimate issue.

The complaint should identify each claim, recipient, false portion, value, and factual basis for knowledge and intent. Defense counsel should examine probable cause, duplicity, aggregation, venue, limitations, and whether the charge uses the statute in effect on the alleged date.

Discovery should include source data, complete audit workpapers, sampling method, algorithms, claim history, program guidance, exculpatory material, witness statements, recordings, expert opinions, search materials, and evidence affecting informant credibility.

Pretrial motions may address suppression, warrant particularity, compelled statements, privilege, business records, summaries, expert reliability, other-acts evidence, severance, accomplice instructions, value interrogatories, jury unanimity, restitution scope, and the interaction among overlapping counts.

At trial, a clear claim chart can help only if tied to admissible evidence. In Ruud, the Supreme Court warned of the danger that summary figures can acquire an existence independent of their source evidence. The defense should insist that jurors understand assumptions, exclusions, and underlying documents.

How an effective false-claim defense is organized

First, identify the exact claim and recipient authority. Prove when and how the demand was presented, whether it had reached the authorized public decision-maker, and which individual or entity made each representation.

Second, test falsity under the actual contract, statute, regulation, program manual, grant, policy, amendment, and course of performance. Separate factual fabrication from disputed interpretation, estimate, documentation failure, and civil noncompliance.

Third, trace authorship and knowledge. Determine who created the source record, entered the claim, reviewed it, signed it, received warnings, and understood the disputed fact. Do not permit corporate hierarchy to substitute for individual proof.

Fourth, test intent to defraud. Organize disclosure, professional advice, correction, negotiation, repayment, motive, concealment, and consistent treatment. A known disputed claim openly submitted for decision is different from a hidden falsehood designed to trigger payment.

Finally, calculate value and coordinate parallel proceedings. Isolate the false portion, credits, returned money, unpaid demands, and aggregation. Address licensing, program exclusion, civil false-claims exposure, tax, restitution, and debarment before resolving the criminal case.

Frequently asked questions about presenting false government claims