Research brief · Published
Payroll exempt status change review
A review design for testing whether duty changes, pay practice, and written approvals stay aligned before an exempt classification affects a live pay run.

Research finding
Define the population from role and duty changes, not from the exempt employee list alone.
Methodology
This brief triangulates the headline measure against official Philippine government, regulatory, development, and labor sources. It translates evidence into an operating control and separates context from recommendations.
| Measure | Interpretation |
|---|---|
| 4 evidence gates tested for every status change. | Context signal for planning, not a promise about an individual worker or provider. |
| 4 source records | Primary source links are listed and numbered below for review. |
Key takeaways
- Define the population from role and duty changes, not from the exempt employee list alone.
- Test whether the duties evidence supports the current classification and pay practice.
- Check that a named owner and qualified adviser approved the change before payroll updated.
- Sample the first affected pay run for overtime, deductions, and reporting.
- Classify findings by the pay periods exposed and the authority that approved the change.
Question and scope
This review asks whether an exempt status change is supported by current duties, consistent pay practice, and a written approval before it reaches payroll. The scope is each role whose duties or pay basis changed during the review period. The unit is one role change for one employee or position. The design measures evidence and sequence, not the legal correctness of any classification. Results describe one employer review and are not legal advice.
Population and unit
Build the population from promotion records, reorganized departments, new approval authority, and changes to pay basis. Include roles that were reclassified in either direction and roles where the title changed without a review. For each change, record the employee, the effective date, the prior status, and the new status. A population built only from the payroll status field will miss changes that were never entered.
Duty-change triggers
List the events that should start a review, such as a promotion, a new team, added approval authority, or a shift in the primary duty. Compare the list with the changes that actually reached payroll. Look for a title change with no duty evidence and a duty change with no payroll update. The trigger list becomes the selection frame for the sample.
Classification evidence
Confirm that the file contains the current job description, a manager task list, and examples of independent decisions. Check that the duties are described with enough detail to compare against the applicable test. A generic description copied from a template is weak evidence. The reviewer should be able to see what the employee actually does each week.
Salary basis and pay practice
Test whether the pay practice matches the claimed status. Review recent pay history for deductions, partial-day treatment, and any variable pay that may conflict with the basis. Ask payroll to explain each exception. A classification can be supported on duties and still fail on the way pay is administered.
Written determination
Check that a named owner approved the change and that a qualified adviser reviewed the legal question when needed. The determination should state the effective date, the duties considered, and the conclusion. Look for a file that records who decided, not just who entered the change. An unsigned system update is a process gap even when the outcome is right.
Sequence into payroll
Compare the approval date with the date the payroll status changed. A change entered before approval breaks the control even if the conclusion is later confirmed. Check the first affected pay run for overtime treatment, deductions, and ledger coding. Record the run, the reviewer, and any correction.
Employee communication
Confirm that the employee received a clear explanation of the change and the effective date. Check that the message names a contact for questions and does not promise a result the owner has not approved. A communication sent after the first pay run creates disputes that are harder to resolve. Keep the message version with the change record.
Retroactive correction
Test what happens when a review finds that a prior status was wrong. Identify who calculates the correction, who approves it, and how it is separated from the current run. Confirm that the correction uses the same evidence and authority as the original change. An informal adjustment that skips review creates a second uncontrolled event.
Record retention
Confirm that the duty evidence, determination, pay history, communication, and first-run check are stored together. Check that the record can be retrieved after the manager or payroll preparer leaves. Test one older change for completeness. A file that exists only in a former employee's mailbox is not a retained record.
Provider handoff
When a payroll provider or outsourced specialist supports the change, confirm that the employer owner approves before the provider updates status. Compare the provider's effective date with the employer's approval date. Ask how the provider prevents an update without the signed determination. Record any case where the provider acted first and the employer approved later.
Small-team exceptions
A small payroll team may not have a separate reviewer for every change. Record the exception and the compensating check, such as an owner review of the duty evidence and first run. The compensating check should happen before release and leave its own evidence. A second signature from the same person is not an independent review.
Monitoring and sampling
Sample changes across roles, departments, and effective dates. Include a title-only change, a promotion into a lead role, and a change that reduced authority. Compare the sample result with the trigger list to see whether any change was missed. Record the selection rule so another reviewer can repeat the work.
Findings and severity
Classify each gap by the number of pay periods exposed and the authority that approved the change. A missing duty update before a live run is more severe than a documentation gap caught in review. Record the employee group, the amount at risk, and any compensating check. Severity should lead to a decision, not just a score.
Limitations
The review depends on records that may be incomplete, inconsistent, or written after the change. A manager's task list may reflect an ideal role rather than daily work, and a pay history may not show every deduction. The design cannot determine the legal status of a role. State these limits and avoid treating a clean sample as a legal opinion.
Decision and retest
Name the decision the review supports, such as adding a duty-change trigger, requiring a signed determination, or correcting a pay practice. Record the owner who accepted the finding and the date. Set a retest after the next promotion cycle and after any payroll system change. Reuse the same trigger list and evidence standard so the comparison is meaningful.
Manager attestation
Ask the manager to sign a short statement describing the duties that changed and the date of the change. The statement should name the decisions the employee can make and the people they direct. A general claim that the role is more senior is not enough. The attestation gives the reviewer a starting point and a person to question.
Job description currency
Compare the job description with the tasks the employee actually performs. Check the last review date and whether the description was updated after the reorganisation. A description that predates the change is weak evidence, even when it sounds appropriate. Record the gap and request an update before the classification decision.
Payroll system field review
Inspect the payroll status field, the pay code, and the effective date in the system. Compare them with the signed determination and the first affected pay run. Look for a change entered under a generic reason code or without a supporting document. A system field that cannot be explained is a finding even when the pay looks correct.
Communication evidence
Review the message sent to the employee and the date it was sent. Confirm that it explains the change, the effective date, and how questions will be handled. Check that it does not promise a classification outcome that the owner has not approved. Keep the message with the determination and the first-run evidence.
Quarterly trend comparison
Compare findings across quarters and departments. Look for the same step failing, such as a promotion approved after the payroll change. A repeated pattern points to a design problem in the promotion process. Record the change made after the prior review and whether it held.
Review report
Keep the report short enough for the payroll owner to act on. Show the roles tested, the evidence gaps, the sequence failures, and the decisions needed. Avoid a single compliance percentage that hides a live pay risk. Name the owner and the retest date for each finding.
Evidence sampling by role family
Sample roles from different families, such as operations, finance, and customer support. A classification process can work for one department and fail in another where managers write their own descriptions. Compare the evidence standard across the sample. The report should say whether the gap is local or systematic.
Retest after a promotion cycle
Schedule the retest soon after the next promotion cycle rather than at the end of the year. The files are still current and the managers remember the decisions. Check whether the new trigger and the signed determination were used. A timely retest shows whether the fix changed behavior.
Decision log
Keep a short log of every review decision, the owner, the date, and the evidence reference. The log lets a new reviewer see the history without opening every file. It also shows whether the same role has been reviewed repeatedly without a stable conclusion. A decision log is a management tool, not a substitute for the evidence.
Sources
Prepare a classification change evidence pack
A Philippines-based payroll support specialist can maintain the duty-change trigger list, collect job descriptions, pay history, and approval records, and flag a status update that happened before the signed determination. The specialist can also prepare the first-run check and the sample log for owner review. Your payroll owner and qualified adviser still decide the classification, approve the change, and sign the review conclusion.
Review payroll reporting supportFAQs
Does this review decide whether a role is exempt?
No. It tests whether the employer has current evidence, a written decision, and a consistent sequence. The legal determination belongs to the employer with qualified advice. A clean review is not a legal opinion.
How many role changes should be sampled?
Start with every change in the most recent quarter and add older changes from different departments. Include at least one title-only change and one change that reduced authority. Keep the selection rule so the sample can be repeated.
What if the employee was classified correctly but the file is thin?
Record a documentation finding and set a date to complete the evidence. A correct outcome without support still leaves the employer unable to explain the decision later. Repair the file before the next review cycle.
For adjacent operating context, see Payroll Preparation and the payroll operations guide library.