The next-generation client portal — and everything after it

Run the whole engagement in one continuous flow.

More than a client portal — what clients send becomes internal workpapers your staff refines privately. One client record across tax, audit, and advisory.

Microsoft verified publisherDocuments can live in your own SharePoint25 years inside CPA firms
The part portals don’t have

Two rooms. One flow.

A portal gives you one room — the one your clients are in. InflowSheet gives you the second one, where the documents they send become workpapers your staff actually works on.

The client room
Clients see this

A clear list of what you need, a place to upload it, and status they can read without emailing to ask. Simple for them, and it never exposes how the work is done.

  • Assigned requests only
  • Upload and re-upload
  • Status they can read
  • Messages in context
The internal room
Staff only

What arrives becomes real internal workpapers — reviewed, annotated, mapped, and exported to collaborative Excel in your own SharePoint. Your team works here privately. Clients never see it.

  • Review notes and sign-off
  • Trial balance mapping
  • Collaborative Excel workpapers
  • Private to your staff
One engagement
Continuous
Collect
Review
Automate
Workpapers
E-Sign
Engagement letter
Requested
Source documents
Requested
Bank statements — Q1–Q4
Requested
Trial balance
Requested
TaxAuditAdvisory· one client record

One engagement record spanning both rooms — illustrative view, generic placeholders.

Verified
Microsoft verified publisher
Built by
25 years inside Tax, Audit & Advisory firms
Data
Encrypted in transit and at rest
Access
Entra ID sign-in, admin-consented
Where we start, and where we go

Client portals move files. InflowSheet runs engagements.

A portal is table stakes, and InflowSheet has a good one. But moving a file from the client to the firm is the first step of the work, not the work — engagement management is what happens after the upload.

A client portal
  1. 01Request a document
  2. 02Client uploads it
  3. 03Staff downloads it
  4. 04Done

The file moved. Everything that makes it an engagement — review, judgment, the numbers, the workpapers, the signature — still happens somewhere else.

InflowSheet
  • CollectRequest lists that track their own status
  • ReviewThe agent recommends, a reviewer confirms
  • AutomateValidated documents roll up on their own
  • AnalyzeTrial balance imported, mapped, and checked
  • FileCollaborative Excel workpapers in your SharePoint
  • SignE-signature inside the same engagement record

And all of it across tax, audit, and advisory on one client record — so the engagement moves forward, not just the file.

The differentiator

No more separate portals for Tax, Audit, and Advisory.

One platform. Shared clients, shared documents, role-scoped views.

Almost every tool in this market picks a side — tax workflow, or audit workflow. Firms that do both end up running two systems over one client base, and paying for the seam in re-requested documents, duplicated collection, and status meetings that exist only to sync.

Shared clients

One client record across tax, audit, and advisory engagements.

Shared documents

Collected once. Available to every engagement entitled to it.

Shared history

Last year’s engagement is context, not an archive you dig through.

Role-scoped views

Each discipline sees its own work; permissions decide the rest.

Tax portal
Requests · documents · returns
Audit portal
PBC list · evidence · workpapers
Same client. Collected twice.
One client record
  • Shared documents
  • Shared history
  • Role-scoped views
Collected once. Serves both.

A document the tax team collected is already there when the audit team needs it. Nobody re-requests what the firm already holds.

A day in the life

“What do I need to do today?”

The platform answers that before you ask it. Follow one engagement through a working day — the same record, four moments.

  1. Advancing automatically — pick a step to take over.
Requests & signatures
Outstanding
2
To validate
19
Progress
56%
Ready for export
—
Next action
Review 19 items
Start
Completeness check

Compares received documents against what was requested — wrong type, wrong year, wrong entity.

Illustrative views with generic placeholders. AI-assisted output requires professional review and is not accounting, audit, or tax advice.

The platform

Five stages, one engagement record.

Most firms run these in five systems and spend the season reconciling them. InflowSheet keeps them in a single record, so status is something you read rather than something you assemble.

01

Collect

Request lists that track their own status.

Build a request list once and reuse it across engagements. Clients see only what is assigned to them, upload against each item, and the list keeps its own status — missing, to validate, questioned, validated.

  • PBC and auditor request templates
  • Per-client visibility
  • Drafted follow-ups for approval
  • Bulk and single upload
02

Review

The agent recommends. You confirm.

Received documents are classified, checked for completeness, and their key values extracted — then handed to a reviewer as a recommendation, never a decision. Validate, question, or send back, item by item.

  • Completeness checks
  • Expected versus observed on every check
  • Validate / question / to-validate
  • Suggested client questions
03

Automate

The repetitive middle, handled.

Validated source documents roll up into return-relevant figures without anyone re-reading a file. Follow-ups are drafted for a person to approve, and status follows the work, so the team spends its time on judgment.

  • Source document roll-up
  • No document re-read
  • Status that follows the work
  • Drafted follow-ups for approval
04

Export to Collaborative Workpapers

Client documents become internal workpapers.

What the client sent stops being an attachment and becomes a workpaper. The engagement exports into collaborative Excel written directly into your firm’s SharePoint — a private internal space where your staff works together, under your retention and your permissions. Clients never see it.

  • Collaborative Excel workpapers
  • Private to your staff
  • Written to your SharePoint
  • Linked back to the source document
05

E-Sign

Signatures inside the engagement, not beside it.

Route engagement letters and returns for signature without leaving the workflow. Signer status flows back to the engagement the team is already watching.

  • Send for signature in-flow
  • Signer status on the engagement
  • Executed copies filed automatically
  • Audit record retained
Flagship module

The Financial Workspace.

Import the trial balance and the engagement gains a full financial layer — AI account mapping, variance analysis, adjustments, and export straight into collaborative Excel workpapers filed in your document store.

This is the part no document organizer has. Collection tools stop at the file. The Financial Workspace takes the engagement through the numbers.

Trial balance import

Bring the TB in from the engagement’s own received files.

AI account mapping

Accounts mapped to lead sheets, with a reviewer confirming.

Variance analysis

Period-over-period movement surfaced against the mapping.

Excel workpaper export

Written into the engagement’s document store as .xlsx.

Financial Workspace
Trial balance · mapping · adjustments
TB imported
AI account mapping
4 of 4 mapped
1000 · Cash
Current assets
124,800
1200 · Accounts receivable
Current assets
86,415
4000 · Revenue
Income
1,204,900
6100 · Professional fees
Operating expense
38,220
Variance ▲
Export to Excel workpaper.xlsx

Illustrative workspace view with generic placeholders.

Document management

Client documents in. Internal workpapers out.

Requests, received files, internal workpapers, trial balance files, signed deliverables. One structure per client, one place to look — and it lives in your firm's own SharePoint and Teams rather than in a second repository you have to govern separately. The client side and the staff side stay separate throughout.

Requests and received files — What was asked for and what came back, on the same record.
Internal workpapers and TB files — Staff-only exports, filed beside the source documents that support them.
Signed deliverables — Executed copies filed automatically when signing completes.
Your governance — Your folder structure, retention, permissions, and eDiscovery.
Your SharePoint — engagement documents
X
TB_Workpaper_ClientA_2025_partnership.xlsx
Client A — Internal Tax
X
TB_Workpaper_ClientA_2025_adjustments.xlsx
Client A — Internal Tax
PDF
Form_1040_ClientB.pdf
Client B — Internal Tax
X
Source_docs_ClientB_2025.xlsx
Client B — Internal Tax

Workpapers are written straight into your own SharePoint sites — your structure, your retention, your permissions.

Illustrative file listing with generic placeholders.

Assisted, not automated

AI that assists. Professionals who decide.

Extraction, classification, and completeness checking take the first pass at the reading. They do not sign off, and they are not presented as if they had.

Traceable

Every check shows what was expected and what was found.

Reviewable

By default, nothing goes out without a named person accepting it.

Never training data

Your clients’ documents are never used to train or fine-tune any model.

Microsoft 365 integration

Your documents, your control.

InflowSheet integrates deeply with the Microsoft 365 tenant your firm already governs. Engagement documents can live in your own SharePoint and Teams, inside your structure, under your retention and your permissions — and your people sign in with the Entra ID identities you already manage.

Each engagement links to a private Teams team and channel your firm already has, and its files are stored in that team's SharePoint, so the documents never have to leave the governance perimeter your firm has already built.

SharePoint & Teams

Documents in your sites, your folder structure, your retention.

Entra ID sign-in

Your SSO, MFA, and Conditional Access policies apply.

Admin-consented scopes

Every permission approved by your admin — and revocable.

Published scope list

Every Graph permission listed in the Privacy Policy.

Straight answer on residency: the platform processes and stores engagement data in InflowSheet's Microsoft Azure environment in the US East region. Where the integration is used, content in your tenant stays in your tenant. Read the detail.

Bring the season into one flow.

Every firm is onboarded white-glove, with the request lists and templates your engagements actually use. Tell us how your firm works and we will show you the fit.