How to calculate statutory penalties & fines in Ohio

Quick takeaways

• DocketMath’s Statutory penalties & fines (Ohio) calculator is built to apply Ohio’s general felony financial-sentencing framework under Ohio Rev. Code § 2929.18, including how courts may impose financial sanctions in addition to court costs under § 2947.23.
• Your jurisdiction inputs specify that no claim-type-specific sub-rule was found. In that case, the calculator uses § 2929.18’s general/default authorization framework as the baseline unless another Ohio statute specifically limits or changes the calculation.
• You’ll typically need: (1) confirmation the sentence you’re modeling is for a felony, (2) the financial-sentence components you want to total (sanction amounts you’re including), and (3) whether you want to include court costs that tie back to § 2947.23.
• Expect outputs to change depending on whether your modeled total includes financial sanctions (authorized under § 2929.18), court costs, or both.

If you want the calculator workflow, go straight to: /tools/statutory-penalties-fines

Inputs you need

Before you run DocketMath’s statutory-penalties-fines tool for Ohio (US-OH), gather the items that map to how § 2929.18 authorizes financial sanctions at sentencing.

Required inputs (practical list)

• Case jurisdiction: Ohio (US-OH)
• Offense type: confirm the sentence you’re modeling is for a felony

  • § 2929.18 applies in the felony-sentencing context (“the court imposing a sentence upon an offender for a felony…”).
• Financial-sentence components you want to total

  • For example, if you’re tracking multiple sanction amounts you intend to include, you’ll want those component figures ready to enter or total in the tool.
• Court costs flag (if you’re including them in a total)

  • § 2929.18 references court costs pursuant to § 2947.23, so decide whether to model a combined total or sanctions-only.
• Whether another statute specifically governs the amount

  • Because § 2929.18 is an authorization framework, the correct dollar amounts can come from separate offense-specific penalty provisions. Have that statute/amount information available if you’re overriding the default approach.

Source anchors you’ll be using

• Ohio Rev. Code § 2929.18 (financial sanctions authorized at felony sentencing)
  https://codes.ohio.gov/ohio-revised-code/section-2929.18
• Ohio Rev. Code § 2947.23 (court costs referenced by § 2929.18)
  (Add the official Ohio Codes URL in your sources list once available—see “Sources and references” section.)

How the calculation works

DocketMath uses jurisdiction-aware rules for Ohio, with the core statutory lens provided by Ohio Rev. Code § 2929.18. Here’s how to think about the calculation so your inputs match what the tool is designed to model.

1) Understand the “permission structure” in § 2929.18

Section 2929.18 establishes that for felony sentencing, the sentencing court may impose financial sanctions (or combinations of them) that are authorized by other parts of Ohio law, and it also allows the addition of court costs pursuant to § 2947.23.

Practically, this means:

• § 2929.18 is a gatekeeper/authorization framework—it doesn’t function like a single universal “penalty table” that directly outputs one flat amount by itself.
• The statute also separates (conceptually and often in calculations) financial sanctions from court costs.

2) Use the “default/general period” when no claim-type-specific rule is identified

Your jurisdiction note states: No claim-type-specific sub-rule was found. The content should make this explicit because it affects how the tool applies rules.

So, for this Ohio calculator run:

• Default logic: use § 2929.18’s general/default authorization framework as the baseline.
• Override logic: if you identify a specific, separate Ohio statute that provides the actual penalty amount or a controlling formula for the offense, that statute should drive the amount calculation—rather than relying only on the general authorization framework.

In other words: the calculator’s default structure is used unless another statute specifically limits or changes the calculation.

3) Separate “court costs” from “financial sanctions” when you total

The opening structure of § 2929.18 includes court costs pursuant to § 2947.23.

When you enter figures into DocketMath, decide whether you’re modeling:

• Financial sanctions authorized under the § 2929.18 framework (often reflecting sanction provisions authorized elsewhere), and/or
• Court costs under § 2947.23.

This affects outputs such as:

• Sanctions-only total vs
• Combined total (sanctions + court costs)

4) Use inputs to shape outputs (what changes when you toggle items)

Even without seeing your exact DocketMath screen, statutory penalties/fines tools driven by an authorization framework typically behave like this:

5) Confirm the felony-only scope before you rely on results

Because § 2929.18 is written for felony sentencing:

• If your scenario is truly a felony, the § 2929.18 authorization framework is the correct statutory starting point.
• If your scenario is not a felony, the calculation approach can be materially different.

This is a key “input hygiene” step: verify the offense/sentencing posture first.

Common pitfalls

Here are common ways Ohio penalty/fine calculations can go wrong when using tools like DocketMath:

• Mixing court costs with sanctions

  • § 2929.18 explicitly references court costs under § 2947.23. Treat them distinctly unless your goal is a combined total.
• Using § 2929.18 like it contains the penalty amount formula

  • § 2929.18 is an authorization/structure provision for felony sentencing—not a universal amount schedule by itself.
• Running felony-only logic for a misdemeanor scenario

  • The statutory language targets felony sentencing.
• Assuming a claim-type-specific sub-rule exists

  • Your provided jurisdiction note says no claim-type-specific sub-rule was found, so the calculator should rely on the default/general authorization framework (unless overridden by another specific statute).
• Ignoring offense-specific penalty statutes

  • Ohio frequently has separate penalty provisions with their own constraints, ceilings, or formulas that override general authorization logic for the amount.

Practical note: If the offense has its own penalty provision (ceilings, multipliers, time-based calculations, etc.), that provision usually controls the amount, while § 2929.18 helps explain the sentencing authorization for financial sanctions in felony cases.

Sources and references

• Ohio Rev. Code § 2929.18 — Financial sanctions; court costs reference
  https://codes.ohio.gov/ohio-revised-code/section-2929.18
• TODO: Ohio Rev. Code § 2947.23 — Court costs
  (Add the official Ohio Codes URL once available.)

Next steps

1. Open DocketMath: /tools/statutory-penalties-fines and select Ohio (US-OH).
2. Enter your scenario inputs:

   • confirm it is a felony sentencing scenario
   • provide the sanction components you want counted (financial sanctions)
   • decide whether to include court costs associated with § 2947.23
3. Run the calculation and compare:

   • sanctions-only vs sanctions + court costs (depending on how the tool is configured).
4. If results look inconsistent, double-check:

   • whether an offense-specific penalty statute should control the amount
   • that you didn’t treat § 2929.18 authorization language as the underlying amount formula
   • that the scenario is actually within § 2929.18’s felony scope

Related reading

• How to calculate statutory penalties & fines in California — Full how-to guide with jurisdiction-specific rules
• How to calculate statutory penalties & fines in Florida — Full how-to guide with jurisdiction-specific rules
• How to calculate statutory penalties & fines in New York — Full how-to guide with jurisdiction-specific rules