How to calculate Alimony Child Support in Minnesota

Quick takeaways

• Minnesota handles child support using the income-shares / schedule framework in Minn. Stat. § 518A.34, and handles maintenance (alimony) under Minn. Stat. § 518.552 using discretionary factors (not a single plug-in formula).
• In DocketMath (Minnesota, US-MN) you’ll enter inputs for both components:

  • Child support: net income(s) and number of children to locate the correct Minnesota schedule tier based on combined monthly net.
  • Maintenance: factor-relevant inputs (including marriage duration tier) to reflect Minn. Stat. § 518.552.
• Your totals can change materially when you adjust:

  • combined monthly net (child support schedule tier movement, with presumptive logic up to the verified cap of 20000)
  • number of children (schedule changes)
  • marriage duration tier and other maintenance factors (maintenance changes even when child support stays the same)

Note: This is an educational walkthrough, not legal advice. For any legal strategy, consider a qualified Minnesota family-law attorney.

Inputs you need

Before you run DocketMath’s “Alimony Child Support” calculator for Minnesota (US-MN), gather inputs that feed both components: the child support schedule under Minn. Stat. § 518A.34 and the maintenance factors under Minn. Stat. § 518.552.

A. Child support inputs (Minn. Stat. § 518A.34)

For the child support portion, you’ll need:

• The parties’ monthly net income (or whatever net-income fields DocketMath requires)
• The number of children to determine which schedule row/column applies
• Inputs needed for DocketMath to locate the Minnesota schedule tier based on combined monthly net (the calculator uses verified “combined monthly net” reference points)

B. Maintenance (alimony) inputs (Minn. Stat. § 518.552)

Maintenance in Minnesota is not computed with the same kind of statutory schedule math as child support. Instead, Minn. Stat. § 518.552 directs consideration of eight discretionary factors. To use DocketMath effectively, be ready with:

• Information about marriage length and related facts (maintenance can be temporary, rehabilitative, or permanent, which is discretionary)
• Parties’ financial circumstances (income and needs), consistent with how DocketMath asks for factor inputs
• Other fact categories that DocketMath collects to represent the § 518.552 factors

C. Schedule-related constraints DocketMath uses for US-MN

DocketMath’s verified Minnesota settings affect the result:

• Minimum support order: 50
• Income cap (presumptive): 20000
• Verified schedule table reference points that relate to combined monthly net include:

  • 1399, 1499, 1599, 1699, 1799, 1999, 2099
  • 2499, 2999, 3499, 3999, 4499, 4999
  • 5499, 5999, 6099, 6999, 7999
  • 8999, 9999, 10999, 11999, 12999, 13999, 14999, 15999, 16999, 17999, 18999, 20000

Also note the verified schedule cap used by the tool:

• Schedule cap combined monthly PICS: 20000

How the calculation works

DocketMath’s Minnesota (US-MN) “Alimony Child Support” calculation reflects two different legal structures:

1. Child support uses a schedule-based method under Minn. Stat. § 518A.34 (structured using combined monthly net).
2. Maintenance (alimony) uses a factor-based method under Minn. Stat. § 518.552 (discretionary factors, including marriage duration tiers).

1) Child support: schedule-based, income-driven (Minn. Stat. § 518A.34)

In DocketMath, the child support workflow generally looks like:

1. Enter each party’s monthly net income (or equivalent net-income inputs).
2. DocketMath uses net incomes to determine the relevant combined monthly net figure.
3. The calculator matches that combined monthly net figure to a Minnesota schedule tier using the verified reference structure.
4. The schedule tier then determines the child support amount based on:

   • the combined monthly net tier, and
   • the number of children

Two verified constraints you should keep in mind:

• Presumptive income cap logic: 20000
• Minimum support floor: 50
  So, low-net scenarios will not drop below the minimum, and very high combined monthly net will be handled using the tool’s presumptive cap logic.

2) Minimum support floor

If your inputs produce a computed child support amount below the tool’s verified threshold, DocketMath applies:

• Minimum support order: 50

This prevents the child support output from falling below that minimum number.

3) Maintenance (alimony): factor-based (Minn. Stat. § 518.552)

Maintenance under Minn. Stat. § 518.552 is not reduced to a single statutory schedule. The statute requires consideration of eight discretionary factors, which means:

• Maintenance may be temporary, rehabilitative, or permanent (discretionary rather than formula-driven)
• Two scenarios with the same child support amount could still produce different maintenance outputs, depending on the factor inputs you select in DocketMath

Marriage duration tiers in DocketMath (verified)

DocketMath groups duration-related inputs into verified tiers to help represent marriage-length facts consistently:

• Long: min 20 years
• Mid: min 10 years, max 20 years
• Short: max 10 years

Because marriage duration is part of the overall fact pattern considered under § 518.552, adjusting this tier can change the maintenance output even if your child support schedule tier stays the same.

4) How the combined view can change when you change inputs

Even though the child support and maintenance portions are different “styles” (schedule vs. factors), you’ll still see interactions in your combined results because both depend on the underlying facts you enter:

• Child support changes when combined monthly net moves enough to shift to a different schedule tier (with reference points such as 1499, 1599, … up to 20000).
• Maintenance changes when factor-related inputs shift—especially marriage duration tier, plus other financial circumstances entered for § 518.552.

Here’s a practical way to think about it:

Practical walkthrough in DocketMath

Use this flow for Minnesota (US-MN):

1. Open the Minnesota calculator here: /tools/alimony-child-support
2. Enter the child support inputs first:

   • net income amounts (as requested by the tool)
   • number of children
3. Enter the maintenance inputs:

   • choose the appropriate marriage duration tier (short/mid/long based on years)
   • provide factor-relevant financial details DocketMath requests to represent Minn. Stat. § 518.552
4. Review outputs:

   • Child support: the schedule-tier result under Minn. Stat. § 518A.34
   • Maintenance: the factor-driven result under Minn. Stat. § 518.552
5. Run “what if” scenarios:

   • adjust one key variable (example: combined monthly net or marriage duration tier) while keeping others constant, so you can see what drives each output.

Common pitfalls

• Assuming maintenance behaves like the child support schedule.
  Child support follows the structured schedule framework in Minn. Stat. § 518A.34, while maintenance follows discretionary factors under Minn. Stat. § 518.552. In practice, maintenance often won’t respond to changes the same way child support does.

• Forgetting the tool’s verified constraints:

  • minimum support order 50
  • presumptive income cap 20000
    If you’re comparing two scenarios and you don’t account for these, you may misinterpret why the child support number did or didn’t change.

• Missing a schedule tier boundary.
  Minnesota’s schedule reference points are in a structured set (example values include 1499, 1599, and so on). Small income changes can push combined monthly net to a new tier, which can cause a noticeable jump in the child support output.

• Changing maintenance facts without expecting child support changes.
  If you only adjust maintenance factor inputs (like marriage duration tier) but leave combined monthly net and children count unchanged, the child support portion is likely to remain the same because it is driven by the schedule logic under § 518A.34.

Sources and references

• Minn. Stat. § 518A.34 (child support, revisor link): https://www.revisor.mn.gov/statutes/cite/518A.34
• Minn. Stat. § 518.552 (maintenance, revisor link): https://www.revisor.mn.gov/statutes/cite/518.552
• Minn. Stat. § 518A.35: https://www.revisor.mn.gov/statutes/cite/518A.35
• Minn. Stat. § 518A.36: https://www.re