Hours logged in one currency, paid in another: where the rate gets set
By Jordan Ellis Published 8 min read
On this page (10 sections)
- The short version
- Multi-currency payroll needs a traceable rate
- The rate date decides who carries currency risk
- Separate contractor, client, and payout currencies
- Approved timesheets need a clear lock rule
- Per-entry storage and export recalculation have different trade-offs
- Rounding rules can change the payable amount
- Taxes and payment rails change realized FX
- Use a repeatable vendor demo test
- Questions people still ask
In short: A time tracker for contractors with multi-currency payroll support should show when it fixes an exchange rate, which currency it uses, and how payroll can reproduce the result. The setting affects who carries exchange-rate risk, how approved hours reconcile, and what the contractor receives.
Part of our guide on tracking billable vs non-billable tasks
This page shows where time trackers set exchange rates during multi-currency payroll, including the audit gaps vendors rarely advertise.
| Rate capture | entry, invoice, or export |
|---|---|
| Currency setup | contractor, client, and payout currencies |
| Rate snapshot | fixed rate tied to a record |
| Spread | provider margin inside an exchange rate |
| Audit evidence | export rows, rate source, and timestamps |
The short version
- Exchange rates can apply at time entry, invoice creation, or payroll export.
- A rate snapshot records the rate used for a particular timesheet or payment calculation.
- Payment rails, taxes, fees, and currency spreads can change the amount received.
- Rounding rules and conversion order need written confirmation.
- A demo should produce an export with enough fields to reproduce the calculation.
Multi-currency payroll needs a traceable rate
A time tracker can record hours in one currency while payroll pays the contractor in another. The system must then choose a rate, a timestamp, a source, and a rounding rule.
A rate snapshot is the exchange rate saved with a timesheet, invoice, or payroll record. It maps to accounting fields such as rate_snapshot, rate_timestamp, source_currency, and target_currency.
Export recalculation means the system applies a newer rate when it creates an invoice or export. That can change an approved amount, so ask whether approval freezes the rate or only the hours.
I won't name a product as the safe choice here. Product settings, plan tiers, connectors, and regional payment rules change. Test named vendors in a sandbox and keep their written answers. We cover exporting consultant hours accurately in its own article.
The rate date decides who carries currency risk
A rate fixed at time entry gives each row a known conversion. A rate fixed at invoice or export gives the period a later value instead.
The first approach makes contractor pay easier to predict, but the client may absorb a market move. The second tracks a later market rate, but the contractor may receive less or more than expected.
Hypothetical example: 160 hours at $40 per hour produces $6,400. At an exchange rate of 1.08 dollars per euro, the result is $6,400 ÷ 1.08 = €5,925.93. At 1.14 dollars per euro, it is $6,400 ÷ 1.14 = €5,614.04. We cover azure ad b2b for contractor team in its own article.
The difference is €311.89 in this hypothetical. Real results depend on actual hours, rates, exchange direction, provider spreads, taxes, fees, and contract terms. Put the chosen date and source in writing.
Separate contractor, client, and payout currencies
A contractor may quote a rate in pounds, a client may approve a budget in dollars, and the payout account may accept euros. Those are separate accounting fields, not one currency setting.
A conversion hop is one movement from one currency to another. A spread is the provider's margin between its quoted rate and a reference market rate. The other half of this decision is managing 18 hourly staff shifts.
Two hops can compound the spread. If each hop retains a fraction s of the amount, the combined factor is (1 – s)². With a 0.4% spread, the factor is 0.996², or about 0.992016, before other fees.
That formula is a measurement method, not a general fee claim. Ask the bank, wallet, payroll provider, or payment service for its actual rate and fee at each hop. One conversion is usually easier to reconcile than a round trip.
Approved timesheets need a clear lock rule
Some systems keep the rate snapshot when a row is approved. Others recalculate the amount when an invoice or payroll export is created, even though the hours remain approved. For the detail, see our notes on 15 minute idle time detection without screenshots.
The difference matters because an approved timesheet can show one amount while the later export shows another. A lock flag, approval timestamp, and rate version help accounting explain the change.
Ask for these fields: timesheet_row.approved_at, timesheet_row.rate_snapshot, timesheet_row.rate_timestamp, export.export_rate, export.created_at, and recalculation_status. Request ISO timestamps and the rate provider's name.
A useful audit file contains the original row, the approval event, the rate response, the export, and any later adjustment. Screenshots alone are weak evidence when the amount is disputed. If that sounds like your situation, read up on toggl track daily sync limits next.
Per-entry storage and export recalculation have different trade-offs
Per-entry storage ties each row to its own rate snapshot. Export recalculation applies a later rate to a group of rows, often the whole invoice or pay period.
Per-entry storage favours predictable contractor pay and line-by-line reconciliation. Export recalculation favours a current valuation, but it places more currency risk on whoever receives the later amount.
Storage grows with the number of records. Estimate rate rows with: contractors × average timesheet entries per contractor per period. Use your own entry count, not a generic hourly assumption.
Ask whether archived snapshots remain readable after a plan change, whether edits create a new version, and whether exports preserve the original rate. Those answers matter more than a dashboard label.
| Feature | Rate stored per entry | Recalculated on export |
|---|---|---|
| Pay stability | Usually higher | Can vary with export time |
| Audit trail | Row-level | Period-level unless detailed logs exist |
| Currency risk | Set when the row is rated | Set at invoice or export |
| Best fit | Fixed payroll rules | Contracts tied to a later rate |
Rounding rules can change the payable amount
Rounding means reducing hours or money to a chosen increment. Conversion order means deciding whether the system rounds hours before conversion or rounds the converted money afterward.
Hypothetical demonstration: 7.49 hours at $85 per hour equals $636.65. If the system rounds hours down to 7, it calculates 7 × $85 = $595. If it converts the unrounded amount at 1.10 dollars per euro, $636.65 ÷ 1.10 = €578.77 before money rounding.
Those paths differ because the first removes 0.49 hours before valuation. The example demonstrates arithmetic, not a universal payroll rule. Ask for the configured hour increment, currency precision, rounding direction, and stage where rounding occurs.
Check whether the system rounds each row or only the invoice total. A small row-level difference can accumulate across many entries, especially when the payment currency uses fewer decimal places.
Taxes and payment rails change realized FX
The payroll conversion is not always the amount the contractor receives. Withholding tax, social contributions, bank fees, and payment-provider charges can be deducted before or after currency conversion.
A bank transfer may use the bank's rate and a stated fee. PayPal can apply its own conversion rate and currency charge. Stripe may convert during payment or settlement, depending on the account and payout currency.
Ask whether tax withholding is calculated in the contract currency, payroll currency, or payout currency. A contractor may owe tax on the gross amount while receiving a lower net amount after conversion and fees.
Record gross currency, tax currency, payout currency, provider rate, provider fee, settlement date, and net amount. Accounting should reconcile those fields separately rather than treating the payout as proof of the payroll rate.
Use a repeatable vendor demo test
Use a sandbox and record every screen, export, timestamp, and vendor response. The same test works for a named time tracker, payroll connector, or payment provider.
1. Create a contractor with source currency USD, payout currency EUR, and a $40 hourly rate. Create a client project in GBP. Ask the vendor to identify every conversion path.
2. Enter two rows with the same hours on different dates. Approve the period, change the displayed FX rate if the sandbox permits it, and export the invoice and payroll file.
3. Compare the original rows with the export. Expected evidence includes the rate source, rate timestamp, source and target currencies, rounding method, approval state, and any recalculation flag.
4. Send the same payable amount through the proposed bank, PayPal, or Stripe route. Record the quoted rate, fee, settlement currency, tax deduction, and net receipt. Repeat only in a test environment.
5. Request a corrected-row export and an audit log. Expected evidence includes old value, new value, editor, reason, time, and whether the original rate snapshot remains available.
- Create a sandbox contractor, client, and payout account with three currencies.
- Enter dated rows, approve them, and export timesheet, invoice, and payroll files.
- Change the rate or export date, then compare totals and row-level fields.
- Test the proposed payment rail and record its rate, fee, tax treatment, and net amount.
- Save vendor answers, files, timestamps, screenshots, and audit logs in one evidence folder.
Prefer a tool that preserves a rate snapshot, exposes the conversion source, and exports enough fields to reproduce payroll. The contract should assign any remaining currency risk.
Questions people still ask
Can exchange rates change after time is logged?
Yes. An invoice or export recalculation can apply a later rate unless approval freezes the rate snapshot.
What is a rate snapshot?
It is the exchange rate saved with a row, invoice, or payroll record, usually with its timestamp, source, and currency pair.
What if contractor and client currencies differ?
Ask which currency is the contract basis and whether the system converts once or uses an intermediate currency.
How do taxes and payment services affect pay?
Withholding, bank fees, PayPal, Stripe, and other providers can use different rates or charges, so reconcile gross, deductions, fees, and net receipt separately.
What should a contract say about FX risk?
A short clause can state: “The payable amount is fixed in [currency] using the [source] rate at [timestamp]. The contractor bears, or the client bears, changes after that point.” Confirm tax and accounting treatment before signing.
What export fields should I request?
Request timesheet_row.timestamp, timesheet_row.rate_snapshot, timesheet_row.rate_timestamp, currency_code, source_currency, target_currency, rounding_method, invoice.export_rate, export.created_at, fee_amount, tax_amount, and net_amount.