Outsourced Philippines guide
Run a Payroll Cutoff Calendar With Named Owners
A cutoff calendar is a control, not a reminder: each input has a gate, an owner, an evidence field, and a documented exception path.
Payroll fails at the edges: a late timesheet, a missing approval, a change that arrived after the file was frozen. A cutoff calendar turns those edges into visible gates. It does not calculate pay or interpret Philippine labor rules. It makes the inputs, owners, and exceptions reviewable before the payroll owner approves the run.
Define the payroll input map
List every input the payroll owner needs: time and attendance, new hires, exits, status changes, leave, overtime, allowances, deductions, bank details, and cost center allocations. For each input, name the source system, the preparing role, the approving role, and the evidence that proves the input is complete.
Keep the map at the level of a control, not a task list. If two inputs come from the same system but have different owners or acceptance rules, list them separately. The map becomes the index for the calendar, the exception log, and the post-run review, so ambiguity here spreads everywhere else.
Questions to settle
- Is every payroll input on the map?
- Does each input have prepare and approve owners?
Set gates backward from the pay date
Start with the pay date and the bank or payment provider deadline, then work backward. Place gates for source extraction, employee change review, exception resolution, payroll calculation, independent check, approval, file release, and payment confirmation. Each gate gets a date, a time, a time zone, and an owner.
Leave a buffer between the internal approval and the external release. A calendar that ends at the last possible minute has no room for a failed file or a rejected bank batch. Publish the calendar before the cycle opens and version it when a date changes, with the reason visible to every owner.
Questions to settle
- Are gates dated with time zones?
- Is there a buffer before external release?
Name one owner per input
Shared ownership is a common source of missed cutoffs. Give each input a single accountable owner who confirms completeness, even if several people prepare parts of it. The owner signs off in the tracking record with a timestamp and a link to the evidence, not with a verbal assurance in a meeting.
Name a backup for each owner and the condition under which the backup acts. The backup needs the same access and the same instructions before the cycle starts, not after the owner is unreachable. Test the backup path at least once so the plan is not discovered to be theoretical during a live run.
Questions to settle
- Is every input owned by one person?
- Is the backup tested before the cycle?
Freeze the file and record the version
At the freeze gate, save the approved input set to a read-only location. Record the file name, version, creation time, checksum, and the person who froze it. From that moment, changes go through a correction record rather than a silent edit to the working sheet.
The correction record should show the old value, the new value, the source of the change, the reason, the approver, and whether the payroll calculation must be rerun. This is the evidence an auditor or a payroll owner needs when a payment differs from the original approval. Without it, every later question becomes a search through chat history.
Questions to settle
- Is the frozen file read-only and hashed?
- Does every post-freeze change have a record?
Route late and corrected inputs
Define what happens when an input misses its gate. The owner records the reason code, the affected employees or records, the earliest safe handling point, and the person who accepts the delay. The default is not to reopen the run; it is to decide whether the item waits for the next cycle or follows an approved off-cycle path.
Off-cycle handling needs its own owner and approval. Keep the decision with the payroll owner and, where treatment is unclear, with qualified Philippine counsel or the payroll provider. The support lane can assemble evidence and route the question, but it should not invent a rule to close a ticket.
Questions to settle
- Does each late item have a reason code and owner?
- Is off-cycle handling separately approved?
Separate preparation from approval
The person who prepares or reconciles an input should not be the only person who approves it. Build an independent check that compares the frozen input to the payroll register, samples changed records, and confirms that exception decisions are present. Record the checker, the sample, and the result.
The approval step should state what the approver reviewed, not only that the run was approved. A useful approval note names the file version, the exception count, the open items, and the decision to proceed or hold. This gives the next cycle a baseline and gives an auditor a clear authority trail.
Questions to settle
- Is there an independent check?
- Does approval name what was reviewed?
Test the calendar with a dry run
Before the first live cycle, run a dry run with representative data. Walk every gate, send every notification, freeze a test file, and produce a mock exception. The purpose is to find missing access, unclear instructions, and owners who are unavailable at the gate time.
Record what failed and fix the calendar or the access before the live date. A dry run that only tests the happy path is not enough. Include a late input, a post-freeze correction, an absent owner, and a bank file rejection so the team practices the states that cause the most damage in production.
Questions to settle
- Does the dry run include adverse cases?
- Are failures assigned and retested?
Review misses after each cycle
After the run, count inputs received on time, late, corrected after freeze, and missing at approval. Group the misses by cause: unclear request, source unavailable, owner unavailable, tool failure, or a genuine change. Report the count against the eligible inputs and the cycle window.
Assign each recurring cause to the person who can repair it. A repeated late timesheet may need a reminder and a different source owner, not more pressure on payroll. The review closes with a small number of changes, each with an owner and a date, and the next cycle tests whether they worked.
Questions to settle
- Are misses grouped by cause?
- Does each repair have an owner and date?
Sources and next steps
Continue with Philippines operations support, then confirm scope, authority, and review ownership before expanding the role.