Outsourced Philippines guide
Prepare a Thirteenth Month Input Checklist for Payroll Review
The support lane can assemble dates, coverage months, and exception evidence while payroll owners and Philippine counsel decide treatment.
Thirteenth month preparation is a payroll input problem before it is a calculation problem. The support lane can establish who was covered, for which months, with what status changes, and which records are missing. It should not decide entitlement, exclusions, or amounts. Those decisions belong to the payroll owner and, where the rule is unclear, to qualified Philippine counsel.
Write the question the checklist answers
State the purpose in one sentence: to give the payroll owner a complete, dated set of coverage and status inputs for the review period. List what the checklist will not do, including deciding entitlement, applying exclusions, or calculating an amount. This boundary keeps the preparation useful and prevents the team from practising law or payroll design.
Agree the review period, the payroll calendar version, and the employee population with the payroll owner. Record the source of the population, such as the employee master as of a stated date. A checklist built against an undefined population cannot be reconciled, and a later dispute will not show whether an employee was missed or excluded.
Questions to settle
- Is the purpose stated in one sentence?
- Is the population source and date recorded?
Fix the employee and period keys
Use the payroll employee identifier as the primary key, not a name or a chat handle. Add the legal entity, pay group, location, and cost center where the payroll owner needs them. Names can change, and duplicate names are common enough that a name based reconciliation will eventually fail.
For each employee, record the coverage start and end dates, the pay frequency, and the months included in the review. Keep the periods as explicit dates rather than labels such as first half or last quarter. A date range can be checked against the calendar; a label cannot.
Questions to settle
- Is the payroll identifier the primary key?
- Are coverage periods explicit dates?
Collect coverage month evidence
For each month in scope, record whether the employee had a paid status, the pay basis, and the source record that supports it. If the source is a payroll register, preserve the register version and the extraction date. If the source is an HR status change, preserve the effective date and the approver.
Do not collapse the year into a single total before the monthly evidence exists. A total can hide a missing month, a duplicate payment, or a period of unpaid leave. The monthly view is the audit trail that lets the payroll owner see how the total was built and where a question remains.
Questions to settle
- Does each month have a source record?
- Is the register version preserved?
Flag gaps instead of guessing treatment
Create a short reason code list for gaps: missing hire date, missing exit date, conflicting status, unpaid leave, no pay record, duplicate identifier, or source unavailable. Each flag gets the employee key, the period, the source checked, the date checked, and the owner who can resolve it.
The support lane should not fill a gap with a plausible value. A guessed hire date or leave period can change the input and create a correction later. Leave the field blank, mark the flag, and route the question. A blank field with an owner is safer than a complete looking record with an invented fact.
Questions to settle
- Does every gap have a reason code and owner?
- Are blanks left blank rather than guessed?
Record new hires, exits, and status changes
Build a separate change list for the review period: hires, exits, transfers, pay basis changes, and leave status changes. Each row needs the effective date, the old value, the new value, the source, and the approver. This list explains most of the difference between a simple headcount and the payroll population.
Check the change list against the monthly coverage evidence. A hire with no first pay record, an exit with a payment after the last working date, or a transfer with two cost centers is a question for the payroll owner. The change list makes those questions visible before the run rather than after a payslip is disputed.
Questions to settle
- Is there a dated change list?
- Are changes reconciled to monthly coverage?
Keep sensitive inputs in a restricted file
The checklist will contain identifiers, pay data, leave information, and possibly family or health related details. Store it in the approved location with named access, not in a shared drive open to the whole company. Use the minimum fields needed for the review and remove columns that the payroll owner does not require.
Record who accessed the file, why, and when access was removed. Set a retention date at creation. If the checklist is exported for review, mark the export and delete it after the review. A convenience copy is a second uncontrolled record and often the one that leaks.
Questions to settle
- Is the file in an approved location?
- Are access and retention recorded?
Route policy questions to payroll and counsel
Some questions are not data questions: whether a particular absence counts, how a status change affects the period, or which employees are in scope. Route those to the payroll owner with the facts and the source references. If the owner needs a legal interpretation, the question goes to qualified Philippine counsel through the agreed channel.
Keep a question log with the date asked, the facts provided, the answer, the person who answered, and the records affected. This log prevents the same question from being answered differently in the next cycle. It also shows an auditor that the team distinguished preparation from interpretation.
Questions to settle
- Is there a policy question log?
- Are answers attributed to an authorized owner?
Reconcile the checklist before handoff
Before sending the checklist, reconcile the row count to the employee population and the change list. Confirm that every employee has a coverage row, every flag has an owner, and every resolved flag has a source. Record the reconciliation counts and the person who performed it.
Hand off the file with a short cover note: period, population source, counts, open flags, and the decisions the payroll owner must make. Keep the checklist version and the handoff timestamp. The goal is a packet the owner can review without reopening five systems or asking the support team what a column means.
Questions to settle
- Do row counts reconcile to the population?
- Does the handoff list open decisions?
Sources and next steps
Continue with Philippines operations support, then confirm scope, authority, and review ownership before expanding the role.