How to calculate Alimony Child Support in Georgia

Quick takeaways

• Georgia separates “child support” and “alimony.” You calculate child support under O.C.G.A. § 19-6-15 and alimony under O.C.G.A. § 19-6-1 and O.C.G.A. § 19-6-5.
• DocketMath’s “alimony-child-support” calculator (jurisdiction US-GA) helps you generate estimates using Georgia-specific inputs and a jurisdiction-aware workflow. It also shows how changes to income, parenting time, and modeled needs/ability can shift outcomes.
• Alimony in Georgia is not a one-size-fits-all number. Under O.C.G.A. § 19-6-5(a), the finder of fact may award permanent alimony based on:

  • the needs of the requesting party, and
  • the ability of the other party to pay,
  • while considering eight statutory factors enumerated in the statute.
• Alimony duration note (required clarity): Use the calculator’s general/default period unless your case parameters explicitly call for a different duration request. In the provided brief, no claim-type-specific sub-rule was found, so this content treats alimony duration as a default modeling assumption, not a tailored duration rule for a particular claim type.

Pitfall: A common mistake is plugging the same income figures into both child support and alimony without confirming that your assumptions match how each component is intended to be modeled. Even small mismatches can materially change totals.

Inputs you need

Before you run DocketMath for Georgia (US-GA), gather the inputs below. Keeping them organized will also help you compare scenarios (for example, “with overtime included” vs. “without overtime included”).

Core financial inputs

• Obligor income (payer)

  • Gross monthly income (or your preferred recurring monthly figure used in your workflow)
  • Any relevant deductions you plan to model (keep consistent across scenarios)
• Recipient income (payee) (if your workflow uses both parties’ income)
• Other income streams (if applicable)

  • Bonuses, commissions, rental income, etc.

Parenting and child support inputs (Georgia child support)

• Number of children
• Parenting time / overnights allocation (or the split you want the model to assume)
• Monthly support calculation assumptions (whatever DocketMath asks you to provide inside the tool)

Alimony inputs (Georgia alimony)

DocketMath can help you translate your inputs into an estimate, but it does not replace the statutory factor analysis required in real cases. For context and modeling, prepare:

• Needs of the requesting party (recipient/payee)
• Ability of the other party to pay (obligor/payer)
• Eight statutory factors data points for context when you review results (even if you don’t input every factor directly, you’ll want your case notes to track what matters under O.C.G.A. § 19-6-5(a)), including:

  • the requesting party’s needs
  • the other party’s ability to pay
  • the length of marriage and other circumstances reflected in the factor list

Quick checklist (use while you enter data)

• I have both parties’ income figures in a consistent monthly format
• I have the number of children
• I have parenting time allocation inputs ready
• I have alimony needs/ability inputs ready
• I understand the calculator’s general/default alimony period (not a claim-type-specific duration rule)

How the calculation works

Below is the practical logic behind how DocketMath approaches an “alimony + child support” workflow for Georgia. This is a workflow explanation—not legal advice.

1) Child support component (Georgia)

Georgia child support is anchored in O.C.G.A. § 19-6-15. In a typical calculation workflow, DocketMath uses the inputs you provide—such as number of children and parenting time—to estimate a monthly child support amount aligned with Georgia’s framework.

What changes your child support output most:

• the number of children
• the parenting time allocation
• changes in either party’s income assumptions—especially the payer’s income

2) Alimony component (Georgia)

Georgia alimony is governed by O.C.G.A. § 19-6-1 and O.C.G.A. § 19-6-5. The core statutory anchor for permanent alimony is in O.C.G.A. § 19-6-5(a).

Per O.C.G.A. § 19-6-5(a), the finder of fact may award permanent alimony based on:

• the needs of the party requesting alimony
• the ability of the other party to pay
• consideration of the eight statutory factors enumerated in the statute

DocketMath’s operational value is that it helps you translate your inputs into an estimate, so you can test scenarios quickly.

Warning: The eight-factor analysis in O.C.G.A. § 19-6-5(a) is broader than “income difference.” If you enter only income numbers, you may get a result that looks precise even though statutory factors can shift outcomes in real proceedings.

3) How DocketMath combines them in your estimate

DocketMath’s alimony-child-support calculator is designed to produce a combined view:

• Child support estimated under the Georgia child support framework tied to O.C.G.A. § 19-6-15
• Alimony estimated using your alimony-relevant inputs under the framework reflected in O.C.G.A. § 19-6-1 and O.C.G.A. § 19-6-5

The tool then outputs monthly figures (and often scenario comparisons, depending on how you run it).

Scenario sensitivity: what to watch

Use DocketMath to run “what-if” updates and track which inputs move outputs the most.

4) Alimony period note (required clarity)

Alimony duration in this guide is handled as a default modeling assumption.

Follow the calculator’s general/default period unless your inputs or case parameters explicitly reflect a different duration request. As the brief notes, no claim-type-specific sub-rule was found, so this content treats alimony duration as a default period rather than a tailored duration rule for a specific claim type.

Common pitfalls

These are the most frequent errors people make when calculating alimony and child support in Georgia using calculators.

1) Mixing up income inputs across components

Child support and alimony can treat “income” differently in practice. Even if you only have one set of income numbers, keep assumptions consistent per run and document what you assumed.

• Same monthly format for both components
• Consistent treatment of bonuses/commissions across scenarios

2) Ignoring parenting time when calculating child support

If parenting time inputs are stale, rounded incorrectly, or based on the wrong schedule, child support can shift significantly.

• Verify overnights/schedule assumptions before you calculate

3) Assuming alimony is a fixed percentage

Georgia alimony under O.C.G.A. § 19-6-5(a) is not a simple fixed-percentage formula. It depends on needs, ability to pay, and the eight statutory factors. DocketMath can support planning and scenario testing, but it doesn’t replace factor-driven judicial analysis.

Pitfall: Treating an alimony estimate as guaranteed can lead to poor budgeting. Use results as a planning range, then align inputs to your actual supporting documentation.

4) Forgetting the “finder of fact” framing

The statute emphasizes that the finder of fact may grant permanent alimony under O.C.G.A. § 19-6-5(a). That matters when interpreting outputs: calculators model assumptions; they don’t decide statutory weight.

5) Not tying results back to the governing statutory anchors

When reviewing your outputs, keep these anchors in mind:

• Child support: O.C.G.A. § 19-6-15
• Alimony: O.C.G.A. § 19-6-1 and O.C.G.A. § 19-6-5 (especially § 19-6-5(a))

Sources and references

• O.C.G.A. § 19-6-15 (child support)
• O.C.G.A. § 19-6-1 and O.C.G.A. § 19-6-5 (alimony), including § 19-6-5(a) on permanent alimony based on needs, ability to pay, and eight statutory factors:

  • “Pursuant to O.C.G.A. § 19-6-5(a), the finder of fact may grant permanent alimony to either party, in accordance with the needs of the party and the ability of the other party to pay, considering the eight statutory factors enumerated therein.”
• Georgia Child Support Commission PDF (jurisdiction context):
  https://law.ga.gov/sites/default/files/related_files/site_page/Georgia%20Child%20Support%20Commission.pdf

Next steps

1. Open DocketMath’s Georgia tool here: /tools/alimony-child-support
2. Enter inputs in this order to reduce errors:

   • number of children → parenting time allocation → payer/recipient income assumptions → alimony needs/ability inputs
3. Run at least