Finance requests, out of the inbox.
A ticketing and operations system for finance teams. Invoice queries, payment requests, new-supplier setups and approvals arrive as structured tickets, so everyone can see what has been asked, who owns it and where it is.
- Status
- Prototype, internal demo
- Built for
- A finance team serving several group entities
- Roles
- Requester, finance agent, manager, admin
- Stack
- React, TypeScript, Postgres
"Has my invoice been paid?" arrives forty different ways.
Finance teams are asked the same questions every day, by email, by chat, in the corridor. Each one needs the same information to answer, and each one disappears into an inbox where nobody can see whether it has been dealt with. Approvals wait on a reply that was sent to the wrong person. New suppliers get set up twice.
FinTiq grew out of doing that job. It gives each kind of request its own form, so the question arrives complete, and a single queue where the team and the requester can both see progress.
Built and working in the prototype.
These features exist in the code. The prototype uses a role switcher rather than real sign-in, which is one of the things that separates it from a production system.
Six request types
Invoice status, supplier payment or pay run, new supplier, expense issue, budget approval and general query, each with its own form so the request arrives complete.
Tickets with a life cycle
Automatic ticket numbers, seven statuses and four priority levels. Assign, change status, escalate or reopen.
Threads and internal notes
Replies the requester sees, and internal notes they don't, on the same ticket. Attach files and preview them in place.
A view per role
Requesters see their tickets. Agents see the queue. Managers approve or reject. Admins see the whole picture with charts.
Live notifications
In-app notifications that update as tickets change, so nobody refreshes to find out.
Team settings
Pay-run dates per entity, a link to the supplier form, and an on-leave toggle so requests route around absences.
A prototype, described as one.
- It is a working prototype that was built around a real finance team's workflow and demonstrated internally.
- It is not in production use, and it has no customers. We don't quote adoption figures because there aren't any.
- Before production it needs real authentication and per-user permissions, which the prototype deliberately skips, plus reporting views that are currently placeholders.
- No screenshots yet. The prototype carries another organisation's branding and data, so we will publish screens once a neutral demo build exists.
Run a finance team that lives in its inbox?
Tell us how requests reach you today. FinTiq may fit, or a lighter fix to your existing tools may do the job.