Manual month-end close cost: a worked labor model

What is the manual month-end close cost?

Manual month-end close cost is the labor and documented direct expense required to move one accounting period from open inputs to approved, closed books. The Zyphh build options framework helps compare ways to change that workflow. First, though, measure the current process without treating every calendar day as paid work.

Use active time by role. Include preparation, reconciliation, correction, review, approval, and close supervision. Exclude passive wait time unless someone is actively chasing an input or the delay creates a separate, evidenced cost.

Which work belongs inside the close boundary?

Set one start event and one finish event before timing anything. The U.S. Department of Justice's monthly close guide describes the work as reviewing, recording, and reconciling accounting information, with named responsibility for the process. For this estimate, the finish is the approved period lock and its required reporting handoff.

Keep optional board analysis and unrelated planning outside the boundary. Also separate accounting close work from a later management-reporting cycle. A wide boundary can make the cost look larger without making the model more useful.

Step 1: Capture active hours by task and role

Record active minutes for each task during one normal close and one close with meaningful exceptions. Calendar duration is not enough. A task can stay open for two days while consuming 20 minutes of work, or it can hide several hours of checks inside a single completed status.

1. Name the task, owner, reviewer, trigger, and completed state.
2. Record hands-on time, review time, correction time, and follow-up time separately.
3. Capture the systems, file versions, source links, and approvals used as evidence.
4. Mark dependencies and the reason for every blocked or reopened task.
5. Repeat the sample when volume, entity count, or quarter-end work changes materially.

Microsoft's financial period close documentation models recurring tasks with owners, due dates, dependencies, attachments, scheduled and actual completion dates, and task history. Those fields are a useful measurement blueprint even when the team uses a spreadsheet or ticket queue instead of Dynamics 365.

Step 2: Set a loaded hourly cost for each role

Use the employer's cost for the role, not take-home pay and not one blended rate for everyone. The U.S. Bureau of Labor Statistics reported that benefits were 30 percent of private-industry employer compensation in June 2026. That national average shows why salary alone can understate labor cost, but it is not a finance or SaaS benchmark.

Ask finance for an approved hourly rate or build one from annual wages, employer-paid benefits, payroll costs, and the productive-hour convention the company already uses. Add facilities or shared overhead only if the business case normally allocates it, then state that choice. Do not apply the same overhead again as a separate line.

Calculate preparers, reviewers, and approvers separately. This keeps a controller's review rate from inflating analyst preparation time and makes the model easier to update when ownership changes.

What does a worked month-end close example cost?

Consider an illustrative SaaS close with 38.75 active hours and five role or rework lines. The hours and rates below are invented to demonstrate the calculation. They do not describe Zyphh work, a client, or a typical company.

The weighted labor cost is $68.89 per active hour. At 12 closes, the same assumptions produce $32,034 in annual labor. Those are arithmetic outputs, not market benchmarks. They omit software, audit fees, policy work, and any cost that the example has not measured.

Do not call the full $32,034 a saving opportunity. A redesigned close will still need review, exception handling, maintenance, and final approval. Recovered hours are capacity unless payroll, overtime, contractor spend, or a hiring plan will actually change.

How should wait time, rework, and risk be treated?

Keep paid effort, elapsed time, and risk in different rows. Elapsed days measure speed. Active hours measure labor. Rework measures repeated effort. Risk is a possible future consequence and should not be inserted into the labor baseline without incident evidence.

• Count an hour spent chasing a missing input as labor. Do not count the following overnight wait as eight more labor hours.
• Count a reconciliation rerun once as rework. Do not also hide the same time in a generic inefficiency multiplier.
• Record late reporting as an operating delay. Monetize it only when it triggers a documented fee, overtime, credit, or other distinct consequence.
• Track post-close adjustments and reopened periods as quality measures. Price them from actual correction work and direct outlays.

Oracle's accounting period close documentation treats review and reconciliation as prerequisites to the final lock. It also warns that Quick Close marks tasks complete without running them. A faster status change is not evidence that the work or control disappeared.

Which close work should you automate first?

Start with stable, repeated work that already has an owner, a defined source, and a testable output. Good candidates include scheduled data collection, duplicate and missing-record checks, deterministic matching, task creation, reminder routing, evidence attachment, and exception queues.

The broader manual workflow cost guide explains how to add rework, delay, and risk when the evidence supports them. For the close itself, begin with one task inventory and one measured period. The first fix may be a source cutoff or ownership rule, not software.

When is the cost model ready for a decision?

The model is ready when another person can reproduce the total and see what the estimate excludes. It should name the close boundary, roles, tasks, active hours, loaded-rate source, rework, direct expenses, assumptions, and control owners.

• Finance approved the rate method and cost categories.
• The time sample includes normal work and meaningful exceptions.
• Waiting, active labor, rework, and risk remain separate.
• Each automation candidate has a source, owner, expected output, and review path.
• The comparison includes residual manual work, implementation, maintenance, and control testing.

Use the current total as a baseline, not a promise. After a change, measure the same tasks again, verify that the close remains correct, and report cash savings separately from capacity released.