Philippines AP staffing guide

Control supplier self-billing and evaluated receipt invoices in AP

Connect purchase, receipt, price, generated invoice, supplier acknowledgment, and exception evidence when the buyer's system creates the payable document.

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

Direct answer

What this role should do

Connect purchase, receipt, price, generated invoice, supplier acknowledgment, and exception evidence when the buyer's system creates the payable document.

A practical example

Start with a working record that another reviewer can follow without opening a private inbox. For a self-billing or evaluated receipt process where the buyer creates the invoice record from purchasing and receiving data, keep the approved agreement, purchase order, receipt, price record, generated document, supplier response, and system audit trail together by stable identifiers. The system creates a payable for 100 received units, but the supplier says 96 shipped. AP should preserve the receipt and supplier claim, pause the four-unit difference, and route it to receiving rather than editing the quantity. 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 approved agreement, purchase order, receipt, price record, generated document, supplier response, and system audit trail, while the purchasing, tax, or finance 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.

Confirm the supplier and process scope

Use the source record even when the queue is busy. For a self-billing or evaluated receipt process where the buyer creates the invoice record from purchasing and receiving data, a familiar supplier name or expected amount is not enough to fill a missing field. Record the legal entities, supplier identifier, agreement, document type, currencies, locations, goods or services, and effective dates covered by self-billing. 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. Do not assume that every purchase from the supplier belongs in the program. Keep excluded categories and ordinary supplier invoices visible in intake rules. 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.

Trace each generated amount

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. Link the purchase line, receipt, accepted quantity, unit price, tax input, currency, and calculation used to create the document. Retain the system document number and creation time. 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 a price or receipt changed later, preserve the version used at generation. A current screen may not explain the original payable. 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.

Handle supplier documents without duplication

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. When the supplier also sends an invoice, compare it with the generated record before posting anything new. Record whether it is informational, a dispute, or outside the self-billing scope. 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 self-billing or evaluated receipt process where the buyer creates the invoice record from purchasing and receiving data, keep the approved agreement, purchase order, receipt, price record, generated document, supplier response, and system audit trail together by stable identifiers. Do not delete the supplier document as a duplicate without preserving its identifier and disposition. It may contain a price, quantity, or tax difference that needs an owner. 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.

Route receipt and price differences

Start with a working record that another reviewer can follow without opening a private inbox. For a self-billing or evaluated receipt process where the buyer creates the invoice record from purchasing and receiving data, keep the approved agreement, purchase order, receipt, price record, generated document, supplier response, and system audit trail together by stable identifiers. State the exact line, source values, amount at issue, and missing decision. Receiving owns receipt corrections; purchasing owns commercial terms; tax and finance retain their decisions. 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 approved agreement, purchase order, receipt, price record, generated document, supplier response, and system audit trail, while the purchasing, tax, or finance owner answers the question that changes money, accounting, access, or supplier data. AP support can keep the uncontested record moving only when the approved process permits it. It should never change source quantities or prices to clear a match. For quality review, sample one ordinary item and one exception. Check whether a second reviewer can reproduce the comparison and identify the decision owner.

Reconcile the supplier relationship

This step is preparation, not approval. The specialist can collect and compare the approved agreement, purchase order, receipt, price record, generated document, supplier response, and system audit trail, while the purchasing, tax, or finance owner answers the question that changes money, accounting, access, or supplier data. Compare generated documents, credits, payments, and supplier statements using stable references. Keep timing differences separate from true amount differences. 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 self-billing or evaluated receipt process where the buyer creates the invoice record from purchasing and receiving data, a familiar supplier name or expected amount is not enough to fill a missing field. Sample corrections and documents near an agreement change. Confirm that the supplier response and internal audit trail still point to the same obligation. 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 purchasing, tax, or finance 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 purchase order reconciliation 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 purchase order reconciliation 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 self-billing or evaluated receipt process where the buyer creates the invoice record from purchasing and receiving data, document the exception, maintain the queue, and send a focused question to the purchasing, tax, or finance 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.