Fintra Feature
Work management, and automations that draft the next move
My Work & Automations
Example figures- MY WORK
- 9 due today
- 3 approvals
- RULES LIVE
- 17
- signal, then action
- AWAITING APPROVAL
- 5 drafts
- human-in-loop
- Board: Month-end close
- 12 tasks · 4 blocked
- Rule: bank detail changed, then verify + hold
- drafted, needs approval
- Rule: invoice 30d overdue, then dunning draft
- queued
- Rule: control failing, then owner task + note
- assigned
- Calendar · deposit due Fri
- reminder set
Tasks, My Work, calendar, and boards
The everyday workspace lives where the work’s subject matter already is. A close task, an onboarding checklist, a collections follow-up: none of it is stranded in a separate project tool that knows nothing about the invoice or the employee it’s about.
- My Work: one list of what’s due and what’s waiting on you, across every domain
- Boards: Kanban for month-end close, onboarding, collections, or a project
- Calendar: deadlines, deposit dates, and review cycles in one view
- Every item links back to the record it’s about: the invoice, the employee, the control
Automations that draft, then wait for a human
An automation rule turns a signal into a drafted action. A vendor’s bank details change, an invoice crosses 30 days overdue, a control starts failing: each can trigger a governed, pre-drafted action that lands in the right person’s approval queue, already written, with the context attached.
| When this happens | Fintra drafts | Who approves |
|---|---|---|
| Vendor bank detail changes | A verify-and-hold on the next payment | AP approver |
| Invoice hits 30 days overdue | A dunning email, ready to send | AR owner |
| A control starts failing | A task to the control owner, with a note | Compliance owner |
Questions people ask
What can an automation rule do?
It turns a signal (a changed vendor bank detail, an invoice 30 days overdue, a failing control) into a pre-drafted, governed action routed to the right approver’s queue, with the context already attached.
Do automations act on their own?
No. Every rule drafts and routes; a human approves before anything sends, pays, or changes. It’s human-in-the-loop by design, so the automation removes the drafting busywork, not the accountability.
Do I need to write code to build a rule?
No scripting. Rules are built in plain “when this happens, draft that, route to them” terms, so an ops or finance owner can create one without engineering.
How is this different from a standalone task app?
Tasks, My Work, calendar, and boards live on the same platform as the money and the people, and every item links back to the record it’s about. A standalone PM tool knows nothing about the invoice, employee, or control behind the task.
Can I test a rule before turning it on?
Yes: a rule can show what it would have done on recent history before you switch it live, so you turn it on with your eyes open rather than hoping it behaves.
Keep reading
Guides
Calculators
One finance briefing a week
New guides, checklists and benchmarks, by email. Unsubscribe from any issue.
One brain for people, work, and money
See humans, AI agents, support, and finance decisions in a single governed workspace.