How to run Structured Settlement in DocketMath for New York

Step-by-step

This guide walks you through running a Structured Settlement calculation in DocketMath for New York (US-NY) using jurisdiction-aware rules aligned with the Structured Settlement Protection Act: N.Y. Gen. Oblig. Law §§ 5-1701 to 5-1709 (Structured Settlement Protection Act).

1) Open the Structured Settlement calculator

1. Go to the calculator:

   • Primary CTA: /tools/structured-settlement
2. Set jurisdiction:

   • Select jurisdiction = US-NY so DocketMath applies New York–specific structured settlement rules.

2) Enter the core settlement inputs

In DocketMath, use the structured settlement form to enter the economic terms that drive the payment schedule and totals. The exact field names can vary slightly by UI version, but most workflows require inputs that let DocketMath compute a payment stream and related totals.

Use this checklist to ensure your dataset is calculation-complete:

• Total settlement amount (or an equivalent starting figure)
• Payment structure type (e.g., fixed stream vs. term-based stream, depending on what DocketMath offers)
• Number of payments / duration
• Payment timing (start date and interval)
• Discount rate / present value settings (if DocketMath prompts for it)

How outputs change: once you run the calculation, you should see schedule-derived outputs (amounts and timing) and—depending on your selected mode—present value metrics. If you later change start date, interval, or number of payments, expect the totals and timing-based metrics to shift accordingly.

3) Add New York SSPA workflow inputs (jurisdiction-aware)

New York’s Structured Settlement Protection Act is centered on court oversight and required disclosures. In DocketMath’s US-NY mode, you should look for jurisdiction-specific workflow inputs tied to that disclosure and signing process.

Populate any fields you see for the following compliance-related items supported by the verified rules configuration:

• Disclosure timing before signing: DocketMath’s US-NY ruleset includes disclosure requirements 10 days before signing.
• Disclosure formatting minimum: DocketMath’s US-NY ruleset includes a minimum typeface size of 14 points.

Practical guidance:

• If DocketMath asks for disclosure date, signing date, or disclosure document metadata, fill them in so the tool can validate internal consistency.
• Treat the resulting outputs as calculation and documentation support, not a determination of legal compliance.

4) Configure tax-related settings (federal inputs)

Structured settlement tax handling may require Internal Revenue Code inputs. In the verified facts packet, DocketMath’s US-NY configuration includes:

• Federal excise tax rate: 40

If your DocketMath workflow includes a tax configuration section, confirm it is enabled (or correctly set) for your scenario, and ensure your selections align with the following allowed federal references used by DocketMath:

• 26 U.S.C. § 5891
• 26 U.S.C. § 104(a)(2)
• 26 U.S.C. § 130

Practical input guidance:

• Confirm whether your scenario includes an excise tax component (DocketMath will typically prompt if it’s relevant)
• Select the tax mode/options that match what you’re modeling in your structure
• Do not leave required tax fields blank if your calculation mode expects them

How outputs change: enabling or adjusting tax settings can affect tax-related computed figures in the output (for example, changing amounts shown in any “tax” section). If outputs suddenly show unexpected nonzero values (or zeros), that’s often a sign that the tax module toggle or required inputs weren’t aligned with your scenario.

5) Run the calculation and review the outputs

Run the calculation after entering:

• the core payment schedule inputs, and
• any applicable US-NY disclosure/workflow inputs, and
• the relevant tax settings (if your scenario requires them).

Typical DocketMath outputs include:

• a payment schedule summary (amounts and timing)
• aggregated totals (e.g., total nominal payments)
• present value metrics (if enabled by your chosen calculation mode)
• a separation of computation results vs. workflow notes (when available)

Then do quick consistency checks:

• Does the payment count match your intended duration?
• Do the start date and interval match your timeline?
• Do schedule totals reconcile with the settlement amount you entered (or your equivalent starting figure)?
• If the tax module is enabled, do you see tax-related figures where you expect them?

6) Export or capture the calculation results

If DocketMath provides export/download options:

• Export a summary (PDF or similar) for recordkeeping
• Save the input dataset so you can rerun quickly if any term changes (start date, interval, payment count, etc.)
• When you build your submission package, align the calculation outputs with your broader narrative and documentation workflow consistent with N.Y. Gen. Oblig. Law §§ 5-1701 to 5-1709

7) Tie outputs to the New York SSPA framework (without overstepping)

Your operational goal is to generate outputs that are internally consistent and ready to be reviewed within an SSPA-style documentation workflow for New York.

In DocketMath terms, that means:

• your disclosure timing fields should match the US-NY rule requirement of 10 days before signing
• your disclosure formatting should satisfy the 14-point minimum setting supported by the verified configuration
• your schedule outputs should reflect the structure you describe
• your federal tax configuration should match your selected modeling approach and the allowed referenced sections that DocketMath uses

Reminder: this is guidance for using the tool and building consistent calculation artifacts—not legal advice.

Common pitfalls

These are the most common issues that cause friction when running structured settlement calculations in US-NY mode in DocketMath.

1. Leaving New York disclosure timing fields blank

   • In US-NY mode, the verified rules configuration includes disclosure requirements 10 days before signing. Missing or inconsistent dates can trigger confusing validation warnings.

2. Ignoring disclosure formatting inputs

   • If DocketMath asks for disclosure formatting settings, ensure they meet the 14-point minimum typeface requirement supported by the verified configuration.

3. Input schedule mismatch

   • Even if the calculation “runs,” the schedule may not match your intended terms. Always reconcile:

     • start date
     • interval frequency
     • number of payments
     • totals vs. the settlement amount you entered

4. Tax module left in the wrong state

   • The verified configuration includes federal excise tax rate: 40. If your scenario requires tax modeling and the tax section is disabled—or the rate isn’t set as expected—outputs may not match your intended assumptions.

5. Reviewing results without checking timing logic

   • Structured settlement outputs are highly timing-dependent. Verify that the output schedule dates and intervals align with what you plan to document.

Try it

Follow this quick trial run to confirm your DocketMath setup for New York (US-NY).

A. Minimal run (get confidence in the schedule)

• Set jurisdiction to US-NY
• Enter a basic payment structure (start date + interval + number of payments)
• Run the calculation
• Confirm the payment count and totals appear as expected

B. Compliance workflow validation run

• Add signing date and disclosure date fields (if shown in the US-NY UI)
• Ensure disclosure timing matches 10 days before signing
• Ensure disclosure formatting setting matches 14-point minimum typeface
• Rerun the calculation and confirm the workflow checks pass

C. Federal tax settings run

• Enable tax configuration (if your scenario requires it)
• Confirm the federal excise tax rate setting is 40
• Verify the relevant federal references you selected align with:

  • 26 U.S.C. § 5891
  • 26 U.S.C. § 104(a)(2)
  • 26 U.S.C. § 130
• Rerun and compare outputs to the minimal run

D. Compare outputs to confirm input sensitivity

Run at least 2 scenarios:

• Scenario 1: keep everything the same except change payment start date
• Scenario 2: keep everything the same except change payment interval or number of payments

Track what changes in the outputs (especially totals and any present value metrics, if your mode includes them).

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