Why Damages Allocation results differ in New Jersey

5 min read

Published April 15, 2026 • By DocketMath Team

The top 5 reasons results differ

When you run DocketMath’s damages-allocation calculator for New Jersey (US-NJ), you may see different results across runs, teams, or case files. Those differences usually trace back to how the tool interprets inputs and how New Jersey’s governing time limits interact with the claim timeline.

Below are the top 5 reasons results differ in New Jersey.

  1. The statute of limitations (SOL) gate changes what damages are “in-range”
  • New Jersey’s general SOL for contract-based damages is 4 years under N.J.S.A. 12A:2-725 (UCC § 2-725).
  • DocketMath can effectively “trim” damages to the measurable window once the relevant accrual date is set.
  • If the accrual date (or event date) differs by even a few months, the included damages window can shift.

Note: The period cited here is the general/default SOL. The jurisdiction data you provided does not identify a claim-type-specific sub-rule, so the 4-year period is used as the default baseline.

  1. Accrual date selection is the single biggest driver
    In practice, parties disagree on when the clock starts (e.g., delivery vs. breach vs. discovery-like triggers). DocketMath’s outputs will differ if you input different accrual assumptions because the calculator can apply the 4-year measurement window.

Common causes of mismatch:

  • Different “breach” dates in the record
  • A later “notice” date treated as the start of the claim period
  • Using a settlement/termination date instead of the accrual date
  1. “Loss period” boundaries aren’t aligned
    Even if everyone agrees on “4 years,” they may not agree on:
  • Start boundary (first unpaid invoice month? first defective shipment? first missed performance?)
  • End boundary (last payment? last performance? suit filing date?)

DocketMath’s allocation results can move materially when the loss period is stretched or tightened inside that SOL frame.

  1. Inconsistent allocation inputs (amounts, rates, or counts)
    Allocation differences often come from:
  • Different line-item sums (e.g., one worksheet totals $182,400; another totals $181,900)
  • Different item counts (shipments, invoices, time entries)
  • Different per-unit or monthly rate inputs

Small numeric discrepancies can compound when the calculator prorates amounts across months or categories.

  1. Treatment of partial periods and rounding
    When damages are allocated over time, partial months and rounding policies can create noticeable variation—especially if your inputs break down by month.

For example:

  • One run prorates daily using a specific mid-month accrual date
  • Another run allocates the full month to the earlier bucket

How to isolate the variable

Use this diagnostic workflow in DocketMath to pinpoint what’s driving the change.

  • Freeze the jurisdiction and tool settings so both runs use the same rule set.
  • Compare one input at a time (dates, rates, amounts) and re-run after each change.
  • Review the breakdown to see which segment or assumption drives the difference.

Step-by-step checklist

  • Accrual date (one specific date)
    • Loss period start/end dates
    • Damage amounts (category totals or line items)
    • Accrual date (e.g., shift by ±90 days)
    • Loss period end date
    • Allocation amounts/rates
    • Rounding or proration options (if available in the tool UI)

Quick diagnostic table

Changed variableExpected effect in NJ allocationHow to verify in DocketMath
Accrual dateDamages window expands/contracts within 4-year SOLCompare “included months/period” before vs. after
Loss period endTrims or adds trailing monthsCheck last month included
Line-item totalsDirectly shifts allocated sumsReconcile category totals used as inputs
Proration/roundingAlters month-by-month distributionCompare allocation per month bucket

Next steps

  1. Capture the exact run settings
    Save or screenshot the inputs used for:
  • accrual date
  • loss period boundaries
  • category totals/rates
  1. Run a “SOL sensitivity” mini-test
    Do three runs in DocketMath:
  • Accrual date as entered
  • Accrual date +90 days
  • Accrual date -90 days

If totals swing sharply, your mismatch is likely tied to what portion of damages falls within the 4-year default window under N.J.S.A. 12A:2-725.

  1. Reconcile timeline language
    Compare the underlying documents:
  • delivery/performance records
  • breach/termination notices
  • payment ledgers

Differences in dates are frequently the reason two teams produce different allocations even when they cite the same statute.

  1. Document your assumptions (without arguing the law)
    DocketMath outputs are only as consistent as the inputs. If you’re sharing results internally, add a short “assumptions” note describing:
  • which date was used as accrual
  • which period was treated as the loss window
  • that the SOL baseline is the general/default 4-year period under N.J.S.A. 12A:2-725

Warning: This post describes general mechanics and the default SOL period you supplied. It does not address claim-type-specific nuances beyond the provided jurisdiction data, and it’s not legal advice.

Want to run your own scenario now? Use /tools/damages-allocation:
Run the calculator

Related reading