Your documents stay in your SharePoint.
FigsFlow handles document management for accounting firms inside the Microsoft 365 setup you already run. Every client document is saved directly to your SharePoint or OneDrive, using the folder structure and permissions your firm already has — no separate archive, no filing system to learn, and no second place to search.
Partner or principal, start with the tour below. IT or compliance, the permissions model and the retention position are what you want — and the detail sits on security.
The tour runs in your browser. No form until you want one.
- Destination Your SharePoint library
- Folder Clients / Ridgeline / 2026
- Named by Your naming convention
- Permissions Inherited · Entra ID
- Retention Your policy · unchanged
nobody files it by hand
Click a document to file it. It is written to your SharePoint library within one to two minutes of submission — not to a FigsFlow archive.
- Clients
- Ridgeline Foods Inc.
- 2026
The signed lease is somewhere. Finding it is the problem.
Between old emails, personal OneDrive folders and inconsistent shared-drive structures, finding one document can become a search across the whole firm.
That is not a training problem — it is what happens when everyone has their own way of filing. FigsFlow gives every client document a consistent, searchable home inside the Microsoft 365 environment your firm already owns.
Where documents sit on the client record
Documents do not arrive from nowhere, and they do not dead-end once they are filed.
What feeds this module
- Client uploads through forms and information requests — every document a client submits through a form request lands here automatically.
- Attachments handled through the email module — inbound client attachments follow the same routing into the firm's client and job folder structure.
- Files added directly into SharePoint by staff or clients, outside FigsFlow entirely — detected and reflected back onto the correct client and job record, provided they land in the agreed folder structure.
What it feeds downstream
- The AI Processing engine picks up filed documents and extracts structured data for the relevant service — a Self Assessment computation, an annual accounts schedule, and so on. No re-entry, no re-filing.
- There is no direct accounting-software feed today. Nothing is written back into your ledger software from this module.
Four questions firms ask about where the file actually goes
How does FigsFlow keep SharePoint as the master copy?
Every document synced through FigsFlow is written to your firm's Microsoft 365 SharePoint or OneDrive library within one to two minutes of submission, with SharePoint treated as the master repository — not FigsFlow's own database. Each document carries a visible sync status. If a sync fails, the document is retained safely inside FigsFlow, retried automatically at a configurable interval, and an admin is alerted if it is still failing after the maximum retries, with a manual re-trigger available.
How are client folders built and named automatically?
FigsFlow mirrors your firm's agreed folder hierarchy in SharePoint, auto-creating folders where they do not already exist rather than requiring anyone to set them up by hand. Saved documents are automatically renamed to a configurable convention — client reference, document type, submission date — and tagged with metadata.
What happens if a file is saved directly to SharePoint?
Filing does not only run one way. A document added straight into SharePoint — by a staff member working outside FigsFlow, or in line with the firm's agreed folder structure — is detected and automatically reflected back onto the correct client and job record, subject to the firm's own access controls. Nobody has to remember to "also put it in FigsFlow".
Who can access these files, and under whose rules?
Staff reach client documents through their own synced OneDrive folder — via Windows Explorer or Mac Finder — without a separate FigsFlow login. Permissions are not reinvented: documents inherit the structure your firm already has configured through Microsoft Entra ID, and FigsFlow does not override or bypass that model. Because SharePoint remains the system of record, documents also stay governed by whatever retention policy your firm already applies there.
One governed folder vs. five places a file could be
This is not a comparison against another piece of software. It is against the personal OneDrive folder, the email attachment, and the shared drive nobody has kept tidy since the last reorganisation.
Where it goes today
Five plausible destinations, none of them agreed.
- 01Whoever opened it saves it where they were working
- 02Folder names drift as people reorganise their own view
- 03The file is renamed to whatever made sense that day
- 04Nobody records whether it was ever actually received
- 05Finding it again depends on asking the right person
The structure exists only in individual habit, so it stops existing the moment that person is on leave.
Where it goes with FigsFlow
One structure, applied the same way every time.
- 01Filed into your agreed folder hierarchy automatically
- 02Named to your convention and tagged with its metadata
- 03Permissions inherited from your existing Entra ID groups
Folders, naming, metadata and permissions are applied consistently, inside the Microsoft 365 environment your firm already owns — rather than left to whoever happened to handle the file.
What this looks like at your size
One clean, consistent folder per client from the first job — no manual setup to maintain on top of everything else you are already doing yourself.
Running a solo practice → 2 to 10Every staff member's client work lands in the same structure, without a shared-drive policy document that nobody actually follows.
Software for a small firm → 10 to 50Folder and naming standards apply automatically as headcount grows, instead of being re-explained to every new hire.
See how growing firms standardize onboarding → 50+ and multi-officeDocuments stay inside your own Microsoft tenant, under the retention and access policy your IT function already owns — governance your IT lead can verify directly, not take on faith.
See how larger firms run FigsFlow under their existing IT policy →We will look at your existing folder structure, not a demo tenant.
One integration, and it is the one that holds your files
Microsoft 365 is the only live document integration, and that is a stated choice rather than a gap. Depth inside one environment is what lets FigsFlow inherit your permissions instead of recreating them, and leave your retention policy where it already sits.
Google Drive is not supported. If your firm runs on Google Workspace, this module is not built for you today.
- SharePoint and OneDrive — the master document repository, in your own tenant.
- Microsoft Graph API — how documents are written, read back and detected.
- Microsoft Entra ID — single sign-on, and the permission structure documents inherit.
Who's building this alongside FigsFlow — before you do?
There are no US customer stories yet. Rather than borrow one, here is what actually exists.
The tour above, not a claim about it
A document landing in a synced SharePoint folder, with the folder created, the file renamed and the status flipping to Synced. It is the same behaviour your team would see on day one.
Built inside working firms
FigsFlow is used day to day by UK Property Accountants, and supported by the Sterling Wells team in Nepal. That is practitioner-built proof of the product — not a customer logo, and not an endorsement of anyone's accountancy services.
This slot stays empty until a real, signed-off US firm is willing to put their name to it. When one is added it will carry a country label.
We are inviting the first 10 to 15 US firms to run this module in anger and become its US proof points. No invented quote in the meantime.
Which plan, and since when?
Live at US launch, September 2026. No exact calendar date is confirmed beyond that month.
Tier To be confirmed — SharePoint and OneDrive sync underpins forms, email, the client portal and AI processing, so it is likely to sit in every tier as foundational infrastructure. That is a reasoned expectation rather than a published position, and we are not going to print a tier name we cannot stand behind.
Filing the document isn't where the job ends
Forms and information requests
See how a client's form upload lands here automatically.
Collecting documents from clients →See how email attachments join the same client folder.
Client correspondence on the record →Client portal
See how a filed document becomes visible to your client.
What your client opens →API and webhooks
How another system can read the same document record. The page for this module is not live yet.
Coming after launchWhat firms ask before they connect a tenant
Yes. FigsFlow does not replace SharePoint, it automates what goes into it. SharePoint stays your firm's own document system; FigsFlow handles the filing, naming and syncing so nobody has to do it by hand.
In your firm's own Microsoft 365 tenant. SharePoint is the master document repository, and FigsFlow does not hold a separate, permanent copy outside it.
No. Documents inherit the permission structure already configured in your SharePoint environment through Microsoft Entra ID groups. FigsFlow does not bypass or replace that model.
Yes — through their own synced OneDrive folder, via Windows Explorer or Mac Finder. No separate login is needed to open a client document.
It is retained safely inside FigsFlow, retried automatically, and an admin is alerted if it is still failing after the configured number of attempts. A manual re-trigger is available at any point.
Not currently. FigsFlow's document integration is built specifically for Microsoft 365 — SharePoint and OneDrive. That is a deliberate choice consistent with the platform's Microsoft-native positioning, rather than a gap we are working around.
No. Retention stays governed by whatever policy your firm already applies in SharePoint. FigsFlow does not run a separate or competing retention schedule.
Bring the folder structure you already use
We will file a document into it on screen: your hierarchy, your naming convention, your Entra ID groups, and the retention policy you already have in place.
Once a document is filed and organised, FigsFlow's AI engine can start extracting what it needs for the return, the accounts, or whatever the service calls for — no re-entry, no re-filing.
Start Smarter. Grow Faster.
From proposals to pricing, streamline every step with automation designed particularly for accountants, bookkeepers and tax advisers.