Research brief · Published
Payroll suspense account clearance review
A review design for testing whether payroll suspense items are identified, owned, and cleared before the general ledger close rather than carried forward.

Research finding
Define the account purpose and the transactions it may hold.
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 |
|---|---|
| 6 clearance tests applied to every open suspense item. | 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 account purpose and the transactions it may hold.
- Reconcile the balance to the bank, payroll register, and interface files.
- Test aging, ownership, and approval for every open item.
- Trace clearing entries to supporting records and the general ledger.
- Classify findings by the value carried and the number of closes exposed.
Question and scope
This review asks whether the payroll suspense account contains only defined items and whether each item is cleared or accepted before the ledger close. The scope is every payroll-related suspense balance for the review period. The unit is one open item at one close. The design measures reconciliation evidence and clearance discipline, not the accounting policy itself. Results describe one employer review.
Population and unit
Build the population from the general ledger detail, not from the reconciliation summary. Include every debit and credit in the account, including items that net to zero. For each item, record the source, pay cycle, amount, open date, owner, and current status. A summary balance hides the old item that keeps the account open.
Account definition
Read the accounting policy and confirm which payroll transactions may use the account. Compare the policy with the items actually posted. Identify transactions that belong to an employee, tax, or funding account instead. A broad definition makes every unexplained balance look acceptable.
Reconciliation to source
Compare the account balance with the payroll register, the bank funding, and the interface files. Investigate differences in amount and timing. Confirm that a returned payment, duplicate draw, or rejected file is represented once rather than duplicated. The reconciliation should explain the balance, not just restate it.
Aging and ownership
Calculate the age of each item from its original pay cycle. Assign one accountable owner who can complete the next action. Check that the owner is not simply the person who last updated the note. An item that is reviewed every month but never cleared is still an open control gap.
Clearing evidence
Trace a sample of cleared items to the journal entry, the approval, and the supporting record. Confirm that the entry references the original item and explains the treatment. Check that a write-off has the required authority. A clearing entry without support moves the problem rather than solving it.
Funding and bank trace
Select funding differences and returned payments and match them to the bank statement and provider confirmation. Check whether a reissue or stop payment was recorded in the same period. Look for a draw that was posted twice or a return that was never reversed. The bank trace is the strongest evidence that a suspense item is real.
Interface and mapping errors
Review rejected or duplicate interface files and the correction that followed. Confirm that the source system was fixed before the suspense entry was cleared. Check whether the same mapping error appears in later cycles. A recurring interface cause points to a configuration problem, not a one-time reconciliation.
Period-close sequencing
Compare the date the item was identified with the date it was cleared or accepted. Check whether the close happened before the reconciliation was complete. Look for a journal posted after the ledger locked without a reopening record. The sequence shows whether the close depended on an unreviewed adjustment.
Segregation of duties
Map who can post to the account, prepare the reconciliation, approve a clearing entry, and release the payroll funding. Look for one person holding adjacent steps without a compensating check. Record the compensating control and the evidence it leaves. A small team may need a controller or owner review outside the payroll cycle.
Provider handoff
When a payroll provider prepares the reconciliation, confirm that the employer reviews the open items before the provider clears them. Compare the provider's clearing file with the employer's approval. Ask how a provider handles an item it cannot resolve. Record any case where the provider posted a clearing entry without employer sign-off.
Recurring balance
Compare the closing balance and item count across three periods. A stable total may hide a changing mix of old and new items. A growing total may point to a new interface or funding issue. Show the composition by age and cause so the controller can see what is actually happening.
Small-team exceptions
Record any case where the same person prepares and approves a clearing entry. Name the compensating check, such as a controller review of the journal and the supporting record before the close. The check should be documented and repeatable. State the limitation in the review report rather than treating the signature as independent.
Findings and severity
Classify each finding by the value carried, the number of closes affected, and whether the item could mask a payment or tax error. A small unexplained balance that has survived several closes may be more serious than a larger item cleared in the same period. Record the owner and the retest date.
Limitations
The review depends on ledger, bank, and payroll records that may use different reference formats or retention periods. A manually cleared item may leave only a journal note, and a provider may not share its full workpaper. The design cannot prove that every underlying payment was correct. State these limits and avoid treating a clean reconciliation as complete assurance.
Decision and retest
Name the decision the review supports, such as narrowing the account definition, adding an aging threshold, or requiring controller approval for carryforwards. Record who accepted the finding and the date. Set a retest at the next ledger close and after any payroll system or provider change. Reuse the same item list and evidence standard so the comparison is meaningful.
Opening balance confirmation
Confirm the opening balance with the prior close package before testing the current period. Reconcile the opening items to the closing items and explain every movement. A balance that rolls forward without a trace makes the current reconciliation unreliable. Record who confirmed the opening figure and when.
Materiality and threshold
Set a threshold for item-level review based on value, age, and risk. Review every item above the threshold and sample below it. Do not use a high threshold to ignore a recurring small error that affects many employees. Record the threshold and the reason for it in the workpaper.
Recurring cause analysis
Group closed items by cause, such as bank return, duplicate draw, mapping error, or timing. Count how often each cause appears and how long it takes to clear. A cause that repeats every cycle needs a process or system fix. The analysis should lead to one owner and one change.
System migration check
After a payroll or ledger migration, compare the suspense account mapping with the prior system. Test one funding cycle and one returned payment end to end. Confirm that the new interface sends the same reference fields. A migration can create new suspense items while the old ones are still open.
Quarterly trend comparison
Compare the closing balance, item count, and age profile across quarters. Look for a change in the mix even when the total is stable. Record the change made after the prior review and whether it reduced the open items. Trend comparison shows whether the control is improving or merely being documented.
Review report
Show the balance tested, the items sampled, the clearing evidence, and the carried items. Separate an accounting question from a payroll process defect. Name the owner and the retest date for each finding. A report that only restates the balance has not helped the controller decide.
Journal cut-off testing
Check whether clearing entries were posted in the period they belong to. Compare the journal date with the source event and the close calendar. A late journal can make a clean period look open and an open period look clean. Record the cut-off rule and any exception.
Sampling by item type
Sample each item type, including funding differences, returned payments, mapping errors, and manual adjustments. A control can work for one type and fail for another. Record the type and the result for each sample. The report should show where the process is strong and where it is not.
Decision log
Record each carryforward or write-off decision, the approver, the date, and the evidence. The log should show whether the same item has been accepted more than once. A repeated acceptance is a signal that the underlying cause is not being fixed. The controller can use the log to challenge the pattern.
Follow-up after the close
Revisit the carried items after the next close and confirm that the dated action happened. If an item remains open, ask whether the cause or the owner changed. Do not accept the same explanation twice without evidence. The follow-up is where the control proves it is more than a report.
Sources
Prepare a suspense clearance workpaper
A Philippines-based payroll support specialist can maintain the open item list, match funding and returns to the bank, and assemble the journal support for controller review. The specialist can also age each item and flag a carryforward without a dated action. Your controller still approves clearing entries, write-offs, and the final account treatment.
Review payroll reporting supportFAQs
Is a zero balance proof that the account is clean?
No. A zero balance can result from an offsetting error or a clearing entry posted without support. Review the item detail and the journal evidence, not only the ending total.
Who should approve a write-off?
Use the authority defined in the accounting policy, usually the controller or finance owner. The approval should reference the item, the reason, and the evidence. A payroll preparer should not write off an item they own.
How old is too old for a suspense item?
Set the threshold from the cause and the close cycle, then escalate anything that crosses it. A funding difference may clear in days, while a mapping fix may take a system release. The key is a dated plan and an owner, not a universal age.
For adjacent operating context, see Payroll Preparation and the payroll operations guide library.