Financial anomaly detection: catch costly errors early
A deterministic needs-attention feed that flags duplicate payments, outliers, missing docs and flagged counterparties — ranked for a human.
Running payroll in Ukraine is not just paying salaries. Every pay run carries three separate state charges — ЄСВ, ПДФО and військовий збір — each with its own base, its own bearer, and its own deadline. Get the split wrong and you either short the employee, short the budget, or expose the company to penalties from ДПС. It is repetitive, deadline-bound, document-heavy work — exactly what an autonomous finance department is built to carry.
This article explains what each charge is and who bears it, then walks through how the FINMOZG Payroll Agent runs a full payroll cycle from gross to net — with a human approving the release and КЕП-signing the reporting before anything reaches the tax service.
The cost of employing someone in Ukraine is larger than the salary on the contract. The gross figure is the starting point, and three flows branch off it:
Because the company both withholds employee taxes and pays its own contribution, payroll is really two obligations in one run: paying people correctly and remitting the right amounts to the budget on time.
Each charge has a distinct role, and confusing them is the most common source of payroll error.
ЄСВ (єдиний соціальний внесок) funds the social and pension system. It is charged on the gross salary and paid by the employer in addition to the gross. It is not withheld from the employee, which is why it is easy to forget when budgeting a hire: the headline salary understates the real cost.
ПДФО (податок на доходи фізичних осіб) is the employee's income tax. The employer withholds it from the gross and remits it to ДПС on the employee's behalf. The company is the tax agent here, responsible for both the calculation and the timely transfer.
військовий збір is a separate levy, also withheld from the employee's gross alongside ПДФО. It is a distinct line with its own remittance, not a part of income tax, and it has to be reported and paid as its own item.
The Payroll Agent runs the cycle as a sequence of deterministic steps, the same way the rest of the platform moves work through fixed states. The payroll engine is one of FINMOZG's deterministic engines — the calculation of ЄСВ, ПДФО and військовий збір follows the rules, not a language model's guess.
For each employee the engine starts from the gross, withholds ПДФО and військовий збір to reach the net, and computes the employer ЄСВ on top. Because this is a rules engine rather than a generative model, нарахування зарплати is reproducible: the same inputs always produce the same figures, and every line is traceable.
From those per-employee calculations the agent assembles the payroll register — gross, each withholding, net, and the employer ЄСВ, totalled across the team. The register is the single document a human reviews: it shows exactly what each person will receive and exactly what the company owes the budget.
Payroll generates obligations that have to be reported and remitted. FINMOZG prepares the reporting and moves it to approval; an authorised person signs with their КЕП, the qualified electronic signature, and only then does the agent submit to ДПС. This is the same hard boundary that governs every tax submission across the platform — covered in detail for VAT in ПДВ automation.
Releasing payroll is a hard boundary. The Payroll Agent will prepare everything — the register, the net amounts, the employer ЄСВ, the reporting — but it stops at Awaiting approval. A person reviews the register, confirms the figures, and approves the release. Only after that approval is a payment instruction created.
Payroll taxes do not stand alone. ЄСВ, ПДФО and військовий збір sit on the same compliance calendar as the monthly ПДВ return and every other filing. FINMOZG turns each deadline into a tracked task with the draft prepared ahead of time, so the payroll run and its reporting are queued for review before they are due rather than reconstructed in a rush. Missing a deadline becomes a visible decision, not an accident.
Not everyone on the payment list is an employee. A ФОП contractor invoices for services and settles their own unified tax and ЄСВ, so their payment is a supplier expense, not payroll, and it does not go through the payroll engine. The distinction matters because treating an employee as a ФОП to save on charges is a classic misclassification risk. The Compliance Agent surfaces arrangements that look like disguised employment so the issue is visible before it becomes a liability — and the broader ФОП-versus-ТОВ structure question is covered in ФОП vs ТОВ.
Payroll in FINMOZG is not "AI paying your staff." It is a payroll cycle that computes ЄСВ, ПДФО and військовий збір by the rules, builds a register you can read line by line, and stops for a human to approve the payout and sign the reporting with their КЕП — with the whole Ukrainian setup described in the Ukraine pack.
A deterministic needs-attention feed that flags duplicate payments, outliers, missing docs and flagged counterparties — ranked for a human.
In-house, outsourced, or autonomous: how the three finance models trade control, cost and visibility, and which fits your stage.
A financial copilot grounded in your posted ledger: trustworthy narrative, KPIs, runway and scenarios — never a guessing chatbot.
Book a 30-minute demo and watch accounting, tax, payroll and the CFO Agent work end to end — with audit-grade control.