Spreadsheet checks before running Alimony Child Support in New Jersey
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
Before you run DocketMath’s Alimony Child Support calculator for New Jersey (US-NJ), a quick spreadsheet check can prevent avoidable math and timing errors. This is especially helpful when your worksheet does more than one thing—like tracking income, support components, and payment timing—because a single mis-specified cell can ripple through every output.
Here are the most common issues the spreadsheet checker is designed to catch for New Jersey inputs you plan to feed into the calculator.
1) Date fields that don’t line up with the “lookback” window
New Jersey’s general statute of limitations period is 4 years, under N.J.S.A. 12A:2-725. In this workflow, that is treated as the general/default period—no claim-type-specific sub-rule was found for this checker. Practically, your spreadsheet should clearly define:
- the date range you’re analyzing (e.g., “from 4 years ago through today”)
- the “as-of” date you want DocketMath to base calculations on
Why this matters: If your spreadsheet uses inconsistent date formats or pulls from the wrong year, the effective limitation window can change. That can make results look “off” even when the arithmetic is correct.
Pitfall: A worksheet formatted as MM/DD/YYYY but entered as YYYY/MM/DD can silently shift dates by months—changing which payments fall inside vs. outside a 4-year general window.
2) Rows and columns that mismatch the calculator’s expected structure
Many spreadsheet errors are structural, not mathematical:
- one income value placed in a “weekly” row but treated as “monthly”
- a number meant for a “support start date” placed into an “end date” cell
- a one-time payment intended to be excluded accidentally included as recurring income
The checker flags these as consistency problems, so you can correct them before you run the DocketMath alimony-child-support calculation.
3) Unintended blanks and zeroes
Blank cells and zeros can behave very differently in spreadsheet logic:
- a missing payment count can get interpreted as
0 - a missing income value can become an empty string that downstream formulas treat like
0
The checker helps identify spots where formulas depend on blank/near-blank values, unusually small values, or patterns that don’t match the rest of the sheet.
4) Inconsistent “units” across the sheet
Support worksheets often mix:
- gross vs. net
- annual vs. monthly vs. weekly amounts
- pre-tax vs. after-tax estimates
Even if DocketMath is computing correctly, mixed units can make outputs appear unreasonable. The checker looks for unit-consistency patterns (for example, one row set to annual while neighboring rows are monthly).
5) Payment frequency mismatches
If your spreadsheet lists payments “per month,” but your schedule assumes “per week,” totals can be off by a factor that’s hard to catch by eye. The checker checks that frequency-related settings and cumulative columns align across the sheet, including:
- schedule generation
- totals
- any reconciliation/cumulative columns
(Gentle reminder: this is for spreadsheet hygiene—not legal advice. Always review your inputs and assumptions carefully.)
When to run it
Run the checker right before you use DocketMath to calculate alimony and/or child support figures. The goal is to eliminate errors at the source, so the calculator is working from clean, internally consistent data.
A practical trigger list:
Because New Jersey’s general limitations period is 4 years under N.J.S.A. 12A:2-725 (and no claim-type-specific sub-rule was found for this checker), confirm your spreadsheet’s date window reflects a 4-year lookback where your workflow assumes that limitation concept.
Quick “run order” recommendation
- Fix any date formatting issues in your sheet
- Verify units (annual/monthly/weekly)
- Confirm payment frequency consistency
- Run the calculator in DocketMath
- Then reconcile totals in your spreadsheet (spot-check 2–3 rows)
Try the checker
You can use DocketMath’s Alimony Child Support tool workflow here:
When you’re setting up, keep these spreadsheet practices front-and-center so the checker has clean signals to verify:
Inputs to review (check these in your sheet)
- Date range (start date, end date, and/or “as-of” date)
- Income values and units (annual vs monthly vs weekly)
- Payment frequency (weekly/monthly)
- Any one-time payments vs recurring income
- Totals logic (are totals summing the same columns you intend?)
What outputs should change when inputs are fixed
After corrections, you’ll typically see changes in:
- cumulative totals (if frequency or unit mismatches were present)
- the effective inclusion/exclusion of payments tied to the date window
- row-level amounts that feed monthly/period totals
If the checker reports nothing and your recalculated outputs barely move after edits, that can be a good sign—you may have fixed formatting issues that weren’t actually affecting the computation. Still, verify that the right columns are populated (see the warning below).
Warning: A spreadsheet can “pass” superficial checks but still be wrong if values are placed in the wrong column (for example, weekly amount entered where monthly amount is expected). Confirm units and frequency, not just presence/absence of data.