How to calculate Structured Settlement in New York
8 min read
Published June 4, 2026 • By DocketMath Team
This page has current canonical verification receipts.
Quoted from the source law itself. Not legal advice; confirm how it applies to your matter.
Current verified answer
New York structured-settlement: limitation period is see statute; disclosure days before signing is 10.
Calculate nowAuthority and key facts
Citation: N.Y. Gen. Oblig. Law §§ 5-1701 to 5-1709 (Structured Settlement Protection Act)
View the primary sourceVerified April 26, 2026
- Limitation Period: see statute
- Disclosure Days Before Signing: 10
- Disclosure Typeface Minimum Points: 14
- Federal Excise Tax Rate: 40
Quick takeaways
- DocketMath’s structured-settlement calculator for New York (US-NY) helps you build an installment schedule and then frames results using the relevant Structured Settlement Protection Act concepts in N.Y. Gen. Oblig. Law §§ 5-1701 to 5-1709 (Structured Settlement Protection Act).
- In New York, the Structured Settlement Protection Act governs key process items that affect how you finalize a structured settlement (including disclosure-before-signing concepts), not just the payment math.
- For federal tax inputs, the calculator’s assumptions are aligned with the allowed federal references, including 26 U.S.C. § 104(a)(2) and information-reporting concepts tied to 26 U.S.C. § 5891, with additional mechanics potentially reflected from 26 U.S.C. § 130.
- If you enter the wrong payment timing, or you mix up lump sum vs. periodic amounts, your downstream schedule-driven outputs will be off quickly.
- This guide is about how to set up the calculation in DocketMath for New York and how the New York framework affects what you should document before execution—not about legal advice.
Note: This guide explains how to set up the calculation in DocketMath and how New York’s framework affects the inputs you choose. It does not provide legal advice.
Inputs you need
Before you click /tools/structured-settlement, collect the items below. DocketMath will use them to build the payment stream and related outputs.
Payment structure inputs (core to the calculation)
Use the checklist and keep your numbers consistent across documents:
- Total claim value to structure (the amount you’re allocating into the structured payout)
- Payment type(s)
- Lump sum amount (if any)
- Periodic payments (monthly/quarterly/annual—whatever you’re modeling)
- Payment frequency for each periodic component
- Start timing (e.g., first payment date or “payments begin at contract signing”)
- Number of periods or end date (when periodic payments stop)
- Escalation terms (if periodic payments increase over time—if your structure includes this)
- Discounting / present value assumption (if DocketMath requests an assumption for valuation)
- Any commutation provisions (optional, only if your settlement terms include them)
New York process inputs (affects finalization steps)
These inputs relate to the structured settlement “protection” process described in the New York Act and help ensure your modeling aligns with what parties typically must satisfy.
- Disclosure package readiness: confirm whether the parties plan to comply with New York’s disclosure before signing concept captured in the statute framework. DocketMath’s verified dataset models 10 days as the disclosure lead time.
- Document formatting expectation: confirm whether the disclosure’s typeface minimum is satisfied. The verified dataset models a 14-point minimum type requirement.
- Receipts / limitation period tracking: DocketMath may prompt you to track timing tied to the Act’s process. The verified dataset flags “limitation period” as governed by the statute rather than treated as a fixed calculator constant.
Federal tax modeling inputs (fed into DocketMath outputs)
DocketMath’s structured-settlement calculator may need enough information to align outputs with common federal tax framing represented by the allowed federal references:
- Nature of damages (so the tool can align category selection with 26 U.S.C. § 104(a)(2) framing)
- Information reporting posture (so outputs can align with concepts reflected by 26 U.S.C. § 5891)
- Federal tax mechanics parameter (if applicable in the calculator workflow)
- The allowed references include 26 U.S.C. § 130, which may appear in modeled workflows as additional mechanics.
Warning: Feeding DocketMath a payment stream that doesn’t match the settlement agreement’s timing and composition will distort the outputs. Even a correct tax category cannot fix a wrong schedule.
How the calculation works
DocketMath’s structured-settlement calculator (US-NY) translates settlement economics into a schedule and then associates modeled amounts with tax/reporting concepts reflected in the allowed statutes.
Step 1: Build the payment schedule
DocketMath generates a timeline of payments based on your inputs:
- Lump sum: treated as a single payment on the specified date.
- Periodic payments: treated as a repeating cash flow with:
- your chosen frequency
- a start timing
- and either an end date or number of periods
- optional escalation if you specify it
The schedule is the backbone for every later output.
Step 2: Compute totals and valuation measures
Once the cash flow series is established, DocketMath can produce summary metrics such as:
- total payout across all periods
- totals by component (lump sum vs periodic)
- present-value style valuation measures (depending on the calculator mode/inputs)
If you change frequency (annual → monthly) while keeping total dollars constant, the timing changes—and, if discounting is enabled, the present value measure can change as well.
Step 3: Apply New York jurisdiction-aware process logic
For New York (US-NY), DocketMath’s jurisdiction-aware workflow incorporates structured-settlement protection process inputs associated with the Structured Settlement Protection Act in N.Y. Gen. Oblig. Law §§ 5-1701 to 5-1709 (Structured Settlement Protection Act).
In the DocketMath calculator experience, this shows up as jurisdiction-aware prompts aligned with the verified dataset, including:
- disclosure timing before signing, modeled as 10 days
- a document formatting requirement modeled as 14-point minimum type
- process-aligned toggles tied to the New York protection framework
These items typically don’t change the pure math of the payment schedule, but they affect what you should finalize and document during the structured settlement execution process.
Step 4: Associate federal tax and reporting concepts
DocketMath also uses the allowed federal references to align output categories, including:
- 26 U.S.C. § 104(a)(2): used to help frame whether certain damages components are treated in a way consistent with exclusion concepts in the relevant context
- 26 U.S.C. § 5891: used to reflect information-reporting concepts that may be relevant to structured settlement arrangements
- 26 U.S.C. § 130: may appear in the allowed set for additional federal tax mechanics in modeled workflows
In practice, your inputs (especially the nature of damages and information reporting posture) determine which category options the calculator uses alongside your schedule.
Step 5: Excise tax modeling (where the calculator includes it)
Some structured settlement setups can trigger an excise-tax-related concept in modeling. DocketMath’s verified dataset includes a modeled federal excise tax rate of 40 in its US-NY structured settlement workflow.
That means:
- if your selected configuration in DocketMath indicates the excise-tax-relevant posture, you’ll see output adjustments tied to that 40 rate
- if your configuration doesn’t align with excise-tax-triggering conditions, excise-tax-related adjustments may not appear
Pitfall: “Tax modeling” is not uniform across all setups. Even with the same payment schedule, tax-related outputs depend on your chosen inputs about damages category and reporting posture.
Common pitfalls
Use this section like a pre-flight checklist before you trust the calculator outputs.
Payment schedule errors
- Incorrect start date: shifting the first payment by weeks can materially affect any timing-based valuation outputs.
- Wrong frequency: annual vs. monthly is a common cause of mismatched totals and timelines.
- Mixing lump sum and periodic amounts: if a lump sum is accidentally included in the periodic stream (or vice versa), totals and timing will drift.
- Forgetting escalation: leaving escalation at “none” when your contract escalates payments can understate later periods.
New York workflow/compliance mismatches
- Skipping disclosure timing prompts: DocketMath’s US-NY rules reflect 10 days disclosure lead time as modeled in the verified dataset.
- Document readiness issues: DocketMath’s jurisdiction-aware workflow includes a modeled 14-point minimum type expectation for disclosures.
- Ignoring limitation period tracking prompts: the statute governs timing concepts; DocketMath flags limitation-period-linked tracking rather than treating timing as arbitrary.
Federal tax/reporting confusion
- Choosing the wrong damages category for 26 U.S.C. § 104(a)(2)-consistent framing.
- Assuming reporting outputs don’t depend on inputs: 26 U.S.C. § 5891 concepts are represented in the tool through the reporting posture you select.
- Misreading excise-tax-related outputs: if the calculator flags excise-tax modeling, the verified dataset uses a modeled 40 rate.
Sources and references
- New York Structured Settlement Protection Act: N.Y. Gen. Oblig. Law §§ 5-1701 to 5-1709 (Structured Settlement Protection Act)
https://www.nysenate.gov/legislation/laws/GOB/A5T17 - New York (selected section): N.Y. Gen. Oblig. Law § 5-1706
https://www.nysenate.gov/legislation/laws/GOB/5-1706 - New York (selected section): N.Y. Gen. Oblig. Law § 5-1705
https://www.nysenate.gov/legislation/laws/GOB/5-1705 - Federal tax: 26 U.S.C. § 5891
https://www.law.cornell.edu/uscode/text/26/5891 - Federal tax: 26 U.S.C. § 104
https://www.law.cornell.edu/uscode/text/26/104 - Federal tax: **26 U.S.C. §
