P.A.Y.
My account
P.A.Y. · H.C.G.

Free learning · payroll and finance

Turn payroll results into a useful business conversation.

Explain what changed, reconcile the evidence, show the cost of the options and make the next decision clear. This guide is public. A current free profile opens the interactive worksheets and five editable HTML templates; optional email choices do not affect access.

Every example below is fictional aggregate planning. Employer tax and benefit costs are supplied amounts, not calculated tax rates. Use no real employee records, confidential employer data, bank details or identifying information. These resources do not authorize pay, funding, staffing or journal entries.

1. Build a monthly employer-cost bridge

Start with the same population, currency, date basis and earning definitions in the budget and result. Keep employee gross separate from employer costs: employee withholding and employee deductions reduce net pay; they are not another employer expense added to gross. An employer contribution is a separate cost.

Fictional month · USD
ComponentBudgetObserved scenarioDifference
Regular pay3,200 hours × $25 = $80,0003,360 hours × $26 = $87,360$7,360
Overtime pay · supplied 1.5× assumption80 hours = $3,000120 hours = $4,680$1,680
Bonus / other supplied earnings$5,000$6,500$1,500
Employee gross$88,000$98,540$10,540
Employer tax cost · supplied$6,000$6,500$500
Employer benefit cost · supplied$8,000$9,000$1,000
Total employer cost$102,000$114,040$12,040

The increase is about 11.80%. A useful bridge explains the $12,040 once: $5,500 volume, $3,320 blended-rate, $220 volume/rate interaction and $3,000 bonus, employer-tax and benefit changes. The worksheet keeps a separate premium/rounding residual when the multiplier changes or rounded components differ.

A blended-rate change can reflect pay changes, job mix, different people or effective dates. It does not establish a merit increase. Split departments, jobs and comparable populations before assigning a cause. Separate timing differences such as a bonus paid this month instead of next month from continuing changes.

Questions before explaining a variance

  • Does the period mean pay date, work date or accounting period?
  • Did the headcount, paid hours, mix or number of pay dates change?
  • Were rates and employer costs effective for the same dates?
  • Are corrections, accruals and reversals included once?

Evidence to retain

Keep the approved budget version, source extract version, population rule, effective-date logic, earning mapping and control totals. A plausible explanation still needs support. Do not label an unresolved difference “timing” without identifying when and where it reverses.

2. Connect the month, quarter and annual plan

A run rate is a starting point. Multiplying the observed $114,040 by 12 produces $1,368,480. It repeats this month's bonus and assumes the same hours, rate, employer costs and mix every month. An annual plan should instead place events in their expected months and state what remains constant.

Our annual scenario uses monthly regular pay of $87,360, OT of $4,680, supplied employer tax cost of $6,500 and benefits of $9,000. A 3% regular-pay change starts in April; an additional supplied total employer cost of $10,000 per month starts in July; a $26,000 annual bonus is paid in December. OT and supplied employer tax/benefit amounts remain constant in this exercise and need review after changes.

Explicit annual scenario · not an actual forecast
QuarterEmployer costReview focus
Q1$322,620.00Baseline assumptions and source completeness
Q2$330,482.40Regular-pay change from April
Q3$360,482.40Additional total monthly cost from July
Q4$386,482.40December bonus and continuing changes
Year$1,400,067.20$31,587.20 above straight annualization

Present a base case and a small number of alternatives. Identify which inputs are assumptions, who owns them, when they will be refreshed and how a change flows into the quarter and year. Additional monthly cost in this worksheet is a supplied total; it is not an automatically priced hire or a calculated tax burden.

3. Use headcount and capacity as different signals

Twenty-two people do not automatically supply the same capacity every month. In our example, separately documented scheduled capacity is 3,520 hours. At a supplied 90% availability assumption, modeled availability is 3,168 hours. Work demand of 3,480 hours creates a 312-hour gap.

With a chosen planning denominator of 160 hours per FTE, demand equals 21.75 planning FTE and the gap equals 1.95 planning FTE. This is a planning convention, not a legal FTE definition. It is not a recommendation to hire two people.

Before choosing an option, check skills, location, shift coverage, peak timing, leave, service expectations and the difference between productive work and paid time. Compare alternatives such as removing avoidable rework, adjusting schedules, changing priorities or adding capacity. State the cost and operational tradeoff of each; do not assume every gap can be resolved with overtime or that all people are interchangeable.

4. Write a one-page executive brief

  1. Question: What decision is needed, for which period and by when?
  2. Evidence: What changed, by how much, and which reconciled sources support it?
  3. Options and cost: What could be done, with what supplied financial and operating assumptions?
  4. Risks and unknowns: Which facts still need validation, and what happens if the assumptions change?
  5. Request, owner and date: Who decides, who acts and when will the result be reviewed?

Fictional example

Question: How should the team address the modeled 312-hour capacity gap next month?

Evidence: Employer cost is $12,040 above the comparable budget; the hours/rate bridge reconciles. Three rejected source rows remain held and must be resolved separately.

Options: Compare a scoped rework reduction, a schedule change and added capacity using separately approved cost and service assumptions. No option has been approved by this worksheet.

Request: The fictional finance owner and operations owner validate the assumptions, select an option and agree an internal decision date and follow-up measure.

Label facts, assumptions and proposals visibly. Use a chart or short bridge to answer the decision question; keep the detailed register and reconciliation available as evidence. A concise brief should make uncertainty easier to see.

5. Reconcile time → payroll → vendors → general ledger

A matching total is one control. It cannot prove that the right records, employees, effective dates and instructions reached the right destination. Follow the record population and the money.

InterfaceRequired checksException handling
Time and attendance → payrollBatch/version; worker + date + earning + segment keys; record and hour totals; approved time; deduplication; pay-period boundaries; effective rates and department mappingSeparate rejected unique records from confirmed duplicates. Identify the owner and corrected replacement; do not silently remove hours.
Payroll inputs → registerImported counts; approved separate earnings; deductions and elections; hire, leave and termination dates; reversals; gross-to-net controlsCompare source totals to accepted records. Prevent stale imports and accidental reapplication of an accepted file.
Payroll → benefit / retirement vendorSelected liability definition; employee and employer portions; eligibility/effective dates; loan repayment versus loan principal; accepted/rejected totals; acknowledgment IDAn upload or balanced export is not proof of acceptance. Reconcile vendor acknowledgments and resolve missing or rejected records.
Payroll → GLEmployee gross versus employer costs; liability and expense mapping; department/cost center; debits and credits; accounting-period rule; clearing and reversalsA balanced journal can use the wrong accounts or population. Trace the mapping, supporting subledger and posting acknowledgment.

Our fictional control example begins with 100 source time-summary rows: remove 2 confirmed duplicates and hold 3 rejected unique rows, leaving 95 accepted time rows. Add 5 separately approved earning lines for 100 processed lines. Counts across systems differ for an explicit reason.

Gross of $98,540 less supplied employee withholding of $20,000 and deductions of $5,000 gives net of $73,540. Adding only employer tax of $6,500 and employer benefits of $9,000 to gross produces the $114,040 employer-cost debit, with matching credits. A separately defined vendor liability of $14,000 has a matching acknowledgment. The three rejected rows still need resolution; none of these matching controls approves the payroll.

6. A twelve-month operating calendar

These are internal planning prompts, not statutory filing or deposit due dates. Use current official sources and the organization's reviewed calendar for legal deadlines. Repeat payroll controls throughout the year.

MonthFocusPractical task
JanuaryOpening assumptionsReconcile opening balances, approved budget versions, populations and ownership.
FebruaryRate and mixCompare effective rates and job mix; identify recurring versus one-time changes.
MarchQuarter outlookRefresh remaining-quarter assumptions and document decisions and unresolved differences.
AprilQuarter bridgeExplain the completed quarter and connect recurring changes to the annual outlook.
MayCapacityReview skills, shifts, planned leave and demand; cost alternatives without automatic staffing conclusions.
JuneMidyear assumptionsReconcile half-year actuals and refresh second-half pay, benefit and timing assumptions.
JulyInterface controlsSample source-to-target keys, duplicate handling, rejected records and vendor acknowledgments.
AugustNext-year inputsCollect approved business drivers, scenario ranges and assumption owners.
SeptemberBudget challengeTest volume, rate, mix and timing separately; identify which inputs need evidence.
OctoberYear-end preparationReconcile year-to-date populations and codes; assign correction owners before internal cutoffs.
NovemberDecision readinessConfirm open decisions, year-end scenarios, upcoming source changes and handoffs.
DecemberClose and learnDocument final bridges, unresolved items, recurring improvements and next-year opening assumptions.

7. Build the dashboard a CFO can act on

A useful quick glance answers four questions: What changed? Why? What is still unknown? What decision is needed? Agree the decision, comparable population and reporting basis with finance and operations before selecting a chart. Avoid a page of unrelated payroll counts.

Keep the executive view short

Start with total employer cost, the same-period budget variance in dollars and percent, month-end headcount, a clearly defined planning FTE, full overtime pay and worked hours, the annual outlook versus budget, and unresolved exceptions. Put source versions and an as-of date beside the view.

In the worked month above, employer cost is $114,040, or $12,040 / 11.80% over the $102,000 budget. Full OT pay is $4,680 for 120 hours and is already included in gross; do not add it again. The numbers alone do not explain why the variance happened.

Finish with an executive action

“Finance and operations will validate the hours and blended-rate bridge, resolve the three rejected rows and compare a schedule change with scoped rework reduction by the internal decision date.” Name the accountable owner, evidence needed and next review date. Separate a proposal from a decision actually made.

Choose your own reviewed escalation thresholds. This guide supplies no market benchmark, target staffing ratio or recommendation to add headcount.

Define the metric before presenting it
MetricCalculation / definitionGuardrail
Total employer costEmployee gross + employer taxes + employer benefits, using reviewed source totalsEmployee withholding and employee-funded deductions are not extra employer expense. Separate reimbursements, accruals and noncash items according to the approved accounting definition.
Dollar / percentage varianceComparable actual minus budget; difference ÷ budgetUse the same currency, population and work/pay/accounting date basis. A zero or unknown budget has no meaningful percentage denominator.
Headcount versus planning FTEMonth-end people versus productive worked hours ÷ supplied hours per FTE for that monthThis template's productive hours include OT and exclude nonproductive PTO. State the denominator; do not sum monthly headcounts or call this a statutory FTE definition.
OT cost / hoursFull OT pay already in gross, and separately supplied OT worked hoursFull pay and premium-only cost answer different questions. Label the choice. Paid leave is not worked OT in this planning view.
MTD / QTD / YTD and annual outlookSelected full-month actual; quarter/year actuals through it; annual actuals to date + forecast for remaining monthsA partial-month MTD needs a comparable budget-to-date; do not compare it silently with a full-month budget. Recompute ratios from their totals rather than averaging percentages.
Exceptions and freshnessOpen items at the reporting cutoff; source as-of date, version and ownerOpen exceptions are a point-in-time count, not a cumulative sum. Missing or stale data is unknown, not zero, and a refresh does not prove source acceptance.

Build the data path before the presentation

  1. Define the grain and ownership. Use one row per month, department or reviewed aggregate, with a stable period key, currency and population rule. Payroll owns the register/control totals; finance owns the budget, accounting mapping and forecasts; operations validates hours and drivers. Confirm these responsibilities locally.
  2. Reconcile the inputs. Trace the time/export version, payroll gross, supplied employer tax and benefits, and GL mapping. Hold rejected rows and unexplained differences. A balanced amount does not establish the correct keys, period or population.
  3. Separate inputs, calculations and display. Keep numeric types and units consistent. Use effective dates, explicit correction/reversal rules and an assumption log. Check duplicates before aggregating and retain the approved source version.
  4. Show a small trend and the decision. Pair a few cards with monthly budget/actual bars, an exception note and the next action. Provide the cost bridge and source controls behind the summary.
  5. Assign the refresh and review. Record who supplies each input, the cutoff, who refreshes, who reviews, the last successful source check and when the next review is due. Reconcile changed results before distributing them. This page installs no scheduled refresh or connector.
  6. Protect the audience. Share only the aggregate detail the decision needs. Suppress small groups under your organization's approved disclosure policy. Keep employee-level pay, bank, tax and identifying details out of executive summary exports and public tools. Review permissions on both reports and underlying sources.

Choose tools around the controlled workflow

Platform capabilities checked November 2, 2026. These are implementation options, not connected accounts or installed dashboards. P.A.Y.'s local HTML template is free; external subscriptions, permissions, connectors and administration are separate.

OptionPractical starting pointAccess and refresh reality
Excel + Power Query + PivotTablesMaintain a typed aggregate table; clean approved exports with Power Query where available; summarize by period/department in pivots and charts. Reconcile before refreshing the executive view.Basic Excel web access is free with a Microsoft account. Power Query web capabilities depend on subscription and feature support; do not assume all query tooling is included in free access. See Microsoft's PivotTable guide.
Power BIA reusable model with controlled measures, period filters, a cost bridge and a separate exception page can serve a governed reporting workflow.Free service use is for personal reporting; sharing and collaboration depend on paid licenses or qualifying capacity. A free authoring path is not a promise of free organization-wide sharing. Validate tenant permissions, refresh and capacity with your administrator.
Google Sheets + Looker Studio / Data StudioUse a controlled Sheet of monthly aggregates and a pivot table, then build a view with the Google Sheets connector.Current Google documentation calls it Data Studio, formerly Looker Studio, with no-cost reporting. Some community connectors cost money. Source credentials and report permissions can expose different data; review both. Pro/organizational administration is separate.
SmartsheetUse your organization's approved sheets, reports and dashboard workflow for source ownership, exceptions and review dates. Treat imported aggregates as a controlled snapshot until refreshed and reconciled.New Free plan enrollment is discontinued. Use an existing appropriate plan and permissions; import availability and Excel formula compatibility have limits. No account, paid plan, connector or automation is provisioned here.

Start locally with the executive dashboard HTML template below. It includes fictional monthly employer-cost cards, headcount/FTE, OT, exceptions, a budget-versus-outlook trend, and editable source/owner/as-of notes. Missing inputs remain unknown. It has no connection, upload or external script; refresh means recalculate the aggregates you entered.

Free interactive worksheets and working templates

Use the fictional starting values, then change aggregate assumptions. Nothing is uploaded or saved to your account by these worksheets. Downloads are five standalone, fillable HTML files with local calculation, print and “Save filled HTML copy” controls. They are working templates, not spreadsheets or approved financial records. Save only fictional or nonconfidential information.

Open with a current free profile. All four profile audiences are eligible. Marketing and newsletter choices are optional. Audience preview does not open personal worksheets.

Continue with the evidence

Search the official-source regulations library, use the work-organization templates, review the Year-End guide and practice a fictional workflow in the payroll technology lab. For federal employer-tax context, consult IRS Publication 15 (2026), Employer's Tax Guide. This page's supplied tax amounts do not implement those rules.