Philippines bookkeeper accounts payable controls

A Philippines bookkeeper can take a large share of the daily accounts payable work when the boundaries are written down. The role can collect bills, route questions, maintain due-date notes, and prepare the reconciliation packet.

The role should not create a vendor and approve that vendor, change bank details and release a payment, or clear its own exception. Those decisions stay with the owner, controller, or another finance lead who can check the evidence and accept the business risk.

The FBI recorded 21,442 business email compromise complaints in its 2024 Internet Crime Report. Reported losses for that crime type reached $2,770,151,146, so an email that looks routine can carry a very large risk when it asks for a payment or bank change.

The same report said all 2024 complaints produced $16.6 billion in reported losses, a 33 percent increase from 2023. These are complaint figures, not a forecast for one company, but they explain why an accounts payable role needs a second set of eyes before money moves.

Start with a written list of what the bookkeeper may do in the accounting system and shared inbox. Give each task an owner, a required source document, an expected output, and a clear point where the bookkeeper must stop and ask.

Use named accounts rather than a shared password, and turn on multi-factor authentication for email and finance tools. CISA says MFA adds another layer of protection when a password is compromised, while NIST control AC-6 calls for giving users only the access needed for assigned tasks.

Send every bill to one controlled intake point, whether that is an AP inbox or an approved upload folder. The bookkeeper should record when the bill arrived, the vendor name, invoice number, invoice date, service period, amount, due date, purchase record, and the person expected to approve it.

A bill that arrives by chat, personal email, or an unfamiliar file-sharing link should move to a hold queue. The bookkeeper can ask the vendor to resend it through the normal channel, but should not make a rushed exception just because the message says it is urgent.

The first check is basic but useful: does the legal vendor name match the vendor record, and has the invoice number already been entered? Then compare the amount, quantity, tax line, purchase record, receipt of goods or services, and any approval limit that applies.

The bookkeeper should mark each check as passed, missing, or not applicable instead of relying on memory. If the bill does not match, the record stays on hold with a short note that tells the approver exactly what must be answered.

A bank-detail change should never ride through as a normal invoice update. The bookkeeper can log the request and gather the supporting record, but a finance owner should verify it by calling a known number or using a trusted contact already stored in the vendor file.

Do not use the phone number, email address, or link supplied inside the change request for that verification. After the owner approves the change, keep the old value, new value, verification date, verifier name, and evidence reference in a change log.

The person who knows the purchase should confirm that the goods or service were received and that the amount is correct. The bookkeeper can route the bill and remind the approver, but silence is not approval and an email reaction is not enough unless the written process accepts it as evidence.

Approval should name the invoice, amount, decision, date, and approver. If the approver asks for a split, credit, or account change, the bookkeeper records the instruction and keeps it with the bill so the controller can follow the history later.

After approval, the bookkeeper can prepare a payment batch or a payment-ready list without having release rights. A separate finance owner checks the payee, destination account, amount, due date, approval record, duplicate flag, and any late change before releasing funds.

The bank confirmation should return to a controlled record that the bookkeeper can use for reconciliation. This keeps preparation and release separate while still letting the offshore role finish the follow-up work and keep the books current.

An exception log stops open questions from disappearing across inboxes and chat threads. Each row should include the vendor, invoice, issue, amount, date raised, evidence link, person who must decide, due date, and current status.

Use plain status names such as waiting for vendor, waiting for approver, duplicate review, bank change hold, tax review, and ready after correction. The bookkeeper updates the facts, while the named owner records the final decision and why it was made.

A weekly review can be short if the records are clean. Look at bills entered without purchase support, changes to vendor details, duplicate warnings, overdue approvals, manual journal requests, released payments that lack a complete packet, and exceptions that have remained open too long.

The ACFE's 2024 study of 1,921 occupational fraud cases found that tips uncovered 43 percent of cases, compared with 14 percent found by internal audit and 13 percent by management review. That result does not measure one AP team, but it supports giving staff and vendors a clear way to report something that looks wrong.

On day one, explain the task boundary and show a clean invoice packet beside a held packet. On day two, let the bookkeeper process redacted examples, then compare every field and note with the reviewer before any live entry.

Days three and four can use a small live batch with no payment access and same-day review. On day five, review the exception log, fix unclear instructions, confirm access is still limited, and decide whether the bookkeeper is ready for a larger batch.

Ask the candidate what they would do if a familiar vendor sends new bank details and asks for payment that afternoon. A strong answer separates logging and evidence gathering from independent verification, owner approval, and payment release.

Then show two invoices with the same number and slightly different amounts. The candidate should pause both records, compare source documents and prior entries, write a clear exception note, and avoid choosing one without approval.

Useful checks include the share of bills with complete support, duplicate alerts resolved before entry, bank changes verified through a trusted path, exceptions with named owners, and reconciled payments linked to approval evidence. These checks show whether the process is complete without pushing the bookkeeper to clear bills too quickly.

Do not use bill volume alone as the score. A careful hold on a suspicious request is good work, even when it lowers the number of bills processed that day.