CMS Rates 2025/26 - Basic, Reduced, Flat & Nil Explained

What this calculator does

Run this scenario in DocketMath using the Cms Child Maintenance calculator.

DocketMath’s CMS child maintenance calculator helps you work out which Child Maintenance Service (CMS) rate model applies and what the weekly amount could be for a qualifying child based on gross weekly income (and, where relevant, the number of children, other qualifying children, use of “flat” rates, and period-of-time rules).

For the 2025/26 calculation window, the CMS system commonly uses four broad rate categories you’ll see referenced as:

• Basic rates (income-related, calculated with a sliding scale)
• Reduced rates (typically when the paying parent has a lower income, receives certain credits, or there are circumstances that reduce the assessable amount)
• Flat rates (fixed weekly amounts used when income falls into a band or specific conditions are met)
• Nil rates (cases where the calculation produces a £0 weekly amount)

This guide explains the rate types in plain English and shows how your inputs drive the outcome in the DocketMath tool. It does not replace official CMS decision-making, and it does not provide legal advice.

When to use it

Use the DocketMath CMS child maintenance calculator when you want to estimate a CMS-style weekly amount for 2025/26, especially if you’re trying to understand:

• Which rate category applies (Basic vs Reduced vs Flat vs Nil)
• How changing your gross weekly income changes the weekly maintenance figure
• How the number of qualifying children affects the assessment
• Whether your situation falls into a flat-rate band rather than a sliding-scale calculation
• Whether a nil outcome is possible based on the input you plan to enter

You might also find it useful before:

• finalising budgeting for the coming maintenance period (2025/26)
• comparing scenarios (for example, two different income assumptions)
• preparing information for a CMS application or review

If you’re using a rough income figure (for example, converting annual salary to weekly), treat results as directional and keep your assumptions visible.

Step-by-step example

Below is a practical walk-through showing how DocketMath would typically behave conceptually. (Exact bands and reductions are encoded inside the tool; this example shows how to use the tool and interpret outputs.)

Example: Estimating a Basic weekly amount

Assumptions for this example

• Period: 2025/26
• Number of qualifying children: 1
• Paying parent gross weekly income: £450
• No additional complexities (assume the scenario triggers “basic-style” logic rather than flat or nil)

Step 1 — Open the calculator

Go to the tool here: /tools/cms-child-maintenance

Step 2 — Enter the key inputs

Fill in:

• Tax year / period: select 2025/26
• Number of children: enter 1
• Gross weekly income: enter 450

Optional inputs (if your tool asks for them) might include:

• other qualifying children
• any special circumstances that the CMS system treats differently
• calculation-date references

Step 3 — Read the rate category the tool selects

The tool should indicate which of these it is applying:

• Basic
• Reduced
• Flat
• Nil

If the tool selects Basic, that indicates your income level fell into a sliding-scale style outcome rather than a fixed “flat” band.

Step 4 — Compare output to your income assumptions

When you click calculate, you typically get:

• an estimated weekly amount
• a breakdown (or at least a label) showing the chosen rate category
• possibly a note showing what input caused the band selection

Step 5 — Try “what-if” adjustments

To test sensitivity:

• Change income from £450 → £480
• Recalculate and check whether the tool stays in Basic or moves into a different category (for example, into a higher band)

Checklist for interpreting results:

Common scenarios

CMS-rate outcomes often turn on a handful of recurring scenario patterns. Here are the most common ones you may want to model in DocketMath.

1) Income levels that land in Flat rates

If the paying parent’s income sits in a band where CMS uses a fixed weekly rate (rather than a sliding percentage), your result will typically look like a Flat amount.

How to use this in the calculator:

• Enter your best estimate of gross weekly income
• Observe the rate category label
• Adjust the income slightly (for example, ±£25) to see whether you’re near a threshold

2) Lower-income situations that trigger Reduced rates

In reduced cases, the assessment commonly reflects that the paying parent has less capacity to pay within the CMS framework.

In DocketMath:

• Keep the income input consistent with how your figures are derived (annual-to-week conversions should be done carefully)
• Recalculate after any change in income or the number of children

Practical check:

3) Very low income leading to Nil

Some scenarios can produce a Nil outcome (weekly amount of £0), typically when the CMS logic indicates no payable amount under the relevant rate model for the period and income assumptions.

What to do:

• Enter the lowest realistic gross weekly income
• Confirm the calculator shows Nil
• If you expect income to change soon, run a second scenario with a higher income figure to see the transition point

4) Multiple qualifying children

The presence of more than one qualifying child can change how the weekly assessment scales. DocketMath typically asks for the number of children as a primary selector for the rate calculation approach.

How to model quickly:

• Run scenario A: 1 child
• Run scenario B: 2 children (same income)
• Compare the selected rate category and weekly total

Use this to understand:

• whether adding another qualifying child keeps you in the same rate category
• whether the weekly amount increases in a linear or banded way

5) Comparing “Basic vs Flat” quickly

If you’re unsure whether your income sits just above/below a flat threshold:

• Try three runs: income − £25, income (estimate), income + £25
• Track which rate category label appears each time
• Use the outputs to inform budgeting assumptions

Tips for accuracy

To get estimates that are more useful (and less likely to confuse you later), focus on input discipline and repeatable assumptions.

Get your income input method consistent

The CMS framework is sensitive to gross weekly income. A common accuracy failure is switching between calculation methods across scenarios.

Checklist:

Use “band probing” around thresholds

When a result changes unexpectedly, you may have crossed a band boundary.

Practical workflow:

Treat reductions as scenario-dependent

Reduced or nil outcomes often depend on additional facts besides income. In DocketMath, any extra inputs you provide that relate to those facts should be:

• entered carefully
• kept consistent across comparisons
• changed only when you’re intentionally modelling a different scenario

Save your assumptions

Since the tool output depends on your inputs, keep a short note of:

• your entered gross weekly income
• number of qualifying children
• whether you changed any optional fields

Then you can interpret the result like a “scenario report” rather than a single number.

Don’t assume linear changes

CMS outcomes can shift between rate categories. That means:

• a £30 income increase may change the output by more than you expect if you cross a threshold
• similarly, a decrease might not reduce the weekly amount proportionally if you remain in the same band

Related reading

• Spreadsheet checks before running interest in United Kingdom — Spreadsheet validation before import
• How to interpret interest results in United Kingdom — What each output means and what moves the result
• Choosing the right interest tool for United Kingdom — How to choose the right calculator