Philippines AP staffing guide

Match a posted invoice to its accrual and reversal record

Assemble invoice, service-period, accrual, reversal, and posting evidence so finance can resolve differences without AP choosing the accounting treatment.

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

Direct answer

What this role should do

Assemble invoice, service-period, accrual, reversal, and posting evidence so finance can resolve differences without AP choosing the accounting treatment.

A practical example

Start with a working record that another reviewer can follow without opening a private inbox. For an invoice arriving after finance recorded an accrual and scheduled or posted a reversal, keep the invoice, service evidence, accrual support, reversal entry, ledger detail, purchase record, and finance instruction together by stable identifiers. Finance accrued $8,000 for August services. The September invoice is $8,450 and covers the same period. AP should link both records and show the $450 difference without choosing the period or adjustment. 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 invoice, service evidence, accrual support, reversal entry, ledger detail, purchase record, and finance instruction, while the controller or designated accounting 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.

Prove the relationship before matching

Use the source record even when the queue is busy. For an invoice arriving after finance recorded an accrual and scheduled or posted a reversal, a familiar supplier name or expected amount is not enough to fill a missing field. Compare entity, supplier, service period, purchase reference, description, currency, amount, and owner across the invoice and accrual support. Record both system identifiers. 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. A similar amount and supplier are clues, not proof. One accrual may cover several invoices, and one invoice may span more than one estimate. 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.

Preserve the accounting chronology

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. List the accrual date, amount, currency, source, approver, scheduled reversal, actual reversal, invoice receipt, and invoice posting events. Keep the system timestamps. 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. Do not rewrite the invoice receipt date to fit the close period. Receipt, service, approval, and posting dates answer different questions. 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.

Explain the difference factually

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. Calculate the visible difference and identify which input changed, such as quantity, rate, tax, currency, service scope, or invoice coverage. Link the source for that input. 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 an invoice arriving after finance recorded an accrual and scheduled or posted a reversal, keep the invoice, service evidence, accrual support, reversal entry, ledger detail, purchase record, and finance instruction together by stable identifiers. If the cause is unknown, label it unknown and ask the accounting owner. AP support should not create an explanation that makes the entry reconcile. 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 the accounting decision

Start with a working record that another reviewer can follow without opening a private inbox. For an invoice arriving after finance recorded an accrual and scheduled or posted a reversal, keep the invoice, service evidence, accrual support, reversal entry, ledger detail, purchase record, and finance instruction together by stable identifiers. Provide the invoice and linked ledger facts in one packet with a narrow decision request. The controller or delegated accountant decides posting period, true-up, reversal, coding, and materiality. 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 invoice, service evidence, accrual support, reversal entry, ledger detail, purchase record, and finance instruction, while the controller or designated accounting owner answers the question that changes money, accounting, access, or supplier data. If the invoice also fails ordinary approval or match rules, keep that exception visible. An accrual does not substitute for invoice approval. For quality review, sample one ordinary item and one exception. Check whether a second reviewer can reproduce the comparison and identify the decision owner.

Close both records together

This step is preparation, not approval. The specialist can collect and compare the invoice, service evidence, accrual support, reversal entry, ledger detail, purchase record, and finance instruction, while the controller or designated accounting owner answers the question that changes money, accounting, access, or supplier data. After the owner responds, link the approved invoice posting and any journal action to the original accrual record. Record who decided and when. 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 an invoice arriving after finance recorded an accrual and scheduled or posted a reversal, a familiar supplier name or expected amount is not enough to fill a missing field. Review unmatched accruals and invoices at the next close checkpoint. Do not close the pair merely because their net balance looks reasonable. 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 controller or designated accounting 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 month end AP close support 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 month end AP close support 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 an invoice arriving after finance recorded an accrual and scheduled or posted a reversal, document the exception, maintain the queue, and send a focused question to the controller or designated accounting 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.