How to calculate Settlement Allocator in South Dakota

Quick takeaways

• South Dakota uses a default “calculation period” approach for Settlement Allocator. The key statutory reference is S.D. Codified Laws § 15-6-23.
• DocketMath “settlement-allocator” converts your inputs (damages amounts and the statutory time window) into an allocator output you can use for settlement accounting.
• Your biggest accuracy lever is the time period that § 15-6-23 applies to the underlying claims—it affects how much of the total damages falls inside vs. outside the allocator’s calculation window.
• No claim-type-specific sub-rule was found for South Dakota in this brief. That means the statute’s general/default period drives the allocator rather than different periods for different claim types.

Inputs you need

Before you open DocketMath → /tools/settlement-allocator, gather the items below. Having them ready reduces rework when you discover that a date boundary changes the calculation.

Core inputs (usually required)

• Total settlement amount (the number you’re allocating)
• Total damages base (the combined damages figure your allocator will distribute)
• Calculation window dates for South Dakota under S.D. Codified Laws § 15-6-23

  • Start date that triggers the statutory period
  • End date that closes the statutory period
• Any known allocation categories your workflow requires (for example, the portions you want split across time periods or buckets in your case spreadsheet)

Case- and workflow inputs (often required in practice)

• How you’re mapping your damages to the allocator buckets

  • Example: you might separate “inside the window” vs. “outside the window” portions, then multiply by the settlement-to-damages ratio.
• Whether your damages totals already exclude setoffs or credits

  • If you already net certain amounts, keep that consistent across all buckets.

Sanity-check inputs

• Units: confirm whether your damages are expressed in dollars, totals, or line-item sums.
• Rounding rules: decide whether DocketMath outputs will be rounded to the nearest dollar, cent, or whole percentage points for downstream accounting.

Quick checklist (copy into your work log)

• I have the settlement amount
• I have the damages base amount (and it matches my filings)
• I have the statutory calculation window start and end dates under § 15-6-23
• I know how my damages will be bucketed for allocation
• I’ve decided on rounding conventions for the final allocator output

How the calculation works

DocketMath’s settlement-allocator follows a ratio-based workflow: it allocates your settlement across damages buckets using a ratio anchored to your damages base, while applying South Dakota’s statutory calculation window from S.D. Codified Laws § 15-6-23.

1) Set the statutory calculation period (South Dakota default rule)

South Dakota’s allocator calculation relies on the statutory period referenced in S.D. Codified Laws § 15-6-23 (see the statute link below). For this jurisdiction, no claim-type-specific sub-rule was found, so you should treat the statute’s general/default period as the controlling time window for the allocator.

In practical terms, that means:

• Determine which portion of your damages falls within the § 15-6-23 period.
• Any portion outside that period is handled through your bucket mapping (commonly as “outside period,” receiving a proportionally smaller or zero allocated share depending on how your damages are structured).

2) Compute the allocation ratio

DocketMath uses your settlement and damages base to establish a scaling ratio.

A typical ratio structure is:

• Settlement-to-damages ratio = Total settlement amount ÷ Total damages base

This ratio is then applied to each damages bucket to scale it into an allocated settlement amount.

3) Bucket damages based on the § 15-6-23 period

Next, split your damages base into buckets aligned to your workflow mapping. Many teams use:

• Bucket A: Damages within the statutory period
• Bucket B: Damages outside the statutory period

Then compute:

• Allocated settlement for Bucket A = Settlement-to-damages ratio × Damages in Bucket A
• Allocated settlement for Bucket B = Settlement-to-damages ratio × Damages in Bucket B

4) Adjust for any workflow-specific accounting choices

If your pipeline requires additional adjustments (for example, excluding amounts your internal policy treats separately), do those before entering values into DocketMath. This helps keep the ratio consistent with the accounting scope you intend to reconcile later.

5) Review outputs for proportionality and totals

DocketMath’s outputs should generally satisfy:

• Sum of allocated buckets ≈ Total settlement amount (allowing for rounding)

Allocator outputs should also move predictably when you change inputs, especially the date boundary and the bucketed damages.

What changes when you change inputs?

• Start date moves later → less damages fall “within period,” so Bucket A allocated amount typically drops.
• End date moves earlier → same directional effect: smaller “within period” bucket.
• Total settlement increases → all bucket allocations scale upward proportionally.
• Damages base changes (holding settlement constant) → the ratio changes; bucket allocations scale inversely with the ratio denominator.
• Reclassifying damages between buckets → allocations shift between buckets, while the overall total remains anchored to the ratio (subject to rounding).

Common pitfalls

These are the issues that most often cause allocator results to fail internal checks or misalign with case documentation in South Dakota.

1) Using a different time window than § 15-6-23

If your team uses a window derived from a different statute, timeline, or claim type, the allocator can diverge from the South Dakota default approach tied to § 15-6-23.

• Fix: lock the window dates to the § 15-6-23 calculation period and document the chosen trigger events.

2) Applying claim-type-specific sub-rules that aren’t supported here

This brief states: no claim-type-specific sub-rule was found. If you introduce different windows by claim category, you may unintentionally override the general/default rule.

• Fix: use the same general/default period for the allocator calculation across all buckets you’re allocating.

3) Feeding netted damages into one bucket but gross damages into another

A common spreadsheet failure is mixing:

• gross damages in one bucket
• netted damages (after exclusions) in another bucket

That breaks proportionality and causes total allocations to drift.

• Fix: ensure your damages base and bucket inputs use the same accounting basis.

4) Rounding too early

If you round percentages or bucket totals before scaling, the sum of allocations may not reconcile to the settlement.

• Fix: round only at the end (or keep extra precision during intermediate steps), then reconcile.

5) Mismatch between “damages base” and “settlement basis”

If your “total damages base” includes categories the settlement doesn’t cover (or excludes categories the settlement does), the settlement-to-damages ratio will be off.

• Fix: confirm the damages base reflects the same scope as what the settlement is intended to cover in your internal method.

Sources and references

• S.D. Codified Laws § 15-6-23 (South Dakota Legislature)
  https://sdlegislature.gov/Statutes/15-6-23

Next steps

1. Open DocketMath at /tools/settlement-allocator and select South Dakota (US-SD) jurisdiction settings if prompted.
2. Enter the statutory window dates tied to S.D. Codified Laws § 15-6-23.
3. Enter your settlement amount and damages base using the same accounting scope.
4. Split damages into your allocator buckets (commonly “within period” vs. “outside period”).
5. Run the calculation and do a reconciliation check:

   • Do the allocated bucket amounts sum to the total settlement (allowing for rounding)?
   • If you shift the statutory date boundary by a day, does the output change in the expected direction?
6. Export results and keep a short note describing:

   • the chosen § 15-6-23 period
   • your bucket mapping method

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations