How Settlement Allocator rules vary in North Dakota

What varies by jurisdiction

Run this scenario in DocketMath using the Settlement Allocator calculator.

Settlement allocations aren’t just spreadsheet math. In North Dakota (US-ND), how funds are allocated can affect tax reporting, liens, and how future disputes get framed, even when the underlying case settles for the same total amount.

With DocketMath’s Settlement Allocator, the core workflow is consistent: you input settlement components, then allocate amounts across categories. What changes by jurisdiction is the rule logic behind which categories are permitted, how they’re mapped to real-world payment obligations, and which verification steps are expected before you finalize the allocation.

In North Dakota specifically, you’ll typically see variation in these areas:

• Treatment of attorney fees and costs

  • Whether the allocation assumes fees are deducted “before” allocation (net) or applied separately (gross) can change downstream numbers.
  • For DocketMath users, this usually shows up in how you set fee entries—whether they reduce a category or appear as separate line items.

• Whether settlement categories need to align with claim types

  • Allocations tied to actual claims (for example, wage-related amounts versus non-wage damages) tend to be more defensible in later record reviews.
  • DocketMath outputs are only as accurate as the claim-type mapping you select.

• **Interaction with recovery obligations (liens/letters of protection)

  • North Dakota cases involving statutory or contractual payment priorities may require you to incorporate amounts payable to third parties before you compute “remaining to plaintiff.”
  • DocketMath can model third-party payees if you enter them as separate obligations, but you must have the amounts and triggers.

• Consistency with the settlement agreement’s structure

  • If the settlement agreement labels payments as “for lost wages” or “for emotional distress,” you’ll want your DocketMath allocation to match that labeling (or document why it differs).
  • DocketMath can help you produce a structured allocation, but it can’t fix an internal mismatch between the agreement and your worksheet.

What to verify

Before you rely on DocketMath’s /tools/settlement-allocator, verify the items that most directly change allocator outputs in North Dakota. Use this as a practical checklist to prevent allocation drift.

• The governing rule or statute for the jurisdiction.
• Any local rule overrides or administrative guidance.
• Effective dates and whether amendments apply.

1) Confirm which “allocation basis” you’re using

In DocketMath, decide whether you’re allocating:

• Gross settlement amount (then separately account for fees/costs), or
• Net settlement amount (where fees/costs are already withheld)

These two approaches can produce different category numbers even when the total is the same.

Check that:

2) Verify the claim categories you’re allowed to allocate

North Dakota-specific outcomes can depend on how damages are classified. A common failure point is using categories that don’t map cleanly to the pleaded basis of damages.

Verify:

3) Check third-party payment obligations that can “steal” from the allocatable pool

Allocator outputs are sensitive to liens, subrogation, or other repayment obligations because they reduce the residual plaintiff amount and can change the implied character of what remains.

For North Dakota files, confirm:

4) Ensure your settlement agreement and allocation document reconcile line-by-line

A strong allocator isn’t just numerically correct—it’s document-ready.

Verify:

5) Capture the dates and triggers that can affect reporting

Even if you only care about the allocation worksheet now, later reporting can hinge on timing and conditions.

Confirm:

These details matter because a component that appears “final” in the allocator may not be finalized for reporting until later.

Using DocketMath for North Dakota (inputs → outputs)

If you’re running DocketMath, the same tool can yield different results depending on how you input North Dakota-specific agreement details.

Typical workflow:

1. Open /tools/settlement-allocator
2. Enter:

   • Settlement total (gross or net—match the agreement)
   • Attorney fees/costs treatment (separate or deducted)
   • Category amounts (or let DocketMath allocate based on your provided percentages)
   • Any third-party obligations (payees and amounts)
3. Review:

   • Category totals
   • “Remaining to plaintiff”
   • Consistency warnings (if your inputs conflict internally)

Practical impact examples:

• If you switch from gross to net basis

  • DocketMath will change the category totals because fees/costs are either included in or excluded from the allocatable pool.
• If you add a third-party obligation

  • DocketMath recalculates the residual plaintiff amount and may require you to re-allocate categories if you entered category totals as fixed dollar amounts.

Gentle reminder: this article is for planning and workflow support, not legal or tax advice. Settlement allocation requirements can vary by facts and documentation.

Sources and references

Start with the primary authority for North Dakota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado