Philippines AP staffing guide

Review freight accessorial charges before routing the invoice

Compare detention, liftgate, redelivery, and other accessorial charges with the shipment record instead of approving an unfamiliar line from the carrier invoice alone.

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

Direct answer

What this role should do

Compare detention, liftgate, redelivery, and other accessorial charges with the shipment record instead of approving an unfamiliar line from the carrier invoice alone.

A practical example

Start with a working record that another reviewer can follow without opening a private inbox. For a freight invoice with charges beyond the planned transportation rate, keep the carrier invoice, rate agreement, bill of lading, tender, delivery record, event timestamps, and approved exception together by stable identifiers. A carrier adds two hours of detention to a load. The packet should preserve the arrival and release timestamps, the free-time rule, the billed units, and the named logistics reviewer rather than accepting the fee because the shipment was delivered. 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 carrier invoice, rate agreement, bill of lading, tender, delivery record, event timestamps, and approved exception, while the logistics, purchasing, 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.

Classify the extra charge

Use the source record even when the queue is busy. For a freight invoice with charges beyond the planned transportation rate, a familiar supplier name or expected amount is not enough to fill a missing field. Capture the carrier wording, code, amount, currency, shipment reference, location, and event date. Map it to the company category only when the mapping is documented. 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. Keep detention, demurrage, redelivery, address correction, fuel, liftgate, and storage separate. They may depend on different records and decision owners. 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.

Rebuild the billed calculation

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. Show the rate, units, free allowance, minimum, cap, tax, and arithmetic visible in the invoice or agreement. Flag a missing input instead of selecting the value that makes the charge work. 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 rate sheet changed, retain both versions and identify which shipment or service date falls near the change. An employee decides which version governs. 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.

Connect operational events

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. Link pickup, arrival, appointment, loading, departure, delivery, and exception evidence by stable shipment identifiers. Email descriptions should not replace the controlled transport record when one exists. 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 freight invoice with charges beyond the planned transportation rate, keep the carrier invoice, rate agreement, bill of lading, tender, delivery record, event timestamps, and approved exception together by stable identifiers. When timestamps conflict, list the source and timezone for each one. Do not convert a conflict into a clean duration without owner review. 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 responsibility questions

Start with a working record that another reviewer can follow without opening a private inbox. For a freight invoice with charges beyond the planned transportation rate, keep the carrier invoice, rate agreement, bill of lading, tender, delivery record, event timestamps, and approved exception together by stable identifiers. The record can show what happened and what the contract says. It should not decide whether the carrier, warehouse, customer, or company caused the event. 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 carrier invoice, rate agreement, bill of lading, tender, delivery record, event timestamps, and approved exception, while the logistics, purchasing, or finance owner answers the question that changes money, accounting, access, or supplier data. Send one narrow question with the disputed amount and evidence gap to the logistics owner. Keep the ordinary freight amount separate if company policy permits partial processing. 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 outcomes to improve intake

This step is preparation, not approval. The specialist can collect and compare the carrier invoice, rate agreement, bill of lading, tender, delivery record, event timestamps, and approved exception, while the logistics, purchasing, or finance owner answers the question that changes money, accounting, access, or supplier data. Record whether the charge was accepted, credited, disputed, or corrected and link the authorized response. Keep supplier correspondence beside the internal decision. 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 freight invoice with charges beyond the planned transportation rate, a familiar supplier name or expected amount is not enough to fill a missing field. Review repeated charges by lane and reason, but do not claim savings from avoided charges unless the finance record supports that calculation. 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 logistics, purchasing, 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 three-way match 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 three-way match 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 a freight invoice with charges beyond the planned transportation rate, document the exception, maintain the queue, and send a focused question to the logistics, purchasing, 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.