Clients ignore messages that do not tell them exactly what to send. “Documents for GST” is not a request. “Sales register, purchase invoices, and bank statement for July 2026” is a request.
Fyliio’s first request lists each open item by name for that month. The AI that checks the replies sees exactly the same list, which only works because the list is short and named the same way for staff and for the AI.
Fyliio starts with GSTR-3B on purpose: it is the monthly rhythm every GST practice already runs. GSTR-1, TDS, and ITR checklists will reuse the same flow: a cycle, a list, WhatsApp requests, checking, reminders, and the board.
Validation is part of “complete”. A bank statement for the wrong month should not check off July. A file sent twice should not count as a second document. When real life is messier than the checklist, staff can waive an item or reassign a file in the review queue.
When the list is complete, nudges stop. The packet can be exported. Filing remains outside Fyliio — by design. Collection is the layer that was never a product.
Found this useful? Share it with a colleague.