Philippines AP staffing guide

Route intercompany invoices without treating them like vendor bills

Identify both legal entities, agreement, service period, coding owner, and settlement path before an intercompany charge enters the ordinary AP queue.

Published: September 22, 2026 · 12 minute read · Philippines-only staffing

Route intercompany invoices without treating them like vendor bills illustration

Direct answer

What this role should do

Identify both legal entities, agreement, service period, coding owner, and settlement path before an intercompany charge enters the ordinary AP queue.

A practical AP example

For a charge sent by one group company to another company entity, begin with a record that a second reviewer can reproduce. Keep the invoice, entity directory, intercompany agreement, allocation support, service-period evidence, coding instruction, and settlement record linked by stable identifiers rather than relying on an email subject or a familiar supplier name. A parent company bills shared software costs to three subsidiaries. The invoice names the group brand but not the receiving legal entity, so AP should not choose one from the email recipient list. Keep the original value after any correction and link the person, time, reason, and controlled source for the new value. That history supports duplicate review and later reconciliation.

The outsourced specialist prepares and compares evidence; the intercompany accounting or finance owner makes the decision that changes money, accounting, access, tax treatment, or supplier data. Write that boundary into the queue and the procedure. Before the first item enters the queue, agree on the authoritative sources, required fields, stop conditions, permitted system actions, and employee owners. Use examples from the real company workflow and keep the approved procedure beside the work record. The queue entry should end with a current status, named next owner, due or review date, and source link. “Handled” is not a useful close state without evidence.

Confirm both sides of the transaction

Dates need labels and timezones. Record when the source was issued, received, reviewed, approved, and changed so a later reviewer can distinguish sequence from assumption. Capture the issuing and receiving legal names, entity codes, addresses, tax identifiers when applicable, currency, and document reference. A shared brand is not an entity decision. Quality review should sample one ordinary record and one exception. A reviewer should be able to repeat the comparison without asking the processor to reconstruct it from memory.

State the exception in plain language: what one source says, what another source says, the amount or record affected, and the specific owner response needed. Write down the source reference and what the processor observed. If the records conflict, the item stays in the exception queue with the owner who can resolve it. Do not borrow a value from a prior transaction merely because the source is incomplete. Flag the gap and preserve the supplier’s actual document.

Link the charge to its governing record

State the exception in plain language: what one source says, what another source says, the amount or record affected, and the specific owner response needed. Attach the current agreement or approved allocation instruction and its effective period. Flag a missing schedule instead of repeating last month’s percentage. Do not borrow a value from a prior transaction merely because the source is incomplete. Flag the gap and preserve the supplier’s actual document.

Use least-privilege access for this task. A support role should see and change only the fields required to prepare the packet, while approval and release remain with authorized employees. Keep the proposed next action beside the evidence. Missing access or a missing document is a work status, not a reason to push the item into the next step. Keep the original value after any correction and link the person, time, reason, and controlled source for the new value. That history supports duplicate review and later reconciliation.

Separate allocation from arithmetic

Use least-privilege access for this task. A support role should see and change only the fields required to prepare the packet, while approval and release remain with authorized employees. Recalculate the stated allocation and total while preserving the source basis. Finance decides whether the basis and accounting treatment are appropriate. Keep the original value after any correction and link the person, time, reason, and controlled source for the new value. That history supports duplicate review and later reconciliation.

If a message introduces a new link, contact, bank detail, or urgent instruction, stop and use the company security route. Details from the same message are not independent verification. A short note should let the owner see the affected record and answer the question without reopening the whole history. Link the source rather than copying an unlabeled value. The queue entry should end with a current status, named next owner, due or review date, and source link. “Handled” is not a useful close state without evidence.

Keep service period visible

If a message introduces a new link, contact, bank detail, or urgent instruction, stop and use the company security route. Details from the same message are not independent verification. Record the stated service dates, invoice date, receipt date, and proposed posting period separately. Do not turn invoice timing into a close conclusion. The queue entry should end with a current status, named next owner, due or review date, and source link. “Handled” is not a useful close state without evidence.

For a charge sent by one group company to another company entity, begin with a record that a second reviewer can reproduce. Keep the invoice, entity directory, intercompany agreement, allocation support, service-period evidence, coding instruction, and settlement record linked by stable identifiers rather than relying on an email subject or a familiar supplier name. Record who may authorize the next move. Until that response arrives, keep the item visible and preserve the last confirmed state. Quality review should sample one ordinary record and one exception. A reviewer should be able to repeat the comparison without asking the processor to reconstruct it from memory.

Use the designated workflow

For a charge sent by one group company to another company entity, begin with a record that a second reviewer can reproduce. Keep the invoice, entity directory, intercompany agreement, allocation support, service-period evidence, coding instruction, and settlement record linked by stable identifiers rather than relying on an email subject or a familiar supplier name. Route the packet through the intercompany owner and system path rather than a vendor-master shortcut. Keep settlement approval and journal authority with employees. Quality review should sample one ordinary record and one exception. A reviewer should be able to repeat the comparison without asking the processor to reconstruct it from memory.

The outsourced specialist prepares and compares evidence; the intercompany accounting or finance owner makes the decision that changes money, accounting, access, tax treatment, or supplier data. Write that boundary into the queue and the procedure. Use the queue status that describes the actual stop. The processor should not mark the record complete simply because the preparation work is finished. Do not borrow a value from a prior transaction merely because the source is incomplete. Flag the gap and preserve the supplier’s actual document.

Reconcile both entity records

The outsourced specialist prepares and compares evidence; the intercompany accounting or finance owner makes the decision that changes money, accounting, access, tax treatment, or supplier data. Write that boundary into the queue and the procedure. Link the receiving entry, issuing entry, dispute, credit, and settlement identifiers where access permits. Escalate unmatched values without editing the other entity’s record. Do not borrow a value from a prior transaction merely because the source is incomplete. Flag the gap and preserve the supplier’s actual document.

Dates need labels and timezones. Record when the source was issued, received, reviewed, approved, and changed so a later reviewer can distinguish sequence from assumption. Before handoff, check the identifier, amount or quantity at issue, source date, and owner. Those details prevent a general reply from being mistaken for a decision. Keep the original value after any correction and link the person, time, reason, and controlled source for the new value. That history supports duplicate review and later reconciliation.

Start the routine with a controlled sample

State the exception in plain language: what one source says, what another source says, the amount or record affected, and the specific owner response needed. Choose a small set that includes ordinary records and at least two realistic exceptions. Review every packet with the intercompany accounting or finance owner, correct unclear fields and escalation wording, and confirm that each status has a defined meaning before volume increases. The queue entry should end with a current status, named next owner, due or review date, and source link. “Handled” is not a useful close state without evidence.

Use least-privilege access for this task. A support role should see and change only the fields required to prepare the packet, while approval and release remain with authorized employees. Track completion from the underlying record, not the number of emails sent or fields touched. Useful measures include aged unresolved items, packets returned for missing evidence, confirmed duplicate paths, and owner response time, provided the company defines each measure and its source. Quality review should sample one ordinary record and one exception. A reviewer should be able to repeat the comparison without asking the processor to reconstruct it from memory.

Turn the control into a scoped handoff

If a message introduces a new link, contact, bank detail, or urgent instruction, stop and use the company security route. Details from the same message are not independent verification. Document intake channels, expected volume, busy periods, system access, review cadence, retention rules, and coverage when an owner is away. The invoice data capture service page can help frame the work lane without transferring company decisions to the support role. Do not borrow a value from a prior transaction merely because the source is incomplete. Flag the gap and preserve the supplier’s actual document.

For a charge sent by one group company to another company entity, begin with a record that a second reviewer can reproduce. Keep the invoice, entity directory, intercompany agreement, allocation support, service-period evidence, coding instruction, and settlement record linked by stable identifiers rather than relying on an email subject or a familiar supplier name. Use the contact and scoping page when the lane is stable enough to describe with real inputs and outputs. A narrow, reviewable handoff is safer to train and improve than a promise to “handle AP” without sources, owners, or stop conditions. Keep the original value after any correction and link the person, time, reason, and controlled source for the new value. That history supports duplicate review and later reconciliation.

Continue with invoice data capture and the contact and scoping page.

Review the packet before handoff

Original source and stable identifiers retained
Conflict or missing evidence stated plainly
Authorized employee owner named
Status, next action, and review date recorded
Approval, master-data authorization, and payment release kept with the company

Common questions

Accounts payable virtual assistant FAQs

What can an outsourced AP specialist prepare?

The specialist can collect and compare the invoice, entity directory, intercompany agreement, allocation support, service-period evidence, coding instruction, and settlement record, document the exception, maintain the queue, and send a focused question to the intercompany accounting 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 begin?

Start with a small controlled sample, review routine and exception cases, and expand only after the sources, statuses, owners, 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 supporting limited access for AP systems and mailboxes.
CISA: Recognize and Report PhishingCurrent government guidance supporting independent handling of suspicious payment and message requests.
IRS: About Form W-9First-party description of a common U.S. supplier tax document; tax judgments remain with the company.

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