- Retain the original transaction currency and rate — reporting currency alone is not enough.
- Local entities usually need local accounts, and card availability differs by country.
- Authentication requirements differ by region and can affect card acceptance.
- Tax treatment of expenses is jurisdiction-specific and cannot be globalised.
- One global policy with documented local exceptions beats many local policies.
Multi-currency handling
A transaction in a foreign currency has at least three relevant numbers: the amount in the original currency, the rate applied, and the amount in the reporting currency. Systems that keep only the last make variance analysis and dispute handling far harder than they need to be.
Foreign exchange treatment also affects cost. The applied rate and any conversion margin are part of the true cost of a card programme, and they are frequently omitted from comparisons that focus on rewards.
- Confirm which rate is used and when it is captured.
- Establish whether a conversion margin applies and how it is disclosed.
- Check that the original currency is retained end to end through the accounting export.
- Decide the group's revaluation policy and apply it consistently.
Local entities and availability
Card programmes are issued under licences that are country-specific. A programme available to a United States entity may not be available to a subsidiary elsewhere, or may be available with different features.
This is the single most common surprise in international rollouts. Confirm availability per entity and per country before designing a global process around a single product.
- Which countries can be issued cards under which entity?
- Are local currency accounts available, or only foreign-currency holdings?
- Do local statutory reporting requirements affect what data must be retained?
- Which local payment rails are supported for vendor payments?
Regional authentication differences
Authentication requirements are not globally uniform. In the European Economic Area, for example, rules on strong customer authentication mean cardholders may be prompted for additional verification on online transactions that would complete without a prompt elsewhere.
For travellers this shows up as declined transactions abroad when a verification prompt cannot be completed. Briefing travelling employees on what to expect prevents most support tickets.
Background: European Banking Authority — payment services.
Tax treatment does not globalise
Recoverable tax on business expenses, documentation requirements and category-specific rules differ substantially between jurisdictions. A single global expense category structure will not carry a correct tax treatment everywhere.
The workable approach is a global category structure with jurisdiction-specific tax codes mapped underneath it, so reporting is comparable while compliance stays local.
One policy, documented exceptions
Companies that write a separate expense policy per country end up with contradictions nobody can resolve. Companies that impose a single policy without local exceptions end up with rules that are illegal or unworkable somewhere.
The middle path is a single global policy with a short, explicit annex per country covering the genuine differences — per diem practice, mandatory documentation and any category treated differently by local law.
Frequently asked questions
Rarely without qualification. Issuance is licensed per country, so availability and features differ. Confirm entity-by-entity coverage before designing a global process.
Retain the original amount and currency, the rate applied and the reporting-currency amount. Keeping only the converted figure makes disputes and variance analysis unnecessarily difficult.
Common causes include additional authentication requirements in the region, merchant category rules, per-card limits and fraud controls reacting to an unusual location. Brief travellers in advance and give them a route to reach a human quickly.
Global, with a short documented annex per country for genuine legal or practical differences. Fully local policies drift apart and become impossible to compare.
Keep reading
Sources and further reading
Every factual statement on this page is checked against primary documentation. Terms change frequently, so confirm details with the provider before acting on them.
- Brex — official website Primary source for current product names, availability and terms.
- European Banking Authority — strong customer authentication Background for statements about additional verification steps outside the United States.
- Visa — commercial payment solutions Network-level background on commercial card products and data levels.
- FASB Accounting Standards Codification Reference point for accrual, expense recognition and close-process statements.