Security

What runs where.

Anonymisation runs inside your perimeter, offline. Only an anonymised package crosses to Reconora: codes, hashed identifiers, amounts, statuses and timestamps, with a verification report and SHA-256 fingerprints. Reconora reconciles it and returns the result in the same codes. The encoding table never leaves your company, so only you can decode the result.

  1. Logs and statements. One day of your orchestrator log and provider statements, exported as they are.
  2. Anonymised at your site. The module runs offline with the Python standard library and no network access; you can audit its full source code.
  3. The encoding table stays with you. The table and the secret are created at your site on the first run. Reconora never receives them.
  4. Only the package crosses. Provider and currency codes, hashed identifiers, amounts, statuses and timestamps, with a verification report and SHA-256 fingerprints.
  5. Reconora reconciles. The record balance is checked, every provider is translated into one model, and your log, notifications and statements are matched.
  6. The result comes back in codes. Outcomes, discrepancies with row addresses, claim candidates and blind spots.
  7. Decoded at your site. With your own table — only you can read it.
Everything left of the line runs inside your company. Only the anonymised package crosses it, and only the result in codes comes back.

Inside your perimeter

Your team exports one day of the orchestrator log and the provider statements, as they are. The anonymisation module runs on an ordinary computer at your site. It works offline, uses only the Python standard library and makes no network calls. You receive its full source code, so your security team can read every line before it touches your data.

On the first run the module creates the encoding table and the secret. Both stay at your site. Without them the codes in the package cannot be reversed.

What crosses the line

Only the anonymised package leaves your company:

  • provider and currency codes instead of names;
  • identifiers as shape-preserving hashes, so matching still works;
  • amounts, statuses and timestamps;
  • a verification report and SHA-256 fingerprints of every package and source file.

Names, e-mails, phone numbers, IP addresses, full card numbers, IBANs, document numbers and provider names never leave. Neither do the encoding table and the secret. What leaves, what never does

At Reconora

Reconora first checks the package: the declared record count must equal parsed plus skipped plus quarantined records — the record balance. A package is used only after your controller accepts it. The engine then reads every provider’s messages in their native format, translates them into one canonical model and reconciles your log, the notifications and the statements line by line. Every action — intake, runs, approvals, claims, rule changes — goes into a tamper-evident audit trail.

What comes back

The result comes back in the same codes: every payment in one of four outcomes, discrepancies with reasons and the addresses of their source rows, claim candidates with evidence, and blind spots where no statement exists. You decode it at your site with your own table. Reconora never moves money: there is no pay, block or refund button.

What you do not need

No access to your production systems, no API integration to start, no personal data and no change to your finance team’s processes. How the pilot works

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.

By Reconora Research · Updated