Abstract background illustration for How to run Alimony Child Support in DocketMath for Oklahoma

How to run Alimony Child Support in DocketMath for Oklahoma

7 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

Below is a practical way to run Alimony + Child Support using DocketMath for Oklahoma (US-OK), with jurisdiction-aware rules. This walkthrough focuses on how to enter facts and understand outputs—not legal strategy.

1) Open the correct DocketMath tool (and confirm US-OK)

  1. Go to the calculator: /tools/alimony-child-support
  2. Inside DocketMath, confirm the jurisdiction is set to Oklahoma (US-OK).

Note: Oklahoma uses separate statutory frameworks for child support (43 O.S. § 118 et seq., including § 119 for the schedule) and alimony (43 O.S. § 134). In DocketMath, you’ll generally drive both calculations through the inputs you enter (such as income, dependents, and any alimony-related assumptions the tool requests).

2) Enter the child-support inputs (Oklahoma guidelines)

Oklahoma child support is computed as a percentage of the combined gross income of both parents under the guidelines in 43 O.S. § 118 et seq., using the schedule in 43 O.S. § 119.

In DocketMath, enter items such as:

  • Gross income for Parent A
  • Gross income for Parent B
  • Number of children covered by the calculation
  • Any additional coverage inputs the tool requests (for example, health insurance adjustments, if included in the tool’s Oklahoma setup)

Oklahoma’s guidelines create a rebuttable presumption tied to the schedule:

  • Child support shall be computed as a percentage of the combined gross income of both parents… There shall be a rebuttable presumption …” under 43 O.S. § 118 et seq.

How outputs change (child support):

  • If you increase either parent’s gross income, the percentage schedule applied to combined income generally increases the monthly child-support amount.
  • If you change the number of children, Oklahoma’s § 119 schedule changes the applicable percentage and therefore the monthly amount.

3) Enter the alimony inputs (Oklahoma alimony framework)

For alimony, Oklahoma’s key statutory authority is 43 O.S. § 134. While child support uses the explicit percentage schedule under § 118 et seq. and § 119, alimony is determined under the § 134 framework and the facts presented.

In DocketMath, enter the alimony-related inputs the tool asks for, such as:

  • Parties’ incomes (or whichever income measure the tool uses)
  • Length of marriage (often a key driver of alimony term/duration in calculator frameworks)
  • Any requested/assumed alimony duration settings (if the tool provides them)
  • Any other Oklahoma alimony inputs the tool includes

How outputs change (alimony):

  • Longer marriages typically correspond to longer or more substantial alimony ranges in calculator-style computations.
  • Larger income disparities often increase the alimony estimate.
  • Changing duration/term assumptions can change total payments even if the monthly figure is similar.

Disclaimer: This guide shows how to run the calculation in DocketMath. It does not predict what a court will order. Oklahoma alimony under 43 O.S. § 134 depends on the case facts and judicial discretion; treat tool output as a computational starting point.

4) Handle time-period settings correctly (defaults vs. your chosen horizon)

DocketMath may present results as:

  • a monthly estimate, and/or
  • total projected payments over a selected time period

If you notice a time-period setting (for example, how many months/years to project), pay close attention—especially when comparing runs.

Because no claim-type-specific sub-rule was identified for this write-up, apply this rule clearly:

  • Default period disclosure (for clarity): If DocketMath is using a general/default period (and you don’t see a claim-type-specific sub-rule), treat the result’s period as the general/default period shown by the calculator.

This matters when you compare results:

  • Monthly amounts are typically the most comparable across “what-if” scenarios.
  • Projected totals depend on the chosen/default duration.

5) Review results side-by-side: child support vs. alimony

After you run the calculation, separate the outputs conceptually:

  1. Child support (guidelines-based)

    • Based on the percentage-of-combined-gross-income framework in 43 O.S. § 118 et seq.
    • Uses the schedule at 43 O.S. § 119
    • Applies a rebuttable presumption concept (guidelines are presumptive, not automatic) under 43 O.S. § 118 et seq.
  2. Alimony (framework-based)

    • Based on 43 O.S. § 134 within the tool’s Oklahoma alimony input model

Practical tip: When reviewing, check which input changes most strongly affected the output (often combined income, number of children, and alimony duration/term assumptions).

6) Save/export your run and document assumptions

To make the results usable (and to compare scenarios), save your inputs or export the run if DocketMath provides that option. At minimum, jot down:

  • the US-OK selection
  • the income figures
  • number of children
  • any alimony term/duration assumptions

This makes it easy to do “what-if” comparisons without accidentally mixing assumptions between runs.

Common pitfalls

Use this checklist to reduce mistakes when running Oklahoma (US-OK) in DocketMath.

Input and interpretation issues

  • Mixing net income with gross income
    Oklahoma child support uses a percentage structure based on combined gross income under 43 O.S. § 118 et seq.
  • Forgetting to update the number of children
    Changing dependents changes how § 119 applies, which can change the monthly guideline result.
  • Assuming tool totals are the same as a court order
    The guidelines create a rebuttable presumption concept under 43 O.S. § 118 et seq.—outputs are presumptive/computational, not guaranteed orders.
  • Not distinguishing child support from alimony
    • Child support: 43 O.S. § 118 et seq. (schedule at § 119)
    • Alimony: 43 O.S. § 134
  • Leaving alimony duration/term at a default when you meant a different assumption
    DocketMath’s projection horizon (if present) can materially affect total payments.

Time-period misunderstandings

  • Comparing runs with different horizons
    If two runs use different durations, the monthly numbers may be comparable, but total projected payments will not be apples-to-apples.
  • Ignoring the “default period” behavior
    If there’s no claim-type-specific sub-rule visible, treat the time horizon as the general/default period the calculator displays and rely more on the monthly output for comparisons.

Jurisdiction confusion

  • Running a non-Oklahoma preset accidentally
    Reconfirm US-OK every time you rerun or after changing assumptions.

Try it

Here’s a straightforward first run you can do in DocketMath:

  1. Open /tools/alimony-child-support
  2. Select Oklahoma (US-OK)
  3. Enter:
    • Parent A gross income
    • Parent B gross income
    • Number of children
    • Length of marriage (and any other alimony fields the tool requests)
  4. Click Run (or the tool’s equivalent action)
  5. Read:
    • Child support output as guideline-based under 43 O.S. § 118 et seq. and schedule at § 119
    • Alimony output under the § 134 framework modeled by the tool
  6. Do two quick scenarios to see sensitivity:
    • Change combined income slightly (for example, increase Parent A gross income by $500)
    • Add or remove one child (to test how § 119 affects the schedule)

To keep results comparable:

  • Keep the same duration assumptions across scenarios.
  • Change only one variable at a time when you’re learning.

Example comparison structure:

ScenarioParent A Gross IncomeParent B Gross IncomeChildrenBiggest driver to watch
Baseline(enter)(enter)(enter)Combined income + § 119 schedule
Increase A by $500(baseline + 500)(same)(same)Child support increases via combined income
Add 1 child(same)(same)(baseline + 1)§ 119 schedule change

Related reading