Product
A pilot in six steps.
A Reconora pilot takes one day of your own data through six steps: you export the day, anonymise it at your site and hand over the package; Reconora checks it, reconciles your log, notifications and statements, and returns your day in four outcomes with claim candidates and blind spots. The examples below are synthetic.
Step 1 · At your site
Export one day
Any recent day with a log export and provider statements. No integration and no production access.
orchestrator_log.csvyour log and the provider messages it recordsstatement_provider_A.xlsxthe provider’s statement for the same daystatement_provider_B.csveach provider in its own format…one statement per provider you include
Step 2 · At your site
Anonymise at your site
The module runs offline on an ordinary laptop: 1.5 million log records took 40.3 minutes on the measured day. The encoding table and the secret stay with you.
provider: DemoPay
currency: EUR
customer: Jane Example
email: jane@example.org
phone: +00 000 000 0000
ip: 198.51.100.24
card: 4000 0000 0000 0002
customer_id: C-104233
txn_id: DP-20260115-0091
amount: 150.00
status: success→provider: P-017
currency: C-03
customer: —
email: —
phone: —
ip: —
card: 400000******0002
customer_id: U-7d2f91c0
txn_id: DP-20260115-0091
amount: 150.00
status: successStep 3 · At Reconora
Check the package
Every package carries SHA-256 fingerprints and a verification report. Every record must be accounted for before anything is reconciled.
records 1.5 million
parsed 1,187,215
skipped 329,997
quarantined 9,635
balance OK
sha256 7c41…e09a (illustrative)Step 4 · At Reconora
Reconcile three sources
Your log, the provider’s notifications and its statement are matched line by line; every payment ends in one outcome with a reason.
| Payment | Provider | Log | Notif. | Stmt | Outcome |
|---|---|---|---|---|---|
PAY-18D1B100.00 CUR-1 | Provider F | ✓ success | ✓ success | ✓ success | Matched |
PAY-BC44991.00 CUR-3 | Provider C | ✕ declined | ✕ declined | ✓ success | Differs in factsClaim candidate |
PAY-9D1C254.00 CUR-2 | Provider B | ✓ success | ✓ success | ✓ success | Differs in money |
PAY-B2F9E667.00 CUR-3 | Provider C | ✓ success | ✓ success | ✓ success | Matched |
STL-7C9361.00 CUR-4 | Provider G | — No record | — No notification | ✓ success | Differs in facts |
PAY-C1A0844.00 CUR-2 | Provider Q | ✓ success | ✓ success | — The provider sent no statement | Nothing to reconcile against |
PAY-F339348.00 CUR-3 | Provider P | ✓ success | ✓ success | — Not in the statement | Differs in facts |
PAY-13E79143.00 CUR-1 | Provider F | ✓ success | ✓ success | ✓ success | Matched |
PAY-31F2F66.00 CUR-1 | Provider A | ✓ success | ✓ success | — In the next day’s statement | Awaiting |
Step 5 · At your site
Read your day in four outcomes
Matched, differs in money, differs in facts, nothing to reconcile against — and what is still awaiting a statement. Every figure opens down to its source row.
Synthetic data
| Outcome | Payments | Share | What it means |
|---|---|---|---|
| Matched | 5,014 | 83.0% | Amount and outcome agree on every side. |
| Differs in money | 13 | 0.2% | The amount differs; the difference is stated. |
| Differs in facts | 130 | 2.2% | One side only, or reversed outcomes. |
| Nothing to reconcile against | 702 | 11.6% | No statement, none for the currency, or an incomplete one. |
| Awaiting | 182 | 3.0% | No final status yet, or the payment falls into the next day’s statement. |
Step 6 · At your site
Send claims, request statements
Discrepancies with one provider are grouped into a claim with evidence. Blind spots tell you which statements to request first.
Synthetic data
Provider C · players charged, not credited · 18 payments · 5,681.00 CUR-3
| Payment | Amount | Log | Notification | Statement | Source rows |
|---|---|---|---|---|---|
PAY-BC449 | 91.00 CUR-3 | declined | declined | success | log.csv · row 81stmt_C.xlsx · row 10 |
PAY-C49E6 | 21.00 CUR-3 | declined | declined | success | log.csv · row 780stmt_C.xlsx · row 70 |
PAY-310A8 | 37.00 CUR-3 | declined | declined | success | log.csv · row 1,537stmt_C.xlsx · row 137 |
PAY-FCCCC | 79.00 CUR-3 | declined | declined | success | log.csv · row 1,571stmt_C.xlsx · row 138 |
PAY-96883 | 344.00 CUR-3 | declined | declined | success | log.csv · row 1,951stmt_C.xlsx · row 176 |
…and 13 more in the CSV register. Status: not filed. Next step: approve and send the package to the provider.
Who does what
Three of the six steps happen at your site: exporting the day, anonymising it and reading the result. Reconora only ever handles the anonymised package — see what runs where. The examples in the tour are synthetic: fictional providers (Provider A…T), placeholder currencies and invented amounts.
Try it with a synthetic day
Pick any payment from a synthetic day and see the three sources side by side in the sandbox, or read the full sample pilot report. To prepare your own pilot, see the pilot quickstart.
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