# From raw logs to a reconciled day in about an hour.

You install a small anonymisation module, run it on one day of your orchestrator logs and provider statements, and hand over the anonymised package. Reconora translates every provider’s format into one model, reconciles it line by line and returns a result you decode locally. Measured on a real day: about an hour of machine time.

## Four steps

1. **Install the module.** One folder, Python 3.11+, standard library only. It works offline and sends nothing over the network. You receive its full source code — [how the anonymiser works](https://reconora.com/security/anonymiser).
2. **Anonymise a day.** 1.5 million log records took 40.3 minutes on an ordinary laptop; a full statement workbook took 2.9 minutes. The encoding table and secret are created at your site and stay there.
3. **Hand over the package.** Anonymised files plus a verification report. Nothing personal, no provider names.
4. **Get the result.** Reconciliation, discrepancies with reasons, claim candidates and blind spots — in codes you decode with your own table.

> **Fact.** Measured machine time to the first reconciliation: 63.1 minutes (40.3 logs + 2.9 statements + 17.3 engine + 0.1 reconciliation).

## What happens inside

1. **Read in native format.** Each provider’s callbacks, responses and statement lines are read as they are — own fields, statuses, units, time formats. Providers are recognised by the structure of their messages; nobody on the provider side has to change anything.
2. **Translate into one model.** Every message becomes an event in one [canonical model](https://reconora.com/canonical-model): the same status, amount, time and identifier, whatever the provider called them.
3. **Fold into transactions.** Many events describe one payment. 790,948 events folded into 318,804 transactions in one day; repeated observations of the same fact are counted, not duplicated.
4. **Reconcile three sides.** Your log, your notifications and the provider’s statement are matched line by line, using several keys — your ID, the order ID, the provider’s ID.
5. **Name the outcome.** Every line ends in one of four outcomes, with a reason.

## Nothing is lost silently

Every record is accounted for: 1.5 million records = 1,187,215 parsed + 329,997 skipped by rule + 9,635 quarantined with an address and a reason. The balance is checked on every run.

## Measured, not promised

Every figure below was measured on one anonymised merchant day; none is an estimate or a vendor average.

| What was measured | Result |
|---|---|
| Log records anonymised on an ordinary laptop | 1.5 million in 40.3 minutes |
| A full statement workbook anonymised | 2.9 minutes |
| Engine run | 17.3 minutes |
| Reconciliation | 0.1 minutes |
| Machine time to the first full result | 63.1 minutes |
| Events folded into transactions | 790,948 into 318,804 |
| Message shapes recognised | 1,198, from 96 providers |
| Raw status values translated | 318, into 9 meanings |
| Statement formats configured | 35 |
| Records lost without a reason | None: every record is parsed, skipped by rule or quarantined |

[How every number is produced](https://reconora.com/methodology)

## What we need — and what we don’t

| We need | We don’t need |
|---|---|
| Orchestrator log export (CSV) | Access to production systems |
| Provider statement workbook (xlsx) | An API integration to start |
| A computer with Python 3.11+ | Any personal data |
| | Changes to your finance team’s processes |

[Start a free pilot](https://reconora.com/pilot) · [Book a 20-min call](https://calendar.google.com/calendar/appointments/schedules/AcZssZ2qcg1D27PGeYQ91fuYaSo7oy6D4tQ0onTGhC2mSdAWZpCuMUozMxIan4qYWtSk56H-hZTTZAC7)

---
Source: https://reconora.com/how-it-works · Updated 2026-10-18
