Stop chasing clients for documents. The recipe tells them exactly what's missing, automatically.
Document collection is a chasing problem, not a filing problem. A client uploads their tax forms, invoices, and bank statements through one secure form. AI compares what arrived against your required-document checklist for that purpose and returns complete or incomplete with a specific list of what's missing. Complete packages ping your accounting team and confirm receipt to the client. Incomplete ones email the client the exact list to re-upload, no one on your side writing that email.
Free · no credit card · you connect your own apps
Installing provisions each one, wired together and ready to run.
Secure intake for a client's period documents: name, email, purpose, period, tax forms, invoices, bank statements, notes. Each submission creates one row in the form's response sheet.
One template with a received variant and a missing-items variant, selected automatically by which branch the workflow takes.
On submission: logs the package, runs the AI completeness check against your checklist, then either notifies accounting and confirms receipt, or emails the client the exact list of what's missing.
You connect your own accounts. Swap any app that offers an alternative at install.
Notifies the accounting team when a complete document package is ready for review. Swap for Telegram or Discord.
Emails the client a receipt confirmation or a request for missing documents. Swap for Brevo.
The client completes the Financial Document Upload form (name, email, purpose, period, notes) and attaches their tax forms, invoices, and bank statements in one go. Publishing the form auto-creates its response sheet, so every submission is captured with nothing to set up.
Each package is stamped with a submission ID and timestamp and stored with status received, one searchable row per client submission. When someone asks what a client sent and when, it's a lookup, not an inbox archaeology exercise.
A TinyGPT step compares which required document types were actually attached against your per-purpose checklist and returns completeness (complete or incomplete) plus missing_items. To be precise about what this does: it checks presence, not contents. It never opens or reads a document. That stays your team's judgement.
When everything required is present, the row is marked ready-for-review, your accounting Slack channel is pinged, and the client gets a receipt confirmation. Your team is interrupted only by packages they can actually start work on. Swap Slack for Telegram, Discord, or Google Chat at install.
If something's missing, the row is marked awaiting-docs and the client gets an email listing exactly which documents to re-upload. Not a vague nudge, a specific list. That single detail is what collapses the usual three-round back-and-forth into one.
Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.
