How are foreign-currency expenses converted for accounting?
Short answer
Foreign-currency expenses are recorded in the merchant's currency, then translated into the entity's functional currency using the rate and date required by your accounting policy. Card transactions commonly use the cleared or posted amount because that is the final amount charged.
What to retain
Keep both the original receipt amount and the converted amount with the transaction record. That gives your finance team the information needed to reconcile the card statement, apply the right tax treatment, and explain any difference from the purchase-date estimate.
How it works in Ramp
On the transaction page, Ramp shows the statement amount in the card’s statement currency. When the merchant charged the purchase in a different currency, Ramp marks the transaction so finance can compare the original purchase amount with the settled card amount.
This gives finance the two amounts needed for reconciliation:
- The amount charged by the merchant in the original currency
- The amount that settled on the Ramp card statement
Your accounting-provider settings determine which currency reaches the ledger. This should be configured before rollout so finance does not have to translate transactions manually at month-end.
NetSuite currency conversion
For NetSuite, Ramp syncs the transaction in its original currency when the vendor accepts that currency. If the vendor does not accept it, Ramp uses the NetSuite subsidiary’s primary currency instead.
When a card’s issuing currency differs from the entity’s functional currency, Ramp can record the difference between transaction-level conversion and statement-payment conversion as an FX gain or loss. This workflow applies to Ramp card transactions.
Foreign transaction fees
When a card transaction’s original currency differs from its statement currency, the transaction undergoes currency conversion.
See Ramp's card programs by global region:
Related questions
GL codes can differ for foreign and domestic charges to reflect variations in currency, tax rules, and entity structure. This distinction helps maintain accurate reporting and compliance across regions. Ramp automatically identifies the transaction’s country, currency, and entity, then applies the appropriate GL code and tax settings based on your accounting integrations.
Read moreA single transaction can be split across multiple GL codes when it covers different departments, projects, or expense categories. This ensures each portion of the spend is recorded accurately and supports cleaner, more detailed financial reporting.
Read moreManagers usually cannot override accounting codes after month-end close to preserve data integrity. Any post-close adjustments must go through formal journal entries or finance approvals.
Read moreCoding rules typically apply only to new transactions after they are created. Past transactions may remain unchanged unless updated manually or through specific retroactive adjustments.
Read moreTax-deductible and non-deductible expenses are coded under separate GL accounts to ensure accurate tax reporting. This distinction helps you track eligible deductions and maintain compliance during audits. Ramp automatically applies the correct GL code based on your accounting integrations and internal rules.
Read moreRecurring SaaS charges are auto-coded through connected bank feeds, vendor recognition, and past transaction patterns. Each charge is matched to the correct GL code automatically, keeping monthly bookkeeping consistent and reducing manual effort. Every month, the system detects the same vendor, payment amount, and frequency, then assigns the correct GL code based on your previous entries. This consistency ensures that recurring software costs appear in the right expense categories across reporting periods.
Read more