CASHFISH FOR FINANCE & OPERATIONS TEAMS

One version
of the numbers,reviewed by
the right people.

More hands on the money means more places for it to blur. CashFish puts documents, records and dashboards in one shared workspace where roles decide who edits, who reviews and who only views — so the number in the meeting is the number in the system.

Start your 4-day free trial

FinanceOperationsLeadershipAgencies & studios

Teams from $96/month · 4 users included · 4-day free trial · Full refund guarantee

01Nobody’s version of the truth

The number in the meeting isn’t
the number in the system.

Every team keeps its own copy because every team has been burned by someone else’s. Month-end becomes a negotiation between exports — someone wins, everyone loses an afternoon.

final_numbers_v7_REAL.xlsx

Seven versions deep, and the meeting is running on v5.

Finance sent v7 at 23:10. The board deck was built from v5 that afternoon. Both are named final. Neither is.

vendors_OPS-COPY.xlsx

The vendor list operations trusts is not the one finance pays from.

A supplier changed bank details in March. One copy knows. The payment run uses the other one.

Re: Re: who approved this invoice?

A $12,400 invoice is paid, and a thread is opened to find out who said yes.

Three replies, two shrugs, one “I thought you did.” The PDF is in someone’s downloads folder.

dashboard_screenshot_tuesday.png

Leadership reads a screenshot of a dashboard that has since moved on.

The cash figure on the slide is nine days old. Nobody in the room knows that, including the presenter.

shared-login · everyone

Everyone has every permission, so nobody is responsible for anything.

One password in a channel. Viewers can delete, approvers can’t be told apart, and the audit question has no answer.

Six people don’t need six copies. They need one reviewed record — and every deck, export and seat reading from it.

02Roles that match the org chart

Who edits, who reviews,
who only looks.

An admin sets the role once. From then on, access follows the person — not a password in a channel. Below is how one six-person team set theirs; yours follow your own org chart.

Role	Manage connections	Review documents	Edit records	View dashboards
R Admin sets roles, manages connections, sees everything
M Finance reviews documents, edits records
D Operations vendors, payables, documents in
L Viewer dashboards only, nothing to click

Attribution

Every review carries a name and a time. “Reviewed by M. · 11:40” lives on the record itself, next to the source document — not in anyone’s memory.

Activity trail

Who connected what, who reviewed which record, what changed afterwards. Team activity is traceable without opening a thread.

Admin controls

Roles are set centrally. When a person moves seat or leaves, an admin changes one thing and their access changes with it.

03The systems around the workspace

Records in, events out —
no manual export in the middle.

→ Records insources the workspace reads from

Gmail · Outlook · IMAPthe shared inbox, on every plan

Salesforceaccounts and deals alongside the same records

HubSpotcontacts and pipeline next to the records

QuickBooks · Xeroone-way import into CashFish, not back out

Events out →where reviewed records go next

Slackthe channel your team already reads

Zapierthe rest of the stack, without code

API & Webhooksyour keys, your lifecycle · Scale and Teams

CSV · PDFthe paper trail, whenever it is asked for

Bank sync is read-only. QuickBooks and Xero import one way into CashFish; nothing is written back. Every connection shows its health in settings and can be disconnected by an admin.

04One invoice, through the controls

One invoice.
Six people.
Two hours, twenty-seven minutes.

Harbor & Co. sends a $12,400 invoice on the 14th. Here is everything that happens to it, and who touched it.

Published figure across CashFish customers: month-end close from 3–4 weeks to 2–3 days.