Abstract background illustration for How to run Structured Settlement in DocketMath for Arkansas

How to run Structured Settlement in DocketMath for Arkansas

7 min read

Published June 4, 2026 • By DocketMath Team

Partially verified

older_than_packet

Step-by-step

Below is a practical walkthrough for running a Structured Settlement calculation in DocketMath for Arkansas (US-AR), including jurisdiction-aware rules tied to Arkansas’s Structured Settlement Protection Act (Ark. Code Ann. § 23-81-701 to § 23-81-708).

Note: This guide focuses on how to run the Structured Settlement calculator in DocketMath and how Arkansas rules may affect the workflow. It does not provide legal advice.

1) Start the correct tool and select the right calculator

  1. Open DocketMath’s structured settlement calculator here:
    Primary CTA: /tools/structured-settlement
  2. Confirm the jurisdiction is set to Arkansas (US-AR).
  3. Choose the calculation mode shown in the tool (typically “structured settlement” rather than “sale/assignment” views, if both exist).

2) Enter the structured settlement inputs

DocketMath’s structured settlement calculator generally needs the economic terms that define the payment stream. Use this checklist to map what you know into the tool fields:

  • Payment schedule: list each scheduled installment (e.g., annual or monthly payments)
  • Payment amount(s): principal amounts per installment
  • Start date: when the first payment is due
  • Frequency: monthly/quarterly/annual, matching the settlement agreement
  • Cost-of-living or escalation terms (if any): fixed growth rate or CPI-linked increases
  • Discount rate / present value assumptions: the rate used to discount future payments back to today
  • Calculation date (valuation date): “today” or another chosen date for comparison

Tip: If your agreement includes a lump sum at maturity (or a “balloon” installment), enter it explicitly as its own scheduled payment rather than blending it into earlier payments.

3) Ensure Arkansas jurisdiction-aware compliance flags are considered

Arkansas’s Structured Settlement Protection Act framework regulates transfers of structured settlement payment rights. In practical tool terms, you want to ensure you’re not modeling an “approval-free transfer” as if court/authority review weren’t required.

Arkansas’s Act generally requires prior court or responsible administrative authority approval before structured settlement payment rights can be transferred, including express findings that the transfer is in the best interest of the payee and other statutory factors (Ark. Code Ann. § 23-81-701 et seq.).

In DocketMath, that typically translates into:

  • Using Arkansas (US-AR) as the jurisdiction context so outputs and any workflow prompts align with Ark. Code Ann. § 23-81-701 to § 23-81-708.
  • Avoiding any workflow interpretation that treats “transfer economics” as a substitute for the required approval process.

Reminder: DocketMath can help you calculate economics (timing, present value), but it doesn’t replace legal filings or the approval process required by statute.

4) Understand the outputs you’ll see in DocketMath

After you enter inputs, DocketMath will typically compute measures such as:

  • Present value: discounted value of the payment stream at the selected valuation date
  • Future value / payoff totals (depending on tool settings): what the stream totals to over time
  • Comparative values: scenario-based comparisons if the interface lets you vary assumptions

If your workflow includes a transfer/sale angle, the tool may also provide workflow notes reflecting the need for statutory approval. Treat these as operational guidance, not as confirmation of legal compliance.

5) Use scenarios to reflect how Arkansas assumptions change results

Even with the same underlying payment schedule, your outputs can change materially if you vary:

  • the discount rate (often the biggest driver of present value),
  • whether payments escalate (fixed COLA/CPI-style increases),
  • and the valuation date.

Run at least these scenarios:

  • Scenario A: baseline schedule + baseline discount rate
  • Scenario B: slightly higher discount rate (e.g., +1% or +2% if your interface allows)
  • Scenario C: escalation enabled vs. disabled (only if your agreement data supports an escalation toggle)

Record the PV deltas across scenarios so you can explain how sensitive your results are to key assumptions.

6) Confirm your calculation aligns with the “default” period

For the Arkansas setup described here, no claim-type-specific sub-rule was found. That means the calculator should rely on the general/default period rather than a special override.

Practically:

  • Use the standard payment schedule you entered (frequency + start date).
  • Do not apply a special “claim type” time rule in the absence of a detected Arkansas claim-type sub-rule for this workflow.

7) Review the computation before exporting or saving

Before saving/exporting:

  • Check that payment dates align with the agreement’s schedule
  • Verify the first payment date matches the tool’s start date logic
  • Confirm frequency (monthly vs. annual) matches your schedule
  • Ensure the discount rate is entered in the unit/format DocketMath expects (for example, 4.25 vs 0.0425)

Warning: A single date mis-entry (e.g., first payment one year too early) can shift present value substantially because discounting is time-sensitive.

Common pitfalls

These issues tend to cause the most frustration when running Arkansas structured settlement calculations in DocketMath:

  1. Using the wrong jurisdiction context

    • If the tool isn’t set to US-AR, workflow notes and compliance-aligned prompts may not reference Ark. Code Ann. § 23-81-701 to § 23-81-708.
  2. Overlooking escalation terms

    • If the settlement includes COLA/CPI or fixed escalation, failing to model it can understate future totals and skew present value.
  3. Inconsistent discount rate units

    • Many calculators expect either a percentage (e.g., 4.25) or a decimal (e.g., 0.0425). Match what DocketMath’s input field specifies.
  4. Misaligning payment frequency

    • Entering annual amounts while the tool interprets them as monthly (or vice versa) changes the timing of payments and can inflate/deflate present value.
  5. Assuming transfer approval is “automatic”

    • Arkansas’s Structured Settlement Protection Act requires prior court or responsible administrative authority approval before transfers of structured settlement payment rights, with express findings such as that the transfer is in the payee’s best interest (Ark. Code Ann. § 23-81-701 et seq.).
    • DocketMath can compute economics, but it doesn’t replace the required approval process.
  6. Trying to apply a special claim-type time rule

    • For the Arkansas setup described here, no claim-type-specific sub-rule was found, so use the general/default period.

Try it

Use this workflow as a quick “sanity test” run in DocketMath for Arkansas (US-AR):

A. Do a baseline run

  • Set jurisdiction to US-AR
  • Enter a simple schedule (for example, 20 annual payments of the same amount)
  • Use a reasonable discount rate consistent with your valuation assumption
  • Confirm DocketMath produces a present value

B. Stress-test with two scenario changes

  • Increase the discount rate slightly and confirm present value decreases
  • Add escalation (if supported by your agreement data/interface) and confirm present value increases vs. non-escalation

C. Validate the timeline

  • Ensure the first payment date results in the expected number of periods until the last payment
  • Check that frequency matches the schedule you entered

If your results behave counter to expectations (for example, PV increases when discount rate increases), pause and re-check:

  • discount rate formatting,
  • frequency,
  • and start/first payment date.

Finally, save or export the calculation from DocketMath once the model matches the payment terms you intended.

Related reading