Multi-currency payroll: a practical guide for global teams

Key takeaways

Multi-currency payroll covers the currency side of a payroll cycle: the amount promised, the currency used for calculation, the conversion point, the currency received by the worker, and the records needed to reconcile them. Multi-country payroll is a broader jurisdiction-based category covering local employment, tax and reporting duties. The two can overlap, but a company operating across countries still needs a currency policy for each pay cycle.
Separate employees from independent contractors before choosing a route. Employee payroll generally brings calculation, withholding, reporting and pay-date obligations. Contractor administration relies on a different set of contractual, service and rights records. Currency choice does not determine worker status: in the United States, the IRS examines behavioral control, financial control and the relationship between the parties, while UK guidance likewise starts with the reality of the working relationship.
Record more than one currency and date. The contractual amount, the worker’s expected receipt, the taxable measure and the accounting translation can use different currencies and dates. A contract currency is therefore not enough; your records must show which rate applies, when it was fixed and why.
Compare the complete cost, including worker receipt. Ask for the FX spread, explicit provider and intermediary charges, and any recipient-side deduction separately. In the Financial Stability Board’s March 2025 sample of retail business-to-person cross-border services for a USD 5,000 transfer, average FX cost was 1.4% and average explicit fee cost was 0.5%. These figures illustrate why a headline rate is incomplete; they are not payroll prices.
Work backward from the applicable pay date. Assign owners for HR inputs, payroll calculation, funding, approval, release, recipient credit and exception handling. A sent payment instruction is not evidence that the worker has received the money; the credit step has its own route, timing and escalation conditions.
Reconcile the obligation with the actual outcome. Keep the approved amount, rate source, fees, funding amount, delivered amount, payment status and supporting statements together. Employee payroll records also need the calculation and reporting trail, while contractor records need the agreement, evidence of work and agreed rights terms.

What multi-currency payroll covers

Multi-currency payroll is the part of an operating cycle that determines which currency applies to each amount, when that amount is converted, what the worker receives and how the transaction is recorded. Multi-country payroll covers a different scope: the employment, tax, reporting and payment rules that apply when people work in multiple jurisdictions. A multi-country operation may require several currencies, but a currency policy cannot determine worker status or replace local payroll review.

Multi-currency and multi-country payroll

The distinction becomes practical as soon as a team combines workers in different locations, currencies or employment arrangements.

Multi-currency payroll answers monetary questions: What amount is promised? In which currency is it calculated? Which rate applies? When is the rate fixed? What deductions and charges reduce the amount received? Which record proves what was owed, funded and delivered?
Multi-country payroll answers jurisdictional questions: Which employment and tax rules apply? Who calculates and reports the payroll? What deductions are required? Which pay date, currency and local payment conditions govern the cycle?
Contractor administration asks a third set of questions: What work was commissioned? Which agreement governs it? What supporting documents demonstrate delivery? Were the rights to the result addressed?

These tracks may overlap, but they have different owners and records. An employee belongs on the payroll track after the actual working relationship has been assessed. An independent contractor belongs on the contract and service-record track. Currency does not decide that classification: US federal employment-tax guidance examines behavioral control, financial control and the relationship between the parties, while UK guidance states that the correct employment-rights classification follows the reality of the working relationship. UK guidance also distinguishes employment-rights status from the separate system for tax status.

Treat contractor payments as part of the company’s workflow without placing them inside employee payroll. Employee payroll normally involves statutory calculation, withholding and reporting for employees; contractors require an agreement, evidence of the service, treatment of the agreed amount and, where relevant, a rights record. A mixed workforce therefore needs two connected but separate operating paths.

The amounts and currencies in one pay cycle

One cycle can contain several currencies and several valuation moments. Treating them as a single exchange rate makes the transaction harder to explain and reconcile.

A practical worksheet separates at least four values:

Value	What it records	Why it must be explicit
Contract or promised amount	The amount and currency agreed with the worker	Establishes the obligation communicated before the cycle
Calculation amount	The gross or net amount calculated for payroll or contractor work	Connects the obligation to deductions and the route used to deliver it
Expected receipt	The currency and amount the worker should receive after stated charges or deductions	Sets the expectation against which actual credit can be checked
Recorded amount	The amount carried into tax, accounting and financial records	Prevents the transaction rate from being reused automatically for another purpose

The dates also need separation. The entitlement date, payroll calculation date, transaction date, payment-release date, settlement date, local tax measurement date and accounting reporting date can each matter for a different purpose. A UK employee statement template, for example, includes the currency in which an employee working abroad will be paid. HMRC applies a separate sterling measurement rule to the cited foreign-currency earnings taxable when received. For IFRS reporters, IAS 21 uses the transaction-date spot rate for initial recognition and the closing rate for later monetary-item measurement.

The worksheet should therefore record the rate source and date for each use instead of adding a generic exchange-rate field. It must also state who owns each decision. HR and payroll may own the promised terms and calculation; finance may own funding and approvals; a local payroll or tax adviser must verify the applicable jurisdictional rule; accounting owns the treatment under the entity’s reporting framework.

When a growing team needs a formal process

A formal process becomes necessary when separate contracts, spreadsheets, chat approvals and provider portals begin to carry the same cycle in different places. The trigger is not a particular headcount. It appears when recurring cross-currency work creates coordination or evidence problems.

Common signs include:

The same worker appears in several spreadsheets with different promised currencies, pay dates or deduction assumptions.
Finance cannot connect an approved payroll calculation to the amount funded, the rate used and the amount credited.
Managers approve a contractor’s work through one system while accounting receives the supporting record from another.
A late HR change reaches payroll after the input cutoff, yet the original date remains unchanged.
Worker receipt differs from the expected amount, but no record identifies whether the difference came from conversion, fees, deductions or a rejected instruction.
A tax or accounting report requires a rate that the operational payment record does not preserve.
Contractor work, closing documents and rights agreements cannot be retrieved together for a review.

At this point, the company needs a repeatable cycle with named owners rather than a larger collection of templates. The minimum operating record links the worker relationship to the promised amount and currency, the calculation, the rate source and date, applicable deductions, approval, funding, delivery route, expected receipt, actual credit, exception status and supporting documents. Employee records then connect to payroll reporting; contractor records connect to the agreement, evidence of work and rights terms.

This structure also creates a cleaner control point for scale. Before adding another currency, country or provider, the team can test the existing process against a representative worker group and cycle. If the company cannot reconstruct one completed cycle, adding another route will multiply the same ambiguity rather than solve it.

Separate employee payroll from contractor operations

The worker’s actual relationship determines the operating track. Employee payroll brings calculation, withholding, reporting and pay-date duties; independent-contractor administration brings contract, service-delivery and rights records. A currency choice or payment route cannot decide the relationship, and treating both worker groups as one payroll population obscures who must act.

Assess the working relationship and applicable jurisdiction, then follow either the employee payroll track or the independent-contractor records track. — A proposed operating split, not a universal classification test. Assess the actual relationship and applicable local rules before assigning a track. IRS: Independent contractor vs. employee · UK employment status checklist · UK PAYE for employers · IRS: What records should I keep? · UK copyright ownership guidance

Who owns the employee payroll obligation?

The employing company retains the employee payroll obligation under the arrangement it has entered. Its payroll or HR function owns the calculation; finance owns funding and approval; a qualified payroll or tax adviser verifies the rules for each employee’s applicable jurisdiction. A provider’s calculation or delivery role alone does not identify the legal employer; the employment arrangement and local rules determine responsibilities.

The actual responsibilities depend on the jurisdiction and employment arrangement. In Great Britain, an employer running PAYE deducts tax and National Insurance from most employees’ payments and reports those payments and deductions to HMRC on or before each payday. US employers generally withhold federal income tax, Social Security and Medicare taxes from employee wages and deposit and report the applicable employment taxes, subject to the circumstances of the employment.

That structure becomes multi-currency when the company calculates the wage in one currency, funds it in another and expects the employee to receive it in a third. HR and payroll still need to determine:

the gross and net amounts owed to the employee;
the applicable statutory deductions;
the promised pay currency and payment date;
the local tax and reporting treatment;
the rate and date used for the taxable amount; and
the amount and currency the employee is expected to receive.

The distinction between employment-rights status and tax status also needs attention. UK guidance states that the correct employment-rights classification follows the reality of the working relationship and notes that a separate system determines employment status for tax. The employer therefore needs a status review based on the working relationship, not a payment method or a label chosen by the payroll provider.

A contracted payroll provider can perform specified calculations and submissions, but its role does not erase the company’s underlying responsibility. UK payroll setup guidance describes payroll software as recording employee details, calculating pay and deductions, and reporting to HMRC. Whoever performs the task, the employer must be able to produce the underlying calculation, approval and reporting record.

What changes for an independent contractor?

An independent contractor’s arrangement begins with the engagement terms rather than an employer payroll calculation. The company needs to define the work, the contractual amount and currency, the payment terms, the evidence required for acceptance and the treatment of any rights in the result. It should also check whether the arrangement changes the legal status of the person doing the work.

The questions differ from employee payroll:

Which agreement governs the engagement?
What service or deliverable does the contractor owe?
Which document confirms that the work was completed and accepted?
What amount is owed, in which currency and by which date?
Does the agreement transfer rights in the deliverable to the company?
Which records support the payment for tax and accounting purposes?

US federal recordkeeping guidance illustrates the documentation side of the contractor track. Supporting documents for business expenses should identify the payee, amount paid, proof of payment, date incurred and a description of the service received; a combination of documents may be needed. That record supports the expense, but it does not establish ownership of the work.

Rights require an additional check. In the United Kingdom, the first legal owner of copyright in commissioned work is normally the creator, unless ownership is otherwise agreed in writing. An implied licence may exist without transferring ownership. For that reason, the contract and task record should state what happens to the rights in each commissioned result instead of assuming that payment settles ownership.

Contractor administration also changes what your reconciliation must contain. The amount paid remains part of the company’s financial record, while the agreement, service evidence and rights term explain why that amount was owed. A payment without those documents can be processed yet remain weak evidence when finance, an auditor or an investor asks what the company received.

Where 4dev.com fits in contractor administration

4dev.com fits on the independent-contractor track through the Contractor Platform. Its role is to administer contractor work after selection: tasks, statuses, agreements, closing documents and engagement history.

The platform’s contractor records answer operational questions that a currency field cannot. They show which task was assigned, what agreement governs it, whether the work reached the relevant status and which closing document supports the engagement. That gives the company a place to inspect the contractual and operational record alongside its accounting records.

The company should check the applicable rights term for each commissioned deliverable and retain it with the task and closing documents.

A company that needs employee payroll calculation, statutory withholding and local reporting must assess the provider responsible for those duties. A company that needs contractor engagements, work statuses and supporting documentation can assess 4dev.com for that distinct administrative function. Each track needs its own owner and records.

Set the currency terms before the first cycle

Before the first cycle, record the promised amount, calculation currency, rate rule and expected worker receipt. A single exchange-rate field cannot answer those questions: contractual currency, worker receipt, tax measurement and accounting translation may use different currencies and dates.

Contract amount and calculation currency

The contractual amount is the starting point. Record the amount, currency, pay frequency and date, and explain whether the amount changes under any stated condition. Acas’s UK employee written-statement template includes a field for the currency in which an employee working abroad will be paid. That template demonstrates how the currency belongs in the employment terms; it does not authorize every foreign-currency wage arrangement.

The calculation currency then determines how the gross amount is calculated before deductions. It may be the same currency as the contractual amount, or it may reflect the currency in which the company calculates the payroll obligation. The record should make that distinction explicit:

Field	Question answered
Contracted amount and currency	What has the company promised?
Calculation currency	In which currency is the payroll amount calculated?
Deduction basis and currency	Which amounts are withheld or deducted, and how are they measured?
Funding currency	From which currency balance will the company fund the cycle?
Receipt currency	Which currency is expected to reach the worker?

For contractors, add the payment terms to the engagement record rather than treating the payment as employee gross pay. The agreement should identify the work, amount, currency, payment date and the evidence required for acceptance. That record then supports both the operating workflow and the accounting trail.

The company should also assign ownership. HR and payroll normally own the employment terms and calculation; the engagement owner and legal reviewer own contractor terms; finance owns funding and approvals. A tax adviser must verify the local tax treatment of the worker arrangement. The currency field is a contractual and operational input, not a substitute for either review.

Receipt currency and worker expectations

The receipt currency is the currency the worker is expected to have available after the agreed deductions and charges. It is a separate decision from the company’s funding currency. If the company funds in USD, calculates a EUR obligation and pays into a GBP account, the worker’s expected receipt must still be stated in the currency they will receive.

Write the expected outcome plainly. For each worker or worker group, record:

the promised gross or net amount;
the currency in which the worker expects to receive it;
the applicable deductions;
which charges may affect the amount received;
the applicable pay date; and
what happens if the route, account details or rate change.

Acas’s example of a currency term for work abroad provides a useful drafting pattern, but the company must also check the applicable wage law. ILO Convention 95 addresses legal-tender wage payment, regular payment intervals and information about wage conditions and each payment. Its application depends on ratification and local implementation, so it cannot be used as a universal permission to pay in a particular currency.

The worker’s expectation should not depend on a support note explaining an unexpected deduction after the fact. If the contract amount, calculation currency and receipt currency differ, state the conversion point and rate source in the terms or in a controlled schedule linked to them. If the worker receives a different amount from the expected amount, the cycle needs a status and evidence trail that identifies the cause.

Conversion point, rate source and rate lock

The conversion point determines when the currency obligation becomes a monetary amount in another currency. It should be stated separately from the rate source and from any period during which the rate is fixed.

A rate lock answers one narrow question: what rate applies to this conversion, and until when? It does not remove every cost from the route. The company still needs to record the FX spread, explicit charges, possible intermediary charges and any recipient-side deduction. It also needs to know whether the rate applies to the full amount, a portion of it or a particular fee component.

Use separate records for these decisions:

Conversion point: when the amount is converted;
Rate source: the reference rate or provider rate used;
Rate lock: the amount or period to which the quoted rate applies;
Spread or markup: the difference between the reference rate and the rate applied to the transaction;
Explicit charges: provider, bank, intermediary or other separately stated costs;
Recipient treatment: whether a charge is deducted from the amount received or invoiced separately.

The rate used for the operational transaction may also differ from the rate used for tax or accounting. HMRC’s employment-income manual measures the cited UK foreign-currency general earnings taxable when received in sterling at the entitlement date or, if earlier, the payment date, using the rates then in operation. The manual gives a different conversion date for earnings taxable on remittance. Those rules belong to their stated UK context and cannot be generalized to contractors or every jurisdiction.

IFRS reporters also keep the accounting rate separate from the payment rate. IAS 21, as reproduced in an IFRS Foundation staff paper, requires initial recognition of a foreign-currency transaction using the transaction-date spot rate and later translation of foreign-currency monetary items using the closing rate. Exchange differences then require their own accounting review.

Exchange-rate exposure between cycles

Exchange-rate exposure arises when the currency of the obligation, the calculation, funding, tax measurement or receipt differs, and the rate can move before the relevant conversion or measurement date. The exposure is not simply the difference between two headline rates. Its size depends on the amount, currency pair, timing and the rate rule chosen.

For recurring payroll, document which rate is fixed for which part of the cycle. For example, a company may promise a EUR amount, fund it from a USD balance and deliver a GBP receipt. If the promised amount remains fixed in EUR, exchange-rate movement changes the USD funding requirement unless the contract allocates that exposure differently. If the worker is instead promised a fixed GBP receipt, the GBP obligation stays fixed while the amount needed to fund it changes.

The practical exposure review should identify:

the currency in which each recurring amount is fixed;
the currency in which each balance is held;
the date on which the rate is fixed;
the date on which the rate is used for tax or accounting;
the amount exposed if the rate moves before that date; and
the person who approves any change to the policy.

For each recurring cycle, compare the actual funding currency, receipt currency, corridor and amount; a generic rate will not describe those terms.

A rate lock can reduce uncertainty within its stated scope. It does not determine whether the wage currency is lawful, whether the tax measure is correct, whether the provider supports the required corridor or whether the worker receives the expected amount. Those decisions need separate owners and records. Set the terms first so each later step can show which rule it applied.

Find the full cost of conversion

The full cost of a cross-currency route includes the FX spread, explicit provider and intermediary charges, and any recipient-side deduction. Compare those components for the same corridor, transfer amount and route, then calculate the amount the worker should receive after every stated cost.

In the FSB sample, average FX cost was 1.4% of the transfer amount and average explicit fee cost was 0.5%. — FSB, March 2025: sampled retail cross-border B2P services for a $5,000 transfer. Separately rounded costs as a share of the transfer; not a payroll price benchmark. Service count not stated. Financial Stability Board, 2025 cross-border payments progress report, Table 8

FX spread, explicit fees and recipient deductions

The FX spread is the difference between the reference rate and the rate applied to the transaction. It may be disclosed as a markup, a margin or an exchange rate that differs from the market rate. A rate alone does not reveal the spread because the reference point and the amount to which the rate applies also matter.

Explicit charges are separate amounts stated by a provider, bank or intermediary. They can include a fixed fee, an amount-based fee or another route-specific charge. A third category is the recipient deduction. It may reduce the amount credited to the worker or be invoiced elsewhere in the payment chain, so the amount sent and the amount received remain different figures.

Use one worksheet for each quote:

Cost field	Record
Funding amount and currency	What the company sends or debits
Contracted or expected receipt	What the worker should receive
Reference rate	The stated market or benchmark rate
Applied rate	The rate used for the conversion
FX spread	The difference between the reference and applied rates
Explicit provider fee	Every separately stated provider charge
Intermediary charges	Bank or intermediary costs passed into the route
Recipient-side deduction	Any amount withheld from or charged against receipt
Expected net receipt	The amount after all known deductions
Quote reference and validity period	The basis for the comparison

Ask each route to quote the same funding and receipt currencies for the same amount. Record whether a charge is fixed or proportional, who bears it and whether it can change between approval and release. Also record who receives the amount after intermediary processing. A provider may describe its own fee but may not control every charge imposed later in the route.

The worker-facing amount should appear in the approval record. Comparing only the employer’s debit shows what left the company; comparing only the headline exchange rate shows neither the explicit cost nor the final receipt. The decision needs both.

Compare representative amounts and corridors

Compare routes with the amount and corridor that your business will actually use. Request the applied rate, explicit fees and expected receipt for those same terms from each route.

A repeatable comparison contains the following steps:

Select the worker group, funding currency, receipt currency, corridor and recurring amount band.
Obtain the current rate, spread, explicit fees, recipient treatment and quote validity for each route.
Calculate the expected amount credited to the worker under the same assumptions.
Apply the route’s stated cutoffs and operating hours.
Record the evidence required to confirm actual credit.
Repeat the comparison when the amount band, corridor or delivery route changes.

Use a recurring representative amount as well as a smaller test amount when the route supports both. A quote for one amount may reflect fixed charges, minimums or tiered pricing; it cannot be assumed to describe another amount. Likewise, a route that works for one currency corridor does not establish the cost or availability of another.

The comparison should reflect the obligation, not just the transfer mechanics. Include any net amount expected after employee deductions or contractor terms, the funding balance used and the accounting or tax treatment assigned to the cycle. Those amounts determine the financial result even when the rail appears unchanged.

Keep the FSB source populations separate: its sampled retail B2P services and receiver-side survey are distinct datasets, and neither is a payroll benchmark.

What the FSB payment sample can and cannot tell you

The FSB’s March 2025 sample covers retail business-to-person cross-border payment services for a USD 5,000 transfer. In its B2P row, average FX cost was reported as 1.4% of the transfer amount, while average explicit fee cost was separately reported as 0.5%. The source uses FXC Intelligence observations and does not state the underlying service count in Table 8.

The sample shows that a cross-border quote can contain two separately visible cost components even when the service is presented as one transfer. Ask a provider to separate the FX cost from its stated fee in the quote. The headline rate alone is not the complete cost.

The FSB cannot supply a payroll price, a provider benchmark or a universal expected total for your business. Its population is retail B2P services rather than employee payroll or contractor batches. The transfer amount, currencies, corridors and provider mix may differ from your cycle. The two percentages are separately rounded, and the source does not support adding them into a precise combined figure.

The FSB also reports a separate voluntary receiver-side provider survey. Across transfer-value bands, average receiver-side fees ranged from 0.1% to 1.3% of the amount sent. The report warns that sender-side and receiver-side datasets cannot simply be added. Receiver charges may be deducted from the nominal amount received or invoiced by an intermediary payment service provider. That survey had 262 responses from 48 jurisdictions and was not an employee-payroll sample, so it illustrates the need to ask who bears a recipient-side charge rather than supplying a payroll estimate.

Use the FSB evidence for three decisions:

Ask for the FX spread and explicit fee separately.
Confirm whether the worker receives the quoted net amount.
Compare your actual corridor and amount with a provider’s current quote instead of transferring the FSB percentages into a payroll forecast.

Check local payroll duties and reporting

Multi-currency payroll does not create one global set of employment, tax or wage rules. The company must identify the worker’s relationship and applicable jurisdiction, then have the appropriate payroll, tax or legal owner verify the calculation, deductions and reporting for that arrangement. Currency terms affect the records, but they cannot answer those local questions.

Classification, tax and deductions

Worker classification comes first because it determines which operating track applies. For US federal employment-tax purposes, the IRS examines behavioral control, financial control and the relationship between the parties. The payment currency or choice of platform does not establish whether someone is an employee or an independent contractor.

The UK framework also starts with the reality of the working relationship. UK employment-rights guidance states that the correct classification follows the reality of the work relationship and notes that employment status for tax uses a separate system. The company therefore needs both a relationship review and the applicable tax review; one conclusion cannot silently replace the other.

Once the relationship and jurisdiction are established, the responsible team must determine:

who employs or engages the person;
which payroll or contracting arrangement applies;
which tax and social-contribution obligations apply;
which amounts must be withheld or deducted;
which currency rules apply to the wage or engagement;
which reports and payments are due;
which records support the calculation; and
who reviews and approves the cycle.

Under UK PAYE, the employer deducts tax and National Insurance from most employees’ payments and reports employee payments and deductions to HMRC on or before each payday if it runs payroll itself. US employers generally withhold federal income tax and Social Security and Medicare taxes from employee wages and deposit and report federal employment taxes, subject to the circumstances of the employment.

The currency conversion rate cannot replace the statutory calculation. A company may convert a gross amount for funding or receipt, while the payroll calculation, taxable amount and reporting currency follow their own applicable rules. Keep the operational rate, tax measure and accounting translation in separate fields so that a change to one does not silently alter another.

This review belongs with qualified local professionals. The applicable rules depend on the worker’s jurisdiction. For an EU worker, a qualified payroll adviser or local counsel must verify the member state’s requirements before the first cycle.

Wage currency and pay terms

The wage currency, amount, frequency and pay date belong in the worker’s terms. A rate and a currency conversion cannot repair an unclear promise. Acas’s UK employee written-statement template includes the currency in which an employee working abroad will be paid, illustrating how the currency should appear alongside the pay terms.

The applicable wage law still needs review. ILO Convention 95 addresses legal-tender wage payment, regular payment intervals and information to workers about wage conditions and each payment. Whether those provisions apply to a particular employment relationship depends on ratification and local implementation. The Convention is not a source of permission to use any currency, and its employee provisions cannot be transferred to independent contractors.

For each employee, the payroll or legal owner should confirm:

the currency in which the wage is agreed or calculated;
whether local law permits that arrangement;
any permitted deductions and the basis for calculating them;
the agreed payday or payment interval;
the currency and information to be provided with each payment;
how changes to currency or pay terms take effect; and
which local reporting and recordkeeping rules apply.

The same discipline applies to contractor terms, with a different legal framework. The agreement should identify the amount and currency, payment date, service, acceptance evidence and rights treatment. Local tax review determines whether any withholding or reporting obligation applies to that arrangement.

Do not use a platform’s ability to make a payment as evidence that the wage arrangement is permissible. A route may support a currency technically while the employment terms or local wage rule prohibits the intended arrangement. Conversely, a documented term such as Acas’s currency field does not prove that every working-abroad arrangement is valid.

UK foreign-currency tax measurement as a bounded example

The UK tax measurement rule shows why the operational conversion rate and the taxable amount must be recorded separately. HMRC’s employment-income manual addresses foreign-currency earnings taxable when received. It states that the chargeable amount is the sterling equivalent at the date the employee becomes entitled to payment or, if earlier, the date they are paid, using the relevant exchange rates then in operation.

In a multi-currency cycle, that creates several distinct figures:

The employee’s contractual or payroll amount in the agreed currency.
The sterling amount HMRC measures under the cited rule.
The rate source and date used for that tax measurement.
The operational rate used for funding and receipt.
The amount actually credited to the employee.

The tax measurement does not automatically become the payment rate, and the payment rate does not automatically become the taxable amount. The company must preserve the basis for both.

The scope also matters. HMRC gives a different conversion date for earnings taxable on remittance: the remittance date. The entitlement-or-payment rule therefore cannot be extended to every UK earnings category, another jurisdiction, an independent contractor or a different accounting framework.

For the company preparing a UK payroll cycle, a qualified payroll or tax owner should verify the employee’s tax treatment and measurement date. The finance and accounting teams should retain the sterling tax measure, the operational rate and the delivery evidence in the cycle record. Any apparent difference between them then has a documented explanation rather than becoming an unexplained reconciliation item.

Local tax rules determine the taxable currency and date, while an IFRS reporter follows IAS 21 for accounting translation and remeasurement. Those are separate questions, even when they use the same transaction.

Build a payment calendar that meets the due date

A payroll calendar should work backward from the applicable agreed pay date and assign an owner to every handoff: HR input, payroll calculation, funding, approval, release, recipient credit and exception handling. The calendar must distinguish a payment instruction from actual credit in the worker’s account.

Starting with the applicable due date, plan recipient credit, payment release, funding and approval, then payroll inputs and calculation. Confirm credit and assign exception handling. — An editorial planning sequence: assign owners and route-specific buffers. A sent instruction is not confirmation of recipient credit; no universal lead time is implied. Acas: If wages are not paid · CPMI: SWIFT gpi payment timing · CPMI: Payment system operating hours

HR input and payroll calculation cutoffs

Start with the date promised to the worker or contractor, then work backward to the inputs that determine the amount. In the United Kingdom, employers must pay wages on an agreed payday. That UK rule establishes the relevant due date; the backward calendar is the company’s operating method for meeting it.

The calendar should identify the deadline for each class of change:

new and departing workers;
salary, rate or currency changes;
approved leave or other pay adjustments;
corrected hours or work records;
contractor task, acceptance and payment changes; and
changes to recipient or account details.

Each cutoff needs a named owner. HR normally owns worker data and approved employment changes; the payroll or operations team owns calculation inputs; the engagement owner confirms contractor acceptance and the evidence required for payment. A request that arrives after the cutoff needs a defined treatment: hold it for the next cycle, process it under an approved exception, or use another route where the worker and company have agreed terms in advance.

The calculation cutoff should fall after the relevant inputs have been approved and leave enough time for review. The company must also record which currency and rate rule the calculation uses. If an employee’s terms change between cycles, the new contract currency, calculation treatment and reporting treatment need to be visible in the approved input rather than introduced during release.

A late change should not disappear into a chat message. The cycle record should show what arrived, when it was accepted, who approved it and which cycle will carry it. This protects the payroll result from an undocumented manual adjustment and gives the exception owner enough context to communicate the decision.

Funding, approval and release

Funding and approval are separate controls. Finance needs enough time to confirm the required balance in the funding currency; the designated approver needs the calculated obligation, rate, costs and funding request; the release owner needs an instruction that matches the approved cycle.

Work backward through these gates:

Calculation approved: the payroll or contracting record is complete and reconciles to the approved worker terms.
Funding confirmed: finance confirms the required amount, including known spread, fees and expected deductions.
Payment approved: an authorized person approves the release and its route.
Instruction released: the provider or bank receives the instruction with complete beneficiary data and references.
Status monitored: the team records the provider’s status and follows the payment until customer credit or an exception is confirmed.

The record should distinguish the amount approved for funding from the amount sent and the amount received. It should also identify who can approve an exception. A changed beneficiary account, unusual corridor, higher-than-expected fee or incomplete input should trigger a defined review rather than pass through a routine release.

The funding amount should reflect the full expected employer obligation and known route costs. For an employee, statutory deductions change the amount credited relative to gross pay; for a contractor, the agreement determines the payable amount. Neither changes the need to retain the rate, fees and expected receipt.

Payment-system hours can affect the release timetable. CPMI says that aligning operating hours across jurisdictions could speed cross-border payments, particularly where there are significant time-zone differences. That supports checking destination and funding-system hours before setting a cutoff; it does not establish a payroll delivery time or a universal number of days to reserve.

Clearing windows, recipient credit and exceptions

A worker has received pay only when the relevant account is credited. A release confirmation proves that an instruction was sent; it does not prove receipt. In the BIS/CPMI SWIFT gpi study, the observation clock ran from the originating bank’s instruction to the beneficiary bank’s credit of the end customer’s account.

The calendar should therefore include a recipient-credit checkpoint after release. For each route, identify:

the provider’s release cutoff;
the destination and funding-system operating hours;
the status events the provider exposes;
the evidence available when credit is confirmed;
the route-specific clearing buffer;
the person who monitors status; and
the person who handles exceptions.

The SWIFT gpi evidence is historical and route-specific. It covered approximately 20 million confirmed payments from September to October 2020 and found that prolonged processing time was largely associated with the beneficiary-bank leg. It is not a present payroll service-level guarantee. Its practical value is the distinction between release and credit and the need to name an escalation owner for the last leg.

Exception handling should begin as soon as the expected credit checkpoint passes. The owner checks the instruction status, beneficiary details, route and supporting reference. If the payment remains pending, the provider escalates it through the applicable route. If it was rejected, the team verifies the cause, corrects the data through the authorized process and decides whether a replacement payment is safe. The company should not send a second instruction while the status of the first remains unresolved.

Worker communication also belongs in the procedure. If the due date is at risk, the employer should identify what is known, when the next update will come and who owns the next step. A delayed instruction without a status trail leaves the worker and the internal teams working from different assumptions.

The calendar starts with the applicable due date, assigns each handoff and ends with confirmed recipient credit. A sent instruction alone does not close the cycle.

Choose the funding and delivery route

Choose the route by separating two functions: the provider calculates and reports employee payroll, while a bank or payment route carries and delivers the funds. The legal and operating arrangement determines who owns each obligation; the delivery rail moves an amount between accounts. A route that works for employees does not automatically provide the contract and rights records required for independent contractors.

Bank, payroll provider and managed models

A bank route gives the company direct control over funding and delivery, but the company must operate the surrounding payroll process. UK payroll setup guidance describes payroll software as recording employee details, calculating pay and deductions, and reporting to HMRC. The same distinction applies to other jurisdictions: the calculation and reporting owner cannot be replaced by the institution that carries the funds.

A payroll provider can combine parts of the employee process with delivery capabilities. The buyer must still establish which functions the provider performs, which remain with the company and which depend on another bank or service provider. In particular, check:

who calculates gross pay, deductions and net pay;
who verifies worker status and local payroll obligations;
who makes statutory reports and payments;
which entity funds the cycle;
which entity sends the instruction;
which entity confirms recipient credit;
which contract and fees apply; and
who owns an exception or delayed credit.

A managed model may combine calculation, local administration and delivery under one operating agreement. That can reduce the number of handoffs for the company, but it also makes the boundaries more important. The agreement should identify the legal employer or employing entity, the payroll calculation owner, the reporting owner, the delivery route, the worker agreement and the data each party retains. A managed-service label does not establish those responsibilities by itself.

Independent contractors require a separate choice. For that track, the company needs the engagement agreement, task and acceptance records, closing documents, payment terms and any agreed rights. The Contractor Platform at 4dev.com addresses that administration after contractor selection; it does not replace employee payroll calculation, withholding or local reporting.

When comparing models, assess the whole cycle rather than the delivery screen alone:

Decision	Evidence to request
Employee calculation	Calculation inputs, deductions, jurisdiction and approval controls
Tax and reporting	Named reporting owner, applicable scope and supporting records
Funding	Source balance, approval and reconciliation fields
Delivery	Route, currencies, cutoffs, cost components and status visibility
Contractor administration	Agreement, task, acceptance, closing documents and rights terms
Failure handling	Named owner, escalation path, correction and fallback process

The route with the lowest visible delivery charge may still require the most manual work if it leaves payroll, approvals and reconciliation outside one controlled workflow. Conversely, a provider that handles several steps may still fail a particular corridor or recipient account. The right model depends on the obligations and routes the company actually has.

Local coverage, accounts and recipient details

Check coverage against the worker’s location, receipt currency and funding currency. A country name on a coverage list does not establish that every account type, amount band or delivery route works there. Ask for the actual corridors, currencies, transfer sizes and cutoffs that apply to the company’s recurring cycles.

Recipient readiness is part of coverage. The company must know what information the route requires, which fields the provider validates and what happens when an account is unavailable, closed, restricted or still in the verification process. A representative first-cycle test should confirm that the intended local account can receive the planned currency and amount before the provider is made responsible for a live payroll deadline.

I’ve personally launched in a new country where we had unforeseen bank account issues after hiring people, and couldn’t pay them until month two.
— CJ Gustafson, Tech CFO

This personal account illustrates why account readiness belongs in the test plan. It is one CFO’s experience, not a failure rate for a route or a finding about a particular country.

Use a pre-release checklist for each worker group:

confirm the worker’s legal name against the account title;
verify the beneficiary currency and account location;
check whether the route supports the expected amount and payment frequency;
record any provider or bank requirements for account activation;
capture the date when account readiness was confirmed;
retain the source of the recipient data and the person who approved it; and
define what happens if the account cannot be used by the first cycle.

Swift reports that formatting errors, account issues and invalid data accounted for 72% of the payment exceptions it analysed on its network. The source does not disclose the underlying population denominator, so that figure is not a payroll failure rate. It nevertheless supports a practical control: validate beneficiary information before release and retain the validation result with the payment record.

Recipient checks should be proportionate to the route and the change. A previously verified account may still require review after a new payment instruction if the provider’s pre-validation rules identify an inconsistency. The company should know which changes trigger a second approval and who performs it.

Controls, integrations, support and fallback

A route is operable only when the company can see what happened and act when it does not match the plan. The controls should cover the full sequence from input to confirmed credit:

separation of calculation, approval, release and reconciliation duties;
role-based access to worker and recipient data;
validation of beneficiary and payment details;
a complete rate, fee and funding record;
status monitoring after release;
evidence of actual recipient credit;
named exception ownership;
worker communication; and
an exportable cycle history.

Integrations should connect the systems that own adjacent steps without obscuring ownership. A payroll system may feed approved amounts to finance; a bank or provider may return transaction status; the accounting system may receive the recorded amount and exchange rate. Test whether these fields match across systems and whether duplicate or late updates can be detected. An API connection alone does not prove that the teams agree on the status definitions.

Support coverage needs practical boundaries. Ask which channels serve the relevant time zones, who handles an instruction that has already been released, what information the company must provide and whether the provider or the bank owns escalation. The worker should receive a clear internal contact when a payment misses the expected credit date. The company should not tell the worker that funds have been sent when the provider still shows the instruction as pending.

The fallback route should be decided before an exception occurs. It needs an approved owner, available balance or funding arrangement, permitted currency and corridor, recipient-data check and communication plan. The fallback must also preserve the original cycle reference so the finance team can reconcile both instructions and determine whether a replacement is required.

Finally, test the evidence export. The route should expose enough information to reconstruct what was approved, funded, released, charged and credited. If a status export, statement or beneficiary confirmation is unavailable, the company must know how it will obtain that evidence during a review.

Check that the route fits the worker groups and obligations, exposes the complete cost, supports recipient credit and has a defined exception process. A country and currency list alone cannot establish that fit.

Reconcile every currency and record

A cross-currency cycle is reconciled when a reviewer can connect the original obligation to the approved calculation, funding instruction, costs and final worker receipt. The record must also preserve separate tax and accounting measurements and, for contractors, the agreement, evidence of work and agreed rights.

Tie calculation to funding and worker receipt

Reconciliation begins with identifiers that connect every stage of the cycle. At minimum, retain the worker or contractor reference, cycle and payment reference, currency of the obligation, approved amount, funding amount, applied rate, explicit charges, expected receipt, actual credit and status reference.

A practical reconciliation table should contain the following fields:

Field	What it establishes
Worker and relationship	Which employee or contractor record the transaction belongs to
Contract or cycle reference	Where the approved obligation and payment instructions are stored
Contracted amount and currency	What the company agreed to pay
Gross calculation	The amount before applicable deductions
Deductions	The amounts withheld or otherwise deducted, with their basis
Net or payable amount	The amount expected after deductions
Funding amount and currency	What the company debited and from which balance
Rate source and date	Which rate applied to the operational conversion
FX spread	The difference between the stated reference and applied rates
Explicit charges	Provider, bank, intermediary and other separate charges
Expected receipt	What the worker should receive in the receipt currency
Actual credit	What the beneficiary account received
Statement or status reference	The evidence supporting the payment outcome
Approval and exception	Who approved the cycle and how deviations were handled

This record should make differences explainable. If the funding debit exceeds the payable amount, the record needs the applicable deductions and charges. If the credit is lower than expected, it needs the route and fee information. A status that ends with a rejection should retain the correction or replacement decision. Removing the intermediate values leaves finance with two unmatched totals.

Keep the employer’s debit and the worker’s receipt visible together. They answer different questions and can move in opposite directions when a route deducts a fee. A statement that only shows the amount sent confirms funding, not receipt. A confirmation that only shows the amount received does not explain how the obligation was calculated or approved.

For recurring payroll, reconcile at two levels. The cycle-level comparison ties the approved population and total to the funded instruction, returned status and actual credits. The per-worker record explains each individual difference. A balanced total can conceal one incorrectly paid worker, so the operational exception report and the financial reconciliation serve different purposes.

UK PAYE employers must retain records of employee pay, deductions, HMRC reports and tax payments, and those records must demonstrate accurate reporting. The detailed cross-currency field set above is an operating control rather than a statutory HMRC schema, but it preserves the evidence needed to support that reporting trail.

Keep tax and accounting rates distinct

The operational rate answers which rate was used to fund and deliver the payment. The tax rate answers how the jurisdiction measures the taxable amount. The accounting rate answers how an IFRS reporter translates and remeasures the transaction. They may coincide in a cycle, but the record should never assume that they will.

For the cited UK foreign-currency earnings taxable when received, HMRC measures the sterling amount at the entitlement date or, if earlier, the payment date, using the rates then in operation. HMRC provides a different date for earnings taxable on remittance. The company therefore needs to preserve the tax treatment and measurement date selected by its qualified UK payroll or tax owner.

For IFRS reporters, IAS 21 requires initial recognition of a foreign-currency transaction using the transaction-date spot rate. Foreign-currency monetary items are later translated using the closing rate at each reporting date. Exchange differences on settlement or retranslation generally require recognition in profit or loss, subject to the exception in the standard. These requirements come from an IFRS Foundation staff paper reproducing the issued standard; they apply to entities applying IAS 21, not to every company.

Keep the following fields separate:

operational conversion rate and date;
applicable local tax currency and measurement date;
transaction-date rate for initial accounting recognition;
closing rate for later monetary-item translation;
exchange difference recognized on settlement or retranslation; and
accounting treatment approved under the entity’s reporting framework.

This separation also prevents a reporting error when the provider’s rate changes. If the provider applies a new rate at release, that operational change does not alter a previously calculated tax measure or the accounting treatment. Any correction must identify which field changed, who authorized it and which downstream record was updated.

A rate policy should define which rate applies to each purpose, but it cannot choose a tax rule or an accounting standard. The tax adviser owns the jurisdictional treatment; the accountant owns the reporting treatment; payroll and finance own the operational conversion. Reconciliation should show the basis for all three.

Preserve contractor work and rights evidence

A contractor payment is reconciled only when the financial amount is connected to the engagement that created the obligation. The supporting record should identify the payee, amount paid, proof of payment, date incurred and description of the service received. US business-expense guidance states that supporting documents should contain those details and that a combination of documents may be needed.

Currency reconciliation does not establish why the company owed that amount or what rights it received. Preserve the contract, task, acceptance or completion record, closing document and payment record as one reconstructable trail.

US business-expense recordkeeping guidance supports the financial link but does not settle ownership of the work. Rights require a separate contractual check. In the United Kingdom, copyright in commissioned work normally starts with the creator unless ownership is otherwise agreed in writing; an implied licence may exist without transferring ownership. The task or engagement terms should therefore state whether rights in the deliverable transfer and on what terms.

For 4dev.com contractor records, the Contractor Platform keeps tasks, statuses, agreements, closing documents and engagement history in one register.

The reconciliation should preserve:

the agreement or task that defines the work;
the currency, amount and payment terms;
the evidence that the work was completed and accepted;
the closing document supporting the engagement;
the applicable rights term;
proof of payment and the amount credited;
any exception or correction; and
the link between the contract record and the finance record.

Another difficulty, of course, is exchange rates, getting meaningful data from a combination of currencies
— Stuart Hough, Global Payroll Manager at Blue Prism at the time of the interview

That reported difficulty concerns meaningful reporting across currencies. The contractor track adds another requirement: the money record must remain connected to the work and rights record. Without that link, finance can prove that a payment occurred but cannot explain what the company received for it.

Test the operating model with a real cycle

Test a multi-currency payroll model with a representative cycle rather than a list of feature claims. The pilot should cover the actual worker group, currencies, corridor and amount band; compare quoted and received amounts; confirm beneficiary credit; and produce evidence that the team can use to reconcile, manage exceptions and communicate with workers.

A representative-cycle pilot

Define the pilot before selecting the provider or route. A test is representative only when it reflects the arrangements that will run in production. For an employee cycle, include the applicable jurisdiction, worker status, pay terms, statutory deductions and promised date. For a contractor cycle, include the engagement agreement, task, acceptance evidence, payment terms and any rights requirement.

Run separate tests when the routes differ materially. One payment does not establish coverage for another funding currency, receipt currency, corridor, amount band or account type. If the company expects to use several routes, test each one or define a smaller set that represents the recurring population.

The pilot should measure five outcomes:

Outcome	Evidence to capture
Correct calculation	Approved input, gross or payable amount, deductions, expected receipt and worker agreement
Complete cost	Applied rate, FX spread, explicit charges, receiver-side treatment and total employer debit
Recipient credit	Amount and date credited to the worker’s account, with a provider or bank reference
Timing	Instruction, release and credit timestamps compared with the applicable due date
Evidence and exceptions	Status history, error reason, escalation owner, correction, worker communication and final reconciliation

Confirm recipient credit rather than treating a sent instruction as payment. The BIS/CPMI SWIFT gpi study used the point at which the beneficiary bank credited the end customer’s account as the end of its observed payment clock. That historical study does not establish a present payroll delivery time, but it provides the right control for the pilot: verify what reached the worker’s account.

Include a reconciliation before the pilot is accepted. Tie the approved obligation to the debit, every known cost, the expected receipt and the actual credit. If those amounts differ, record the cause and whether the evidence supports it. A provider’s status message alone is not a substitute for the beneficiary confirmation or statement required by the company’s finance process.

A successful pilot shows that the arrangement worked for the tested corridor, amount and worker group. It does not establish performance for untested routes or guarantee future receipt dates.

Questions to ask before changing providers

Ask providers to demonstrate the operating model with the company’s facts rather than describing it in general terms. Include the worker group, countries, currencies, recurring amount, funding source, reporting needs and due date in the request.

For coverage and quoted economics, ask:

Which worker relationships, countries, currencies and recurring corridors does the proposal cover?
Which calculations, deductions, tax reports and statutory payments does the provider perform, and which remain with the company?
What are the applied rate, reference rate, FX spread and explicit fee for the proposed corridor and amount?
Can any intermediary or recipient-side charge reduce the amount credited to the worker?
Which costs vary by amount band, currency, route or cycle frequency?
Does the quote expire before the company’s approval and release process is complete?

For the calendar and delivery, ask:

What are the cutoffs for worker inputs, funding, approval and release?
Which payment-system hours and destination-country restrictions apply?
What status events are exposed, and when is recipient credit confirmed?
What buffer does the provider recommend for the tested corridor?
How are weekends, local holidays and cutoff changes communicated?

A provider should identify timing information that applies to the tested route rather than present a generic processing promise. CPMI’s analysis of operating-hour alignment explains how time-zone differences can affect cross-border payments, but it provides no payroll lead-time guarantee.

For controls, records and support, ask:

Which data does the provider collect, retain and export?
Can the company retrieve the calculation, rate, fees, approval, status and beneficiary confirmation for each cycle?
What beneficiary details are validated before release, and what triggers a second approval?
Which roles can change a recipient, amount, currency or route?
Who handles a rejected, delayed or misdirected transaction, and through which support channel?
What happens to records and open exceptions if the company changes providers?

For implementation evidence, ask:

What information must the company provide for the first productive cycle?
How are local accounts, currencies and worker data validated?
Can the company reproduce one completed cycle from an exported record?
Which implementation tasks and cutoffs are required for the first cycle?
Can the test cover both an employee and a contractor arrangement without treating their records as one payroll population?

These questions should produce testable answers and named owners. A feature list does not show whether the arrangement fits the actual corridor or whether the company can reconstruct the result.

What to do when a transaction fails

Treat a failure as a process with an owner, status and next action. The first step is to establish what happened: rejected instruction, pending instruction, delayed beneficiary credit, misdirected credit or a completed credit that differs from the expected amount. Do not send a replacement while the status of the original instruction remains unresolved.

The response should follow the payment stage:

Identify the failing step. Compare the payment reference and status with the funding instruction, beneficiary data, route and calculation.
Validate the available evidence. Check the provider’s error, the beneficiary details, the amount and currency, and the expected credit checkpoint.
Escalate through the route owner. The provider handles the transaction it submitted; the company supplies the calculation, approval, beneficiary details and reference.
Correct the cause through the authorized process. Do not overwrite an instruction or create a duplicate without confirming that the route permits it.
Reconcile every resulting entry. If a replacement or returned amount appears, link both records to the original cycle and net them correctly.
Communicate with the worker. State what is known, what action is underway and when the company will provide the next update.
Close the exception. Retain the reason, owner, timestamps, evidence, decision and final accounting treatment.

Swift reports that formatting errors, account issues and invalid data accounted for 72% of the payment exceptions it analysed on its network. The source does not disclose the population denominator, so this is not a payroll failure rate or a forecast for a particular provider. It is a reason to validate beneficiary data and monitor exceptions before release.

Reversal depends on the route and payment stage. Swift describes a stop-and-recall process for eligible Customer Credit Transfer payments with an active tracking reference, but the existence of that process does not establish that funds can be recovered after customer credit. Contact the provider promptly, preserve the reference and ask what recovery options remain available for the actual transaction.

The pilot should include at least one test of the exception workflow. It should show who detects the issue, who can correct it, how the worker is informed, what records remain after the incident and how finance prevents a duplicate or unexplained balance. A provider with a workable normal cycle still needs a controlled answer when the payment fails.

Frequently asked questions

Is multi-currency payroll the same as multi-country payroll?

No. Multi-currency payroll concerns the monetary side of a cycle: the amount promised, the calculation currency, the conversion point, the worker’s receipt and the rates and costs recorded. Multi-country payroll concerns the employment, tax, reporting and payment rules of each jurisdiction.

The two can overlap. A company paying employees across several countries may need both, but it must handle them as separate decisions. First establish each worker’s relationship and applicable jurisdiction. Then define the currency terms, local payroll duties, funding route and reconciliation records for that worker.

Are contractor payments part of employee payroll?

No. Employee payroll generally includes calculation, withholding, reporting and pay-date obligations. Independent-contractor administration relies on an engagement agreement, evidence of the service, payment terms and any applicable rights documentation.

Contractor amounts may enter the company’s financial records and cash flow, but that does not turn the engagement into employee payroll. Currency choice does not determine worker status: US federal guidance examines behavioral control, financial control and the relationship between the parties, while UK guidance states that employment-rights classification follows the reality of the working relationship.

For contractors, preserve the agreement, task, acceptance or completion evidence, closing document, payment record and agreed rights treatment alongside the amount charged.

Can an employee receive pay items in different currencies?

It depends on the employment agreement, the applicable jurisdiction’s wage rules, the tax treatment and the payroll provider’s capability.

Do not assume that the ability to calculate or deliver several currencies resolves the question. A qualified payroll or legal owner must verify whether the arrangement is permitted, how each component is measured for tax and reporting, and how the employee receives and understands each amount. The company should also document the promised currency, amount, frequency, deductions and applicable pay date for every component.

Can a foreign-currency balance fund salaries?

A foreign-currency balance may provide funding for a cycle when the company has that balance and the route permits the required conversion and delivery. Whether the company may maintain or use that balance for the purpose is a separate question requiring treasury, tax, accounting and legal review.

Before using one, confirm the applicable local rules, the company’s treasury and accounting treatment, the available balance, the funding currency, the conversion route and the treatment of gains or losses. Preserve the funding amount, rate source, date, fees and final worker receipt in the cycle record.

Can an international payroll payment be reversed?

Sometimes a payment can be stopped or recalled, but reversal is not guaranteed. The available action depends on the route and the payment’s stage. Swift describes a stop-and-recall process for eligible Customer Credit Transfer payments with an active tracking reference, yet the existence of that process does not establish that money can be recovered after customer credit.

If a payment appears failed, delayed or misdirected, contact the provider promptly with the payment reference and ask which recovery or correction options remain available. Do not issue a replacement while the original instruction’s status is unresolved. Preserve both records if a return or replacement occurs so finance can reconcile the cycle without duplicating the expense.

How do you record a foreign-currency payroll transaction?

Record the obligation, calculation, rates, funding, charges, delivery and receipt as a connected trail. At minimum, retain the worker reference, contractual amount and currency, gross calculation, deductions, net or payable amount, funding amount, rate source and date, FX spread, explicit charges, expected receipt, actual credit, approval, status and statement reference.

Keep three rate purposes separate. The operational rate supports funding and delivery. The local tax rule determines the taxable currency and measurement date. The accounting framework determines translation and remeasurement. For IFRS reporters, IAS 21 uses the transaction-date spot rate for initial recognition and the closing rate for later monetary-item measurement; local tax treatment and exchange differences still require their own review.

The completed entry should let a reviewer reconstruct why the amount was owed, what the company funded, what the worker received and which difference arose at each stage.