Outsourced CompanyPowered by StealthAgents

Philippines staffing research · Published · Updated

How recurring journal entry approvals shape an outsourced accounting close

A recurring entry is an estimate that repeats until someone tests it. Approval design decides whether the close carries current evidence or last month's assumptions.

An accounting reviewer comparing a recurring journal entry with its supporting schedule

Research findings

A recurring journal entry is a standing estimate, and its repetition makes it feel like a fact. Rent, depreciation, accruals, and allocations are booked on a schedule because the underlying event is predictable, not because the amount is exact. The approval step exists to test the estimate against current evidence. When the step becomes a rubber stamp, the close inherits last month's assumptions. A short test at each close is enough to reveal whether the review still has teeth, and it costs less than a full rebuild.

The preparer should not be the only reviewer. Even in a small finance team, a second person should see the support and the amount before the entry posts. That person does not need to rebuild the calculation, but should confirm the basis, the period, and the account. A name on the approval line is not evidence that anyone looked. Ask the reviewer to note the support checked and any question resolved, even when the answer is that nothing changed.

Support should travel with the entry. A recurring entry without a schedule, a contract, or a calculation is a number with a memory attached. Attach the current support to the entry template and date it. If the support changed, the entry should change or the reviewer should record why it did not. Store the old support beside the new version so the reviewer can see what moved.

Approval thresholds should follow risk, not habit. A small allocation may need one reviewer, while a large accrual or an entry touching a covenant metric may need a second. Write the threshold in the close calendar. A threshold that nobody can state from memory is not a control. Keep the threshold in the close calendar and review it when the client's risk profile changes.

Timing matters as much as amount. An entry posted after the close cutoff lands in the wrong period and distorts two months at once. Record the cutoff and the actual post time. If the entry must be late, the client's controller should decide whether to accrue or reverse. Record that decision in the close file with the date and the owner.

Reversals need their own review. An automatic reversal can clear an accrual that the next period still needs, or leave a balance that nobody owns. Tie the reversal to the original entry and check that the next period's estimate reflects the change. A reversal that runs on a schedule without review is an assumption with a timer. Review the reversal list each period before the entries post.

Discussion

Version control protects the close from quiet edits. Keep the approved version, the support version, and the posted version linked. If someone changes the amount after approval, the change needs a new approval. A file name that says final is not version control. A version number, a date, and an approver are more useful than another folder. Name the approver in the file, not only in the email that carried it.

Segregation of duties is harder in a small team, and the desk should say so rather than pretend. If the same person prepares and posts, add a compensating review by the client's controller. Record the compensating control and the sample tested. The goal is a visible control, not a perfect org chart. The compensating review should be written down and sampled like any other control.

The audit trail should show who prepared, who reviewed, what changed, and when it posted. Export the trail before the system closes the period, because some tools hide the detail afterward. Keep the export with the close file. A trail that only exists in the tool is a trail the client may not be able to produce. Save the export in a format the client can open without the accounting tool.

Implications and limits

Measure the approval cycle, not only the entry count. Track how many entries wait for review, how often support is missing, and how many are corrected after posting. Those numbers show where the close slows down. A fast close with repeated corrections is not a controlled close. Report the correction count beside the close date so speed and quality are read together.

Test a sample each quarter by rebuilding the entry from support. Choose one recurring and one adjusted entry. Compare the rebuilt amount with the posted amount and record the difference. The test is not about catching a person; it is about whether the support still explains the number. Keep the rebuild note with the sample so the next test starts from the same evidence.

No approval process can make an estimate exact. It can make the basis visible, the reviewer accountable, and the change explainable. State that limit in the close memo instead of implying precision. A modest claim that matches the method survives an audit better than a confident one that does not. The close memo should say what the approval does and does not prove.

Map the recurring entry inventory

Start with the trial balance and the prior close file, not with the names people remember. List every entry that posts on a schedule, including the small allocations that rarely attract attention. Record the account, the amount basis, the preparer, the reviewer, and the support location. A complete inventory is the first control, because an entry that is not listed is not reviewed. Reconcile the inventory with the trial balance at each quarter end.

Group the entries by risk: size, judgment, covenant impact, and proximity to cash. A large accrual that depends on an estimate needs more evidence than a fixed depreciation line. Use the groups to set review depth, not to skip the review. Revisit the map when the client changes an accounting system or adds an entity. The map should name who owns each entry and who reviews it.

Set approval evidence by risk

Define what the reviewer must see for each risk group. For a low-risk entry, the schedule and the prior amount may be enough. For a high-risk entry, the reviewer should see the calculation, the source document, and the reason for any change. Write the requirement beside the entry in the close calendar so the preparer can assemble it once. A requirement added after the close starts is a sign the calendar is incomplete.

Keep the approval evidence with the entry, not in a separate email folder. A reviewer's reply that says looks good does not show what was reviewed. Ask for a short note that names the support checked and any question resolved. The note can be two sentences, but it must point to the record. Store the note with the entry rather than in a separate approval mailbox.

Test one close cycle end to end

Choose a closed period and follow five entries from support to posting. Confirm that the support existed before the approval, that the reviewer saw the current version, and that the posted amount matches the approved amount. Record every break in the chain, even when the final number is correct. A correct number reached through an untraceable path is still weak evidence. The path matters because an auditor may test the path rather than the total.

Repeat the test with one entry that changed during the close. Look for the new approval and the reason for the change. If the change was verbal, write down who gave it and when. The test should end with a short list of fixes, not a score. A close that cannot survive five entries will not survive an audit sample. Fix the first break before adding more entries to the test.

Handle reversals and changes

List the automatic reversals and the entries that depend on them. Confirm that the reversal date, the amount, and the account match the original entry. Check the next period to see whether the balance cleared or whether a new estimate replaced it. An unowned balance after a reversal is a finding waiting to be discovered. Assign the balance to a person and a date before the next close begins.

When an entry changes after approval, require a new approval rather than an edited note. Record the old amount, the new amount, and the reason. If the change happens after posting, the client's controller should decide whether to adjust or reverse. The desk can prepare the correction, but the decision stays with the owner. The record should show the question asked and the answer received.

Questions

Does every recurring entry need a second reviewer?

Not every entry, but every entry needs a review level set by risk. Large or judgment-heavy entries should have a second reviewer even in a small team.

What counts as support for a recurring entry?

The schedule, contract, calculation, or approved estimate that explains the amount. It should be dated and linked to the entry.

Can the preparer also post the entry?

In a small team it may happen, but the client should add a compensating review. Record the control and test it.

How should a post-close change be handled?

With a new approval and a recorded reason. The client's controller decides whether to adjust or reverse the entry.

Philippines staffing intake

Define the position before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us