Spreadsheet checks before running Alimony Child Support in Texas

What the checker catches

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

Before you run alimony + child support calculations in Texas (US-TX) with DocketMath, a spreadsheet-style checker helps you catch issues that usually cause the biggest downstream errors—especially when a worksheet silently uses the wrong assumptions.

Because you’re working in Texas (US-TX), the checker focuses on jurisdiction-aware validations and data consistency checks, including timing logic.

Limitation-period baseline (Texas)

Texas commonly uses a general/default limitation period as a timing baseline. In the provided jurisdiction data, the general/default period is:

• 0.0833333333 years (≈ about 1 month)

Important: No claim-type-specific sub-rule was identified in the jurisdiction inputs you provided. That means the checker should treat 0.0833333333 years (~1 month) as the general/default period only, and it should not attempt to apply a claim-type-specific limitation period.

For the underlying statute reference, see Texas Code of Criminal Procedure, Chapter 12: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

What a practical spreadsheet checker catches in an alimony-child-support workflow

• Date-format and “time delta” errors

  • Detects if date cells are stored as text (e.g., 01/15/2026 stored as a string rather than a real date).
  • Verifies that differences between dates are computed in days and then converted correctly into months/years for timing windows.

• Jurisdiction code mismatch

  • Ensures the sheet is labeled US-TX and not accidentally using an old value (for example, copied from another state tab).
  • Confirms that any rule toggles (like “Texas”) are actually active in the calculation sheet feeding into DocketMath.

• Default limitation-period application

  • If your spreadsheet has a “timeliness” or “limitations” column, the checker confirms it uses the general/default period of 0.0833333333 years (~1 month).
  • Flags situations where the limitation period cell is blank, outdated, or copied from another configuration.
  • Warns if someone attempts to apply a claim-type-specific limitation period—even though the provided Texas jurisdiction data only supports the general/default baseline.

  Common pitfall: A limitations/timeliness column can “look filled in” but still be wrong if it was copied from a non-Texas tab or the period value was never updated. The checker should explicitly confirm the 0.0833333333 years (~1 month) general/default period is what’s being used.

• Missing or inconsistent inputs

  • Flags blank cells for key drivers such as:

    • order effective date (when used for timing)
    • last payment date (when estimating arrears/timing)
    • income fields used for support-related calculations
  • Checks that numeric fields are truly numeric:

    • e.g., “$2,500” should be parsed as 2500 (or equivalent clean numeric values), not left as text.

• Sign and direction errors

  • Verifies support amounts aren’t entered with the wrong sign.
  • Detects cases where “paid” unexpectedly exceeds “owed,” unless your model is explicitly designed to allow that.

Example: how the checker surfaces issues

To make spreadsheet debugging faster, the checker typically produces a results grid like:

Gentle note: This is meant to reduce math and configuration errors. It’s not a substitute for professional/legal review of your specific situation.

When to run it

Run the checker twice: (1) before you finalize inputs and (2) after you update spreadsheet ranges or re-import data.

Run the checker before importing a spreadsheet into the Alimony Child Support workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

1) Before first calculation

Run it as soon as you’ve filled in your initial worksheet:

• jurisdiction label (US-TX)
• relevant dates (order/payment/timing dates)
• income numbers
• any toggles or columns that feed into timing/limitations logic

Goal: prevent “bad data in” so DocketMath doesn’t compute using flawed assumptions.

2) Immediately after updates

Re-run the checker whenever you change any inputs that typically affect timing or totals, including:

• order effective date
• payment dates used for arrears/timing
• income fields (even small edits)
• jurisdiction selection/toggles
• any cell that controls the “timeliness/limitations” baseline

A quick checklist you can reuse

If your spreadsheet includes optional columns (like “timeliness” or “limitations”), the checker should enforce that those optional logic paths are either:

• correctly configured for Texas general/default, or
• disabled rather than silently using a wrong baseline.

Try the checker

You can use DocketMath to compute alimony-child-support after you’ve run the spreadsheet checks.

Start here: /tools/alimony-child-support

To get the most reliable outputs, set up your sheet so the fields you enter into DocketMath (or that feed into it) are normalized:

• Dates

  • Use a consistent format (e.g., YYYY-MM-DD)
• Numbers

  • Remove currency symbols and commas so values are plain numerics
• Jurisdiction

  • Explicitly set US-TX in the worksheet rules/toggles
• Timing default

  • If you include a limitation window, ensure it uses 0.0833333333 years (≈ 1 month) as the general/default period
  • Don’t try to apply a claim-type-specific limitation period based on missing data; the provided Texas inputs only support the general/default baseline

If results don’t seem right

Don’t assume the calculation is correct or incorrect immediately—first rerun the checker and look for common causes:

• date differences are off by a factor of ~30–31 (often date parsing)
• totals jump when you change one cell (often wrong references)
• timeliness/toggles behave unexpectedly (often default period mismatch)

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado