Evidence and attestation
The reconciliation you can hand to an auditor without a covering note
If you hold funds on behalf of customers, someone will eventually ask you to prove that the money was where you said it was, on a specific day, and that a named person checked. Assure produces that proof as a by-product of the work your team already does.
7 years
of runs replayable at their original engine version
What it does
Inside Assure
Daily attestation record
A dated statement of relevant balances against the corresponding obligation, the reconciling items, and the named approver. Generated from the run, not retyped from it.
Immutable run history
Inputs are hashed on ingestion. Every match, every override and every posting is written to an append-only record with the operator, the timestamp and the engine version.
Replay at original version
Rules change. A run from eighteen months ago replays under the rules that were live that day, which is the only way to answer an auditor's question honestly.
Four-eyes controls
Configurable segregation of duties by value band, reason code and account. The approver can never be the preparer, and the system will not let a workaround exist.
Evidence packs
Any period exported as a structured pack — reconciliation summary, exception register with resolutions, override log, control attestations, and the underlying source files.
Break ageing register
Every unresolved item with its age, owner, value and last action, so the question 'what is still open and who has it' has one answer rather than four spreadsheets.
In depth
Built for the conversation you will have later
Assure exists because the hardest part of an audit is never the reconciliation itself. It is reconstructing, months afterwards, what was known at the time and who decided what to do about it.
- 01Source files retained exactly as received, hashed, alongside the canonical records derived from them.
- 02Every parameter change recorded with who changed it, when, and what the previous value was.
- 03Overrides require a reason from a controlled list plus free text, and are reported separately.
- 04Exports are structured data, not screenshots, so an auditor can test them independently.
- 05Retention configurable to your regulatory obligation, with legal hold on any period.
Specification
- Record model
- Append-only, hash-chained
- Segregation of duties
- By value, reason code and account
- Export
- Structured pack with source files included
- Retention
- Configurable, default 7 years
- Data residency
- EU, single region, no cross-border processing
“I care about one thing: can I show an auditor what was known on a given day and who decided what to do about it. Replay at the original engine version answered that in a way no other tool we looked at could.”
Chiara Bettoni
Group Financial Controller, Aurelio Capital · Italy