Spreadsheet checks before running small claims fees and limits in New York

5 min read

Published April 15, 2026 • By DocketMath Team

What the checker catches

Before you calculate small-claims fees and limits in New York, your spreadsheet should survive a quick “sanity pass.” DocketMath’s small-claims-fee-limit checker is built to catch common spreadsheet failures that can quietly distort outputs—especially when your workbook applies filing rules, cap amounts, or fee-related thresholds.

Use it to confirm your workbook is internally consistent before you rely on a final number.

The checker is designed to detect or flag issues like these:

  • Broken assumptions

    • Wrong unit conversions (for example, mixing dollars vs. cents).
    • Misapplied thresholds (for example, testing a limit against “total claim” when your sheet’s logic actually intends a different basis such as a “net amount” definition).
  • Formula drift

    • A cell references an old tab, outdated column, or an earlier version of a calculation range.
    • One row follows different logic than the rest (often caused by copying formulas from a slightly different row block).
  • Edge-case math

    • Off-by-one comparisons around exact dollar cutoffs.
    • Rounding inconsistencies (for example, using ROUND vs. TRUNC, or comparing values before rounding rather than after rounding).
  • Sign and formatting errors

    • Negative values stored as text.
    • Values like “$1,200” imported as strings with commas/symbols, causing comparisons that won’t behave as expected.
  • Time-based misalignment

    • The spreadsheet computes “age of claim” from the wrong date field (e.g., using the wrong event vs. filing date).
    • The logic assumes a claim-type-specific statute of limitations sub-rule that your sheet does not actually have, or that you do not intend to apply.

Statute of limitations check (default period)

For this New York scenario, use the general/default five-year period as your fallback: N.Y. Crim. Proc. Law § 30.10(2)(c) (General SOL Period: 5 years), from: https://www.nysenate.gov/legislation/laws/CPL/30.10.

Important: your brief notes that no claim-type-specific sub-rule was found for the default period. That means your spreadsheet should treat five years as the default/general period rather than inventing a different pathway inside the sheet.

A good sanity check confirms that:

  • the “event date” (or equivalent) input is the same one used to compute elapsed time, and
  • the elapsed-time logic uses 5 years as the baseline when you’re in the default pathway.

Gentle note: This is a spreadsheet logic check, not legal advice. If you’re unsure what limitations rule applies to a specific fact pattern, consider getting help from a qualified professional.

When to run it

Run the checker at two points: (1) when you’re about to trust new inputs and (2) right before you export or submit your results.

A practical workflow:

  1. After you import or update inputs

    • Party/customer amounts changed
    • Fee schedule dates changed
    • Any “claim date” / “event date” fields were edited
  2. After you change formulas, even slightly

    • Reordered columns
    • Inserted a new row/column
    • Updated rounding logic or threshold comparisons
  3. Before you copy values into another sheet/tab

    • Copy-paste can convert formulas into static values, meaning you may keep an error even after you fix the original logic.

Think of the sheet like an instrument you calibrate: check early, then re-check right before output.

Inputs checklist (do before running the tool)

Outputs checklist (do after running the tool)

Because spreadsheet errors are often deterministic (and therefore repeatable), catching them with a structured check can prevent “silent wrong answers.”

Try the checker

Open DocketMath and run the small-claims-fee-limit checker using your spreadsheet-derived numbers.

If you’re working in stages, you can paste only the minimum input set required to reproduce the fee/limit outputs—then compare the checker’s interpretation to what your sheet calculates.

Primary CTA: ** /tools/small-claims-fee-limit

“Input → behavior → output” map

Use this table to guide what to confirm when you test your sheet:

Spreadsheet inputWhat to confirmHow outputs should change
Claim amount / amount tested against the limitThat you’re using the correct definition (gross vs. net) consistent with your sheet’s logicIf you increase by $1 across a threshold, the fee/limit category should flip only at the true cutoff
Date used for elapsed-time logicThat it’s pulled from the correct date fieldSwitching the date forward beyond the default 5-year window should move your internal logic into the appropriate “default SOL pathway” behavior
Fee-related inputsCorrect units and the correct rounding stageChanging decimals should not cause sudden threshold jumps unless a cutoff is actually crossed under your rounding/comparison rules
Any intermediate totals used in downstream mathRow-level consistency and correct aggregationTotals should match component sums; totals should align with the checker’s interpretation

While testing, focus on boundary conditions:

  • Test values at exactly the limit.
  • Test values one unit above and below the limit.
  • Test dates just inside the 5-year window vs just outside it.

Warning: A spreadsheet can appear “mathematically correct” but still be wrong for limit/fee logic if it compares numbers at the wrong rounding stage (for example, comparing a rounded number to an unrounded threshold). The checker is meant to surface these mismatches.

If the checker output doesn’t match your sheet:

  • first identify which input changed the classification (amount threshold, rounding bucket, or the default 5-year SOL pathway using N.Y. Crim. Proc. Law § 30.10(2)(c)),
  • then inspect the specific formula/branch that governs that decision point.

Related reading