Spreadsheet checks before running Alimony Child Support in Arkansas
5 min read
Published April 15, 2026 • By DocketMath Team
What the checker catches
Running an alimony/child-support workflow in Arkansas is easy to do incorrectly because spreadsheets can “look right” while silently using the wrong timing assumptions. DocketMath’s alimony-child-support spreadsheet checker is designed to catch the common spreadsheet failures that create downstream errors—especially issues tied to payment timing and the calculation window.
Below are the main categories the checker is built to surface in an Arkansas run (US-AR):
Date arithmetic mismatches
- Detects when your spreadsheet calculates elapsed time using the wrong start/end dates (for example, using the filing date for an obligation that began later).
- Flags inconsistencies such as “period length” changing when you edit only one date—an early sign that formulas are referencing the wrong cell(s).
Statute-of-limitations (SOL) window misalignment
- Uses Arkansas’s provided general/default SOL period: Ark. Code Ann. § 5-1-109(b)(2) (general SOL period 6 years).
- If your spreadsheet effectively assumes a longer or shorter lookback without adjusting the calculation window accordingly, the checker highlights it before you interpret results.
- Important clarity for this jurisdiction data: your provided notes indicate no claim-type-specific sub-rule was found. So the checker applies the general/default 6-year period from Ark. Code Ann. § 5-1-109(b)(2) rather than attempting to select a specialized SOL by claim type.
Payment frequency and proration errors
- Catches cases where the schedule is treated as monthly when your inputs are weekly (or vice versa).
- Identifies when proration creates fractional periods that later get rounded in a way that changes totals.
Rounding drift across rows
- Detects when rounding happens per-row (for example, rounding each month) instead of at the aggregate level.
- Flags when your sheet’s totals don’t match recomputed totals from the same inputs—often caused by row-level rounding and inconsistent formula references.
Sign and direction mistakes
- Flags negative values that may indicate “credits” entered with the wrong sign.
- Alerts when a worksheet mixes “amount due” and “payments made” conventions in opposite directions, which can invert the meaning of a payment or credit.
A practical way to use the checker: treat its results like a quality assurance pass for spreadsheet assumptions. It won’t determine legal rights or decide your case, but it can prevent your spreadsheet from silently doing the wrong math.
Quick reference: Arkansas SOL assumption used by the checker
| Item | Arkansas default value used in US-AR |
|---|---|
| General SOL period | 6 years |
| Statute citation | Ark. Code Ann. § 5-1-109(b)(2) |
When to run it
Run the checker early, and then rerun it after any change that could affect timing, period counts, or sign conventions. In spreadsheet workflows, mistakes tend to cluster around these exact points.
A practical workflow:
Before entering payment amounts
- Run the checker after you set up your date range(s) and payment frequency.
- Goal: confirm that the checker recognizes your timeline and isn’t implicitly using a different lookback window than you intended.
After you set (or update) the lookback window
- If your worksheet includes a custom start date intended to reflect the Arkansas limit, run the checker immediately after you update that start date.
- This is where the Arkansas general SOL period (6 years, per Ark. Code Ann. § 5-1-109(b)(2)) most often gets missed.
- Reminder: no claim-type-specific sub-rule was found in the jurisdiction notes you provided, so the general/default 6-year period is the baseline.
After you change payment frequency or schedule
- Any switch between weekly/monthly/biweekly schedules should trigger a re-check.
- The checker is especially good at catching proration and frequency mismatches in the same pass.
After you adjust credits, offsets, or “payments made”
- Run again once amounts are finalized so sign conventions, direction, and rounding drift don’t distort totals.
Common pitfall: If you only run a spreadsheet check after final totals are produced, you may end up “correcting” numbers manually without fixing the underlying timeline mismatch—resulting in totals that look plausible but are logically inconsistent.
Try the checker
Start with a small, controlled test run. The goal isn’t to get perfect final outputs on the first try—it’s to see how the checker responds when you tweak inputs.
- Open DocketMath and navigate to the alimony-child-support spreadsheet checker tool.
- Select Arkansas (US-AR) as the jurisdiction.
- Enter (or import) your timeline inputs, such as:
- Start date and end date for the calculation window
- Payment frequency (for example, monthly)
- Any schedule/amount structure you’re using
- Run the checker before you rely on the computed totals.
What you should expect to change when inputs change
Use these “edit-to-observe” tests:
Change only the start date
- If the checker is correctly applying the general/default 6-year SOL (per Ark. Code Ann. § 5-1-109(b)(2)), results should reflect a narrower or wider window accordingly.
Change payment frequency
- Totals should rebalance due to different period counts.
- If your spreadsheet doesn’t adjust frequency consistently, the checker should warn you.
**Toggle rounding behavior (if your sheet has it)
- The checker may expose row-level rounding drift by comparing computed totals vs. sheet totals.
Primary CTA
Run the workflow directly here: **Go to DocketMath Alimony/Child Support tool
Gentle disclaimer: This is a spreadsheet-checking workflow, not legal advice. Timing and SOL questions can be fact-specific; consider consulting a qualified professional for legal determinations.