The cheapest correction is the one made before the record exists in four systems.
| Entry point | How the rules run | What the person sees |
|---|---|---|
| SAP or Oracle create screens | Through the ERP's own validation exits, which call Lima's rule service with the screen's fields | The ERP's own message, with the fix proposed; the record saves clean or is held |
| CRM forms | Through the CRM's validation rules calling the same service | An inline correction (“GB” for “United Kingdom”) and a duplicate warning with the existing record |
| Lima app forms | The rules are part of the form; the duplicate search runs as the person types | The form corrects as it goes; a held record shows who will review it and when |
| API | The headless API's create call runs the rules and returns the outcome with the findings | The calling system receives accepted, corrected or held, with the reasons |
| Partner files | The file is read in place; each row runs the rules; the outcome is returned per row | A file report with the rows accepted, corrected and held, and why |
The rules are the same objects the golden record uses, so a change to a rule applies at the entry points on the next save. There is a single rule set, and the entry points inherit the packs' thresholds and the four-eyes marks.
The order matters for the person at the screen: format problems are fixed in the field, row problems on the form, duplicates before anything is saved, and verification runs while the form is still open. A held record tells the person who will review it and when, so nothing disappears into a queue unexplained.
| Outcome | When | What happens to the record | What the consumer sees |
|---|---|---|---|
| Accepted | Every applicable rule passes at save | Born golden; write-back to the other owners runs at once, acknowledged | A golden record on the next read |
| Corrected inline | A rule fails and the corrector has a fix above the confidence floor | The fix is shown in the form and accepted by the person; the record is born golden with the correction in its ledger | A golden record, with the correction visible in the history |
| Held for review | A rule fails with no fix, or the field carries the four-eyes mark | Saved in flow; the ticket goes to the escalation route; consumers wait or read the in-flow view | The state 'in flow' with the pending checks, through the API's status field |
In the centralised style, records are created in Lima first, so the form is Lima's and the rules are simply part of it; the record is published to the ERP and the CRM once golden. In the coexistence style, records are created in the ERP or the CRM and the rules reach them through the validation exits and the APIs; the record is read in place at once and checked again as part of the golden loop.
In both styles the same rule set applies, and the result is the same: a record is born clean, or born in flow with its reasons. The implementation styles page explains how the style is chosen per domain.
The cost argument is the reason this page exists. A country typed as “United Kingdom” and corrected in the form costs a second. The same value saved, replicated to three other systems, read by planning and finance, and found a month later costs four corrections, four acknowledgements and a reconciliation of the reports that used it. The estimate of four times is conservative; the reconciliation is usually the larger part.
Column and row rules answer in milliseconds; the duplicate search and the verification run while the person is still typing the rest of the form. On the showcase estate a supplier form with verification completes in under two seconds.
The API path covers it: the create call runs the rules and the ERP receives an accepted record. Where neither is possible, the record is read in place on creation and checked within the minute, and the finding goes to the entry point's owner.
A partner file is read in place, run through the rules per row, and reported back per row. Partners see the same outcomes and reasons the internal entry points see.
Bring one domain and two systems. In a week the sources are profiled, the ten costliest fields are under rules, the first corrections are written back with their acknowledgements and the publish gate is on.