The external confirmation season, built end to end.
Confirmatica is a working platform that runs the audit confirmation season: ledger import, ISA 530 sampling, client e-sign authorization, verified dispatch, zero-login responder intake, AI-assisted extraction with deterministic verification, reconciliation, and working papers — one platform, one evidence trail.
Confirmatica is licensed software, deployed on the licensee's own infrastructure. It is built for the Dutch audit market; Czech is available as an option, and further localizations are planned for later releases. A demonstration runs on a synthetic tenant; no firm's data is on it.
- Eight kinds of request
- Bank balances, bank relationships, receivables, payables, legal, insurance, leases and general.
- Three languages for every third party
- Dutch, English and Czech — the letters, the portals and every e-mail a counterparty or a client's director reads.
- Licensed, not rented
- Deployed on the audit firm's own infrastructure; the firm is the operator and controller of its instance.
- Supported and maintained
- By Bonfleur s.r.o., the developer and licensor, under the maintenance agreement — after a demonstration on synthetic data.
Enclosure — the audit team's home screen
What a confirmation season asks of a firm
The response rate is decided at the responder's desk
A bank's confirmation desk, a customer's bookkeeper, a law office, an insurer has no account, no training and two minutes. Every surface a third party meets is built for that desk: a request in its own language, a portal with no login, a reply route by plain e-mail, and a way to refuse that the file records as a refusal rather than as silence. What the responder seesThe auditor controls the request and receives the reply
ISA 505 ¶7 puts the request, the address it goes to and the route the answer takes in the auditor's hands. Letters and e-mails leave under the firm's own identity, to a contact whose address an auditor has verified, and each confirmation has its own return route back to the auditor. A reply from an address the request was not sent to is still taken as evidence — recorded as a sender mismatch and routed to a person, because that is exactly the doubt the standard asks the auditor to resolve.Most confirmation tools stop at delivery
The request arrives, and the work from response back to reconciled, documented evidence stays manual. Confirmatica was built to own that last mile: the seven stations below are stations in one platform, not separate tools stitched together, and nothing reaches a working paper without either full automated verification or a recorded human decision.Silence is an audit problem, not an inbox problem
Reminders run on a calendar the audit team sets per batch — by default at day 14 and 28, with the counterparty recorded as unresponsive at day 45, and never before the date the letter itself gave it to reply. The file then receives the ISA 505 ¶12 alternative procedures for that instrument, and the platform withholds the one thing it must: the conclusion, which is the auditor's judgement. What the file receives
One season, seven stations
A season on the platform runs like this. A ledger is imported. An ISA 530 sample is drawn and the partner approves it. The client's director e-signs the information-release authorization with a one-time code sent to their mailbox. Letters go out under the firm's own identity. Counterparties answer online, by replying to the e-mail with a document, or off-platform — in which case the firm files what it received with a statement of how it arrived, when, and who received it. A stated balance that agrees reconciles without a person; a difference or an exception waits for a named human. Silence is chased on a calendar and, only after the chase, certified as a non-response, with ISA 505 alternative procedures prepared for the auditor's own conclusion. The season closes into a lead schedule, a working paper per confirmation, and an evidence pack a regulator can read — materiality and the sampling basis stated in it.
Eight kinds of request, one platform
4 answered against the ledger
Bank
The balance held on an account at the as-of date, addressed to the bank's confirmation desk with the IBAN or account number printed so the account can be located without a phone call.
Receivables
The amount a customer owes the audited company at the as-of date, confirmed by the customer against its own books — the classic positive confirmation of a debtor balance.
Payables
The amount the audited company owes a supplier at the as-of date, confirmed by the supplier — the same letter with the direction of the balance reversed.
General
Any other balance a file needs a third party to confirm — a loan, a deposit, an intercompany position — using the same letter, the same portal and the same evidence trail.
4 answered in writing, never as a balance
Legal
An ISA 501 inquiry to the company's lawyers: pending or threatened litigation, claims and assessments, unbilled fees, and anything else relevant to the audit. It is answered in writing, never as a balance — the platform prints no figure on a legal request and offers none to confirm.
Bank relationship
What a bank is asked once rather than per account: every account it holds, loans and credit facilities with their limits and terms, guarantees and sureties given or received, security and pledges and over which assets, and who may sign. It is answered in writing, never as a balance — the platform prints no figure on it and offers none to confirm.
Insurance
What an insurer confirms about the cover it provides: every policy in force at the as-of date and those cancelled during the period, the sums insured and limits of indemnity and the deductibles and exclusions under them, the claims notified, and the premiums outstanding. It is answered in writing, never as a balance — the platform prints no figure on it and offers none to confirm; the premium the insurer states is read against the client's records, not reconciled.
Leases
What a lessor confirms about the leases it has granted: every lease and rental agreement in force at the as-of date and those ended during the period with their assets, dates and remaining terms, the amount outstanding on the lessor's own basis with the payment schedule, the payments received in the period, and the residual value guarantees, options and security. It is answered in writing, never as a balance — the platform prints no figure on it and offers none to confirm; the amount the lessor states is measured on the lessor's basis, not the client's, so it is read against the lease schedule and not reconciled.
What is independently verifiable
- states a confirmation moves through
- 16one status per confirmation, from ledger import to a signed-off working paper
- responder reply channels, zero logins
- 2portal — reached by link or by scanning the paper letter's QR — and plain e-mail reply; both land in the same evidence store
- languages a third party is served in
- 3Dutch, English and Czech — the letters, the responder portal, and every e-mail that leaves the platform for a counterparty
- the standard the workflow is built to
- ISA 505ISA 530 sampling in front of it, alternative procedures behind it for the counterparties who never answer
Human judgement, enforced
A result is auto-accepted only on an exact ledger match, with the responder's currency stated and no deterministic check failing, from a sender the request was actually addressed to — everything else goes to a human. No synthetic confidence percentages anywhere. How review worksControls that cannot be skipped by accident
Dispatch to an unverified contact is refused unless a written override reason is recorded on the audit trail — and the dispatch dialog counts the rows it will skip, and says why, before anything is sent. The partner's controlsA file that shows its own history
Every action on a confirmation is attributable to a named person and the time it happened, and the file cannot be altered afterwards without it showing. The working paper prints that history beside the evidence it belongs to, for a reviewer years after the season closed. The audit fileRun before it is released
The whole season on this site — from a ledger file to an evidence pack, with a third party answering — is run end to end on the real product before a release, in Dutch, English and Czech. Not a slide of it: the season itself. The season, step by step
Architecture and security documentation is available under NDA.
Where the AI stops
The confirmed balance is verified verbatim: it must literally appear in the source document, in some printable variant, or the extraction fails review. Line items are checked by arithmetic — they must foot to that balance — alongside currency and the as-of date.
AI-drafted variance explanations are labelled in the product itself: AI draft — not audit evidence until you confirm or rewrite it. Finalizing requires the auditor's own words. Alternative-procedure conclusions quote ISA 505.12 — the judgement cannot be automated.
Every working paper carries a numbered section recording where a model touched the confirmation, what it proposed, and the named person who accepted, corrected or rejected it. The boundary, as the file records it
How it fits a firm's operating model
One instance per firm, on the firm's own infrastructure
Confirmatica is licensed software. The showcase at this domain runs on synthetic demonstration data. A licensee deploys on their own infrastructure and is the operator and controller of their instance. Bonfleur s.r.o. provides the licence, customization and maintenance. Nothing an audit firm holds in its own deployment reaches Bonfleur: the instance runs on the licensee's stack, under the licensee's control. There is no trial tier, no pricing page and no funnel behind this site — an enquiry reaches a person, and the demonstration runs on the synthetic tenant.Every letter is the firm's own business document
Everything a counterparty receives comes from the firm, not from a vendor: the letter and the e-mail carry the firm's registered name, seat and registration number — its register entry and audit licence too, where the firm has recorded them — and every letter encloses the information-release authorization the audited company's director signed — the document that lets a bank or a counterparty answer the auditor at all.Customization is scoped with the firm, not guessed at
Letter wording, the firm's own directory of counterparties, the ledger formats its clients export, and the storage and e-mail providers of the firm's own stack are agreed before deployment. The curated directory the platform ships with — Dutch banks, Czech banks and insurers — is verified against the public registers and cites each institution's published confirmation channel where one was found.Source-level ownership is a licence conversation
The licence conversation covers the terms, source escrow, an inventory of every third-party component the software depends on, the deployment runbook and the maintenance agreement — under NDA, alongside the architecture and security documentation. No figure and no service level is published here, because a published figure that turns out to be conditional is worse than none.Built for the Dutch market, with Czech as an option
The Dutch reality is engineered in, not localized after: the platform reads real Dutch ledger exports, and Czech ones for the Czech option, and everything a third party receives — the letters, the portals, the outbound e-mail — works in Dutch, English and Czech. The auditor's own screens stay in English.The boundaries are stated before the conversation
Negative confirmation is not offered; custodian and broker confirmations are carved out with the route that ships instead; the Dutch and Czech third-party wording has had no native-speaker legal review. Each position is dated, with its reason and what ships in its place, on the scope page.
From a demonstration to a supported deployment
Step 1: A demonstration
The season described on this site, run on a demonstration instance holding synthetic data. No firm's data is on it.
Step 2: A licence
A written licence agreement with Bonfleur s.r.o. The licence conversation covers the terms, source escrow, an inventory of every third-party component the software depends on, the deployment runbook and the maintenance agreement — under NDA, alongside the architecture and security documentation.
Step 3: The customizations the firm wants
Letter wording, the firm's own directory, the ledger formats its clients export, and the storage and e-mail providers of the firm's own stack — scoped and agreed with the firm before deployment, not guessed at in advance.
Step 4: Deployment on the firm's own infrastructure
The instance runs on the firm's own infrastructure, under the firm's control. The firm is the operator and controller of it; nothing it holds reaches Bonfleur.
Step 5: Support and maintenance
Bonfleur s.r.o. maintains and supports the deployed instance under the maintenance agreement — updates, fixes and the next season's changes reach the firm's own instance.
How a firm comes to run Confirmatica
An enquiry names the firm and roughly how many confirmations its season carries, and a person reads every one. What follows is a demonstration on the synthetic tenant, then a licence, the customizations the firm wants, and deployment onto the firm's own infrastructure — supported and maintained by Bonfleur s.r.o. from then on.
Licensed software, deployed on the licensee's own stack. No trial tier, no self-serve signup.