Spreadsheet checks before running Alimony Child Support in North Carolina

6 min read

Published April 15, 2026 • By DocketMath Team

What the checker catches

Run this scenario in DocketMath using the Alimony Child Support calculator.

Running an alimony and/or child support calculation in North Carolina without a quick “inputs sanity check” can produce misleading results—especially when spreadsheets quietly accept missing, negative, or inconsistent values. DocketMath’s alimony-child-support calculator is jurisdiction-aware, but you can still reduce mistakes by running spreadsheet checks before you click calculate.

Here’s what the checker is designed to catch in US-NC:

  • Missing or mismatched core inputs

    • Child-related fields that are blank (e.g., number of children) while other income fields are filled.
    • Alimony fields (type/status and amounts) filled inconsistently with the scenario you’re modeling.
  • Invalid numeric ranges

    • Negative income, negative deductions, or “$0” where you intended “unknown.”
    • Interest-like values entered as annual amounts when the sheet expects monthly (or vice versa).
  • Time-period inconsistencies

    • Mixing monthly and annual figures (e.g., gross income monthly but deductions annual).
    • Using a “start date” that implies payments before the case timeline you’re modeling.
    • Feeding the calculator values using the wrong frequency (monthly vs. annual), even if the spreadsheet “looks right.”
  • **Jurisdiction-aware timing guardrails (default limits)

    • If your spreadsheet includes a lookback/retroactivity column, the checker verifies you’re applying the correct default general rule for the jurisdiction.
    • General SOL Period: 3 years is applied as the general/default limitation period for US-NC based on the jurisdiction data provided.
      • Clear note: No claim-type-specific sub-rule was found in the jurisdiction data you provided. So the checker uses this general/default 3-year rule rather than a claim-specific variation.
  • Guardrails around “retroactive” spreadsheets

    • Retroactive support tabs sometimes assume you can calculate freely back to an event date.
    • The checker flags when the computed lookback window extends beyond the 3-year general SOL period (based on your inputs and your modeled timeline).
  • Internal consistency within the spreadsheet

    • Total deductions greater than gross income.
    • Net income greater than gross income after deductions.
    • Child-support-specific quantities that don’t align with the scenario scope you selected.

Because spreadsheets don’t automatically enforce logic, these checks prevent a common failure mode: “the math is consistent, but the assumptions are wrong.”

Statute/timing note (US-NC): The jurisdiction data provided also references the SAFE Child Act and indicates a general/default 3-year SOL period. For context, NC DOJ materials discuss child-support-related safety and procedural framing under the broader SAFE Child Act information: https://www.ncdoj.gov/public-protection/supporting-victims-and-survivors-of-sexual-assault/

Gentle disclaimer: This checker is meant to improve input quality and timing sanity—not to determine legal entitlement. If your facts involve a specific theory or a different statutory framework, confirm whether a different timing rule applies before relying on outputs.

When to run it

Use the checker at three points in your workflow: before calculations, while iterating, and before exporting results.

  1. Before your first calculation

    • Confirm your spreadsheet is feeding DocketMath clean values.
    • This is where you catch blank inputs, negative numbers, and unit mix-ups.
  2. After each major change to assumptions

    • Rerun checks whenever you update:
      • Income sources or amounts
      • Pay frequency (monthly vs. annual)
      • Deductions
      • Child-count or other child-related parameters
      • Any retroactivity/lookback dates
  3. Before you share results or finalize a worksheet

    • At this stage, the goal is to stop accidental “garbage-in” scenarios.
    • Exporting a number based on inconsistent time periods is one of the fastest ways people get surprised later.

Timeline logic to double-check

If your worksheet includes a lookback window, anchor it to the general/default 3-year SOL period used by the checker for US-NC based on the jurisdiction data provided.

Also keep in mind the SAFE Child Act reference in the jurisdiction context: the checker’s role is to enforce input correctness and timing guardrails, not to replace procedural or legal review.

Try the checker

You can use DocketMath to run alimony-child-support calculations with spreadsheet discipline. Start with a lightweight checklist, then confirm the output shifts correctly when you tweak inputs.

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Step-by-step workflow (spreadsheet + DocketMath)

  • Step 1: Clean up your spreadsheet inputs

    • Ensure every numeric cell is:
      • Filled (no blanks)
      • Non-negative (unless the sheet is explicitly designed for negatives)
      • Using the expected units (monthly vs. annual)
  • Step 2: Identify any dates used in lookback

    • Note your start date/event date and the date you’re modeling from.
    • Ensure the modeled lookback is consistent with the general/default 3-year SOL period (and that no claim-type-specific sub-rule is being assumed, since none was provided in the jurisdiction data).
  • Step 3: Run DocketMath’s alimony-child-support

    • Use your spreadsheet values as inputs to the calculator.
    • If your spreadsheet includes multiple scenario tabs (e.g., baseline, high income, lower deductions), run checks and calculations for each scenario.
  • Step 4: Validate output sensitivity

    • Change one input at a time and confirm the output responds logically:
      • Increase income → resulting numbers should generally move in the expected direction.
      • Extend deductions → resulting numbers should shift accordingly.
      • Change the number of children → child-support-related outputs should track that change.

Quick validation table

Spreadsheet change you makeExpected behavior from calculator/checker
Update income by +$1,000/monthOutput should change; checker should not flag valid ranges
Switch from annual to monthly in one fieldChecker should flag the unit mismatch (or you should correct it before calculating)
Add a retroactive lookback date beyond 3 years (default)Checker should flag or limit the lookback window based on the 3-year general SOL period
Leave child count blankChecker should stop calculation or flag missing inputs

DocketMath primary CTA

If you’re ready to run the process end-to-end, use the calculator here:

  • /tools/alimony-child-support

Warning: Don’t assume “retroactive” math is valid just because a spreadsheet allows it. When your model reaches beyond the 3-year general SOL period used by the checker for US-NC (based on the jurisdiction data you provided), you risk outputs that exceed the default timing limitation.

Related reading