Common Alimony Child Support mistakes in Arkansas
5 min read
Published April 15, 2026 • By DocketMath Team
The top mistakes
Run this scenario in DocketMath using the Alimony Child Support calculator.
When people calculate alimony and child support in Arkansas with DocketMath, small input errors—and missed jurisdiction-aware rules—can create big downstream problems. Below are the most common mistakes we see when running the DocketMath alimony-child-support calculator for US-AR (Arkansas).
Pitfall: This post covers common calculation and paperwork mistakes. It’s not legal advice, and it can’t replace review by a qualified professional.
1) Using the wrong “time” when gathering income or expenses
A frequent error is pulling income numbers from different time windows (for example, using one parent’s monthly income from 2024 but the other parent’s from 2026). In practice, those mismatches skew the result because DocketMath depends on the period you enter.
What goes wrong
- One parent’s wages reflect a different pay cycle or year.
- Expense entries (child-care, health costs, or housing-related figures) don’t match the same “as-of” date.
Quick fix
- Use consistent snapshots: the same month/year for both parents’ income inputs and any recurring expenses.
2) Confusing alimony with child support inputs
People sometimes treat child-related costs as though they were alimony items (or vice versa). DocketMath separates these concepts, so mixing them causes incorrect modeling.
Watch for
- Recording school costs, childcare, or medical out-of-pocket items in the “alimony” area instead of the child support area.
- Entering a parenting-time or custody assumption that doesn’t match how the input fields are labeled in the calculator.
Quick fix
- Decide what bucket each number belongs in before entering it into DocketMath.
3) Omitting key income components
If you only enter base salary and leave out other recurring income, your model can understate a parent’s ability to pay.
Common omissions include:
- Overtime or shift differentials (when consistent)
- Bonuses or commissions when they recur
- Retirement or disability-related income if it’s recurring and reflected in the information you’re using
Quick fix
- Use “recurring in the last 6–12 months” as your internal rule of thumb when deciding what to include in inputs.
4) Entering child-related costs as one-time expenses
DocketMath works best when inputs reflect amounts you intend to model as ongoing/recurring (even if those costs vary somewhat). If you enter a one-off cost (like a specific purchase) where a recurring cost is expected, the projection can swing.
Quick fix
- Separate recurring monthly costs from one-time costs. Only enter the recurring ones into the fields designed for regular amounts.
5) Relying on outdated or mismatched documentation dates
Another real-world issue: people enter numbers from old pay stubs or outdated tax figures, then compare outputs to current obligations.
Quick fix
- Match the documentation date to your input date range (for example, use current pay stubs for “current income” inputs rather than older filings).
6) Misunderstanding the statute of limitations (SOL) period
In Arkansas, the general/default statute of limitations is 6 years under Ark. Code Ann. § 5-1-109(b)(2).
Important clarification:
No claim-type-specific sub-rule was found here. So, treat the 6-year general/default period as the only period stated in this article.
Warning: The applicable limitations period can change depending on the specific claim type and facts. This article states only the general/default SOL period cited above.
How to avoid them
A smoother DocketMath run depends less on legal complexity and more on disciplined input hygiene. Use this checklist before you hit calculate.
Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.
Step-by-step input discipline (DocketMath)
How outputs change when you correct inputs
Use “single change at a time” testing. For example:
| Scenario change | What typically happens in the DocketMath output | Why it changes |
|---|---|---|
| Add recurring overtime/bonus to income | Modeled obligation often increases | Total available income increases |
| Move a childcare expense from alimony to child-support inputs | Child-support figures tend to rise; alimony modeling adjusts separately | Expenses are now categorized correctly |
| Switch from outdated annual income to current monthly income | Output can swing up or down | Current income better represents ability to pay |
| Convert a one-time cost into a recurring monthly cost (or vice versa) | Output changes significantly | Recurring costs compound across the modeled period |
Recordkeeping tips that prevent rework
Instead of re-running DocketMath repeatedly with “latest numbers,” keep a small audit trail:
- Create a list of the documents used (pay stubs, expense summaries, prior statements).
- Record the effective date range for each input.
- If you update inputs, note what changed (for example: “overtime added—last 4 pay periods”).
Don’t ignore the SOL question—track it, even if you’re just modeling
If you’re working on a timeline for issues that may involve enforcement or disputes, don’t guess on Arkansas’s baseline period.
- Arkansas general/default SOL period: 6 years
- Statute: **Ark. Code Ann. § 5-1-109(b)(2)
Because this article only states the general/default period, you should treat it as a starting reference—not the final word for every claim category.
Note: The 6-year period above is the general/default rule stated here. If your situation involves a specific claim type, the limitations period analysis may differ.
If you want to model quickly, start with the DocketMath tool here: /tools/alimony-child-support.