Philippines AP staffing guide
Build an exchange-rate evidence packet for a foreign-currency invoice
Give finance a reproducible view of the invoice currency, rate source, effective date, conversion arithmetic, and unresolved policy questions.
Direct answer
What this role should do
An exchange-rate packet should reproduce the source invoice and conversion without asking an AP preparer to choose the accounting policy. It records the currencies, relevant dates, approved rate source, arithmetic, review owner, and final disposition in one traceable case.
Start with the decision finance must make
A foreign-currency invoice can enter the AP queue with several plausible dates and amounts. The supplier may issue it in euros, the purchase order may be denominated in dollars, and the receiving record may use the local ledger currency. Before anyone converts a figure, write down the decision that remains open. Finance may need to confirm the booking currency, select the policy date, review a variance, or decide how a later credit should be treated. The AP specialist can make those choices easier to inspect. The specialist should not make them by quietly selecting whichever rate produces the expected total.
Open one case for the invoice and retain its original file, supplier identifier, legal entity, purchase order, receipt or service evidence, invoice date, receipt timestamp, due date, currency code, gross amount, tax, freight, and any credit. Record where each field came from. An invoice image is the source for the supplier demand; it is not automatically the source for the company conversion rule. That distinction prevents a copied number in a spreadsheet from looking like an approved accounting conclusion.
Name every currency and rate source
Use ISO currency codes rather than symbols alone. A dollar sign can refer to more than one currency, and a supplier account may bill different entities in different currencies. Show the invoice currency, purchase-order currency, functional or ledger currency supplied by finance, and payment currency if it differs. If the system already stores a rate, capture the rate value, rate type, effective date, retrieval time, and system record. If a controlled external source is required, link to the exact series or table and preserve the value used. Do not replace a controlled source with the first result returned by a general web search.
The packet should also say what is missing. A rate without a date is incomplete. A date without a named policy basis is only a date. A monthly average and a spot rate answer different questions, even if their values happen to be close. AP support can present the available alternatives and calculate their effects, but the finance owner must identify the applicable policy. Once that owner answers, preserve the approval reference beside the rate instead of relying on a message that will be hard to find during close or audit review.
Reproduce the conversion without hiding rounding
Lay out the arithmetic so another reviewer can repeat it. State whether the quoted rate is foreign units per ledger unit or ledger units per foreign unit. Then show the operation, unrounded result, rounding rule supplied by the system or finance policy, and posted result. Keep line, tax, freight, withholding, and total conversions separate when the source system treats them separately. A one-cent difference may be ordinary rounding, but it still needs an explanation. A larger difference may come from a reversed rate, a different effective date, or a manual override.
Consider an invoice for 18,400 units of the supplier currency. The AP specialist should not write only the converted total. The packet needs the 18,400 source amount, the approved rate, whether the calculation multiplies or divides, the precision used, and the resulting ledger amount. If the purchase order has its own currency, add a separate comparison rather than overwriting either figure. This gives the reviewer a clean bridge between commercial commitment, supplier demand, and proposed accounting entry.
Investigate mismatches before calling them errors
A difference can come from timing, configuration, or the underlying transaction. Compare the invoice date, goods-receipt date, service period, system receipt timestamp, posting date, and proposed payment date. Check whether the purchase order was amended, whether the supplier rebilled in another currency, and whether tax or freight uses a different basis. Also inspect earlier invoices from the same agreement, but treat them as history rather than authority. A prior posting can reveal a pattern while still being wrong for the current invoice.
Route each unresolved point as one answerable question. Ask finance which date and rate type apply. Ask purchasing whether the order currency changed. Ask the business owner whether the service period is correct. Ask the supplier for a corrected invoice if the currency conflicts with the agreement. Avoid a vague status such as "FX issue." A useful queue entry names the conflicting fields, affected amount, evidence already checked, decision owner, and next review date. The packet then supports progress instead of becoming another attachment nobody can interpret.
Keep corrections and settlement evidence connected
Do not erase the first calculation when finance changes the selected basis. Retain the original result, revised result, reason, approver, and timestamp. Link a corrected invoice or credit memo to the same case and show which amount it replaces. When the invoice later enters a payment proposal, compare the approved invoice currency and payment currency with the proposal. Treasury still owns settlement and payment release. The AP packet helps treasury spot an unexpected conversion or currency change before funds move.
Close the case only when the final posting, approval, and subsequent payment or credit treatment can be traced. Record the selected rate source and date, final arithmetic, system document number, residual variance, and owner of any remaining item. Reconcile the posted amount back to the approved packet rather than assuming that successful posting proves the chosen inputs were used. If a later revaluation or settlement entry changes the ledger amount, link that event without rewriting the invoice review. For an outsourced AP role, test the process on a normal invoice, a reversed quote, a missing policy date, and a supplier correction. If a backup reviewer can reproduce each outcome without private chat history, the handoff is ready for routine use.
Continue with invoice data capture and the scope an AP support handoff.
Check the packet before finance review
- Original invoice and related order remain unchanged
- Every currency uses an explicit code
- Rate value, type, source, date, and retrieval time are recorded
- Conversion direction and rounding can be reproduced
- Policy choices and posting approval remain with finance
- Corrections retain the earlier calculation and reason
Common questions
Accounts payable virtual assistant FAQs
Can outsourced AP support choose the exchange rate?
The support role can retrieve an approved rate, reproduce arithmetic, and flag differences. Finance should define the rate source, rate type, policy date, rounding, and accounting treatment.
Which dates belong in the packet?
Keep the invoice date, receipt timestamp, goods or service date, posting date, due date, proposed payment date, and the effective date of the rate. Finance decides which date controls the booking.
How should a corrected conversion be documented?
Retain the first calculation, the revised calculation, the reason for the change, the approving owner, and the system record that reflects the final decision.
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.
- ISO 4217 currency codesPrimary standard reference for identifying currencies without relying on ambiguous symbols.
- IRS foreign currency and currency exchange ratesGovernment example of documenting currency conversion and rate sources; company accounting policy remains with finance.
- NIST least privilege glossarySupports limiting preparation access and retaining approval authority with the designated owner.
International Labour Organization guidance on remote work arrangements reinforces why remote role briefs should document expectations, communication rhythms, and accountable handoffs.
Contact Us to turn this article into a scoped Philippines-based staffing brief.