An engineer on your Belarusian team flies to a conference in Warsaw. Three days, one hotel, a train, a handful of taxis, and dinners with two prospective partners. The engineer pays for most of it herself and expects the money back. From headquarters this looks like a line item someone approves in an afternoon. On the ground in Belarus it is a regulated business trip with its own paperwork, tax treatment, and deadlines — and the person who has to get all of that right is not you. It is your Employer of Record.
This is the part of the EOR relationship founders rarely ask about during the sales process and always run into by month three. Salaries are predictable; expenses are not. A single reimbursed trip touches labour law, tax, currency conversion, and your own month-end close, and if the workflow behind it is improvised, it stops scaling the moment your headcount does. This piece sets out how travel allowances, per diems, and business expense reimbursement actually work through an EOR in Belarus — and how to build the workflow so it holds at ten employees and at a hundred.
Payroll through an EOR is procedural: the salary is fixed, the contributions are statutory, the calendar is known, and the same numbers repeat every month. Expenses are the opposite — irregular in timing, variable in amount, mixed in currency, and dependent on documentation that arrives late and in inconsistent shape.
That matters because the EOR is the legal employer, and under Belarusian law it is the employer — not the parent company — that owes the employee reimbursement, applies the correct tax treatment, and holds the evidence for an audit. When a member of your team travels, the EOR issues the trip order, advances the money, receives and checks the expense report, classifies what is reimbursable and what is taxable, and represents all of it back to you in a usable currency and format. None of that is visible from headquarters, and all of it is where the engagement quietly succeeds or fails.
Teams that hire engineering and product staff through EOR arrangements for tech companies tend to discover this the first time a reimbursement lands in group accounts as an unexplained foreign-currency figure with no breakdown. The money moved correctly; the reporting did not keep up. That gap — between a compliant payment and a usable record — is the subject of this article.
Business trips in Belarus are governed by a specific instrument: the Regulation on the reimbursement of expenses and compensations for business trips, approved by Resolution of the Council of Ministers No. 176 of 19 March 2019. It was amended with effect from 4 April 2026 by Resolution No. 135, which among other changes raised the domestic daily allowance. The regulation binds budget organisations directly and functions as the baseline reference commercial employers — including EOR providers — build their policies around. The consolidated legal text is maintained on the country’s official legal information portal.
Under that framework, a reimbursable trip breaks into three distinct blocks of expense, and it is worth keeping them separate because they are treated differently:
The tax side is what catches most foreign HQs off guard, because it isn’t intuitive. Reimbursements that stay within the norms in Regulation No. 176 are free of personal income tax and of social contributions to the Social Protection Fund (FSZN) and Belgosstrakh. The same goes for actual, documented travel and accommodation that exceeds those norms, as long as it’s backed by receipts. Where it changes is the per diem: pay above the statutory norm and that surplus becomes employee income, subject to the flat 13% rate. So an over-generous policy doesn’t merely cost you more money. It converts a slice of the reimbursement into taxable compensation, and the EOR is the one obliged to withhold on it. Handled by a provider who understands the mechanics, the policy stays clean; handled by one who doesn’t, it creates a liability the client never sees until later.
Then there’s the documentation, which is stricter than most HQs expect. An order has to authorise the trip before it happens, full stop. The employee normally draws an advance before departure — that’s Article 95 of the Labour Code — and files an advance expense report shortly after getting back. None of this is complicated on its own. The problem is that skipping any single step is enough to turn an otherwise ordinary trip into an audit finding, no matter how legitimate the underlying spend was.
The workflow only makes sense as a sequence, so it helps to follow a single trip end to end — and see who does what.
Authorisation. You pass the purpose, destination, and dates to the EOR, which issues the internal trip order in the employee’s name. This is not a formality: without a documented order, the reimbursement becomes contestable, and per diems paid for a trip that was never formally ordered are a classic inspection target.
Advance. The EOR calculates and pays an advance covering the expected per diem, accommodation, and travel — estimated from the trip length and destination against the applicable norms — so the employee is not out of pocket from day one.
The trip. The employee travels and keeps every document — boarding passes, rail ticket, hotel invoice and payment confirmation, taxi and transfer receipts. Foreign-currency spending is recorded as spent; the conversion comes later.
The expense report. On return, within the statutory deadline, the employee submits the advance expense report — per diem as a flat daily figure with no receipts, travel and accommodation against the documents. The EOR checks each line, reconciles it against the advance, and either pays the balance owed or recovers any unspent advance.
Currency conversion. Costs incurred abroad are converted into Belarusian rubles for the statutory record, using the National Bank of the Republic of Belarus rate for the relevant date. This is where your own consolidation rate and the statutory rate can diverge — a difference that matters enormously for reporting and almost not at all for the employee.
Reporting back to you. Finally, the EOR represents the whole event to your finance team: what was reimbursed, split by per diem, accommodation, and travel; what portion (if any) was taxable and why; and the amount in BYN and in your reporting currency. Providers most often skimp on this last step — four of the six are invisible from headquarters — and it is the one that decides whether the trip closes cleanly in your books.
There are two ways to cover the meals-and-incidentals part of a trip, and most companies in Belarus that handle it well end up combining them. A per diem pays a flat amount for each day away, with no meal receipts required. Nothing to itemise, nothing for anyone to pick apart afterward. For a team that travels regularly that saves real administrative effort, and the tax treatment stays clean so long as the daily rate doesn’t exceed the statutory norm.
Actual-cost reimbursement is the other route. You pay back what people actually spent, and you ask for receipts to prove it. On hotels and flights that’s fine, because those are big-ticket items that come with paperwork anyway. Meals are where it gets tiresome. Now every coffee and every sandwich is a receipt that has to be kept, handed in, translated, and checked. Annoying enough for one trip. Once you’ve got a team travelling, it becomes a permanent chore.
What works in Belarus, and what any competent EOR will point you to, is a blend. Put meals and incidentals on a per diem at or below the statutory norm, and reimburse accommodation and travel on documented actual cost. The bulk of the trip then stays outside the tax base, receipt-gathering stays confined to the categories where documents already exist, and you’re left with a record an auditor can follow without needing anything translated. On the surface it looks trivial. In reality it’s one of the higher-leverage calls you’ll make, which is why it belongs in an early conversation with HR consulting support — before the first employee books a flight, not after the third files something you can’t make sense of.
Reimbursement through an EOR fails in a small number of predictable ways, and every one is preventable. The first is the missing or defective trip order: when a trip is arranged informally and the order is written up afterward, the per diem paid for it sits on shaky ground, and inspectors and auditors look for exactly this. The second is the taxable per diem nobody flagged — if the daily rate drifts above the norm, the excess becomes taxable income, and if the EOR does not catch it and withhold, the exposure accumulates quietly until year-end. The third is the late or incomplete report, which stalls reconciliation whenever employees do not understand the deadline or documentation standard.
The fourth is worth its own line: the currency black box. A reimbursement arrives in group accounts as a BYN or foreign-currency figure with no breakdown and no conversion note, and finance cannot tell what was per diem, what was taxable, or what rate was used. The payment was correct; the record is unusable. It is the same disease that afflicts payroll when reporting is an afterthought, and the cure is identical — a point covered in the discussion of payroll reporting cadence a foreign HQ should demand from day one. Expenses belong in that same reporting rhythm, not a separate, ad-hoc channel. None of these are payment problems; the money almost always moves correctly. They are documentation, tax-classification, and reporting problems — workflow problems — and they compound with headcount.
The difference between an expense process that survives growth and one that collapses is that the first was designed and the second accreted. A few decisions, made up front and written into the engagement, do most of the work.
Agree the per diem policy and the tax line up front. Set the daily rate, confirm it sits within the statutory norm so it stays tax-free, and document what happens if a trip warrants exceeding it. This one decision determines whether reimbursement stays administratively light or turns into a per-trip tax calculation.
Standardise the documentation the employee must return, and communicate it in a language they read. A short checklist — order reference, dates, per diem days, accommodation invoice, travel tickets, receipts, deadline — prevents most late and incomplete reports before they happen.
Fold expenses into the same reporting cadence as payroll. Reimbursements should appear in the monthly finance pack, split by category, flagged for any taxable portion, and converted at your consolidation rate — not delivered as a separate stream of payments you have to chase and decode. Because reimbursement and salary share the same source data and cost centre, it is natural to run them through the same payroll administration discipline, so a trip and a salary close in the same rhythm.
Name the currency convention, so the provider does not default to whatever is easiest for them. Where expenses are recharged across the group, the same discipline underpins cost allocation and transfer pricing, which the OECD’s guidance on multinational enterprises increasingly assumes is documented at the entity level.
Finally, confirm the provider treats reimbursement as a compliance function, not a payment button. How they answer on an over-norm per diem, a trip order, and the monthly pack tells you whether expenses will scale with you or become a recurring cleanup — whether the hundredth reimbursement is any harder than the first.
The EOR does, because it is the legal employer and Belarusian law places the reimbursement obligation on the employer. You fund it — the cost flows back through the EOR’s monthly billing — but the provider issues the trip order, advances the money, receives the expense report, applies the correct tax treatment, and pays the reimbursement. You approve; they execute.
Reimbursements within the statutory norms in Regulation No. 176, plus actual documented travel and accommodation costs above those norms, are exempt from personal income tax and from FSZN and Belgosstrakh contributions. A per diem paid above the norm, however, is taxable employee income and attracts personal income tax at 13%. Keeping the policy within the norm is what keeps it tax-free.
No. The per diem is a flat daily allowance entered in the expense report without receipts — that is the whole point of the mechanism. Receipts are required for the other two categories: accommodation (hotel invoice and payment proof) and travel (tickets, boarding passes, transfer receipts).
Belarusian rules require the advance expense report to be submitted within a short window after return — commonly three working days — with supporting documents attached. Building that deadline, and the documentation standard, into onboarding is the simplest way to stop reports arriving late and incomplete.
Yes, and they should be. The statutory record is kept in BYN, but a provider set up for foreign clients will convert reimbursements into your reporting currency at your consolidation rate and show the BYN figures alongside for reconciliation — a methodology worth agreeing in writing at onboarding.
Watching a provider run salaries is not especially revealing. It’s meant to be routine work, and most firms handle routine work fine. What you actually want to know is how they behave under pressure, and the pressure comes from travel. A single trip abroad brings together everything that makes cross-border employment awkward — a one-off cost, a foreign currency, and tax and labour questions that surface right as your reporting deadline does. Payroll never forces those things into the same moment. An expense claim does it as a matter of course.
It’s also worth being clear about how these things go wrong, because it’s not usually the payment. It’s the trip that went ahead before anyone raised the order for it. It’s the per diem set just over the norm, which pulls part of what should have been tax-free into taxable pay. It’s the report that shows up carrying an exchange rate with no record to explain it, or the one that shows up too late to be any use. On their own, none of these is worth worrying about. The catch is that they multiply: the more people you have travelling, the more openings there are for the same small errors to slip through.
For that reason, the firms that stay out of trouble build a workflow instead of handling each case as it arises. The per diem is kept within the statutory ceiling and remains outside the tax base. The contents of a valid claim are fixed beforehand, and reimbursement is processed on the payroll cycle rather than separately. The currency question is settled before any booking is made. Once those choices are in place, the process operates without intervention — and in a jurisdiction you do not run yourself, consolidating both the compliance and the payments with a direct Employer of Record is what keeps a growing team from turning each month-end into remedial work.
Biometric documents are modern documents that contain the owner’s biometric data for identification. In Belarus biometric data increases security and ease of use. This article explains what biometric documents exist in Belarus, how to get them, and what advantages they provide to their owners. What is the meaning of biometric documents? The use of biometric […]
In what cases is a probationary period established? According to the Labor Code of the Republic of Belarus, a probationary period is a period of time to check the compliance of an employee with the work performed. It is preliminary in nature, that is, it can be set only once when an employee is hired. […]
When a foreign company hires someone in Belarus through an Employer of Record, one of the quiet reassurances that makes the model attractive is “taxes are taken care of.” For the salary that runs through payroll every month, that is entirely true. The EOR withholds income tax, pays it to the budget, and files what […]
