Philippines bookkeeper accounts payable controls
A Philippines bookkeeper can prepare bills and keep the approval trail clean. The owner or finance lead should still control vendor changes, invoice approval, exceptions, and payment release.
Published 2026-07-25 · 12 minute readThe short answer
- Let the bookkeeper collect, check, enter, route, and reconcile bills, but do not give one person end-to-end payment control.
- Confirm every vendor bank change through a known contact path that did not come from the change request.
- Keep one exception log so missing proof, duplicates, tax questions, and approval holds stay visible until a named owner decides.
The job is preparation, not payment control
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.
Why a clean approval trail matters
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.
Set the role before sharing the inbox
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.
Build an invoice intake rule
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.
Check the bill before data entry
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.
Treat vendor bank changes as a separate event
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.
Keep invoice approval outside the bookkeeping role
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.
Use a two-step payment handoff
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.
Give exceptions one visible home
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.
Review the controls every week
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.
Run a controlled first week
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.
Use questions that reveal judgment
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.
Measure the work without rewarding shortcuts
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.
Accounts payable control board
This board assigns the daily work to the Philippines bookkeeper and keeps final decisions with the business. Adapt the evidence fields to the accounting system, bank, and approval policy already in use.
| Step | Bookkeeper action | Required proof | Owner control |
|---|---|---|---|
| Invoice intake | Log the bill and source channel | Original file, received date, vendor record | Set accepted intake channels |
| Duplicate check | Search vendor, number, amount, and date | Search result or duplicate flag | Decide any true exception |
| Purchase match | Compare order, receipt, and bill | Purchase and receipt references | Confirm disputed delivery or scope |
| Vendor change | Log and hold the request | Old and new details, request copy | Verify through a known contact and approve |
| Invoice approval | Route the complete packet | Named approval with date and amount | Approve or reject the bill |
| Payment preparation | Prepare a payment-ready list | Approved bill and due-date note | Check and release the payment |
| Reconciliation | Match bank result to the bill | Bank confirmation and ledger entry | Review unmatched or reversed items |
| Exception close | Record the answer and attach proof | Decision, owner, date, reason | Own the decision and any policy change |
How occupational fraud was first detected
Three leading detection methods in the ACFE 2024 studyThe AP handoff in six steps
The bookkeeper prepares and records the work. A finance owner controls approvals, changes, and release."Without the information you report to us through IC3 or your local FBI Field Office, we simply cannot piece together the puzzle of this ever-shifting threat landscape."
Questions owners ask
Can a Philippines bookkeeper approve invoices?
The bookkeeper can check and route an invoice, but approval should come from the person who owns the purchase or finance decision. Keep the named approval with the invoice packet.
Should the bookkeeper have bank access?
Read-only access can help with reconciliation when the bank supports it. Payment creation and release rights should remain limited to authorized finance owners under the company's control policy.
Who verifies a vendor bank change?
A finance owner should verify the change through a known phone number or trusted contact already on file. The bookkeeper can log the request and evidence, but should not verify it using contact details supplied in the same request.
What should happen when an invoice does not match?
Place the invoice on hold and record the exact mismatch in the exception log. The bookkeeper gathers facts, while the purchase owner or finance lead decides what to approve or correct.