Global Payroll

What does global payroll include—and what does it not?

Global payroll connects local pay runs across countries. The local calculation, cross-country coordination and movement of money remain distinct tasks.

How is it different from local payroll and international payments?

Local payroll calculates and records employee pay under the rules that apply to a particular workforce. A global payroll process coordinates two or more such runs: it brings together the employee data, change approvals, pay calendars and results so the organization can see what is due in each country. “International payroll” and “multi-country payroll” are often used for the same coordinating work. The global view does not replace the local calculation or make one country’s deductions and reporting rules apply everywhere.

Consider a company with employees in the UK and the US. It could collect changes through one HR system and review both runs in one dashboard, yet the UK employer still has PAYE pay-recording, deduction, reporting and HMRC-payment tasks, while the US employer has its own federal employment-tax deposit and reporting duties. The shared system tells the team what happened across both workforces; each local run must still produce the outputs its rules require. This example covers UK and US federal duties, not every requirement in either country.

Caption: Illustrative UK and US employer routes. Shared coordination does not replace local calculations, reporting or remittance; other countries and subnational rules need separate checks. HMRC: Running payroll · IRS: Depositing and reporting employment taxes

An international payment service handles the movement of money, sometimes with currency conversion. It can transfer the approved net amount, but the transfer itself does not calculate withholding, produce payroll records, or make statutory reports and remittances. The UK tasks above illustrate why a successful employee payment is only one checkpoint. Paying a genuinely self-employed UK contractor’s invoice is outside employee PAYE; the invoice or the word “contractor” alone does not establish that status under UK employment-status guidance.

When evaluating a service described as global payroll, ask which part it actually performs in each country: local pay calculation, statutory filing and remittance, cross-country coordination, or the payment transfer. A single dashboard or payment provider can cover some of those steps without taking responsibility for the others.

Where do EOR and contractor payments fit?

Who employs the person determines the payroll route. A company employing someone through its own local entity can run that employee’s payroll itself or hire a processor for some of the work. Outsourcing processing does not, by itself, change the employer. For example, the IRS says a US employer using an ordinary payroll service provider generally remains responsible for its federal employment-tax obligations; the result depends on the actual third-party payer arrangement.

An employer of record (EOR) is a different route: in an arrangement permitted by the relevant country’s law, a third party is the legal employer and handles local employment payroll for the worker assigned to the client. A UK government report describes this legal-employer model and cautions that using it does not automatically resolve every cross-border risk. Before treating an EOR service as the payroll solution for a country, check the employment contract, the entity that will run and report pay, and the responsibilities retained by the client. A professional employer organization (PEO) is not an interchangeable label: the employing and tax arrangements need their own local review.

A genuinely independent contractor billing for a deliverable follows a separate payment relationship. The client may approve an invoice and send a cross-border payout through the same platform that displays employee costs, but that payout does not turn the invoice into employee payroll. In the UK, government guidance says a self-employed person is outside employee PAYE while a person called a “contractor” may in fact be self-employed, a worker or an employee. The working facts and applicable local rules determine the status, not the invoice or software label.

For a proposed hire, name both the legal employer and the owner of pay calculation, filing and payment. An employee of the company’s own entity, an employee of an EOR, and an independent contractor can all appear in a consolidated workforce view, yet they need different employment and payment instructions. That check prevents a convenient payment route from obscuring who must carry out the local payroll duties.

How does a multi-country payroll cycle work?

Each country needs a workable local run, from approved employee data through payment and statutory outputs. The cross-country process gives those runs a shared calendar and a way to see missing inputs or unfinished tasks before they affect pay.

What must be in place before the first run?

Start by establishing who employs the workers and who is authorized and equipped to run payroll in that country. For each location, identify the employer or EOR arrangement, the local team or processor that will calculate pay, and the person responsible for filings and payments to authorities. These are separate assignments: buying software or a transfer service does not itself establish an employer arrangement, a payroll registration, or a filing owner.

Country setup varies. For a UK employer, HMRC says registration is normally needed before the first payday and explains what to do if the PAYE reference has not yet arrived. That is a UK example, not a universal rule that every country uses the same registration or that pay must always wait for an issued number. Before starting a new country run, the team should establish which local accounts, reporting routes and records apply there, with local payroll expertise where needed.

Then make the first pay calendar operational. Record the pay period and payday, the cut-off for HR and time data, the date a local processor needs the approved inputs, and when finance must make funds available. Assign an approver who can resolve a missing starter record or an unexpected change before the calculation is finalized. The timetable should also identify who confirms that employee pay and any local reporting or remittance have actually completed; their dates and procedures must be checked locally.

For example, if a company is adding its first UK employee, HR needs a route to provide the starter and pay details to the payroll owner, finance needs the funding instruction and deadline, and the employer needs its PAYE reporting route. The team should be able to trace a starter or hours change from the source HR or time record through approval, local calculation and accounting output. A dashboard entry cannot fill a missing handoff owner before the first run.

How do inputs become country-specific gross-to-net pay?

The local payroll owner needs an approved record of who is being paid, where the work is performed, and which pay items belong in the period. HR supplies starts, departures, contract pay and changes in work location; time or leave records supply hours and absences; approved bonus, allowance and benefit changes may come from other owners. Each item needs an effective date and a source that can be checked. A shared HR system can distribute those inputs; the local payroll owner must determine their treatment under the country’s rules.

Gross pay is the pay for the period before employee deductions. The local calculation applies the deductions and withholding required for that employee and produces the net amount to be paid. Any employer contributions or other employer-side amounts need separate treatment in the employer cost and remittance records; they should not be mistaken for money withheld from the employee’s net pay. In the UK, HMRC identifies wages, bonuses and statutory payments among payroll pay items and explains that deductions depend on employee circumstances. The treatment of a particular allowance, benefit or absence still needs a local check.

Suppose HR approves a bonus for one employee in the UK and one in the US. The shared input can carry the approved amount, pay period and effective date to both teams, but it cannot supply a universal gross-to-net result. Each payroll owner applies the local treatment and records the employee deduction and any employer amount in that country’s run. The US federal employment-tax deposit and reporting duties also differ from the UK PAYE route; neither example covers every state or local requirement.

An input arriving after cut-off needs a decision before it is silently carried into the old settings. If a UK employee starts working abroad and a bonus is submitted late, the payroll owner should confirm the work dates and applicable pay treatment with the local specialists, then decide whether the run can still be changed or whether a documented correction is needed. HMRC says an employee going to work abroad may need to be reported as a change; PAYE Income Tax and National Insurance require separate checks based on destination and expected duration. A foreign bank account or the bonus payment currency does not settle those questions.

How are approvals, funding, payments, filings, and corrections handled?

After calculating pay, the country owner should compare the run with approved changes and investigate exceptions before signing it off. That review can catch a missing starter, an unexpected net-pay change or a payment account edited after the cut-off. Finance then needs the approved employee-payment amount and any separately scheduled authority payments, with enough time to fund the relevant accounts and payment routes. The approver, funding owner and local processor should each know when their part is complete and who can stop or amend a run.

Approval of the calculation is only one completion point. In a UK PAYE run, HMRC separates pay recording and deductions, the Full Payment Submission, and payment to HMRC. Employees must also receive a payslip showing gross pay, deductions and net pay on or before payday. The team should therefore verify the employee net-pay transfer, payslip, authority remittance and report as distinct outputs. Forms, timing and responsibilities must be checked for each other country.

Caption: UK PAYE example. These are separate completion checks; the diagram does not set a universal order or deadline for other countries. HMRC: Running payroll · HMRC: Payslips

Reconcile what was approved against what actually happened: the payroll totals, bank confirmations, statutory-payment records and accounting entries should agree, or the difference should have an owner. A bank file can be rejected because beneficiary details are wrong even when the pay calculation is correct; Swift describes missing or incorrect account data as a cause of payment rejection. In that case, the payment owner needs to trace the rejection, correct the details through an approved route, reissue or arrange the payment, and confirm receipt. The payroll owner should check whether the delay or any changed pay information also requires a local reporting correction rather than assuming a resent transfer closes the case.

Employee questions and corrections belong in the same control trail. Record the reported problem, the original approved input, who changed it, the corrected pay or payment outcome, and whether a filing was amended. For example, HMRC provides correction routes for errors in UK FPS or EPS information; the applicable route depends on the error and period. Keeping the approval and correction evidence lets the next run start from a known result instead of repeating an unresolved difference.

What improves when payroll is coordinated across countries?

Coordination can make missed inputs and unfinished work visible before payday. A shared calendar shows when each country needs approved changes and funding; a common exception log shows which owner must resolve a late bonus, missing starter record or rejected payment. That gives the team time to act across local runs, although it cannot guarantee on-time pay when the underlying data, local calculation or payment route fails.

Comparable local outputs can also give finance a useful consolidated view. Suppose one country sends gross pay, employee deductions and employer contributions, while another sends only the amount transferred to employees. Adding those figures would mix different measures. If both teams agree on the categories, reporting period and currency-conversion method, finance can compare employer cost or net pay across countries and trace a change back to its approved source. The same mapping can reveal an unexplained difference in a country total. The comparison depends on complete local records and an agreed treatment of exchange rates and transfer costs; a dashboard cannot make unlike figures equivalent by displaying them together.

Employees need accurate, timely pay and a clear way to resolve questions. A shared process can track whether a payslip was issued, a payment was confirmed and an employee query reached the local person who can answer it. If the arrangement includes employee self-service, test whether workers can retrieve their locally produced pay information and reach a country owner for corrections. The local team still needs to fix the underlying record. Standardizing the route for questions may reduce handoff confusion, but it does not replace local support or settle a country-specific pay dispute.

Using the same change identifiers, approvers and completion checks across countries can make an audit trail easier to follow: the team can connect a source change to the approved calculation, payment, filing and any correction. This benefit depends on staff recording decisions and closing exceptions, not merely adopting common software. HMRC’s UK payroll guidance distinguishes employer record keeping from the varying tasks a provider may perform; that division is a useful reminder to name the owner of each local output before expecting a consolidated process to improve it.

Why do country differences make global payroll difficult?

Shared calendars and data feeds still require local decisions about each employee’s pay, deductions, payment and records.

Which pay, tax, social-security, and reporting rules vary?

A second country cannot safely inherit the first country’s payroll settings. The local owner needs to confirm how the pay period, hours, overtime, leave, bonuses and benefits affect gross pay, which employee deductions and employer contributions apply, what the payslip must show, and which authority receives each report or payment. These are distinct checks: an income-tax instruction does not by itself settle social-security contributions or an employment-law entitlement. A common HR code can carry the same approved bonus amount to two countries while the local teams determine its treatment and required outputs separately.

In a UK PAYE run, HMRC describes recording pay, calculating deductions, submitting a Full Payment Submission and paying HMRC; UK payslips must show gross pay, deductions and net pay on or before payday. The IRS describes separate US federal employment-tax deposits, employer returns and W-2 reporting. US state and local requirements need their own check. A UK reporting field or deadline cannot simply be copied into the US run, even when both runs use the same HR system.

For a new country, compare the required tasks: which pay items need local interpretation, who determines income-tax withholding and social-insurance treatment, what must appear on the employee’s pay record, and who files and remits each amount. In a UK case, pension treatment and the effect of an inbound or outbound assignment are additional questions for the relevant local specialist; the UK example does not supply a worldwide answer. Work across borders can also call for separate advice on tax residence, employment conditions or a possible corporate establishment. Payroll data may alert the team to those questions, but a completed pay calculation does not decide them.

What changes with currency, banking, deadlines, and data transfers?

Pay calculation and payment routing introduce different variables. Payroll needs the approved pay currency and net amount; finance needs to know the currency in which it will fund the payment and, if conversion is involved, which rate or valuation method applies to its records. The bank route can then add transfer or receiving charges and a separate arrival time. These effects depend on the contract, accounts and route, so a change of bank or currency should trigger a check of the amount due, the transfer terms, who bears any charges and the expected receipt date. The ECB’s own staff bank instructions warn of possible receiving and currency-conversion charges and delays for certain accounts; they do not set a rule for other employers.

Suppose an employee’s approved net pay is in euros but a new payment instruction sends it to an account in another currency. Before releasing the file, compare the approved net amount and pay date with the conversion and fee terms of that route. Afterward, compare the bank confirmation and amount actually received. If the employee receives less or later than expected, trace the currency conversion, charges, account details and funding cut-off before changing the payroll calculation. A correct calculation does not resolve a transfer issue, and an incorrect beneficiary detail can cause rejection, as Swift’s payment guidance explains. The employer’s agreement and local rules determine whether the payment outcome requires a further payroll action.

HR, time, local payroll and payment systems may hold different versions of a work location, bank detail or effective date. Name the authoritative source for each field, record who approved a correction, and ensure the local team can retrieve the underlying pay record even when headquarters sees a consolidated total. A country owner still needs to inspect the local calculation and answer an employee’s pay question in the relevant language.

Access and transfers also need a scoped privacy check. For UK worker records, the Information Commissioner’s Office calls for access limited to authorized people and appropriate security, accuracy and recoverability. If payroll personal data from the EU/EEA is actually sent outside the EEA, the European Commission describes the safeguards required for international transfers. A multinational organization or shared interface alone does not prove such a transfer occurred; check where the data goes, who can use it and which mechanism applies before assuming the setup is covered.

What happens when an employee works across borders?

The payroll instruction can change even if the employment contract, bank account and salary currency stay the same. Where and when the employee actually works may require separate checks of tax withholding, social-security coverage and local reporting.

How should a cross-border assignment change payroll instructions?

Treat a posting or regular work in more than one country as a change to investigate before the next run. Record the physical work locations and dates, expected duration, legal employer, entity paying the salary and any host organization. Then ask the home and host payroll specialists which income-tax, social-security and reporting instructions apply. The answer to one question does not settle the others: a home-country payroll record or a familiar salary currency is not evidence that every deduction can stay as it was. Keep the approved instruction and its supporting coverage or authority correspondence with the employee’s payroll record so a later change in schedule can be reassessed.

EU postings and multi-country work

For a worker sent temporarily from one EU country to another, social-security coverage may remain in the sending country if the posting qualifies under EU coordination rules. The European Commission says the employer should apply to the competent institution for a PD A1 certificate of coverage. Payroll can use the institution’s documented coverage and its applicable period to direct social-security contributions; it should not assume that every trip qualifies or apply a fixed duration rule without checking the conditions. The A1 concerns social security. It does not decide income tax, host employment conditions or immigration permission.

Regular work in several EU countries calls for a different social-security determination from a single temporary posting. The Commission describes a process in which the institution in the worker’s country of residence receives contracts, schedules and other work-arrangement details and the relevant institutions coordinate the applicable social-security law. The payroll owner should provide the actual work pattern and seek that determination rather than choose a contribution country from the headquarters address, payment currency or an assumed percentage of days. If the pattern changes, the underlying instruction may need review. The evidence needed and outcome depend on the case.

Caption: EU social-security coordination only. Eligibility and the applicable country require institutional review; this does not settle income tax, employment law or immigration. European Commission: Social-security contributions

UK employees working abroad

When a UK employee begins working abroad, the UK payroll owner needs the destination and expected duration before changing deductions. HMRC addresses PAYE Income Tax and National Insurance in separate parts of its overseas-employee guidance; coverage certificates and international arrangements may affect the National Insurance question without settling income tax. The owner should check both routes against the employee’s facts and seek host-country advice where relevant. A foreign bank account or payment in another currency is not a reason by itself to stop UK PAYE.

For example, if a UK employee is assigned to work abroad for a defined period, HR should pass the work dates, destination, employer and pay source to payroll before the next run, even if the employee remains on the same salary. HMRC says an employee going to work abroad may need to be reported as a change. The team can then record who will review the UK tax and National Insurance instructions, whether a host payroll record or other local action is needed, and what evidence supports the decision. This is an intake and review step, not a predetermined tax-code or treaty outcome.

When can payment and local payroll reporting split?

Salary payment and local payroll reporting can fall to different parties in certain UK inbound secondments. HMRC says that, in its inbound-secondment circumstances, a UK host that does not actually pay an employee who remains employed by an overseas business is treated as the employer for recording and reporting the worker’s earnings and PAYE deductions. Its guidance covers, among other cases, an employee assigned to work wholly or partly in the UK for a UK resident employer while remaining employed overseas. The rule applies to HMRC’s described UK arrangements; it does not cover every international visit.

The host’s UK payroll record and the overseas net-pay transfer serve different purposes. A reporting or “shadow” payroll can account for local earnings and PAYE without instructing a second salary payment to the employee. The team still needs to decide the correct UK reporting route and reconcile the overseas pay information with the UK record so earnings are not omitted or paid twice. National Insurance needs its own check; a PAYE decision does not establish which social-security system applies.

Caption: HMRC's qualifying inbound-secondment circumstances only. The UK reporting path does not imply a second salary payment; National Insurance needs a separate check. HMRC: New employee coming to work from abroad

Consider an employee who stays on the overseas employer’s payroll during an assignment to a UK host. Before marking the employee “already paid” in a global dashboard, the two payroll owners should exchange the work dates, employer and host details, pay components and payment evidence. The UK owner can then determine whether HMRC’s secondment conditions apply, who records and reports the earnings and deductions, and how any local tax due is handled. The overseas payment confirmation answers whether the employee received salary; it cannot by itself prove that the UK PAYE record is complete. Keep the local conclusion and its supporting facts with the assignment instructions, and revisit it if the work pattern changes.

How can organizations run global payroll?

A company may use one provider for several countries or coordinate its own teams and local providers. In either model, someone must own each local run and consolidate its results.

When is in-house or local-provider payroll workable?

An organization with an established employer arrangement and country expertise can calculate and administer a local run through its own payroll team. It can instead use a separate in-country processor for some or all of the work while retaining people who supply employee records, approve results and check completion. In the UK, HMRC explicitly allows an employer to use its own payroll software or a provider and says the employer remains responsible for PAYE tasks even when it pays someone else to do them. That responsibility statement is UK-specific; the contract and local law need checking elsewhere.

Separate local providers may suit a company that already has a working route in each country or needs local support for different pay cases. The trade-off is coordination: providers can use different input formats, cut-off dates, pay categories and ways of returning results. Someone inside the organization must maintain a common calendar, translate HR and time data into each provider’s requirements, obtain country sign-offs and map the outputs into comparable finance records. The local provider still needs a named contact for a late change, rejected payment or filing correction.

For a two-country employer, one team could run the UK payroll and another provider could process the US run. This can be workable if a central owner knows which team calculates and files in each country, receives evidence that pay and statutory tasks finished, and reconciles figures using agreed definitions. The choice turns on the actual workforce, local capability and handoff workload, rather than a fixed employee-count threshold. A small payroll can still need specialist help when the country rules or a cross-border assignment are unfamiliar.

What do a single provider, aggregator, and hybrid model change?

A single-provider arrangement gives the organization one main service relationship for multiple countries. The provider may run selected local payrolls through its own teams, yet it may use other processors in some locations. Ask where that boundary lies: a single contract or dashboard does not establish that one engine calculates every country’s pay, that the provider employs the workers, or that the same party makes every filing and payment.

An aggregator places a coordination and reporting layer over country processors. Local partners may calculate pay and handle statutory work while the aggregator receives their outputs, applies common categories and provides a consolidated view. That view depends on the central service and country operator handing results and exceptions between them. The contract needs to say who checks the source data, signs off the local result, stores the detailed record and can act when an authority rejects a filing.

In a hybrid arrangement, the employer may keep a trusted local provider in one country and use the broader service for another, while feeding both results into common reporting. It can preserve a working local route, but someone must map different cut-offs, pay categories and evidence into the shared process. “Hybrid” does not specify which party sends employee pay or answers a local worker’s question; those tasks need assignment country by country.

Test the operating model against an exception. If a filing in one country is rejected or payday is at risk, who receives the first notice, who has access to the local record, who corrects and resubmits, who funds or reissues the payment, and who informs the employer and employee? A proposed provider should be able to walk that path for a country it handles directly and for one handled through a partner. Its answer reveals the actual operating model more clearly than a claim of global coverage.

How should a team select and control a global payroll approach?

Evaluate each country route by the tasks it performs, the evidence it returns and the support available when a run fails. Then check those tasks after launch.

What should provider and country coverage checks prove?

Coverage should mean a defined route for each part of the actual workforce. List the countries where employees work, the legal employer arrangement in each, and any planned expansion. Keep genuinely independent contractor payouts separate from employee payroll, and identify where an EOR arrangement would change the employing entity. For every employee route, ask whether the proposed service calculates pay directly or through a country partner, who files and remits locally, who sends net pay, and who can answer an employee or authority query. A broad country list does not answer those questions.

Test the route with a real scenario from a target country. Give the provider a new hire with a later bonus, leave change or departure and ask it to show how HR data enters the run, who checks the local treatment, who approves the calculation, and what evidence shows the employee payment and applicable filing or remittance completed. Then change one fact after cut-off or assume a filing is rejected. The useful answer names the person who detects it, the party with access to the local record, the correction path and who confirms closeout. This is an operational test for the proposed arrangement, not a universal legal checklist.

The test should match the contract and implementation plan. If a partner handles a country, find out what information reaches that partner, which outputs return to the central team, and who escalates a missed payday. Check that the HR and time fields, pay categories, approval cut-offs and reporting format can be mapped before the first live run. A planned new country or a mobile employee may need a different route from the one demonstrated for current staff; treat it as separate coverage until the local process is shown. In the UK, HMRC advises employers to decide what level of support they need from a payroll provider because the tasks a provider handles can vary.

How should data, security, costs, and support be evaluated?

Ask each provider to trace one change from the authoritative HR or time record through the local payroll calculation, payment file and finance output. The answer should identify which system owns work location, pay rate, hours and bank details; how often each interface runs; who can approve or reverse a change; and how the local record can be retrieved if a summary figure is challenged. Test a corrected bank detail or late bonus, not just a clean file import. An automated anomaly flag may help a human reviewer find an unexpected amount, but it does not establish that the source data or local legal treatment is correct.

Test permissions with the same scenario. A central analyst may need comparable totals while a country payroll specialist needs employee-level records and correction rights. For UK worker data, the ICO calls for access limited to authorized people and for secure, accurate and recoverable records. Ask which staff and country partners can see or change the underlying data, where it is stored, and how an employer obtains it during a dispute or provider handover. If EU/EEA payroll personal data will actually be sent outside the EEA, ask which international-transfer safeguard described by the European Commission supports that route; a shared dashboard alone does not prove that such a transfer occurs.

Compare proposals against the same country pay cycle and a failed payment. Request the full charge schedule: setup and integration, per-worker processing, local partner work, corrections, FX conversion or spread, transfer fees and support outside the routine run. Ask which charges are fixed, which depend on volume or currency route, and who pays fees that could affect the amount received. This is a way to compare the offers, not an assumption that every provider uses each fee. The operational answer matters alongside the price: who can inspect the local pay record, speak to the employee in the needed language and time zone, trace a failed transfer, and authorize the fix? A lower processing quote is less useful if those tasks are outside the purchased service or have no named owner.

What should implementation and recurring controls test?

Before the first live run, assign an approver to each country route and test it with employee and pay data checked against the source records. Follow one normal case and one exception, such as a late pay change or rejected payment, through calculation, approval, bank release, local filing and correction. Confirm that the employer, local provider and any central service agree on who receives an error and who can act on it. Assign an owner for employee questions and someone with local expertise to monitor relevant rule changes and approve any resulting payroll-setting change before it is used.

For each subsequent run, reconcile the approved gross and net totals with the employee payment confirmations, applicable authority remittances, filed outputs and finance ledger. A dashboard status is not evidence that all of these finished: a payment can fail after the calculation is approved, or a local report can remain unaccepted. Keep the local confirmations and the person who reviewed them accessible so the team can tell a timing difference from an unresolved error.

A US employer using an ordinary payroll service provider or reporting agent has a concrete deposit check. The IRS says these arrangements generally leave federal employment-tax obligations with the employer and recommends checking deposits through EFTPS. That is a US federal control for those payer arrangements, not a worldwide portal or a rule for every third-party payer. The broader question for each country is who can independently verify that required filings and remittances actually reached the authority.

If the dashboard shows “complete” but the bank or authority rejects an output, record the affected employees or filing, appoint the correction owner, and establish the next action and its local deadline. After reissue or resubmission, close the case only when the payment or filing has a confirmed outcome and the employee and finance records have been updated. Review recurring measures by country—late or incorrect pay, corrections, rejected outputs and open employee queries—alongside the underlying records. Test that those records and the correction history can be handed to a replacement local team or provider; otherwise the next run may inherit an unresolved problem.