A strict setup. Nothing left to chance.
We don't plug an AI into a company and hope for the best. Every step is written, demonstrated, measured. You approve each one.
The process, step by step
Written scope
What it reads, what it doesn't. Which mailboxes, accounts, documents. Your reference details (company name, registered office, VAT number). Signed by you before any installation.
Dedicated, minimal access
Its own sending mailbox, separate from yours. Read access where reading is enough. No shared passwords: revocable, named access.
Identified installation
On a known machine, on your premises or in your name: your computer, or a small dedicated machine. You know where it runs and who can touch it.
Observation period
For at least two weeks it reads, files, matches and prepares. It sends nothing. You see what it would have done, in the log.
Review with you
The register and the log, line by line. What it did well, what it missed, what it asked. We adjust the rules.
Step-by-step activation
One capability at a time: document requests first, then reminders, then send mode if you want it. Each demonstrated before the next.
Throughout
Kill switch, sending cap, copy to you, log. And at any time, an external audit, under NDA if needed.
What is measured, and shown
- Transactions per status: complete, document being searched, exception, delivered.
- The number of questions it asks you, month after month. It must go down.
- The delay between an invoice arriving and the correction request.
- Sends per day, against the cap.
Technical side
- Encryption at rest (BitLocker on the machine) and in transit (TLS to the mail server and the AI provider).
- Backups: yours. Data kept as long as the service is active; the publisher keeps no copy.
- Publisher access for support: with your agreement, traced in the log.
- End of service: your data handed back within 10 working days, the assistant's machine wiped, written confirmation.
Your bank
A precise specification. You set what it sees.
Today the assistant reads a CSV export from your bank. Reading through an API is only offered if your bank meets our specification, and sme luxembourg decides, bank by bank.
What a bank must allow
- Read-only access through its official interface: no payment, transfer or modification capability.
- A scope chosen by you: which accounts, which period, which transaction categories. The rest is not read.
- Access you can revoke at any time, on your side, without going through us.
- An access log you can consult.
What you decide
- What the assistant sees, and what it doesn't.
- What it may do with it: match, file, request a document. Never pay.
- When it stops.
Revolut Business: CSV export verified, read-only API demonstration in progress. BGL BNP Paribas, BIL, Banque Raiffeisen: PSD2 API published, review in progress. The full specification and status per bank are on this page. If your bank doesn't meet these conditions, we stay with the CSV export, which works.
What it never does without you
It doesn't pay. It doesn't send. It doesn't sign. It doesn't commit your company.
Draft mode
Every e-mail, every request waits for your approval.
Log
Every action is traced, dated, readable.
Kill switch
One gesture, and all sending stops.
Sending cap
A maximum number of sends per day, and a copy to you every time.
Where we stand
We are not here to experiment on your company. We are here to keep a precise promise: your documents, your reminders, your deadlines, kept.
No smiling little robot, no elf, no colourful astronaut. A system of algorithms, written rules, a log. It doesn't smile, it works.
So you can focus on what really matters: your business.