Normalisation
Normalisation is the translation of every provider’s callbacks, responses and statement lines into one canonical model, with the same fields for status, amount, currency, time and identifiers. It makes payments from many providers comparable, and it is the precondition for reconciling them with one set of rules.
How it works
Normalisation applies one rule per provider message shape. The rule says where each value sits and how to read it. An illustrative message and its result:
raw: {"payment":{"status":"paid","sum":"15.00","cur":"CUR-1","ts":1760000000}}
normalised: status: success · amount: 1500 (minor units, precision 2)
currency: CUR-1 · time: UTC, source: provider · id: kept with origin
The amount becomes an integer in minor units. The time gets a zone and a source. Every identifier is kept with the place it came from.
Why it matters
Providers disagree on the basics. On one anonymised merchant day Reconora applied 190 amount rules for values in major units and 51 for values in minor units, and read 5 time formats. Read with the wrong rule, an amount is off by a factor of a hundred, or a payment lands on the wrong day.
How to spot it
Look for symptoms in your reports. Amounts that differ by exactly a factor of a hundred. Times shifted by whole hours. Statuses that some provider sends but no mapping covers. Each one points to a value read without a rule.
Related terms
Canonical status · Message shape · Minor units · Record balance · The normalizer
Try it on one day of your data
One day of your data, reconciled, and the report stays with you whether or not you continue.
Updated