Record the exchange-rate source for an expense

The short answer

A foreign-currency expense can show three honest amounts: the merchant's charge, the card issuer's posted amount, and the amount used for reimbursement or accounting. They may use different currencies, dates, rates, and fees. A Filipino expense assistant can reconcile the evidence and arithmetic, but should not choose an accounting policy simply because one rate produces a cleaner number.

Begin with the original purchase. Record the merchant amount and currency, transaction date and local time when available, merchant, business purpose, and receipt reference. Keep full card numbers, personal addresses, and unrelated receipt details out of the working log.

Then capture settlement evidence. A card statement may show a posted amount in the account currency, a posting date, and a separate foreign-transaction fee. The posting date can differ from the purchase date, and the issuer's effective conversion may not equal a public daily reference rate. Preserve what the statement actually reports without reverse-engineering a rate and presenting it as the issuer's disclosed method.

Finally, identify the reporting amount required by the approved expense process. The organization may reimburse the posted card amount, convert a cash receipt using a named public source, or apply an accounting-system rate. That rule belongs to the finance owner. The assistant follows the current policy and flags cases it does not cover.

For every conversion, record the source organization, source URL or system record, quoted currency pair, rate direction, effective date, observation time, units, and calculation. A rate of 0.92 is meaningless unless the record says whether it means euros per dollar or dollars per euro.

Write the formula. If 300 euros are converted using 1.10 US dollars per euro, the calculation is `300 × 1.10 = 330 USD`. If the source quotes euros per dollar, division may be required instead. Keep rounding until the step the policy specifies and show the unrounded value when the system permits it.

Do not silently use today's rate because the receipt is being processed today. The relevant date may be the transaction date, posting date, reimbursement date, month-end date, or another policy date. When a weekend or holiday has no published rate, follow the written fallback rather than selecting the closest date by intuition.

Suppose an employee stays at a hotel in Paris. The receipt shows EUR 600 on September 28. The corporate card posts USD 705 on September 30, including a separately shown USD 9 fee. The employee's expense report is reviewed by a Philippine entity that records reimbursements in pesos.

The assistant should not combine those values into one undocumented conversion. The evidence packet lists EUR 600 as the merchant charge, USD 696 as the posted converted purchase if the statement separates it that way, and USD 9 as the fee. It then applies the organization's approved PHP reporting rule to the permitted base amount and date.

If policy says to use the card statement for card purchases, a public EUR-to-PHP rate is not a replacement merely because it is easy to find. If policy says the fee belongs in another category, preserve it separately. If the statement does not reveal whether the USD 705 includes the fee, flag the ambiguity for finance instead of subtracting USD 9 twice.

Now assume the receipt includes a refundable deposit that the hotel releases later. The assistant records the original charge and later credit as linked transactions. Netting them before both appear can hide the timing and produce a mismatch with the card feed. Finance decides how the accounting period treats the difference.

Compare the calculated reporting amount with the expense-system value and state the variance. Small differences can come from rounding, issuer spreads, fees, rate timing, or data entry. Set a policy-approved tolerance for routine routing, but keep the actual difference visible.

A tolerance is not permission to force values to match. Do not alter the receipt amount, invent a balancing fee, or change a source date to eliminate a variance. Route out-of-policy differences with the receipt, statement reference, formula, and source record.

Label estimates. If a report must be prepared before the card transaction posts, the assistant can use the approved provisional method and mark it pending settlement. When the statement arrives, replace or reconcile the estimate according to policy while retaining the change evidence. An estimate should not quietly become a final posted amount.

Check duplicates across currency representations. A receipt import and card feed may create two expenses with different amounts and currencies for the same purchase. Match merchant, date, traveler, and source reference before proposing a duplicate. Similar converted values alone are not enough.

Use source documents stored in approved expense and accounting systems. Public rate sites may be appropriate only when policy names or permits them. The IRS publishes exchange-rate information for US tax purposes but notes that it does not have an official exchange rate and generally accepts consistently used posted rates. That guidance does not establish a company's reimbursement method.

Restrict receipt and statement access to the work required. Receipts can reveal travel, purchases, partial account details, and personal information. Use an individual assistant account, narrow exports, and a record of changes. Do not download a full card statement when the authorized transaction record is sufficient.

The approver should see merchant amount, settlement amount, fees, reporting calculation, variance, policy reference, and unresolved questions. Approval belongs to the named finance or budget owner. The assistant should not approve their own reconciliation or treat a system's acceptance as policy approval.

Use synthetic examples for a weekend cash purchase, card posting two days later, separate fee, refund, deposit release, partial reimbursement, missing currency symbol, inverse rate, duplicate import, and rate unavailable on the policy date. Predetermine the evidence and route for each.

Measure source completeness, correct rate direction, date compliance, arithmetic corrections, unresolved variances, duplicate findings confirmed, and owner overrides. Processing speed alone can reward undocumented shortcuts. A well-routed exception is a successful outcome when policy cannot resolve it.

OutsourcedAssistants.com describes [expense administration](/services/expense-administration) as a bounded support lane with approval limits. A role brief should name the allowed rate source, date rule, fee treatment, tolerance, evidence system, and finance decision owner. [Request a role plan](/contact-us) when multi-currency expenses depend on unwritten habits.

These sources provide public rate context and support careful data handling. They do not select an employer's reimbursement rate, accounting date, tax treatment, or fee policy. The organization's finance policy and qualified accounting or tax owners govern those decisions.

Build the work lane

• Write the recurring task and its finish rule
• Share an approved example and the source system
• Set response times, approval limits, and escalation rules
• Review a small sample before widening the role

Check the role before you expand it

• Can a new person complete the task from the examples?
• Who reviews the first week and records corrections?
• Which decisions and systems stay with your internal owner?
• What evidence shows the role is ready for another queue?

Common questions