Opyra reads the data already sitting in your ERP, calculates the month's metrics, and checks the payroll rule by rule. Every finding comes with the legal basis, the amount, and the line of the file it came from.
rescisoes.json · line 218 · NKW-0311srd.json · line 4,417 · NKW-0184srh.json · line 96 · NKW-0127A five-step demo of Opyra: the extract arrives from the ERP, 14 metrics are calculated, 147 checks run against the payroll, one finding appears with its evidence, and the executive report is ready.
Counted in the codebase — not a forecast, not an industry average.
Drag to compare: any everyday payroll question, in both scenarios.
It is the very tool our team closes your payroll with — your login, your numbers, included in the BPO contract. If your payroll runs with us, everything on this page is already yours.
If your payroll is already with Nokware®, talk to your contact — we switch the access on.
Every tile below is a screen that exists today, filled with demo data. Nothing here is a mockup of something we plan to build.
rescisoes.json · line 218147 deterministic checks on every close — arithmetic, employer taxes, terminations, job protections, vacation, 13th salary, and the payroll-code bindings the ERP close requires.
Ask in plain language. Opyra resolves the query, routes it for human approval when it's new, and returns the number with the full trail attached.
41 checks across the four official Brazilian clock-in file formats. A score per site, findings with legal basis, and a 30/60/90 remediation plan.
A conformity index over your real filing picture in eSocial (Brazil's unified payroll reporting system): what went through, what bounced, what nobody ever sent.
An opening, four subject notebooks and appendices, every pay period. The rule calculates, the AI writes, a human approves before it ships.
Every answer Opyra knows how to give, browsable by the management question behind it — and which ERP field switches each one on.
Accident-risk and social-fund rates checked against the official tables. The gap comes out in reais.
Ask the union agreement, the contract, the amendment. It answers only from your documents — and cites the page.
The query you run every 5th of the month starts arriving on its own. Set a target on any metric and get an alert when it breaks.
File or API. Pick whatever your IT team will sign off on, and switch later.
Seven screens captured from the real product, on a demonstration company. Each one answers a question your payroll team asks every month.
How is the month going?
The panel that opens with the payroll health score, the calculated metrics and whatever needs attention before you close.
Am I clear to close?
Deterministic checks over the close, every finding with its severity, legal basis and the exact line of the file. Plus honest coverage: a rule without your calibration declares itself unevaluated instead of guessing.
How many people will leave — and what does it cost?
A forecast with its range, the scoreboard of how often the model landed in the past, and a simulator to test the scenario before you decide.
What happened to this person?
A whole working life on one timeline — hiring, raises, promotions, transfers, vacation and leaves — and every milestone cites the table it was read from.
What is still pending with the tax authority?
The scoreboard of events by type — what went through, what bounced back with an error and what nobody filed — with the conformity index of the real state.
Where does this number come from?
Every metric has a card: the management question it answers, how it is calculated, the decision it supports and which fields of your ERP it needs.
Are the official tables really in the calculation?
The versioned archive of official tables, with effective dates, the file fingerprint and a human gate: no official table enters the calculation until a person approves it.
Screenshots of the real product, taken on fictional data — no customer data appears here. The interface is in Portuguese: the platform itself is not translated, and we would rather say so than let the images imply otherwise.
Most payroll BPOs hand over the payroll and a spreadsheet. The Delivery Book is the report of your whole month — what happened, what our team did about it, what it saved you, and what is still open from the previous edition.
The rule calculates, the AI narrates, and a person at Nokware approves before anything is sent. No number in the Book is typed in, and none is an opinion — the opening “The month on one page” lays out the score's own arithmetic, factor by factor, with each one's cap.
What we recommend in one edition comes back with a status in the next, in the same table, showing the progress of every item. It is the document holding itself to what it asked for — and you with the history in hand to hold us to it.
Money that never left the account, penalties that stopped existing, and exposure that went down. The three never collapse into one figure, because they are different in kind — adding them up would sell you a saving that never happened.
The three images come from a real Book, generated on a demonstration company — no customer data appears here. The document opens with “The month on one page” and continues in four subject notebooks — Payroll, Compliance, People and Service — with reference appendices at the end. A notebook without data leaves no gap: it simply is not written. The document is written in Portuguese.
Type it in and every screen on this page updates.
The screens customers open most. Scroll to switch.
A manager types the question. Opyra looks for an already-approved query; if there isn't one, it composes a new query and sends it for human approval before touching the customer's database. The number comes back with the whole trail.
CATALOG_RESOLVEquery reused from the approved library120 msQUERY_VALIDATIONfields checked against the customer's data dictionary340 msHUMAN_APPROVALapproved by Eduardo · 2:32 PM0 msDATABASE_EXECUTIONexecuted on the customer's ERP1180 msDATA_NORMALIZATION196 rows normalized90 msYour official timekeeping files go through 41 checks: record integrity, rest between shifts, meal breaks, hours worked against hours contracted, leave periods, and reconciliation against payroll. The result is a two-part report with a score per site.
The most tangible thing the product makes: the Timekeeping Compliance Report and the Delivery Book. Both ship in a light theme, ready to print and hand to the board.
A signal is not a verdict: each finding is a lead to investigate, with its legal basis and evidence.
The documents shown are facsimiles built from fictional data.
The charts below are drawn by the same functions that draw the customer's report and book. This isn't a picture of the product — it is the product.
| Sep 25 | R$ 6.67M |
|---|---|
| Oct 25 | R$ 6.80M |
| Nov 25 | R$ 6.74M |
| Dec 25 | R$ 6.99M |
| Jan 26 | R$ 7.37M |
| Feb 26 | R$ 9.88M |
| Mar 26 | R$ 7.02M |
| Apr 26 | R$ 7.12M |
| May 26 | R$ 7.08M |
| Jun 26 | R$ 7.47M |
| Jul 26 | R$ 7.67M |
| Aug 26 | R$ 7.80M |
| HQ São Paulo | 486 |
|---|---|
| Site 02 Rio | 322 |
| Site 03 Minas | 244 |
| Site 04 Paraná | 142 |
| Site 05 Bahia | 54 |
| no accepted eSocial filing | 3 |
|---|---|
| Distribution of active headcount. | 1,248 |
| Operations | Mon: 34, Tue: 18, Wed: 9, Thu: 11, Fri: 22, Sat: 6 |
|---|---|
| Sales | Mon: 12, Tue: 7, Wed: 5, Thu: 4, Fri: 15, Sat: 2 |
| Maintenance | Mon: 9, Tue: 6, Wed: 8, Thu: 5, Fri: 10, Sat: 4 |
| Administration | Mon: 4, Tue: 3, Wed: 2, Thu: 3, Fri: 5, Sat: 0 |
| Base pay | R$ 17.00 |
|---|---|
| Payroll taxes | R$ 6.26 |
| Benefits | R$ 3.70 |
| Accruals | R$ 1.43 |
| What an hour really costs | R$ 28.39 |
Opyra asks for no changes to your ERP. Pick the path your IT team will accept — and switch later if you want.
Export using our layout and upload it. Good for starting today, without a ticket.
Your system posts the pay period over REST with its own key. Good if you already automate.
ERP-agnostic on principle: the extraction layout is generated from your system's real data dictionary, never from guessed table names — and you run it, inside your own environment.
Whoever runs payroll does not live in a management screen — they live on the phone. The question goes out on WhatsApp and the answer comes back with the actual figure for the period.
The one answering is Nok. He reads what has already been calculated, never makes up a number, and when he does not know, he says so.
It is the official profile picture of the number — the first thing the client sees before reading a word. The same image appears in the conversation and wherever the channel is mentioned.
One image, three sizes, zero variation. That is what makes the sender recognisable without the name.
Security here isn't a badge in the footer — it's what keeps one customer from seeing another's data, and what lets anyone reconstruct any number.
Every sensitive table carries a row-level policy per tenant, enforced even against the table owner. Isolation by construction, not by convention.
Extracts are stored encrypted. So are their file names.
Every query gets a traceable id: who asked, what ran, how long it took, what came back.
New queries, book delivery, and source publication all pass through a person first. Nothing publishes itself.
Operators, managers, and admins see different screens — configurable per customer.
With no approved rate table in force, recalculation declares itself unavailable. With no calibration, a rule declares itself unevaluated. Opyra would rather say “—” than say zero.
Personal data handling is described in the privacy policy (LGPD is Brazil's data protection law). Read the policy →
Upload a payroll extract and Opyra returns your Health Score and aggregate findings on the spot. No personal data, no install, no commitment.
Upload an extract. Results appear on screen, processed in memory and never stored.
We connect one real month and run the whole close alongside your team.
Schedules, targets, the monthly book, and the auditor running on every extract.
Opyra is licensed per seat, under a contract per customer. Because the number depends on your size and which fronts you turn on, we don't publish a table: the quote follows the assessment, with the scope written down.
One extract. Five minutes. Your own numbers.