Philippines AP staffing guide

How to track supplier prepayments before the final invoice arrives

Use a prepayment register to connect the request, approval, cash result, goods or services, and final supplier invoice without treating the advance as a routine invoice.

Published: September 18, 2026 · 11 minute read · Philippines-only staffing

Direct answer

What this role should do

Use a prepayment register to connect the request, approval, cash result, goods or services, and final supplier invoice without treating the advance as a routine invoice.

A practical example

Start with a working record that another reviewer can follow without opening a private inbox. For a supplier asking for money before the ordinary invoice or delivery cycle is complete, keep the supplier request, contract or purchase order, approval, payment record, receipt evidence, and final invoice together by stable identifiers. A packaging supplier asks for a 30% deposit on a $12,000 order. The packet should show the approved $3,600 advance, the purchase order, the bank result, and the remaining $8,400 without implying that the balance is ready to pay. If an email introduces a new link, contact, or payment instruction, stop and use the company security and verification route. Do not authenticate the request with details taken from the same message.

This step is preparation, not approval. The specialist can collect and compare the supplier request, contract or purchase order, approval, payment record, receipt evidence, and final invoice, while the finance or treasury owner answers the question that changes money, accounting, access, or supplier data. Before work begins, agree on the authoritative source, the fields the specialist may prepare, the stop conditions, and the employee who can clear each exception. Link the written rule from the queue rather than asking the processor to remember it. For quality review, sample one ordinary item and one exception. Check whether a second reviewer can reproduce the comparison and identify the decision owner.

Open a record before the payment proposal

Use the source record even when the queue is busy. For a supplier asking for money before the ordinary invoice or delivery cycle is complete, a familiar supplier name or expected amount is not enough to fill a missing field. Give the advance its own register ID and record the legal entity, supplier, currency, requested amount, percentage, due date, purpose, and source channel. Link the request to the controlled purchase record instead of relying on the email subject line. This record is also useful when the item returns weeks later. Dates, versions, and identifiers prevent the next person from rebuilding the history from memory.

Write the exception in plain terms: what the source says, what the other record says, the amount or item affected, and who must respond. Keep the earlier value after a correction. Label the request as an advance. Do not make it look like a delivered invoice merely because the accounting system needs a document number. If the system uses a placeholder, record what it is and who approved that treatment. The handoff should include a current state, a named next owner, and a review date. If a source is missing, say so instead of borrowing a value from a prior transaction.

Separate commercial approval from payment release

Write the exception in plain terms: what the source says, what the other record says, the amount or item affected, and who must respond. Keep the earlier value after a correction. The commercial owner confirms that the deposit is allowed by the agreement. Finance confirms the proposed amount and coding. Treasury or another authorized employee releases funds. An outsourced AP specialist can assemble the packet but should not collapse those decisions into one checkbox. The handoff should include a current state, a named next owner, and a review date. If a source is missing, say so instead of borrowing a value from a prior transaction.

Close the step from controlled evidence. A message saying the issue is handled should point to the approved decision or system result before the status changes. If the supplier changes bank details while requesting the deposit, move that request to the company bank verification process. The prepayment deadline does not justify using the new details before they are independently checked. Access should follow least privilege: give the support role only the systems and actions needed for this task. Approval and payment release stay with authorized company employees.

Reconcile the cash result

Close the step from controlled evidence. A message saying the issue is handled should point to the approved decision or system result before the status changes. After release, attach the controlled payment result, date, amount, currency, and reference. A submitted batch is not the same as settled cash, and a supplier acknowledgment is not a bank result. Access should follow least privilege: give the support role only the systems and actions needed for this task. Approval and payment release stay with authorized company employees.

Start with a working record that another reviewer can follow without opening a private inbox. For a supplier asking for money before the ordinary invoice or delivery cycle is complete, keep the supplier request, contract or purchase order, approval, payment record, receipt evidence, and final invoice together by stable identifiers. Keep failed, returned, or canceled attempts as separate events. Do not replace the first payment reference with the second one because that makes duplicate review much harder. If an email introduces a new link, contact, or payment instruction, stop and use the company security and verification route. Do not authenticate the request with details taken from the same message.

Match delivery and the final invoice

Start with a working record that another reviewer can follow without opening a private inbox. For a supplier asking for money before the ordinary invoice or delivery cycle is complete, keep the supplier request, contract or purchase order, approval, payment record, receipt evidence, and final invoice together by stable identifiers. When goods or services arrive, link the receipt or service confirmation without changing the original advance record. Then compare the final invoice with the purchase amount, advance, taxes, credits, and remaining balance. If an email introduces a new link, contact, or payment instruction, stop and use the company security and verification route. Do not authenticate the request with details taken from the same message.

This step is preparation, not approval. The specialist can collect and compare the supplier request, contract or purchase order, approval, payment record, receipt evidence, and final invoice, while the finance or treasury owner answers the question that changes money, accounting, access, or supplier data. Ask the designated owner about any difference. The AP specialist should not assume that a deposit is refundable, automatically deductible, or available for another order. For quality review, sample one ordinary item and one exception. Check whether a second reviewer can reproduce the comparison and identify the decision owner.

Review old advances by next action

This step is preparation, not approval. The specialist can collect and compare the supplier request, contract or purchase order, approval, payment record, receipt evidence, and final invoice, while the finance or treasury owner answers the question that changes money, accounting, access, or supplier data. Sort open advances by missing delivery, missing invoice, disputed application, refund expected, or owner review. Age alone does not explain the issue, so keep the reason beside the date. For quality review, sample one ordinary item and one exception. Check whether a second reviewer can reproduce the comparison and identify the decision owner.

Use the source record even when the queue is busy. For a supplier asking for money before the ordinary invoice or delivery cycle is complete, a familiar supplier name or expected amount is not enough to fill a missing field. Use a named owner and review date for each open item. Close the register line only when the accounting record and supporting evidence show how the advance was used or recovered. This record is also useful when the item returns weeks later. Dates, versions, and identifiers prevent the next person from rebuilding the history from memory.

Put the routine into service

Write the exception in plain terms: what the source says, what the other record says, the amount or item affected, and who must respond. Keep the earlier value after a correction. Begin with a small sample from the actual queue. Review the packet with the finance or treasury owner, correct unclear labels, and confirm that the escalation reaches someone who can answer. Add volume only after the record works for both routine items and exceptions. The handoff should include a current state, a named next owner, and a review date. If a source is missing, say so instead of borrowing a value from a prior transaction.

Close the step from controlled evidence. A message saying the issue is handled should point to the approved decision or system result before the status changes. For related implementation detail, use the payment run preparation service page to define the task boundary and the contact page to discuss a Philippines-based support role. Those pages help turn this control into a scoped handoff rather than a broad promise to handle AP. Access should follow least privilege: give the support role only the systems and actions needed for this task. Approval and payment release stay with authorized company employees.

Continue with payment run preparation and the contact and scoping page.

Review the packet before handoff

Original source and stable identifiers retained
Difference or missing evidence stated plainly
Authorized employee owner named
Status, next action, and review date recorded
Approval and payment release kept outside support scope

Common questions

Accounts payable virtual assistant FAQs

What can an outsourced AP specialist prepare?

The specialist can collect and compare the evidence for a supplier asking for money before the ordinary invoice or delivery cycle is complete, document the exception, maintain the queue, and send a focused question to the finance or treasury owner.

Which decisions stay with the company?

Company employees retain invoice approval, accounting and tax judgments, vendor master authorization, bank detail verification, access ownership, and payment release.

How should the team start?

Start with a small controlled sample, review both normal and exception cases, and expand only after the source, owner, and escalation path are clear.

Factual checks

Sources

These sources support the tax-form, access-control, and phishing guidance in this article. The planning numbers above are labeled examples and do not come from these sources.

NIST glossary: least privilegeDefinition used for limiting system access to assigned AP work.
CISA: Recognize and Report PhishingGuidance used for suspicious messages, links, and independent reporting paths.
IRS: About Form W-9First-party description of Form W-9 and its purpose.

International Labour Organization guidance on remote work arrangements reinforces why remote role briefs should document expectations, communication rhythms, and accountable handoffs.