How to run Structured Settlement in DocketMath for Minnesota

Step-by-step

This guide shows how to run a Structured Settlement calculation in DocketMath for Minnesota (US-MN), using jurisdiction-aware rules designed around the Minnesota Structured Settlement Protection Act.

1) Start your DocketMath Structured Settlement run

• Open DocketMath and go to the structured settlement tool: /tools/structured-settlement
• Choose jurisdiction US-MN (Minnesota).

What this does for your run:

• DocketMath applies Minnesota-specific modeling and output expectations aligned to Minnesota’s structured settlement disclosure and approval framework, including:

  • Required disclosures (Minn. Stat. § 549.32)
  • Approval procedure (Minn. Stat. § 549.33)
  • The Minnesota act generally (Minn. Stat. §§ 549.30–549.34)

2) Enter the payment stream (the “settlement” side)

In DocketMath, enter the payment schedule you’re structuring (or converting), including:

• Payment dates
• Payment amounts
• Whether payments are fixed or follow a defined pattern

How the output changes:

• Changing payment dates changes the timing used in valuation/discounting, which can shift totals.
• Changing payment amounts obviously changes the valuation results, but timing changes can materially alter the relative value of earlier vs. later payments.

3) Use the Minnesota calculation framework (jurisdiction-aware settings)

After you enter the payment stream, DocketMath should apply Minnesota-specific rule behavior for the run.

In particular, the Minnesota workflow includes:

• Best interest standard: enabled
• Minimum disclosure days: 10
• Discount rate basis: IRS § 7520 rate

How these affect outputs:

• Best interest standard: used to produce/reflect a Minnesota-aligned “best interest” result status for the scenario.
• Minimum disclosure days (10): shapes the disclosure workflow timing so your generated disclosure outputs reflect the minimum disclosure period logic.
• Discount rate basis (IRS § 7520): is used as the valuation discount-rate foundation inside the Minnesota logic.

4) Configure the transferee overlay (if your scenario uses it)

For scenarios where the federal overlay applies, DocketMath’s Minnesota rules include:

• Federal excise tax overlay: 40%
• Overlay basis aligned with 26 U.S.C. § 5891

How the output changes:

• Turning the overlay on applies the federal overlay logic, which changes net economics and the implied after-overlay valuation in the model.
• If the overlay is not appropriate for your scenario, leaving it out can keep the valuation focused on the pre-overlay economics.

5) Generate and review Minnesota disclosure-ready outputs

Minnesota disclosure requirements are addressed in Minn. Stat. § 549.32.

In DocketMath, review the generated disclosure-related outputs to confirm they reflect the Minnesota workflow expectations, including:

• Minimum disclosure days: 10
• The Minnesota disclosure framing based on the Minnesota statute workflow (Minn. Stat. § 549.32)

Practical review checklist:

• Disclosure timing reflects minimum disclosure days = 10
• The disclosures shown are consistent with the Minnesota disclosure framework (Minn. Stat. § 549.32)
• Valuation assumptions shown in the disclosures match your run inputs (notably the discount-rate basis)

6) Review approval-procedure support outputs

Minnesota approval procedure is addressed in Minn. Stat. § 549.33.

In DocketMath, your run outputs typically help you assemble the information you’ll want to reconcile with the approval process, such as:

• The payment schedule and valuation basis produced by the calculator
• The Minnesota-aligned best-interest result behavior (best interest standard enabled)

Action steps:

• Confirm the tool’s best interest standard output/status aligns with your scenario.
• Confirm the numbers in the summary/disclosure outputs align with your entered dates and amounts.

7) Export and finalize your results package

Before you finish:

• Re-check payment dates (small date changes can affect valuation)
• Re-check that the overlay setting matches your scenario
• Verify disclosure timing outputs reflect 10 days in the Minnesota workflow

Finally, export any calculator outputs you plan to reference in your structured settlement documentation workflow.

Common pitfalls

1. Incorrect discount-rate basis assumptions

• DocketMath’s Minnesota workflow uses a discount-rate basis tied to IRS § 7520 rate.
• If you try to substitute a different approach outside the tool, your valuation and disclosure outputs may not reconcile with the Minnesota-modeled results.

1. Forgetting the disclosure timing model

• The Minnesota workflow includes minimum disclosure days: 10.
• If your internal narrative uses a different timeline than what DocketMath outputs, your documentation may look inconsistent.

1. Overlay mismatch (when applicable)

• For scenarios involving the transferee overlay, DocketMath uses a 40% federal excise tax overlay aligned with 26 U.S.C. § 5891.
• Leaving the overlay out when it should be considered can make results appear more favorable than the Minnesota-modeled overlay output.

1. Payment schedule/date mismatches

• Even if payment amounts are correct, wrong payment dates can change valuation outcomes because discounting depends on time.

Try it

Start here: Structured Settlement calculator in DocketMath

To do a quick Minnesota (US-MN) test run:

• Use a small payment stream (for example, a short series of payments) so you can sanity-check timing and totals.
• Confirm these Minnesota workflow behaviors are present in the output:

  • Minimum disclosure days = 10
  • Best interest standard = enabled
  • Discount rate basis = IRS § 7520 rate
• If your scenario uses the overlay, ensure the 40% overlay aligned with 26 U.S.C. § 5891 is applied.

Quick iteration tip (change one thing at a time):

1. Adjust payment dates and observe how valuation changes.
2. Then adjust payment amounts.
3. Then check whether the overlay setting is correctly aligned with your scenario.

Related reading

• How to calculate Structured Settlement in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Structured Settlement in Philippines — Worked example with real statute citations
• Inputs you need for Structured Settlement in Philippines — Input checklist with sourcing guidance