Connecticut Paid Leave Is 0.5% in 2026: How Employers Can Catch Over-Withholding and Reconcile CTPL

If your payroll software is taking 1% from Connecticut wages for paid leave, stop before the next payroll run. The Connecticut Paid Leave contribution rate is one-half of one percent, or 0.5%, for 2026. The program is employee-funded, but the employer still owns the job of calculating deductions, filing quarterly wage reports, and getting the money to the Connecticut Paid Leave Authority.

That combination creates an easy bookkeeping trap: a small configuration error can double every deduction, while a missed wage cap or duplicate quarterly payment can leave the books and the state account disagreeing. This guide explains the 2026 rule, a repeatable reconciliation process, and what to do when you find an overpayment or underpayment.

The 2026 Connecticut Paid Leave rules in plain English​

Most employers with one or more employees working in Connecticut are covered unless a statutory exception or an approved private plan applies. For an employer participating in the public program:

• The employee contribution rate is 0.5% of subject wages.
• The employee, not the employer, funds the public program. There is no employer match.
• Contributions are withheld through payroll and remitted quarterly.
• Subject wages use the Social Security contribution and benefit base. For 2026, that base is $184,500.
• Once an employee reaches the applicable wage base with an employer, further wages from that employer should not generate more CT Paid Leave deductions for the year.

At the 2026 maximum, the arithmetic is straightforward: $184,500 × 0.005 = $922.50 of potential CT Paid Leave deductions for one employee’s covered wages with one employer. That is a ceiling on the wage base, not a flat annual charge. Someone paid $1,000 in a week contributes $5 for that week; someone paid $80,000 in covered wages during the year contributes $400 if the cap is not reached.

The multi-employer detail matters. If a worker has two employers, each employer generally continues applying the contribution to that employer’s covered wages until the wage base is reached with that employer. Do not assume that one employer’s payroll system can see the other employer’s deductions.

Why a business can accidentally collect too much​

The rate is simple. The wage definition and the payroll handoff are where errors tend to appear. Review these failure points before assuming the amount on a quarterly invoice is correct.

A rate setting carried forward from the wrong rule​

The most obvious error is a 1% configuration. It may come from a mistaken interpretation of the rate, a copied setup from another state’s paid-leave program, or a payroll template that was never updated. A 1% deduction is twice the 2026 public-program rate.

The annual cap is not tracked across pay runs​

Payroll systems often calculate a percentage correctly on each check but fail to stop at the annual wage base. This is especially common when an employee receives a bonus, commission, severance, or a year-end payment, or when payroll is processed by two systems during a provider change.

Wage codes are mapped inconsistently​

Connecticut describes total wages broadly. Salary and hourly wages, vacation pay, holiday pay, tips, commissions, severance pay, and the cash value of in-kind payments can be included. Benefits excluded from FICA taxable wages should be excluded from the CT Paid Leave wage calculation as well.

An employer that excludes every payment other than regular salary may under-withhold. An employer that treats every benefit as subject may over-withhold. Build the wage-code map from the Authority’s definition and your payroll records rather than relying on a generic “state tax” category.

Filing and payment are treated as the same event​

The quarterly return reports wages and calculates a contribution. The payment settles the amount due. A return can exist without a completed payment, and a payment can exist without a correctly filed return. A bank statement showing that money left the account is not proof that the corresponding CT Paid Leave filing was accepted.

A payroll provider is assumed to own the obligation​

You can use a third-party administrator, but the employer remains responsible for compliance. A monthly close should therefore include a check of the CT Paid Leave account, not just a review of the provider’s payroll register.

Know the filing calendar before you reconcile​

The Authority lists contributions as due on the last day of each calendar quarter:

Treat the following month as a compliance grace period, not as permission to delay the close. If contributions are still unpaid after that period, the Authority says a single penalty of up to 10% of the amount owed or $50, whichever is greater, may apply. Unpaid contributions also accrue 1% non-compounding interest monthly under the program’s late-payment rules.

The due-date control should have two owners: the person preparing the wage report and the person checking that both the invoice and payment show as completed in the employer portal. Separating those duties catches a surprising number of “we filed it, but never paid it” problems.

A six-step CT Paid Leave payroll reconciliation​

Do this monthly, then repeat it for the quarter before filing. Monthly work keeps a small error from turning into a quarter-end reconstruction project.

1. Confirm the covered employer setup​

Document which Connecticut workers are included, whether the business has an approved private plan, and which payroll account or third-party administrator is responsible for the public program. Keep the registration and approval records with the payroll close documents.

If the business stops employing people in Connecticut, do not simply stop the deduction and abandon the account. Follow the Authority’s closing instructions and make the required zero-wage filing until the account is properly closed.

2. Build a subject-wage report from gross payroll​

Export payroll by employee and pay date. Keep the gross pay detail, not just the total liability from the payroll summary. Add the included wage categories and remove only the benefits that are excluded under the applicable FICA wage treatment.

Your working report should include:

• Employee identifier and Connecticut work status
• Pay date and payroll period
• Regular wages, overtime, vacation, holiday, tips, commissions, severance, and other included pay
• Excluded benefits and the reason for exclusion
• Year-to-date subject wages before and after the annual cap
• CT Paid Leave withheld on the check
• Expected withholding at 0.5%

Do not use a Connecticut income-tax withholding report as a substitute. The two calculations have different purposes and can have different wage bases.

3. Apply the cap at the employee level​

Calculate the remaining 2026 wage capacity for each employee:

Remaining subject-wage capacity
= $184,500 − prior covered subject wages
 
Current-period subject wages
= the lower of current included wages or remaining capacity
 
Expected CT Paid Leave deduction
= current-period subject wages × 0.005

The formula is a control calculation, not a replacement for professional advice or the Authority’s current instructions. It is most useful for finding a mismatch between payroll configuration and the underlying wage detail.

For a worker who has already reached $184,500 in covered wages with your business, the current-period subject wage is zero. The payroll record should preserve the zero for auditability even though the employee’s gross pay is not zero.

4. Compare three numbers, not one​

For each quarter, compare:

1. Total employee deductions in the payroll register
2. The expected 0.5% of capped subject wages
3. The contribution reported and paid to the Authority

These numbers answer different questions. The first tells you what was taken from workers. The second tells you what should have been taken. The third tells you what the employer represented and remitted. A payroll register can be correct while the remittance is wrong, or a remittance can match the report while both are based on an incorrect wage map.

5. Tie the remittance to the portal​

After filing, save the return confirmation, invoice number, payment confirmation, bank trace or ACH record, and the quarter covered. The online process allows employers to review filing and payment history; an invoice and a payment should both reach completed status.

ACH debits may take several business days to clear and appear as completed. Keep the item in a pending-reconciliation account until the portal and bank records agree. Do not mark the liability fully settled merely because an ACH instruction was submitted.

6. Post the accounting entries clearly​

Because the contribution is withheld from employees and there is no employer match, it should normally be tracked as a payroll liability rather than employer payroll expense. A simplified ledger flow looks like this:

At payroll:
  Debit   Wages expense                         gross wages
  Credit  Payroll withholding liabilities       employee deductions
  Credit  Cash or net-pay payable               remaining net pay
 
At remittance:
  Debit   CT Paid Leave withholding liability   amount remitted
  Credit  Cash                                  amount remitted

Keep penalties and interest in separate employer-paid expense accounts. Do not use employee deductions to pay a late-filing penalty or interest charge. A separate account makes it visible that the business absorbed the compliance cost instead of reducing a worker’s statutory deduction.

Worked example: finding a doubled deduction​

Suppose a small employer’s capped subject-wage report for Q2 contains $160,000 across its employees. The correct contribution is:

$160,000 × 0.005 = $800

The payroll provider was configured at 1%, so the payroll register shows $1,600 withheld. The employer has two separate issues:

1. Employees were over-withheld by $800.
2. The payroll liability and the amount sent to the Authority may be overstated by $800 if the provider used the same setting for the quarterly return.

First, freeze the supporting payroll report and correct the rate before the next run. Then split the $800 difference by employee and pay date. The employer should not simply net the amount against a future quarter: the Authority says overpayments cannot be applied to a future pay period or cancelled.

If the employer overpaid the Authority, use the applicable amended-return or employer-refund process and identify the business, FEIN, quarter, and amount. If the employee’s paycheck deduction was too high, preserve the employee-level calculation and follow the Authority’s process for an employee contribution overpayment. Those are related but distinct records; one is a state-account refund and the other is a payroll correction owed to workers.

What to do when the result is an underpayment or duplicate payment​

An underpayment caused by underreported wages should be corrected as soon as possible, preferably in the same quarter. The Authority’s online guidance describes reporting the missing wages for the relevant pay period and remitting the additional 0.5% contribution. Some employers instead refile the full quarter and then request a refund of the original amount; choose the path that matches the portal instructions and your records.

For an overpayment caused by reported wages or contribution amount, an amended return can generally correct those fields. Employee counts may also be amendable. Other items, such as certain account, period, or employer-identity changes, may require a manual request.

A duplicate payment is not a credit to carry casually into the next quarter. Preserve both invoice numbers, amounts, payment traces, and the quarter they were meant to cover, then request help or a refund through the Authority’s stated channel. Keep the receivable separate in your ledger until the refund is actually approved and received.

The mistakes to prevent at the next payroll close​

Use this short checklist:

• Verify the rate is 0.5%, not 1% or another state’s paid-leave rate.
• Confirm the 2026 wage-base setting is $184,500 and that the cap is tracked year to date per employee and employer.
• Review wage-code mappings for bonuses, tips, commissions, severance, vacation, holidays, and taxable in-kind payments.
• Reconcile employee deductions, capped subject wages, expected contribution, reported contribution, and cash paid.
• Save completed invoice and payment evidence from the Authority portal.
• Keep refunds, amended returns, penalties, and interest in separately labeled accounts.
• Have someone besides the payroll preparer review the quarterly filing and payment status.

This process turns a percentage deduction into an auditable control. It also gives you a defensible answer when an employee asks why the deduction stopped, why a bonus changed the amount, or why a refund is still shown as a receivable.

Simplify Your Financial Management​

Payroll compliance is easier when every deduction, liability, remittance, and correction has a clear trail. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready, so you can review the numbers without being locked inside a black-box payroll export.