The move from “we hired someone in Belarus” to “we can close our monthly books cleanly with Belarus data in them” is where most foreign HQs quietly lose weeks each quarter. The problem is rarely the payroll itself. Belarusian payroll is procedural: fixed statutory contributions, a mature reporting calendar, tight deadlines, and a Labour Code that leaves little room for improvisation. The problem is what shows up in the HQ finance inbox each month — and what doesn’t.
An Employer of Record can absorb the entire employer-side compliance load in Belarus. That is the point of the model. But absorbing the load is not the same as reporting it back to the client at the level of detail an HQ finance team needs to run consolidation, transfer pricing, headcount analytics, or an external audit. The gap between the two is where most Belarus EOR engagements silently degrade — because the client only notices at year-end.
This piece sets out the payroll reporting cadence a foreign HQ should demand from a Belarus EOR from day one, and the deliverables most providers will not offer unless the contract requires them.
What Belarusian law requires — and why it’s not enough for HQ
Belarusian payroll runs on a monthly cycle with a mandatory intra-month advance. The Labour Code requires wages to be paid at least twice per month, so the standard rhythm is an advance in the second half of the month and a final settlement in the first ten days of the following month. Personal income tax (13% flat) is withheld and paid on the day salary is transferred. Social Protection Fund (FSZN) contributions — 34% employer, 1% employee — are paid the same day. Belgosstrakh premiums for occupational injury insurance follow monthly. FSZN individual accounting reports (PU-3) are filed quarterly. Statistical reporting to Belstat runs on a mix of monthly, quarterly, and annual cycles depending on headcount and industry.
That calendar is what a compliant EOR must execute. It is not what an HQ finance team needs in its inbox to close.
The gap sits in the translation layer. A Belarusian payroll run produces statutory registers, tax cards, contribution slips, and bank transfer files — in Russian, in Belarusian rubles (BYN), formatted for local authorities and audit-ready by local standards. None of that maps cleanly into a group ERP, a global HRIS, an IFRS accrual, or a variance analysis against last month’s forecast.
The HQ finance function needs the same underlying data — but restructured, translated, converted, and pre-timed to fit the group close calendar. If the EOR sends only the statutory outputs, the client ends up rebuilding them locally every month. That’s a recurring hidden cost, and it’s the first thing an experienced buyer benchmarks when evaluating providers.
The reporting cadence a foreign HQ should demand
Reporting from a Belarus EOR really needs to run on four separate cycles — pre-run, post-run, monthly close, and quarterly/annual audit support. Each one has its own deliverable and its own deadline attached to it. If a provider won’t put all four in writing, whatever they’re saving you on price is going to get eaten up by your own accounting team doing the cleanup. Every month. Quietly.
Pre-run: the approval file
Before payroll is executed each month, you should receive a draft register showing every employee, gross salary, variable pay for the period, planned deductions, statutory contributions, expected net pay, and the total funding requirement in BYN and in HQ currency. This is the file HQ approves before money moves. It should arrive at least three business days before the salary transfer date, with variance flags for any employee whose gross has changed from the previous month by more than a defined threshold.
Most providers skip this step and send the register only after payroll has run. That works — until the first time a bonus was double-counted, a leaver was still paid, or an FX assumption drifted, and the correction has to happen through a partial return of funds. A pre-run approval file eliminates that class of error.
Post-run: the payroll register and payslips
Give it two business days after salaries go out. By then you should have the final register in hand. Real paid amounts, real withholdings, real remittances, individual payslips. Everything ties back to what you approved earlier — and it ties row by row, not just at the totals level. Any deltas get explained. If the provider is quiet about a variance, that’s usually where problems start.
Payslips should be available in English on request. That is not a legal requirement in Belarus, but it is a practical one whenever HQ HR is fielding compensation questions from employees who don’t read Russian.
Monthly close: the HQ finance pack
This is where most providers stop delivering and most clients silently start losing time. A monthly close pack should include the payroll register, and also:
- A cost report in HQ currency at the FX rate you use for consolidation — not the National Bank rate, not the provider’s default. Your own group close rate.
- A journal-ready entry set mapped to your chart of accounts, that can be pulled into the group ERP without re-keying. Gross wages, employer taxes, employee tax withheld, net paid, FSZN payable, Belgosstrakh payable, and any accruals split as separate lines.
- An accrual view for leave, bonus, and any variable pay that has been earned but not yet paid. Under IAS 19 Employee Benefits, these are period-cost items that need to appear in group accounts before cash moves.
- A cost breakdown per employee in both BYN and HQ currency, showing gross, employer taxes, employer contributions, net pay, and total cost to the company. This is the file that feeds global compensation dashboards.
- A compliance log for the month — what was filed, on which date, to which authority, with confirmation numbers where issued. Short, and never on request.
The accrual line item is the one that gets skipped most often, because it requires the EOR to think beyond statutory registers. It is also the item that decides whether the Belarusian entity closes on time in the group ledger.
Quarterly and annual: giving audit and consolidation something to work with
The quarterly deliverable is a cumulative YTD position per employee, tied to the FSZN PU-3 reports the provider actually filed and to the income tax reconciliations behind them. This one file does a lot of quiet work — it’s what shrinks external audit fieldwork from weeks down to days, because the group auditor can read Belarusian data in a familiar shape instead of asking for translations and clarifications every step of the way.
Year-end gets heavier. Annual income tax certificates for each employee. A reconciliation of total employer costs back to the statutory accounts of the Belarusian entity, if you have one set up. And — this is the part providers routinely skip — the working papers for any leave and bonus accruals rolling into January. Skip those and someone at HQ is rebuilding accruals from memory in Q1. It happens more than you’d think.
What most providers don’t deliver — and why
Three gaps recur across the Belarus EOR market.
The first is currency. Most providers report only in BYN. You have to convert everything monthly, at a rate you have to source yourself, with no clear reconciliation back to the ruble figures. Over twelve months, that’s a rounding-error problem that compounds into a genuine variance in group accounts. Providers who use the National Bank of the Republic of Belarus reference rate as a default rarely explain that the rate diverges from the rates used by your own consolidation team.
The second is granularity. Providers often send a single-line invoice — “payroll and taxes, month X” — with a Russian-language statutory register as backup. That’s enough to prove money moved. It’s not enough to answer any question HQ finance is likely to ask: what did total employer cost look like per role, how did contributions move quarter over quarter, why did net pay drop for employee A, what accrual carried into the current period.
The third is timing. Statutory deadlines drive the provider’s calendar. The group close calendar drives yours. When those don’t align — and they rarely do out of the box — you end up chasing figures during your own month-end. A good EOR delivers to your calendar first, not the local one. Both get met, but the client’s takes priority for reporting purposes.
Under those three sits a broader issue: most EOR providers in the region price on payroll processing volume, not on the reporting they wrap around it. Reporting quality is treated as an add-on. In practice, it is the single feature that decides whether the engagement works for HQ or not — and the one that the OECD’s guidance on multinational reporting increasingly assumes is already in place at the entity level.
Foreign HQs that also run a Belarusian entity face a similar challenge on the accounting side — beneficial ownership tracking, statutory financial statements, and coordination with the payroll layer all need to sit under one reporting rhythm. The mechanics of that broader picture are covered in the note on beneficial ownership reporting for foreign-owned IT companies, and the same principle applies: define the reporting deliverables at contract stage, not after the first close.
How to write reporting requirements into an EOR contract
Reporting cadence should sit in the master services agreement as a defined deliverable, not as a service-level target. A defined deliverable has a name, a format, a due date, and a consequence for missing it. A target is aspirational.
At minimum, the schedule should list: the pre-run approval file with its due date relative to payroll transfer; the post-run register and payslips with their due date; the monthly HQ finance pack with each of its components enumerated; the quarterly YTD file; the year-end pack; and a standard turnaround for ad-hoc requests (three business days is common). The FX convention should be named — either your group rate, an agreed month-end rate, or a specified source. The delivery format should be named — Excel with a defined tab structure is standard; PDFs for signature copies only.
Once these are in the contract, the entire engagement changes shape. The provider is no longer selling processing; the provider is selling reporting with processing behind it. That reframing is the single biggest lever a foreign HQ has when negotiating a Belarus EOR arrangement. It is also the reason why reporting depth on the accounting side tends to move in step with payroll depth — the two functions share the same source data, and a provider who structures one well tends to structure the other well too.
FAQ
Once a month is the minimum, and even that shouldn’t come as one file. You want a few things at different points in the cycle. Before payroll runs, get a draft to look over and approve. After it runs, get the register with everyone’s payslips. Then a separate close pack for finance to work from at month-end. Every quarter, YTD reconciliations. December or January, a year-end pack. Watch out for providers who just send one monthly invoice with a Russian register attached — that’s them ticking the tax box, not actually reporting to you.
You need two versions. In Belarus, the register runs in BYN because the tax authorities require it, and there’s no negotiating that part. But your HQ finance team shouldn’t have to convert anything themselves. The pack they get should already show the numbers in your reporting currency, at your consolidation FX rate. Key thing here — agree on the methodology up front and put it in writing. If you leave it to the provider, they’ll default to whatever’s easiest for them, and you’ll be reconciling FX gaps forever.
Yes, and it is standard practice with providers who work with international clients. The mapping is set up once at onboarding and applied to every subsequent monthly close pack. It removes the re-keying step in your ERP and shortens month-end by several days.
Russian-language statutory outputs are unavoidable — that is what the authorities receive. But your client-facing reports should be in English. Any provider working with foreign HQs should deliver payslips, close packs, and audit files in English as standard. If English is offered as an extra, it usually signals the provider is not set up for foreign clients in the first place.
The EOR should provide an accrual view each month showing earned-but-unpaid leave, accrued bonus, and any deferred variable pay. A provider who cannot produce this file is effectively leaving the accrual work with your team.
Conclusion
Payroll in Belarus, on its own, isn’t hard. Local providers do it every day. What’s hard is turning the local output into something a foreign HQ can act on — quickly, in a currency they use, at a useful level of detail, aligned to their close calendar. That translation is the whole game. Get it right and the EOR fades into the background, which is exactly what you want. Get it wrong and you’ll notice, because someone at HQ will be manually reworking the numbers every month and quietly hating their life.
The reporting cadence set out above — pre-run approval file, post-run register, monthly HQ close pack, quarterly YTD, annual audit support — is what a foreign HQ should be asking for from the first briefing call. Providers who can commit to it in writing are ready for international clients. Providers who cannot are pricing on statutory processing alone, and the shortfall will land somewhere in your own team.
If reporting quality is what you want to benchmark first, that is the right instinct. The most useful conversation to open with a Belarus EOR partner is about deliverables, format, and dates — not headline price.