Your ledger keeps the books. FigsFlow runs the practice.
FigsFlow works alongside Xero and QuickBooks rather than competing with them. The ledger stays the system of record for the accounts; FigsFlow holds the client lifecycle around it — proposal, engagement letter, jobs, deadlines, documents and the invoice.
G2 reviews
Google reviews
Verified reviews
Trustpilot reviews
Trusted by the best
Ledger software was never built to run a practice
Xero and QuickBooks are very good at what they are for. The trouble starts where the bookkeeping ends — and firms fill that gap with spreadsheets, inbox rules and memory.
Client details typed twice
A new client is set up in the ledger, then set up again in a spreadsheet, a proposal tool and an engagement letter. Three of the four go stale within a year.
No single recordDeadlines tracked outside the books
The ledger knows a VAT quarter exists. It does not know who is preparing it, who reviews it, what is still outstanding from the client, or that nobody has chased them.
No workflowThe fee is agreed somewhere else
Scope was set in a proposal, priced in a spreadsheet, promised in an email and eventually invoiced from the ledger — with nothing connecting the four.
No trail
The ledger balances the books. Your team still carries the practice.
Behind every VAT quarter is someone chasing records, someone checking the review and someone answering the client. FigsFlow is built for those hours — the ones no ledger was ever designed to hold.
- PartnersSee every client, fee and deadline in one place, without asking who has the latest spreadsheet.
- ManagersKnow what is in review, what is waiting on the client and who is stretched — before it becomes a missed deadline.
- BookkeepersKeep working in Xero or QuickBooks, with the job, the chasers and the documents already set up around it.
Two systems, one line between them
The most useful thing an integration can do is be honest about where it stops. FigsFlow does not keep a second set of books, and your ledger does not try to run your workflow.
Counts describe how the integration is built, not a performance claim.
Five questions to settle before you connect anything
Integration depth is the part most software is vague about, so it is the part worth pinning down first. Bring these to the call and we will answer each one for your setup rather than in general.
We would rather scope it than sell it
Integration claims are easy to make and expensive to discover. On the call we will walk your actual client mix and tell you what the connection does today, what is configurable and what it does not do — including where a spreadsheet is still the honest answer.
If the fit is wrong for your stack, that is a better outcome in week one than in month six.
Book a scoping callWhat sits either side of the ledger
This connection is one edge of the platform. These are the modules that meet it.
Winning and setting up the work
- Scope and price agreed, then carried into the workflow templates that run the job.
- E-signature and approvals close the engagement letter before any bookkeeping starts.
- AML and client due diligence completed and evidenced against the client, not a folder.
- Records collected through forms and information requests and filed automatically.
Finishing, billing and evidencing
- Jobs, tasks and deadlines track the return through preparation, review and submission.
- Timesheets and billing turn the work done into the fee, against the scope that was agreed.
- The audit trail keeps what happened, when and by whom, for the next file review.
- API and webhooks for anything bespoke you already run alongside the ledger.
What firms ask about the ledger connection
No. FigsFlow is practice management software. It runs the client lifecycle — proposal, engagement, jobs, deadlines, documents and invoice — and sits on the stack your practice already uses. The ledger stays where the bookkeeping and the accounts live.
No — and we would rather say that plainly than let you find out later. FigsFlow tracks, schedules, chases and evidences the cycle, including MTD quarters, VAT staggers, confirmation statements and year ends. The submission itself happens in your tax, ledger and payroll software.
Both are supported, which matters because most practices run a mix across their client base. Ask us on the call how each one is configured for your client mix — the two platforms are not identical, and we will not pretend otherwise.
No. Documents are filed into your own Microsoft 365 SharePoint under your folder structure and retention policy — see documents in your SharePoint. There is no document feed into accounting software today.
The client record in FigsFlow is not tied to a particular ledger, so the history of proposals, engagements, jobs and documents survives a migration. Where a client has several entities, bring the structure to the call — multi-entity setups are worth configuring deliberately rather than by default.
Nothing leaves the ledger. Because FigsFlow sits alongside it rather than replacing it, there is no chart of accounts to move and no bookkeeping to re-enter — the work is agreeing your templates, folder structure and deadlines.