Inputs you need for Alimony Child Support in Minnesota

Inputs you will need

If you’re using DocketMath to estimate alimony and child support in Minnesota, the accuracy of the result depends on whether you can supply the right inputs. Minnesota support calculations rely heavily on (1) each parent’s income and (2) the child’s situation (including parenting time/custody time). For alimony, courts also consider additional facts beyond income—so it helps to collect information that reflects both households as realistically as you can.

This checklist is designed to help you gather the inputs you’ll likely need before you run DocketMath: alimony-child-support (jurisdiction: US-MN).

Quick reminder: This is for estimating with a tool, not for guaranteeing outcomes in court. Actual orders depend on case-specific facts, filings, and evidence.

• Are you estimating for an existing Minnesota case, a modification, or a new filing?

• This usually won’t change every numeric input, but it can affect what you’re trying to measure and what timeline context matters.

• Include wages, bonuses (if reliable/ongoing), commissions, and other recurring earned income.

• If Parent A is self-employed, you’ll typically need a profit/income figure you can support with tax and business records (use whatever measure the calculator expects).

• Include the same categories as Parent A.

• Examples: certain documented pre-tax or required deductions.

• The tool can only use the numbers you enter—so keep documentation handy in case you need to correct something.

• Choose a consistent monthly figure (or an average) that matches what you can reasonably document.

• Provide the monthly cost attributable to the child(ren) if you know it.

• If you don’t yet have the exact premium breakdown, gather the best estimate available from payroll/plan materials so you can update later.

• Enter ongoing, qualifying child care amounts if you have them.

• If you’re missing information, try to locate invoices or provider statements—support results are often sensitive to this category.

• Examples may include required work expenses that a model accepts.

• If the tool doesn’t request them or you don’t have documentation, don’t guess.

• Enter the number of children included in the calculation.

• Enter the split in the format the calculator uses (for example, days overnights/time bands).

• Parenting time can materially change the child support estimate because it affects how the tool allocates child-related costs between households.

• Some models use age bands. Be ready to provide birth dates/ages for accuracy.

• Spousal income disparity is typically captured through the income inputs, but the tool may ask for additional context.

• If the tool requests it: any spouse health insurance costs or other recurring obligations you want reflected (only enter items you can support).

Timeline “default” cautions (Minnesota statute of limitations)

Minnesota has a general statute of limitations for certain claims. Minnesota Statutes § 628.26 provides a 3-year general period.

If you’re tracking deadlines connected to older support-related issues, use this 3-year general default period unless a statute clearly applies a different, claim-specific timeline.

• Important: A 3-year general rule under Minnesota Statutes § 628.26 is not a guarantee about deadlines for every support-related issue. The correct deadline can depend on the exact claim type and how it’s pled.

(General reference noted in the brief: Minnesota Statutes § 628.26, “3-year general period.” Source context: https://minnesotacourtrecords.us/criminal-court-records/gross-misdemeanor/)

Where to find each input

Gathering inputs is easier when you pull them from consistent records. Here are practical places to look by input type:

• **Gross monthly income (both parents)

  • Pay stubs (look at the most recent 4–12 weeks)
  • W-2s and/or 1099s (latest tax year)
  • Payroll portal year-to-date earnings (if you can convert to a reliable monthly figure)
  • Self-employed income: recent tax returns and business financials (or profit/loss statements)

• Income deductions / adjustments

  • Employer statements for pre-tax deductions
  • Documentation of required payments the tool recognizes
  • If the tool uses tax-based inputs: relevant tax return line items

• Overtime / commissions / variable pay

  • Pay stubs showing overtime/shift premiums
  • Commission statements or employer summaries

• Health insurance

  • Payroll benefit enrollment sheets
  • Plan documents or benefit statements showing premiums
  • Determine the portion attributable to the child(ren) (or spouse + child, if the plan is bundled—then allocate what’s requested)

• Child care costs

  • Receipts, invoices, or payment confirmations
  • Provider statements showing the monthly charge

• Parenting time

  • Current schedule (calendar screenshots can help)
  • Temporary order paperwork (if you’re modifying)
  • Any written agreement detailing overnights/days

• Children’s details

  • Birth dates from identification records
  • Case filings (if you need to confirm ages or the children included)

• **Alimony context (when the tool asks)

  • Basic budget items you can support with records (housing/utilities/debt payments)
  • Proof of recurring obligations if the tool requests them

• **Timeline / limitations context (if you’re also checking deadlines)

  • Use the 3-year general period in Minnesota Statutes § 628.26 as the general default unless you confirm a different claim-specific rule applies.

Pitfall to avoid: Don’t estimate parenting time from memory. Enter the schedule as accurately as you can—small differences can change results if the model uses time bands or overnight counts.

Run it

Once you’ve gathered your numbers, run DocketMath: alimony-child-support using the Minnesota setting (US-MN).

1. Open the calculator: /tools/alimony-child-support
2. Confirm the jurisdiction selection is Minnesota (US-MN).
3. Enter each input into the matching categories the calculator provides.
4. Review the output summary, typically including:

   • Child support estimate (most affected by income + parenting time + health insurance/child care inputs)
   • Alimony estimate (most affected by income disparity and any alimony-specific inputs the tool requests)

How outputs change when inputs change

Use this quick review guide while testing different entries:

• Income changes (either parent): child support generally shifts with the income figures; alimony estimates can change if disparity shifts.
• Parenting time shifts toward one parent: child support typically adjusts because the tool reallocates child-related costs based on the schedule.
• Adding credible child care and child health insurance numbers: the child support estimate may increase if the tool includes those costs.
• Removing uncertain entries: if you can’t document an expense, consider not entering it (or revising to a conservative number you can support) so the estimate doesn’t get inflated.

Documentation tip (fast)

Before you finalize entries, keep files organized so you can verify or update numbers:

• A_income_paystubs_YYYYMM-YYYYMM.pdf
• B_income_1099_W2_YYYY.pdf
• insurance_child_premium_monthly.pdf
• childcare_invoices_MMYYYY.pdf
• parenting_time_calendar_YYYY.pdf

This makes it much easier to correct inputs if something doesn’t match what you expected.

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado