Indiana · statutory penalties fines

How to calculate statutory penalties & fines in Indiana

By DocketMath TeamJune 4, 20266 min read
Abstract background illustration for How to calculate statutory penalties & fines in Indiana
Partially verified

older_than_packet

Quick takeaways

  • Indiana criminal fines are driven by offense classification (felony vs. misdemeanor) and are authorized by Ind. Code § 35-50-2-3 et seq. and Ind. Code § 35-50-3-2 et seq.
  • In DocketMath, the statutory-penalties-fines workflow maps the applicable fine authority to your case inputs and applies the statutory cap by class—the fine is generally imposed in addition to imprisonment where the relevant statute authorizes it.
  • Indiana’s fine framework is treated here as the general/default period based on the cited statute scope. This brief does not find a separate claim-type–specific sub-rule. If your charge’s statute includes a specific subsection with different fine terms, you should follow that subsection.
  • Typical workflow: pick the offense classification → confirm the class-based fine authority in the right Indiana statute block → enter the class and compare any entered fine amount to the statutory maximum.

Note: This guide explains how to calculate statutory penalties & fines in Indiana using a jurisdiction-aware workflow in DocketMath. It’s for process and computation—not legal advice.

Inputs you need

To calculate Indiana statutory penalties & fines with DocketMath, you’ll typically need these inputs from your charging documents or the judgment entry:

  • Jurisdiction: US-IN (Indiana)
  • Charge type / classification: felony or misdemeanor (Indiana fine authorization is class-based)
  • Felony/misdemeanor class
    • Felonies: class-based provisions located within Ind. Code § 35-50-2-3 through -7
    • Misdemeanors: class-based provisions located within Ind. Code § 35-50-3-2 through -4
  • Statutory fine authority section (if you have it): the specific subsection that governs the class for the charge you’re evaluating
  • Number of counts (optional, if you want aggregated exposure across multiple counts)
  • Any known court-imposed fine amount (optional, for comparison to the computed statutory maximum)
  • Sentencing format details that affect how fines are recorded (optional, but useful to align your computation with the judgment entry)

Practical tip: if you don’t yet know the exact fine cap for the class, start by identifying the class and the statutory section for that class. Indiana’s fine authorization is tied to those class-specific provisions within the felony and misdemeanor statute blocks.

How the calculation works

1) Choose the correct Indiana fine authority block

Indiana criminal fines are set by classification under two main statute groups:

  • Felonies: Ind. Code § 35-50-2-3 through -7
  • Misdemeanors: Ind. Code § 35-50-3-2 through -4

DocketMath uses these classification blocks to determine what fine authority applies, then applies the statutory cap for the applicable class.

A key concept to keep in mind is how Indiana fines relate to imprisonment:

  • The cited Indiana fine provisions are structured so that the court may impose a fine in addition to the term of imprisonment, subject to the class-based maximum authorized by the statute.

Sources to anchor this workflow:

Note on exceptions: This brief treats the classification framework as the general/default approach. It does not find a claim-type–specific sub-rule within the provided scope. If your statute citation points to a particular subsection with a different fine rule, use that subsection’s terms.

2) Apply the statutory maximum for the class

Once you specify the class (and ideally the exact subsection), DocketMath can compute:

  • The maximum statutory fine for that class (from the applicable Indiana Code subsection)
  • If you enter a proposed/judgment fine amount, a comparison to see whether that amount exceeds the statutory cap

How results change:

  • Selecting the wrong block (felony vs. misdemeanor) will change the fine cap.
  • Selecting the wrong class within the correct block will also change the statutory maximum.

So the critical driver of the output is: correct classification + correct class/subsection mapping.

3) Decide whether you’re calculating per-count or an aggregate

If your case has multiple counts, you’ll need to decide what “total” exposure you want to model:

  • Per-count maximum fine (often best for clarity and accuracy)
  • Aggregate maximum fine across multiple counts (sum of per-count maxima)

A practical way to structure this in DocketMath:

  • Compute the statutory fine maximum per count using the count’s class/subsection
  • Add the counts only if your goal is aggregate exposure across multiple counts

Quick reference:

ScenarioDocketMath inputs to focus onOutput you should review
Single countclassification + class + (ideally) subsectionstatutory fine max for that class
Multiple countsclass/subsection per count + count totalssum of per-count max fines (if aggregating)

Common pitfalls

  • Selecting the wrong statute block (felony vs. misdemeanor)

    • Fix: verify whether the charge falls under Ind. Code § 35-50-2 (felonies) or Ind. Code § 35-50-3 (misdemeanors).
  • Using an offense “name” instead of the class

    • Indiana fine caps are class-driven. “Theft,” “dealing,” etc., don’t by themselves determine the fine maximum.
    • Fix: extract the class (and/or the specific subsection cited) from the charging instrument or statute reference.
  • Ignoring the statutory cap

    • Even when fines are authorized “in addition to imprisonment,” they’re capped by statute.
    • Fix: always compare any entered/judgment fine amount against the computed class maximum.
  • Assuming there’s a claim-type–specific sub-rule

    • This brief does not identify a claim-type-specific rule in the provided statute scope.
    • Fix: treat the classification-based framework as the default, and only deviate if the charge’s specific subsection provides different fine terms.
  • Aggregating counts incorrectly

    • Some workflows sum per-count maxima; others report per-count caps.
    • Fix: decide your target metric (per-count vs. aggregate) and enter counts accordingly.

Sources and references

  • Indiana General Assembly (Indiana Code), Title 35 (fine/class authority blocks):
    https://iga.in.gov/laws/2023/ic/titles/35#35-50-2
  • Ind. Code § 35-50-2-3 et seq. (felony fine authorization by class)
  • Ind. Code § 35-50-3-2 et seq. (misdemeanor fine authorization by class)

Next steps

  1. Identify the class and statutory subsection for each charge:
    • Felony → locate the appropriate fine authorization within Ind. Code § 35-50-2-3 through -7
    • Misdemeanor → locate the appropriate fine authorization within Ind. Code § 35-50-3-2 through -4
  2. Open DocketMath’s Indiana tool:
    /tools/statutory-penalties-fines
  3. Enter inputs in a per-count structure:
    • classification + class + (ideally) subsection citation
  4. Run the calculation and review the computed statutory maximum:
    • If you entered a judgment fine amount, check it against the statutory cap.
  5. Validate the outcome if anything seems off:
    • felony vs. misdemeanor block selection
    • correct class/subsection alignment
    • whether you intended per-count or aggregated totals

Related reading


Run the numbers for your matter against the verified rule for this jurisdiction.

Calculate now