How to track intermittent FMLA hours and leave balances in your leave software

Last verified: October 15, 2026

Key takeaways

• An intermittent absence uses a share of the otherwise-scheduled workweek, so each employee's hourly equivalent depends on their schedule.
• A reproducible balance needs dated event debits and their schedule basis stored alongside the running total.
• The leave-year window determines which designated absences reduce availability on an assessment date.
• Designation is the employer's decision. A payroll code or a source system's leave type records it at most.
• The working ledger sits alongside required records and separate confidential medical files.
• Data synced from an HRIS supplies the inputs; your ledger performs the FMLA accounting.

A running total cannot explain an intermittent FMLA balance. It only shows what someone entered.

Without an absence's schedule basis, its debit can't be reproduced. The balance can also be wrong if the leave-year window is wrong, even when every debit is right. Track each absence as an event, calculate availability under the employer's selected method, and retain the communications and records that explain the result.

This guide is for teams building FMLA tracking into leave, absence, or benefits software, where intermittent absences arrive from timekeeping, HRIS, and payroll data. It covers ordinary FMLA accounting. Eligibility and specialized employee-group rules are out of scope.

Calculate the debit for each absence

Calculate intermittent FMLA usage as the portion of the employee's otherwise-scheduled workweek missed for a qualifying reason. Under DOL's rules in 29 CFR Part 825, ordinary entitlement is generally 12 workweeks, measured against each employee's own schedule. An equitable hourly equivalent works when the schedule is stable; otherwise, store the workweek basis behind the calculation.

Choose the denominator before calculating the debit:

For each absence, follow the same sequence:

1. Establish the schedule: identify the hours the employee otherwise would have worked, including normally required overtime. Unworked voluntary overtime adds no chargeable FMLA time.
2. Identify missed work: record the scheduled time missed for the qualifying reason. For partial-week leave, count a holiday only if the employee was otherwise scheduled and expected to work it; full-week leave follows a different rule.
3. Apply the accounting increment: use the shortest increment the employer applies to other forms of leave, up to a maximum of one hour. Charge only time actually missed. The regulation's physical-impossibility exception is the one case where more can be charged.
4. Calculate and retain the debit: divide chargeable missed time by the otherwise-scheduled workweek, and store both the resulting debit and its denominator basis.

For example, an employee expected to work 40 hours misses two hours of a scheduled shift. The event debits 2 ÷ 40 = 0.05 workweek. If the employee instead missed normally required overtime for the qualifying reason, that time would enter the same proportional calculation. Store why that denominator applied, or the debit can't be checked later.

Preserve an event ledger that can reproduce the balance

A working ledger preserves the calculation's inputs, its result, and any later correction. Treat the table below as a data model for your product. It is a recommended operational design; the regulation prescribes no form, and the full records package is covered later.

A single absence event in that model might look like this:

{
  "event_id": "fmla-evt-20261014-0042",
  "employee_id": "emp-1187",
  "case_ref": "case-2026-031",
  "absence_date": "2026-10-14",
  "missed_scheduled_hours": 2,
  "denominator": {
    "basis": "stable_schedule",
    "scheduled_weekly_hours": 40
  },
  "debit_workweeks": 0.05,
  "designation_status": "designated",
  "source": {
    "system": "hris",
    "record_id": "",
    "request_type": "FMLA",
    "units": "HOURS",
    "amount": 2
  },
  "corrects_event_id": null
}

Keep a case reference so you can trace an absence to its supporting workflow, and key entitlement on the employee, since qualifying reasons share one entitlement. A correction points to the event it changes, so it reads as a correction and never as an extra absence.

The ledger answers what happened to each debit. The leave-year method answers which of those debits belong in today's balance.

Apply the leave-year method to the recorded events

An employee's remaining entitlement depends on the employer's selected leave-year method and the assessment date. DOL Fact Sheet #28H describes the four ordinary methods: calendar year, another fixed year, measured forward, and rolling backward. Qualifying reasons draw on the employee's shared entitlement, so aggregate relevant designated events across case references.

Calculate a dated balance in this order:

1. Select the policy window: read the employee's established method and its applicable boundaries. A calendar year is only correct when it is the employer's method.
2. Select recorded events: include the employee's designated events within that window, across cases. Use each event's stored debit, and leave old absences calculated against the schedule that applied at the time.
3. Calculate availability: sum included usage in a consistent unit and subtract it from the established entitlement. Store the assessment date and included-event references with the result.
4. Test a proposed absence: show availability before posting it, including any other entries already recorded on the assessment date. Then post the proposed event once and calculate the resulting balance.

For a rolling-backward assessment, DOL's example includes the assessment date and excludes the same calendar date one year earlier. An older event restores availability as it leaves the window, one event at a time. Use those calendar boundaries in your date logic, since a fixed count of days drifts across leap years.

Test the calculation for employee isolation, each boundary, returning availability, duplicate entries, corrections, and mixed accounting units. If the employer hasn't selected a method, DOL's rule applies the one most beneficial to the employee, so your product needs an explicit "unset" state. A change of method requires at least 60 days' notice and protection of entitlement during the transition.

Explain designated usage and the remaining amount

Payroll treatment and FMLA designation answer different questions. The employer designates qualifying leave; applicable paid leave may run concurrently, and a paid-leave code or imported absence only records that. Under 29 CFR §825.300, the written designation notice is generally due within five business days after the employer has enough information, absent extenuating circumstances.

Build the required usage communications and the optional balance response as separate features:

When an employee asks how many FMLA hours remain, start with the assessed balance and show what it includes. An hourly answer carries its schedule basis; otherwise, state the remaining amount in workweeks. The explanation should reconcile to the designated events in the ledger, and to the payroll total only as a cross-check.

Keep the supporting records, with medical material separate

The working ledger is one part of the FMLA record package. 29 CFR §825.500 requires covered records to be kept for at least three years and made available to DOL, in any format.

A case reference in the ledger can point to a restricted record without copying a diagnosis or certification into the tracker. Disclosure of the separate medical material is limited: the regulation permits specified information to supervisors or managers about necessary work restrictions or accommodations, to first aid and safety personnel when appropriate for possible emergency treatment, and to officials investigating compliance.

Paragraph (f) lets an employer skip actual-hours records only for FMLA-eligible employees who are not subject to FLSA recordkeeping, provided eligibility is presumed after 12 months of employment and, for intermittent or reduced-schedule leave, the normal schedule or average weekly hours is agreed in writing. If your product supports that exemption, store the agreement as the denominator source for those employees. For deciding which fields reach which part of your system, see employee data field scoping.

Use synced HRIS data as ledger input, not as the ledger

Your product will usually learn about absences from the customer's HRIS, timekeeping, or payroll system. That data feeds the ledger; the FMLA accounting described above happens inside your product.

Through a unified API such as Bindbee, a synced Time Off record carries amount, units (HOURS or DAYS), start_time, end_time, status, and a request_type that can read FMLA. Map those onto the ledger like this:

A request_type of FMLA is the source system's leave-type label. Designation remains the employer's decision, so record it in your ledger as its own field with its own evidence.

Freshness matters for the balance you show. Bindbee syncs each connection every 24 hours by default, and the interval can be changed per connection on request. Its webhooks fire when a sync runs, with created and updated events for models such as hris.time_off. They report what the last sync found. Show the assessment date and the time of the last source read next to any balance your product displays, and recalculate when new events arrive.

A trustworthy balance comes from retained event inputs and the right policy window, with data freshness visible. For the integration work behind those inputs, see HRIS integration for leave management software and how to sync employee leave data between HRIS and payroll. To see how Bindbee can feed absence data from your customers' HRIS and payroll systems into your FMLA tracking, book a demo.

FAQ

How many hours of FMLA leave does an employee get?

The entitlement is 12 workweeks, so the hours depend on the schedule: 480 hours for a 40-hour week. For an undeterminable schedule, use the weekly average over the prior 12 months.

What is the smallest increment intermittent FMLA can be charged in?

The shortest increment the employer uses for other leave, and never more than one hour.

Does missed overtime count against FMLA?

Only overtime the employee would normally be required to work. Voluntary overtime does not count.

Which 12-month method should leave software default to?

None, silently. Support all four, and if the employer hasn't chosen one, apply the method most beneficial to the employee.

Is an HRIS leave type of "FMLA" the same as designation?

No. Designation is the employer's decision, with a written notice generally due within five business days.