Ready for accounting review
Expected evidence present, exceptions resolved.
For modern accounting practices
Know what's ready before you open the file.
Every client in one view. Documents confirmed, bank movements explained, missing evidence visible.
Invited by a client? Your read-only access is already there — nothing to set up. This is for practices running their own dossiers.
Dokus verifies financial evidence and prepares the dossier. The accountant validates accounting treatment and files through the existing accounting system.
Today · your practice
32 clients3 need you2 need you1 needs you
Architectenbureau De Groote
Bank statement missing · Request open
VAT deadline
Intake complete, ready for your review.
This morning
The rest stay quiet.
You shouldn't discover on the 18th who wasn't ready on the 10th.
The practice view
One view across the practice. A dossier is ready when the expected evidence is present and its exceptions are resolved — and when it is not, the row says why.
Today
Architectenbureau De Groote
Bank statement missing · Same invoice, several copies — group unresolved
Adviesbureau Pieters BV
Ready for review
Boomkwekerij Vermeulen
Ready for review
Merelhof BV
Ready for review
32 clients · 31 ready
Expected evidence present, exceptions resolved.
Reasons listed, not reduced to a score.
Sent to clients, not yet answered.
You open the one that needs you. The rest stay quiet.
"Ready" means the expected evidence is present and exceptions are resolved. It does not mean Dokus has made the final accounting or VAT decisions.
The blocked dossier
A dossier is not "87% done" because an average says so. It is ready only when its required evidence is complete — documents confirmed on one side, bank movements explained or categorised on the other.
No comfortable score hiding an unfinished dossier.
Architectenbureau De Groote
Q3 2026Blocked on
A supplier can send Peppol while the client forwards a PDF and photographs the paper copy. Dokus resolves them to one financial fact and keeps every source attached — so nothing gets booked twice.
1 request open — the client has the link.
Requests
Missing evidence becomes a request, not a chase. The request carries a link, the link carries the upload, and the dossier updates as answers land.
No portal to onboard clients into, no account for them to create. A photo from a phone or a forwarded email counts as the upload.
The questions that reach you stay accounting questions.
Start the day knowing what will need you.
Before your ledger
Dokus is the intake layer that sits before accounting: reading documents, matching transactions, and holding back anything it cannot support with evidence. Your practice keeps filing where it files today.
Each client arrives as records checked by Dokus — identities, totals, VAT arithmetic and references — which you export into the software you already run. No general ledger to migrate, no parallel system to reconcile.
Ask any supplier what portability looks like — which formats, how quickly, and what happens on the day you stop. Here: one export, from inside the product, whenever you want it — the source documents included, not only the ledger. Nothing about your clients' records depends on Dokus still being here.
You validate. You file. Dokus only removes the chaos before it reaches you.
Export: CSV with the original documents alongside. Import compatibility per package is tested during the pilot, never claimed in advance.
The handoff
What an export contains, what it holds back, and what it never claims to be.
Practice access
Boundary
Dokus sits before accounting and stops there. What it claims about itself, this page has already shown: Belgian-built, evidence-first, and explicit when something goes wrong.
Built and hosted in Belgium. GDPR by design.
Tenants isolated at the data layer. No cross-client aggregation.
You monitor and request. Dokus does not make you the operator of another accounting system.
Everything held back is listed, with its reason. Failed transmissions say so. Nothing fails silently.
Every figure traces to a document. You are never asked to trust a number you cannot check.
When it breaks
A practice needs an escalation, not a helpdesk script. Filing weeks are inside the window, and so are Saturdays and the 20th — you will not have to explain what a CODA file is, or why that date matters. The window below is the standard we hold ourselves to; it is a commitment, not a contractual service level.
support@dokus.tech, every day between 08:00 and 20:00 CET, except Belgian public holidays and absences announced in advance — never later than the same day. No first line, no second line: the reply comes from the people who build Dokus. Support is the same for whoever writes — the practice, or a client on Free.
Phone and messaging
Quick questions are fine here. Documents and client data go by email, not by chat.
Put URGENT in the subject and a number we can call. An escalation is a phone call, not a faster email.
A Peppol invoice that did not arrive says so, with its reason, and the retry is visible. You will not hear about it from your client first.
What happens to your clients' records if Dokus stops is written down, including the certifications and audits we do not yet hold.
Continuity and supplier assessmentThe clients that need you are visible. The rest stay quiet.
Start with five. Count what reached you that was about the product rather than about the books.
Dokus prepares reality. You validate and file it.