Philippines bookkeeper month-end close controls

A Philippines bookkeeper can gather reports, update schedules, match balances, prepare proposed entries, and assemble the review file. This gives the controller or owner a cleaner packet without handing over the decisions that shape the financial statements.

The bookkeeper should not approve their own journal, decide an accounting policy, write off an old balance, reopen a locked period, or release final reports alone. Put those limits in the close checklist and in the accounting system permissions before live work starts.

List every account and close task in the order the work must happen. Each line needs a preparer, reviewer, due date, source report, expected output, proof location, and a clear point where the preparer must stop and ask.

Dependencies matter because a finished-looking schedule can still be wrong when its source is incomplete. For example, the cash tie-out waits for the final bank feed, while revenue checks may wait for processor settlements, credit notes, or a complete shipment file.

A balance is ready for review when another person can trace it from the ledger to the source without asking where the file came from. Save the report name, covered dates, run date, filter settings, account number, preparer note, and link to the supporting document.

The Internal Revenue Service says business records must clearly show income and expenses, and its examples of supporting documents include invoices, receipts, deposit information, and canceled checks. That guidance does not set a monthly close method, but it supports keeping the source records that explain the books.

Match each bank account and payment account to its statement, ledger detail, and approved reconciliation. Keep deposits in transit, outstanding checks, processor settlements, bank charges, and unknown transactions on separate lines so one net number does not hide several issues.

Read-only access is enough for most preparation work when the bank supports a named user. User setup, security resets, payee changes, transfers, and payment release should remain with authorized staff inside the business.

Review bills received after period end for goods or services that belong to the closing month, then compare customer credits, refunds, deposits, and unbilled work with the same date rule. The bookkeeper gathers the records and marks possible cut-off items instead of quietly moving dates to make a report fit.

A purchase owner or finance lead should decide disputed service dates and approve any proposed accrual, deferral, or correction. Keep the question, answer, evidence, entry, and approver together so the next close does not repeat the same debate.

The bookkeeper can update recurring schedules for prepaid costs, depreciation, payroll clearing, processor fees, or approved accruals. Each proposed journal should show the accounts, amount, period, calculation, source file, reason, preparer, and reviewer.

New estimates and unusual entries need more than a copied formula from last month. The controller or CPA should decide the accounting treatment and approve the entry before posting, especially when the change affects taxes, revenue, reserves, or prior periods.

Tie customer, vendor, payroll, inventory, and fixed-asset detail to the matching general ledger accounts that the business uses. If the two totals differ, list the exact records behind the gap rather than posting an unsupported amount to force agreement.

The bookkeeper can find duplicate records, missing batches, mapping errors, and items posted to the wrong period. A reviewer should approve corrections and check that the fix resolves the source problem instead of moving it to another account.

An exception log should show the account, amount, issue, source link, date raised, person who must answer, next action, due date, and current status. Plain labels such as waiting for statement, missing approval, mapping question, old balance review, and ready for controller make the next step easy to see.

Do not mark an item complete because someone replied in chat. The record closes only when the answer, supporting proof, approved entry or decision, reviewer name, and completion date are attached to the close file.

NIST control AC-6 calls for least privilege, which means people receive only the access needed for assigned tasks. Apply that idea with named users, limited roles, multi-factor authentication, change logs, and a separate person who can alter permissions or reopen a period.

Once the reviewer signs off, lock the period under the company's rule and keep any later change on a controlled path. The request should name the reason, affected accounts, evidence, approver, posting date, and whether reports need to be reissued.

The Association of Certified Fraud Examiners reviewed 1,921 occupational fraud cases from 138 countries and territories for its 2024 report. The cases caused more than $3.1 billion in total losses, so the study is broad evidence about investigated fraud rather than a forecast for one bookkeeping team.

The report found that lack of internal controls was the primary weakness in 32 percent of cases, override of existing controls in 19 percent, and lack of management review in 18 percent. Those findings support a close in which preparation, approval, system authority, and final review do not all sit with one person.

The final packet should include the trial balance, account reconciliations, subledger ties, journal list, variance notes, open-item report, access or period-change log, and reviewer sign-offs. The controller should also confirm that final reports agree with the approved ledger version and that unresolved items are clearly carried forward.

In the ACFE's 2024 study, 82 percent of victim organizations changed their anti-fraud controls after the fraud, and 27 percent of those changes were expected to be extremely effective at preventing similar frauds. A team does not need to wait for a loss to improve the close; it can record review findings now and change the checklist before next month.

On day one, show the close map, one approved packet, and one file with an unresolved exception. On day two, use redacted records so the bookkeeper can practice linking proof, preparing a note, and stopping at an owner-only decision.

Use a small set of live accounts for the rest of the week with same-day review and no independent journal approval. At the end of the week, check note quality, evidence links, access history, open questions, and reviewer feedback before adding more accounts.