Advisor Console
| Client | Inbox | To review |
|---|---|---|
| Cedar Ridge Properties | 3 | 5 |
| Blue Harbor Coffee Co. | 1 | 4 |
| Marlow Construction Group | 0 | Clear |
| Vega Design Studio | 2 | 3 |
| Pinecrest Dental | 0 | 2 |
ClientBox is the document and records hub for accounting firms and the businesses they serve. Documents arrive by email, upload, or photo; ClientBox classifies them, names them, and files them into a consistent folder structure — then locks them so the record stays intact.
| Client | Inbox | To review |
|---|---|---|
| Cedar Ridge Properties | 3 | 5 |
| Blue Harbor Coffee Co. | 1 | 4 |
| Marlow Construction Group | 0 | Clear |
| Vega Design Studio | 2 | 3 |
| Pinecrest Dental | 0 | 2 |
One view across every client and entity. Demo data shown.
Client documents arrive from everywhere — email attachments, portals, scans, phone photos, shoeboxes. Someone has to open each one, figure out what it is, rename it, and drop it in a folder that matches how the last one was filed. That work is invisible until it fails: the statement nobody can find at close, the invoice filed under the wrong vendor, three copies of the same receipt.
ClientBox is a full document lifecycle — capture, review, classify, file, retrieve — built around one rule: filing is derived, never guessed. A document's folder is computed from what the document actually is (client, entity, vendor, document type, date), so identical documents always land in the same place, no matter who processed them or when.
Underneath, documents are held on ClientBox infrastructure and tracked by permanent file IDs rather than names or paths — then pushed, in real time, into whichever storage system you prefer. Rename a vendor, restructure a folder, move a client, or change storage providers entirely: the links hold and the filing stays intact.
ClientBox reads incoming documents and proposes the vendor, date, amount, and document type. It learns your vendors as it goes — the more a vendor appears, the less there is to confirm. AI-assisted classification is available as an optional add-on; without it, no document content leaves our infrastructure.
Every filed document is named by rule, not by habit. 2026-07-31 Meridian Bank 4417 Statement.pdf looks the same whether it was filed today or eighteen months ago.
Folder placement is computed from the document's own fields, and can branch on vendor, jurisdiction, or subtype. Nobody picks a folder from a dropdown, so nobody picks the wrong one.
Admins define the document types — each with its own fields, naming pattern, and routing rules. Change a type once and it applies everywhere. Types are hidden and unhidden, never destroyed.
Each client gets their own intake address. Forward-by-email works the way clients already behave: they forward the bill and stop thinking about it.
Phone photos and HEIC images are cropped, rotated, and placed at true physical size on a Letter or Legal page — so a scanned receipt prints and reads like a receipt, not a stretched image.
Once filed, a document is locked against edits — enforced in ClientBox and carried through to the copy in your own storage. The record can't be quietly altered from either side.
ClientBox flags likely duplicates by entity, vendor, account, amount, and date. Review them side by side, dismiss false matches, or merge — choosing which field wins and which file to keep.
A client is the relationship; an entity is the legal unit where documents live. One client can hold several entities, each with its own folder structure and its own record.
A firm-wide view across every client and entity — what came in, what's waiting on review, what's filed. For firms serving many clients, this is the daily working surface.
Primary storage runs on ClientBox infrastructure, which keeps the system agnostic to whichever provider you use — and to changing it later. Every filed document is pushed to your storage in real time, so a complete, correctly filed copy always sits somewhere you control.
Trash is reversible. Archived is reversible. Hidden document types are reversible. The system is built so that the destructive option is almost never the default one.
Infinite Office builds accounting software and delivers accounting services on top of it. ClientBox is the layer everything else touches, because every engagement starts and ends with documents.
Intake is the front door. Onboarding a client means turning on their intake address and provisioning their file structure. From that point, everything the client sends — bills, statements, notices, receipts — flows into one place instead of into someone's inbox.
The monthly close runs against a complete record. Because documents are classified and filed as they arrive, the source documents behind the books are already organized when the work starts. No end-of-month scramble to reconstruct what came in.
Requests and follow-up have a single reference point. What's missing is visible as what hasn't arrived, per client, per entity — not as a mental list.
The record survives the engagement. Documents are held on ClientBox infrastructure and mirrored in real time into the storage the firm chooses, named consistently and locked. Whether the client stays for a year or a decade — or leaves — the archive is the same shape, and it is already in their hands.
ClientBox is available on its own, and it's the foundation the rest of the Infinite Office platform is being built on.
Managing documents across many clients and entities, who need every staff member to file the same way.
Company mode pins ClientBox to a single entity, with the same intake, classification, and filing behavior.
ClientBox has been used to import and verify a full historical archive, page-count checked, rather than starting from an empty system.
ClientBox is in active use inside Infinite Office today. If you'd like to see it against your own workflow, we'll walk you through it.
Request a demo