KRA/KPI + bell curveCompensation engineVerifiable letters
Rate. Calibrate.
Pay. Document.
KRA and KPI review cycles and bell-curve calibration feed a compensation engine that knows your country’s statutory rules — and every letter it issues can be checked by anyone. Performance decisions become defensible, pay decisions become local-law-aware, and letters stop being disputed.
A rating on its own is an opinion. What makes it hold up three months later is the distribution it was compared against, the session that argued it, the rule that turned it into money, and the document that came out of the other end. PMS keeps all four attached to the same person record.
pms.flowza.ai- 01RateSelf, manager and reviewer stages closed5 KPIs scored · consolidated stage score 4
- 02CalibrateCompared against the cohort distributionSession PMS-CAL-26-Q2-07 · held at 4 · challenge recorded
- 03PayIncrement resolved against the India rule setComponents preserved · EPF, ESI and PT recomputed · INR
- 04DocumentIncrement letter approved and signedLTR-26-0392 · verifiable on a public page
An illustrative cycle record, not a published customer figure. The four stages are the product’s own loop; the identifiers show how each stage is filed against the same person.
The loop
Four stages, and the
handoffs between them.
Most organisations already do all four of these. They do them in four places: a review form, a spreadsheet of ratings, a payroll instruction, and a letter someone types in a word processor. Every join is a retype, and every retype is where the evidence trail breaks. Select a stage to see what enters it, what leaves it, and what it writes down.
01 · Rate · Self, manager and reviewer stages across a KRA/KPI cycle
Elsewhere this leaves the building as a PDF of a form. Here it is the input to the next stage.
Calibration
A rating means little
on its own.
Managers do not rate alike. Two people doing comparable work under different managers can end a cycle a full band apart, and neither manager has done anything unreasonable — one holds a higher bar than the other and always has. Until the ratings are put side by side, that difference is invisible, and the person on the wrong side of it pays for it in money and in promotion.
The same scale, three hands
- R. Iyer10 direct reports8 of 10 at 4 or 5 · none below 3R. Iyer rated two people at 3, five at 4 and three at 5. Nobody in this cohort was rated below 3.
- L. Haddad10 direct reports5 of 10 at 4 or 5 · one at 2L. Haddad rated one person at 2, four at 3, four at 4 and one at 5.
- M. Farooq10 direct reports4 of 10 at 2 or below · none at 5M. Farooq rated one person at 1, three at 2, four at 3 and two at 4. Nobody in this cohort was rated 5.
An illustrative cohort of thirty in one job family and one grade band. The figures are drawn to show the mechanism; they are not a published measurement.
Read the three rows as one question: is a 4 from Iyer the same thing as a 4 from Farooq? On this cohort it plainly is not. Iyer’s cohort has nobody below 3 and Farooq’s has four; Farooq has nobody at 5 at all.
Nothing in a review form catches this, because a form only ever shows one person at a time. It surfaces the moment the ratings are laid against a distribution — which is what calibration is, and why PMS holds the session inside the cycle rather than beside it in a spreadsheet.
Score per KPI, or as one stage score
A cycle can carry a score against every KPI, or one consolidated score for the stage. Both arrive at calibration in the same shape, so a cohort scored either way can still be compared.
Three stages before anyone argues
Self, manager and reviewer stages close first. Calibration examines a rating that has already been through all three, so the session is about comparability rather than about whether the manager filled the form in.
The reference distribution is configured per cycle and is a comparison, not a cap: PMS does not require a cohort to match the curve, and the calibrated result above deliberately does not. What it requires is that a rating which sits away from the distribution has a reason recorded next to it.
What the session moved, and why
| Employee | Rated by | Movement | Reason recorded in the session |
|---|---|---|---|
| A. Nair | Iyer | 5 → 4 | Two of five KPIs were met rather than exceeded. The cross-team outcome claimed belonged to another team's cycle. |
| S. Bhatt | Iyer | 4 → 3 | On plan, not above it. Iyer's cohort had five at 4; the evidence separated three of them from the other two. |
| D. Okafor | Iyer | 4 → 3 | The delivery date moved twice. The KPI was met by rescoping it, which the session recorded rather than passed over. |
| P. Menon | Haddad | 4 → 3 | The consolidated stage score carried a KPI that was not in scope for this cycle. |
| J. Mwangi | Iyer | 3 → 2 | Two KPIs unmet with no mitigating record attached to either. |
| K. Rao | Haddad | 3 → 2 | One KPI was restated mid-cycle without approval. Measured against the target as agreed, it was not met. |
| T. Aziz | Haddad | 3 → 2 | The quality KPI was missed in both halves. The improvement plan began after the cycle closed and was noted for the next one. |
| H. Suleiman | Farooq | 2 → 3 | Met four of five KPIs. Farooq's cohort sat a band below the other two on comparable evidence, and this rating was one of them. |
| N. Verma | Farooq | 2 → 3 | Exceeded the volume KPI and met the rest. Rated against a standard the other two reviewers did not apply. |
| F. Darwish | Farooq | 4, held | Iyer argued for 5. The session held the rating at 4 and minuted the disagreement rather than settling it quietly. |
Nine movements out of thirty ratings: seven down, two up. The last row is the one people forget to build for — a rating that was challenged, examined and not changed. It is worth as much as a movement, because it is the case that will be argued about later.
The minute is the product
A calibration meeting that leaves no record has changed people’s pay on the strength of a conversation nobody can reconstruct. A recorded session is what lets a manager explain a rating to the person who received it, and what lets the organisation answer a challenge months later with something other than recollection.
- Session
- PMS-CAL-26-Q2-07
- Cohort
- 30 employees · one job family · one grade band
- Present
- R. Iyer, L. Haddad, M. Farooq (managers) · S. Krishnan (reviewer stage) · one HR partner
- Reference
- 10 / 20 / 40 / 20 / 10 across five bands, configured for this cycle
- Moved
- 9 ratings — 7 down, 2 up
- Held
- 1 rating challenged and held, with the disagreement minuted
- Dissent
- R. Iyer dissented on two movements. Recorded against those two ratings, not averaged away.
- Outcome
- Each moved rating links to this minute. The minute is appended, not editable — a later change supersedes it and is minuted in turn.
Illustrative minute. What is not illustrative is the shape: a session, an attendance list, a reference distribution, the movements, the dissent, and a link from every rating back to the session that examined it.
The compensation engine
One shape.
Four rule sets.
An agreed rating is not yet money. Turning one into money means resolving a salary structure, the statutory rules of the country the employee is employed in, and an increment strategy — in that country’s currency. Read the table down a column and you have one market’s rules. Read it across a row and you have the point: the engine does the same six things everywhere, and only the rule set changes.
| Resolution step | India | UAE | Saudi Arabia | Oman |
|---|---|---|---|---|
| Currency of computationStep 1 | INR | AED | SAR | OMR |
| Salary structureStep 2 | Same mechanism Country component set, held as data | Same mechanism Country component set, held as data | Same mechanism Country component set, held as data | Same mechanism Country component set, held as data |
| Statutory rules in the engineStep 3 | EPF, ESI, Professional Tax and gratuity | End-of-service, per legal entity | End-of-service, per legal entity | End-of-service, per legal entity |
| Workforce nationalisation dataStep 4 | — | —1 | Saudization workforce data | Omanization workforce data |
| Wage protectionStep 5 | —2 | Figures computedWPS export on roadmap | Figures computedWPS export on roadmap | Figures computedWPS export on roadmap |
| Conduct obligation resolvedStep 6 | POSH — policy, training, committee and complaint workflows | Labour-law conduct duties — the same four workflows | Labour-law conduct duties — the same four workflows | Labour-law conduct duties — the same four workflows |
| How the market was addedNot a step — a claim | Configuration | Configuration | Configuration | Configuration |
1 An em-dash means PMS does not ship it and we do not claim it. The workforce nationalisation datasets in the product are Saudization and Omanization; there is no equivalent UAE dataset today, so the cell is empty rather than filled with something plausible. 2 Wage-protection filing is a Gulf obligation. PMS computes the figures for the three Gulf markets; the bank-file export is on the roadmap and is not in the product today. India’s statutory payroll files are produced in FlowZa Finance, which is where the money actually leaves.
An increment that leaves the structure standing
This is a small mechanism with a long tail. A salary is not one number, it is a set of components, and several statutory computations read individual components rather than the total. An increment that resolves to a single new figure has quietly moved every one of those bases.
The same total, and a different employee. EPF is computed on basic pay; gratuity reads basic as well. Collapse four components into one and those computations have nothing left to read, so the contribution base moves for a reason nobody decided and nobody minuted. PMS applies the increment strategy to the structure and hands back a structure.
Illustrative figures in INR at a single grade. The arithmetic is the mechanism, not a customer’s payroll.
What the engine is, and what it is not
Rules are data, not branches in code
Salary structures, statutory rules and increment strategies are configuration. A fifth market is a rule set someone enters and tests, which is why the claim is configuration rather than a release.
Currency is not a display setting
Each of the four markets is computed in its own currency against its own rules. A figure is not converted for presentation after being worked out somewhere else.
End-of-service is per legal entity
In the Gulf the obligation attaches to the entity that employs the person, so it is resolved per legal entity rather than per group.
It resolves pay; it does not pay
PMS decides what the figure should be and issues it as a structured payroll instruction. Your payroll system runs the payroll, produces the statutory files and posts to the ledger — FlowZa Finance if you hold it, or whatever you already use.
Wage protection, stated plainly
The Gulf wage-protection figures are computed in PMS today. The bank file that a wage-protection system ingests — the WPS export — is on the roadmap. If that file is what you need this quarter, it is produced in FlowZa Finance, a separate application on a separate subscription, and we would rather say so here than let you find out in an implementation.
Verifiable letters
A letter a stranger
can check.
An experience letter is a claim on paper. The person receiving it — a future employer, a bank, a visa officer — has no way to test it, so they either accept it or ring your HR team and wait. PMS signs every letter it issues with your organisation’s key and publishes a page where anyone holding the document can check it themselves. Almost nobody in this category ships this, and it is the least glamorous feature in the range.
ISSUED 14 JUL 2026
TYPE EXPERIENCE
Certificate of employment
This is to certify that Ayesha Rahman, employee ID EMP-4118, was employed by Northwind Metal Works FZ-LLC from 3 March 2022 until 30 June 2026.
Her position on leaving was Production Planner, Grade M3, in the Operations function. She left of her own accord and her final dues were settled in full.
This letter is issued at the employee’s request. It is signed with the organisation’s key, and anyone holding it can check that it was issued by us and has not been altered, at the address below.
14 JUL 2026 · 11:42 GST
KEY FINGERPRINT 4C9E · 21A7 · 88B2 · 0F3D
An illustrative experience letter. Offer letters and increment letters carry the same approval, the same signature and the same public check.
Northwind Metal Works FZ-LLC issued this document.
- ✓IssuerNorthwind Metal Works FZ-LLC · key 4C9E 21A7
- ✓Issued14 July 2026 · letter LTR-26-0418
- ✓TypeExperience letter, approved before issue
- ✓IntegrityContent matches the signed record
- ✓StatusNot revoked, not superseded
Select the second option above to edit two lines of the letter and check the altered copy. The document still looks correct; the comparison against the signed record is what fails.
Be precise about what a verification is worth
What the check proves
- That this document was issued by this organisation, out of its own system, signed with its own key.
- That it has not been altered since it was issued. One changed character fails the check.
- That it has not been revoked, or superseded by a later letter for the same person.
- Who approved it, and when they approved it.
What the check does not prove
- That the contents are true. The facts in the letter are the organisation’s own assertion, as they always were — verification is about origin and integrity, not about truth.
- That the person handing you the letter is the person named in it. Identity remains the checker’s job.
- Anything else about the employee. The page answers one question about one document and volunteers nothing further.
This distinction is the whole reason the feature is worth having. A verification that claimed to prove the contents were true would be a lie about cryptography; a verification that proves the document is authentic and unaltered removes the argument that actually happens — the one about whether the letter is genuine.
Who actually checks
Every one of these is a person who today either accepts an unverifiable document or delays a decision while somebody confirms it by telephone.
A future employer
Background screening that currently ends in an email to an HR inbox and a wait of several days.
A bank or a landlord
A salary or employment letter used in a credit or tenancy decision, where a forged copy is a known risk and everybody knows it.
A visa or immigration officer
Documents assessed by someone with no relationship to your organisation and no way to telephone it during the appointment.
The employee
Someone who wants to know that the letter they were given will stand up before they submit it somewhere that matters.
Respect at Work
Conduct duties, resolved
by jurisdiction.
A conduct obligation is a legal one. Where the statute applies to your organisation, a published policy, a constituted committee, delivered training and a complaint procedure are requirements — and their absence is normally discovered at the worst possible moment, which is when the first complaint arrives. PMS resolves which set of obligations applies from the jurisdiction of the legal entity the person is employed by.
- IndiaPOSH
India's statutory regime for the prevention, prohibition and redressal of sexual harassment at work. Where it applies to your headcount, an internal committee is not a matter of policy preference: it must exist, it must be constituted correctly, and its handling of a complaint must be recorded. PMS carries the policy, the training record, the committee composition and the complaint workflow as part of the same person record the review cycle runs on.
The reason it belongs in this product rather than in a separate compliance tool is that the evidence lives in the same place as everything else about that employee — and a conduct matter under enquiry is precisely the sort of thing a rating and an increment should not be resolved in ignorance of.
- UAE · Saudi Arabia · OmanLabour-law conduct duties
The Gulf markets impose conduct duties through labour law rather than through a single named statute. The obligations are not identical to India's and PMS does not pretend they are: what is identical is the shape of the response — a policy that has been published, training that has been delivered and recorded, a body that hears a complaint, and a procedure whose steps are dated.
That is why the module is described as self-configuring. The four workflows are the same four workflows; which of them the statute requires, of whom, and to what standard is resolved from the jurisdiction rather than from a configuration document your HR team maintains by hand.
Policy
The published document, with a version and a date, and a record of who it was issued to. An unpublished policy is not a policy, and a policy nobody was shown is very hard to rely on afterwards.
Training
Completion tracked per person, so the answer to who has been trained is a list rather than an assumption. It sits on the person record, which means it survives a change of manager.
Committee
Membership recorded and maintained, including the changes to it. A committee whose composition lapsed is a committee that cannot properly hear a complaint, and that is the sort of failure nobody notices until it is examined.
Complaint handling
A restricted record, visible only to those entitled to see it, with each step and its date written down and the outcome recorded. The workflow exists so that an enquiry can be shown to have been conducted, not merely asserted to have been.
How it works
Four steps, not three.
Most performance products stop after two of these, and hand the third to payroll as an instruction. The fourth — the document at the end, and whether anyone can trust it — is usually nobody’s feature at all.
- 01
Rate
Leaves with: a scoreSelf, manager and reviewer stages across KRA and KPI cycles. Score against every KPI, or record one consolidated score for the stage. Succession planning runs on the same cycle rather than as a separate annual exercise, because the evidence a succession conversation needs is the evidence the cycle has just collected.
- 02
Calibrate
Leaves with: an agreed ratingRatings are compared against a distribution with a bell curve, in calibration sessions that are recorded. A rating that moves carries the reason it moved; a rating that is challenged and held carries that too. This is the step that turns an opinion into a defensible decision, and it is the step organisations most often run in a spreadsheet nobody keeps.
- 03
Pay
Leaves with: a resolved figureThe compensation engine resolves the salary structure and the statutory deductions for the country the employee is employed in, in that country’s currency, and applies the increment strategy without flattening the component structure. Gulf wage-protection figures are computed today; the bank-file (WPS) export is on the roadmap and is not in the product. The resolved figure goes to FlowZa Finance to be paid.
- 04
Document
Leaves with: a checkable letterAn approved letter, signed with your organisation’s key, that anyone holding it can verify as authentic from a public page. Then the loop closes: the next cycle opens against the same person record, with the last cycle’s rating, calibration minute, resolved pay and issued letters already attached to it.
Your data, in your region
Per-tenant isolation at the database
Isolation is enforced in the database rather than by application code that has to remember to filter. Performance ratings and pay decisions are among the most sensitive records an organisation holds, and this is the level at which that should be handled.
Region-configurable hosting
Where the data sits is a configuration choice, which matters when the answer has to satisfy a regulator or a group policy rather than a preference.
Full export at any time
Cycles, ratings, calibration minutes, resolved pay and issued letters export on request. No lock-in, and nothing to build first.
What a cycle carries with it
KRAs and KPIs, per cycle
Key result areas and the indicators under them are defined per cycle, so a change of objectives mid-year is a new cycle rather than an edit to the record of the old one.
Succession planning on the same cycle
Successor readiness is assessed against the same evidence as the rating, in the same cycle, by the same reviewers. It is not a separate form filled in from memory in a different quarter.
A payroll instruction, not an email
The resolved increment leaves PMS as a structured instruction carrying the employee reference your payroll system already uses, so it can be read straight in rather than typed into a payroll screen from a PDF.
Where PMS sits in the nine
Payroll pays it.
PMS decides what
payroll should pay.
Separating the decision from the disbursement is the point. PMS owns the review, the calibration and the compensation decision, and issues the result as a structured payroll instruction. Your payroll system owns the run, the statutory filings and the postings — whether that is FlowZa Finance on its own subscription, or the system you already have.
PMS owns
- The KRA and KPI cycle, and the self, manager and reviewer stages within it.
- The calibration session, its reference distribution and its minute.
- The compensation decision: structure, statutory rules and increment strategy resolved for the employee's country.
- The letter, its approval and its signature.
How the handover works
- PMS issues a structured payroll instruction: the resolved figure with its component structure intact, not a single new total.
- Your payroll system reads it — over the PMS API, or as a scheduled file if that suits your process better.
- They are two separate applications with two separate databases. The handover is one you configure deliberately, not something that happens underneath you.
A payroll system owns
- The payroll run that pays the figure PMS resolved.
- The statutory files — including the WPS bank files for the Gulf, which is where that export lives today.
- The postings to the double-entry ledger, so the increment appears in the books as it is paid.
If you buy only one of the two, PMS still resolves the figure and still issues the letter; you would export the figure into whatever runs your payroll. What you lose is the part where nobody types it twice.
Where a customer quote would sit
There is no testimonial on this page. PMS is live and in use, and we will publish a quote when a real, named customer gives us one we can attribute.
On a page whose argument is that a decision should be verifiable, an invented endorsement would be an odd place to start. This sentence tells you more than a plausible one from nobody in particular would.
The four published numbers
Four markets computed in local currency. Four loop stages. Public third-party letter verification. New countries by configuration, not code. Those are the claims this product publishes, and everything shown above them on this page is illustrated mechanism rather than a measured result.
Questions HR leaders ask
Does PMS run our payroll?
No, and that is deliberate — deciding pay and paying it are different jobs with different evidence behind them. PMS resolves what someone should be paid from a rating that has been calibrated, against the statutory rules of their country, preserving the component structure of their salary. It then issues that as a structured payroll instruction your payroll system reads. That can be FlowZa Finance, which is a separate application on a separate subscription, or the payroll system you already run.
Is bell-curve calibration a forced ranking?
No. The distribution is a reference the cohort is compared against, not a quota the cohort has to fill. In the session shown above, nine of thirty ratings moved and the calibrated result deliberately does not match the reference curve. What the mechanism requires is not conformity but explanation: a rating that sits away from the distribution has a recorded reason next to it, and so does a rating that was challenged and left where it was.
What does the public verification page actually prove?
That the document was issued by your organisation, that it has not been altered since it was issued, that it has not been revoked or superseded, and who approved it. It does not prove that the contents are true — the facts in a letter are your organisation’s assertion, as they always were — and it does not prove that the person holding the letter is the person named in it. Those limits are worth stating, because a verification that claimed more would be worth less.
Can PMS produce our WPS bank file?
Not today. PMS computes the Gulf wage-protection figures; the bank-file export is on the roadmap. If that file is what you need this quarter, it is produced in FlowZa Finance, which is where the payroll actually runs. We would rather answer this here than in your second week of implementation.
How do we add a fifth country?
As configuration. Salary structures, statutory rules and increment strategies are data, so a new market is a rule set that is entered, tested and run in parallel for a period — not a change to the product and not a release you wait for. The four markets published today are India, the UAE, Saudi Arabia and Oman, each computed in its own currency.
Who can see a rating, and what is recorded when one changes?
Access follows the role: the employee, the manager, the reviewer and the calibration participants see different things, and a conduct complaint record is restricted further. When a rating changes, what is recorded is the movement, the session it was agreed in, the people present, the reason, and any dissent — including dissent that did not carry. The minute is appended rather than edited; a later decision supersedes it and is minuted in turn.
Is Respect at Work a separate module we configure per country?
It is one module that resolves your obligations from the jurisdiction of the legal entity the person is employed by — POSH in India, labour-law conduct duties in the GCC. The four workflows are the same everywhere: policy, training, committee and complaint handling. What differs is which of them the statute requires of you and to what standard, and that is resolved rather than maintained by hand.