Timing Differences: Accrued Wages, Pay Dates, and Remittance Schedules

Why payroll creates timing gaps

Payroll accounting often involves three different “clocks” that do not line up perfectly: (1) when employees earn wages by working, (2) when the company pays wages on a scheduled payday, and (3) when the company remits withheld taxes and benefit amounts to third parties on a separate schedule. These gaps are normal and are driven by pay cycles (weekly/biweekly/semi-monthly), processing time (approvals, timekeeping, payroll runs), and statutory remittance rules (monthly, semiweekly, etc.).

(1) Accrual vs. cash timing for payroll

Accrual timing (earn date drives expense recognition)

Under accrual accounting, wage expense is recognized in the period when employees perform the work, even if the paycheck is issued later. This is why period-end payroll accruals exist: they ensure the income statement reflects all labor costs incurred during the period and the balance sheet reflects the related liability.

• What problem the accrual solves: If a pay period crosses month-end, some days worked in Month 1 will be paid in Month 2. Without an accrual, Month 1 wage expense would be understated and Month 2 overstated.
• What the accrual represents: A liability for wages earned but not yet paid (often called Accrued Wages Payable or Wages Payable).

Cash timing (pay date drives cash movement)

Cash accounting recognizes expense when cash is paid. Even in an accrual-based system, the cash movement for payroll occurs on the pay date (or funding date), which is typically after the work is performed.

Why period-end accruals are needed

Period-end accruals are needed whenever there is a mismatch between the end of the reporting period and the end of the payroll cycle. Common triggers include:

• Monthly financial statements with weekly/biweekly payroll
• Year-end close when the last pay period ends after the fiscal year-end
• Any situation where time has been worked but not yet paid as of the reporting date

(2) Example: Accrued wages at month-end and the reversing/settlement entry

Scenario setup (pay period spans two months)

Assume:

Continue in our app.

You can listen to the audiobook with the screen off, receive a free certificate for this course, and also have access to 5,000 other free online courses.

Or continue reading below...

Download the app

• Pay period: Jan 25–Feb 7 (14 days)
• Pay date: Feb 14
• Total gross wages for the full pay period: $14,000
• Daily gross wages are even: $14,000 ÷ 14 = $1,000 per day
• Month-end: Jan 31 (employees have worked Jan 25–Jan 31 = 7 days in January)

Wages earned in January but not yet paid: 7 days × $1,000/day = $7,000.

Step 1 — Month-end accrual entry (Jan 31)

At Jan 31, recognize the portion of wages earned in January:

Jan 31  Dr Wage Expense                 7,000
        Cr Accrued Wages Payable               7,000

Ledger effect at Jan 31:

• Income statement: Wage expense increases by $7,000 in January.
• Balance sheet: A current liability (Accrued Wages Payable) increases by $7,000.
• No cash moves yet.

Step 2 — Reverse the accrual (optional but common) on Feb 1

Many organizations use reversing entries so that the upcoming payroll entry can be recorded in full without manually separating “already accrued” vs. “current period” amounts. If you use reversing entries:

Feb 1   Dr Accrued Wages Payable         7,000
        Cr Wage Expense                        7,000

What this accomplishes: It temporarily removes the January accrual from the books in February so the actual payroll entry (recorded later) can be posted normally. Net effect across January and February remains correct when both steps are considered.

Step 3 — Record payroll when paid (Feb 14) and settle the accrual

On Feb 14, the company pays the full $14,000 gross payroll for Jan 25–Feb 7. There are two common approaches depending on whether you used a reversing entry.

Approach A: Using a reversing entry (simplifies the pay-date entry)

If the Feb 1 reversal was posted, then on Feb 14 you record the payroll expense for the full pay period as usual. The earlier reversal ensures February’s net wage expense reflects only the February-earned portion.

Feb 14  Dr Wage Expense                14,000
        Cr Cash (or Payroll Cash)            14,000

Check the expense by month (with reversal):

• January: +$7,000 (accrual)
• February: −$7,000 (reversal) + $14,000 (payroll) = +$7,000

This matches the work performed: $7,000 earned in January (7 days) and $7,000 earned in February (7 days).

Approach B: No reversing entry (settlement built into the pay-date entry)

If you do not reverse, then on Feb 14 you split the pay-date entry between the portion already accrued and the portion that belongs to February:

Feb 14  Dr Accrued Wages Payable         7,000
        Dr Wage Expense                  7,000
        Cr Cash (or Payroll Cash)             14,000

Ledger effect (no reversal):

• The liability created at Jan 31 is cleared (debited) when payroll is paid.
• Only the February-earned portion hits February wage expense.

Practical checklist for period-end wage accruals

• Identify the last day worked included in the current period (e.g., Jan 31).
• Determine days/hours worked but unpaid as of period-end.
• Multiply by the applicable pay rate(s) or use a payroll estimate report.
• Post the accrual at period-end; decide whether your process uses reversing entries.
• When payroll is paid, ensure the accrual is cleared either via reversal + normal entry, or via a split settlement entry.

(3) Remittance cycle: liabilities accumulate and are later paid

Conceptual model

Remittances create a second timing gap: the company may withhold amounts from employees (and may also owe employer-side amounts) at the time payroll is recorded, but it typically pays those amounts to tax authorities and benefit providers later. This produces a “hold-and-pay” cycle:

• At payroll: liabilities are recognized (amounts owed to third parties).
• Between payroll and remittance: liabilities remain on the balance sheet and may accumulate across multiple payroll runs.
• At remittance: cash is paid and the liabilities are reduced.

Why remittance schedules differ from pay schedules

Remittance timing is often dictated by regulations or provider contracts. For example, a company might pay employees weekly but remit payroll taxes monthly, meaning four or five weekly payrolls can accumulate into one remittance payment.

What changes in the ledger during the remittance cycle

Think of remittance as a settlement of liabilities already recorded. Conceptually:

• Payroll date entry creates liabilities (e.g., Payroll Taxes Payable, Benefits Payable).
• Remittance entry reduces liabilities and reduces cash.

Example (conceptual, amounts aggregated for a month):

Remittance Date  Dr Payroll Taxes Payable      XX,XXX
                 Dr Benefits Payable            X,XXX
                 Cr Cash                               XX,XXX

Key point: Remittance does not create new expense; it pays off amounts already recognized as liabilities when payroll was recorded (or accrued, depending on timing).

(4) Timeline diagram narrative: earn date → payroll processing → pay date → remittance date

Timeline (narrative diagram)

Earn date(s) → Payroll processing → Pay date → Remittance date

Milestone 1: Earn date(s) (employees perform work)

• Business reality: Employees earn wages as they work each day/hour.
• Ledger impact: No entry is required day-by-day in most systems. However, at period-end, you may need an accrual to capture earned-but-unpaid wages.
• Typical entry at period-end (if needed): Debit wage expense; credit accrued wages payable.

Milestone 2: Payroll processing (time approval, calculation, payroll run)

• Business reality: The payroll team validates time, applies rates, and finalizes the payroll register.
• Ledger impact: Often none at the moment of processing itself. The accounting entry typically posts when payroll is finalized/posted or on pay date, depending on company policy and system integration.
• Practical note: Processing time is a major reason pay date occurs after earn dates.

Milestone 3: Pay date (employees receive net pay; company funds payroll)

• Business reality: Cash leaves the company to pay employees.
• Ledger impact: Cash decreases. Any wage accrual is settled (either directly in the pay-date entry or indirectly via a reversing entry process).
• Also happening in the ledger: Liabilities to third parties are recognized/updated for amounts that will be remitted later (taxes/benefits), creating a balance-sheet “parking place” until remittance.

Milestone 4: Remittance date (company pays tax authorities/benefit providers)

• Business reality: The company sends payments and/or files required deposits for payroll-related obligations.
• Ledger impact: Cash decreases and the related liabilities decrease. No new wage expense is created at this stage; it is a settlement of previously recorded payables.
• Practical control: Reconcile remittance payments to the liability balances and supporting payroll reports to ensure nothing is missed or duplicated.