What it does
A document automation for an accounting firm. Engagement letters, management reports, board resolutions and client letters are produced from the firm's own templates. AI fills each one from the client file and the source documents, marking every value it filled. The document then moves through approval levels: preparer, manager, partner. Any level can reject with a comment; the document goes back, is revised and starts the approval again. Approved documents are issued and filed with the full trail.
The problem
Staff copied figures and client details into Word templates by hand, approvals happened in email threads, and nobody could tell which version the partner had actually signed off.
Approach
Templates stay exactly as the firm wrote them; only marked fields are filled, and every filled value shows where it came from. Approval levels, and who can approve what, are settings, not code. A rejection always carries a comment and returns to the right person, and every step is kept in an audit trail.
- Input
- AI step
- Rules or code
- Person decides
- Result
Screens
Swipe sideways to see the whole screen.
Client work is shown under confidentiality agreements: no client names, and screens are recreated with sample data.
Stack
- Document templates
- Gemini API
- Approval workflow
- Audit trail
Impact
Typical for systems like this.
