Reconcile staffing records against budget and payroll

Implementation guide · untested

Source-supported actions are attributed evidence. Proposed steps, prompts, synthetic examples and checks are original editorial guidance; the workflow has not been run.

Why this agent / simpler alternative

Agent contribution

An agent can explain how roster, planning and pay-period records disagree, map unfamiliar column labels and produce an evidence-linked exceptions list. Deterministic joins and sums should control the arithmetic; the agent helps interpret and route exceptions.

Simpler alternative

Use a spreadsheet join or established finance reconciliation pipeline if the schemas and cost-center mapping are stable. A language model should not replace a reliable control merely to perform exact arithmetic.

Unsuitable when

The close period or employee identifiers are unclear, payroll information cannot be shared with the selected service, or the output would directly determine pay, employment status or personnel actions.

Source-supported scope

Anthropic documents a file-based reconciliation recipe, categorized differences and reuse. It does not provide an independently checked financial close.

Setup — required, optional and unknown

Required

1. Claude Cowork and a folder of roster, plan, payroll and cost-center mapping files.

2. Editorial pilot: synthetic employee IDs, one explicit reporting cutoff and a finance owner who defines headcount, FTE, contractors, vacancies and payroll-period inclusion.

3. Immutable input copies and a separate private reconciliation output folder.

4. For the local-folder route, Anthropic documents desktop-app and session conditions; verify those before choosing the test surface.

Optional

1. The Academy Finance plugin is optional.

2. Editorial addition: prior-period reconciliation, an approved loaded-cost schedule and position IDs when the budget uses vacant positions.

Unknown

1. Current connector entitlement, plan/model costs and employer payroll definitions were not established.

2. No live Workday connector is inferred from a Workday export. Gusto/NetSuite names in the recipe do not establish access to a particular tenant.

Inputs and access

1. Name

   roster

   Format

   XLSX/CSV: employee_id as text, position_id if available, cost_center, worker_type, FTE, start_date, end_date and snapshot_date

   Source or owner

   HRIS reporting owner

   Access scope

   Minimum fields for the selected period; no bank, tax, medical or national-ID fields

   Permission needed

   Employer approval to process employee data in this service; synthetic records for the first trial

2. Name

   headcount_plan

   Format

   XLSX/CSV: position_id, optional employee_id, planned_cost_center, planned_FTE, position_status, effective_dates and plan_version

   Source or owner

   FP&A plan owner

   Access scope

   Only the approved plan version and in-scope centers

   Permission needed

   Read permission; no authority to alter budget or approve hiring

3. Name

   payroll_register

   Format

   XLSX/CSV: employee_id, pay_period, posting_date, cost_center, pay_type, gross_amount, currency and line_id

   Source or owner

   Payroll/accounting owner

   Access scope

   Selected period only; pay amounts optional if the test is count-only

   Permission needed

   Specific approval for payroll-data processing; no GL posting or payment authority

4. Name

   mapping_and_policy

   Format

   CSV/text: cost-center aliases, effective dates, worker-type rules, cutoff, FTE definition and permitted join keys

   Source or owner

   Finance controller and HR owner

   Access scope

   Authoritative mappings only

   Permission needed

   Approval of the reconciliation rules; unresolved definitions go to the owner

5. Name

   prior_reconciliation

   Format

   Optional XLSX with stable exception IDs and resolution status

   Source or owner

   Close owner

   Access scope

   Prior approved period only

   Permission needed

   Read-only; no inference that last month’s resolution still applies

Documented source actions

1. 1

   Match employee and cost center.

   Input: Roster, plan, payroll and mapping

   Output: Joined comparison.

   Checkpoint: Detailed key checks unknown.

   Source: working-folder and prompt sections ↗

2. 2

   Categorize and save by cost center.

   Input: Differences

   Output: Reconciliation file.

   Checkpoint: Approval unspecified.

   Source: output prompt and scheduling sections ↗

Proposed implementation steps — unexecuted

1. 1

   Inventory versions, dates, row counts, currencies and totals. Separate roster snapshot date, employment-effective dates, pay period and posting date; choose the approved inclusion rule explicitly.

   Input: Four input tables and reporting policy

   Output: source_manifest and period-definition sheet

   Checkpoint: Do not compare a mid-month roster with a full-month payroll as if the cutoffs were identical; unresolved inclusion rules block sign-off.

2. 2

   Keep employee IDs as text, normalize only documented aliases and inspect null/duplicate keys. Aggregate multiple payroll lines per employee-period without counting each line as a separate person.

   Input: Raw tables and effective-dated cost-center map

   Output: normalized tables and rejected-key queue

   Checkpoint: Leading zeros, employee transfers and rehired IDs must remain traceable. Ambiguous maps are exceptions, not guessed replacements.

3. 3

   Join filled positions by approved identifiers. Analyze vacant plan positions separately by position_id and cost center because an unfilled role has no employee ID. Preserve unmatched rows from every source.

   Input: Normalized roster, plan and payroll

   Output: employee reconciliation and vacancy reconciliation

   Checkpoint: A balanced department total cannot hide an unplanned employee and an offsetting vacancy. Verify row conservation and join cardinality.

4. 4

   Classify unplanned hires, planned vacancies, roster-without-payroll, payroll-without-roster, cost-center conflicts and worker-type mismatches. Retain raw evidence and assign a review owner, not an employment conclusion.

   Input: Joined tables and worker-type policy

   Output: exception register with stable exception_id, source rows and proposed owner

   Checkpoint: Missing pay can reflect timing or leave; do not label fraud or terminate access. Contractor versus FTE is governed by the approved policy.

5. 5

   Roll up counts and FTE separately by cost center; reconcile payroll totals by currency. Calculate cost effects only when an approved rate, period basis and inclusion rule exist, otherwise show unknown.

   Input: Exception register and approved cost assumptions, if supplied

   Output: summary with count/FTE bridges, currency-separated sums and uncosted exceptions

   Checkpoint: Totals must reconcile to source controls. Do not annualize a partial payroll or treat every head as 1.0 FTE.

6. 6

   Create a close-review workbook or report with source manifest, normalized detail, exceptions, summary and unresolved questions. If prior data is comparable, label new/resolved/carried exceptions by stable keys.

   Input: Summary, detailed exceptions and prior approved reconciliation

   Output: private reconciliation package ready for controller and HR review

   Checkpoint: No payroll corrections, GL entries, employment decisions, emails or scheduling. The pilot is finished only when reviewers can trace every exception to inputs.

Original starter prompt — proposed

Origin

editorial_proposal

Text

Prepare a read-only reconciliation for {period} using {roster}, {plan}, {payroll} and {policy_and_mapping}. Begin with cutoff dates, row counts, identifier quality and control totals. Preserve employee IDs as text. Reconcile employee records separately from vacant plan positions. Apply only the supplied worker-type and FTE rules, retain unmatched rows, and attach source row references to every exception. Distinguish timing questions from confirmed data mismatches. Show headcount, FTE and pay totals separately; keep currencies separate and show cost impact as unknown unless {cost_assumptions} supplies the basis. Write only private drafts to {output_folder}. Do not change HR/payroll records, post journals, make personnel decisions, send data or set up recurring runs.

Placeholders

1. period

2. roster

3. plan

4. payroll

5. policy_and_mapping

6. cost_assumptions

7. output_folder

Limitations

Original proposed control-oriented prompt, not the source prompt. It cannot establish payroll correctness, employment status or accounting treatment without qualified review.

Synthetic worked example — not an agent run

Status

synthetic

Label

Invented count reconciliation demonstrating offsetting differences; no real payroll processed

Artifact url

Not specified.

Content

Period

2026-09

Fixture controls

Roster people

4

Roster employee fte

3

Roster contractors

1

Plan filled employee positions

2

Plan vacant employee positions

1

Payroll people

3

Exceptions

1. Exception id

   X1

   Subject

   E02

   Cost center

   10

   Category

   unplanned_employee

   Evidence

   roster row 3; no filled plan match

   Owner

   FP&A

2. Exception id

   X2

   Subject

   REQ05

   Cost center

   10

   Category

   planned_vacancy

   Evidence

   plan row 3; no roster position match

   Owner

   HR

3. Exception id

   X3

   Subject

   E04

   Cost center

   20

   Category

   roster_without_payroll

   Evidence

   roster row 5; no in-period pay line

   Owner

   Payroll

   Interpretation

   timing or data issue unresolved

4. Exception id

   X4

   Subject

   E03

   Cost center

   20

   Category

   worker_type_conflict

   Evidence

   roster=contractor; payroll mapping=employee

   Owner

   HR/Payroll

Summary

Planned employee FTE including vacancy = 3; actual employee FTE = 3. The net zero hides an unplanned employee and an open position.

Cost impact

Not specified.

Cost impact reason

Approved loaded-cost assumptions absent

Actions taken

None; review package only.

Costs and effort — unmeasured

Verified prices

Setup work

1. Agree on the period, FTE and vacancy definitions; document cost-center mapping with effective dates.

2. Prepare a synthetic fixture and source-control totals before any employee data is used.

Recurring work

1. Obtain approved exports and freeze their versions each close.

2. Review exceptions with HR, payroll and FP&A; retain the prior approved reconciliation and updated mapping decisions.

Unknowns

1. Platform and connector charges, export preparation time, reviewer effort and actual close-time impact were not measured.

2. A recipe estimate is not evidence of error reduction or successful accounting control.

Failure modes

1. Signal

   Payroll has several lines for one employee.

   Consequence

   A naive join inflates headcount and multiplies amounts.

2. Signal

   Vacant plan positions have no employee ID.

   Consequence

   An inner join drops the very vacancies finance needs to see.

3. Signal

   Employee 00123 is converted to number 123 or a transfer uses an obsolete center.

   Consequence

   False unmatched records or wrong departmental totals result.

4. Signal

   A worker has no pay in the selected period.

   Consequence

   Timing, leave or data latency may be misreported as an improper employee record.

Recovery steps

1. Trigger

   Control totals change after normalization or joining

   Action

   Stop interpretation; produce a row-level conservation report, isolate duplicate join keys and rebuild from immutable inputs.

   Stop condition

   Do not publish a summary until totals and row lineage reconcile.

2. Trigger

   Missing or conflicting period/mapping rules

   Action

   Send the specific rule question and affected synthetic or authorized row IDs to the designated reviewer within the private report.

   Stop condition

   Keep affected entries unresolved; do not choose a payroll policy.

3. Trigger

   Sensitive columns appear in the export

   Action

   Pause agent processing and ask the data owner to provide a minimized approved export.

   Stop condition

   No further transmission of unnecessary sensitive fields.

4. Trigger

   Unexpected formatting or workbook formula errors

   Action

   Retain flat detail and controls, rebuild the affected presentation copy and repeat total checks.

   Stop condition

   No sign-off from an unreadable or arithmetically inconsistent workbook.

Source-observed and proposed approval boundaries

Source observed

Not specified.

Editorial recommendations

1. Authorize employee/payroll data scope and service before processing real records.

2. Use private output only; HR, payroll and controller reviews are distinct from authority to make changes.

3. Any ledger entry, payroll adjustment, personnel action, shared report, new connector or recurring task requires separate authorization.

Unexecuted validation plan

Fixture

Proposed four-person fixture in output_example: E01 planned and paid; E02 unplanned and paid; E03 contractor but payroll-mapped as employee; E04 planned but unpaid; plan includes vacant REQ05. Add two pay lines for E01 and a cost-center alias without changing the expected headcount. No run performed.

Acceptance checks

1. Exactly the four named exception categories are surfaced with source rows; absence of pay is unresolved, not an allegation.

2. Three employee FTE and one contractor are reported separately; the vacancy does not disappear because employee_id is null.

3. Multiple E01 pay lines do not increase people counts or multiply totals; original IDs are preserved.

4. The plan/actual net zero is explained as offsetting differences, cost impact stays unknown, and no external records change.

Stop conditions

1. Source controls do not reconcile or join cardinality is ambiguous.

2. The agent invents a classification, rate or cutoff.

3. Unapproved sensitive data, a GL posting or a personnel action enters the workflow.

Executed

No

Limits

1. The Academy publication date is unknown and model version is unspecified.

2. No workflow was executed, no reconciliation result independently checked and no accounting conclusion established.

3. Canadian payroll and worker-classification applicability are not verified.

Guide source links

https://academy.claude.com/use-cases/headcount-reconciliation ↗
Original recipe or report; see documented_steps locators.

https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile ↗
Local folder route requires an open desktop app and supported session conditions.