Preview. No backend is attached to this page, so nothing here is saved or sent anywhere. Secret fields are switched off on purpose.
FinOps RoboticsAccountant agent

Sign in

Your workspace, your ledger, your rules. Credentials are issued during onboarding — there is no public sign-up.

Forgotten?
Caps Lock is on.

One more step

Open your authenticator app and enter the six digits for your account.

Codes change every 30 seconds. A code from the last window still works.

Read-only to start. A new connection can look and reconcile. It cannot post anything until you release that separately.

Your tenant, your credentials. Keys are encrypted before they are stored and are never shown back to the browser — not even to you.

Seven systems, one agent.

It reads where the work arrives, reconciles what moved and writes to one ledger — stopping at anything a rule says a human should see.

Accounts inbox Bank WhatsApp Shopify Stripe Tabby Rules · tolerances · gates Held · human Posted to the ledger

Where there is no API — and for a bank or a BNPL settlement there usually is not — the agent reads the file or the statement instead. Same reconciliation, one hop later.

FinOps RoboticsAccountant agent
—workspace
——

Good morning.

Reading what the agent did…

Waking up… ·
The agent z z z

Waiting on you

Everything the agent stopped at, with the reason it stopped.

What the agent handled

Documents read and entries prepared, the last fourteen days.

What it can run

The jobs you chose, and whether they have everything they need.

What happened

Newest first. Every posting carries the reference it was given.

FinOps RoboticsAccountant agent
—workspace

Reading the mailbox…

Sorting

What needs you

Show me everything the agent did

The piles are worked out fresh every time this page loads, from mail that has already been read — nothing here goes back to the mailbox. So a rule can be changed and the whole inbox re-sorts, and you can see what the change did before trusting it with anything new. Move a message and your pile wins, but what the rule said is kept underneath.

The agent stops in the same three places it always stops. It prepares entries and does not post them, writes replies and does not send them, works out dates and does not put them in your diary. “Handled” means it has done its half, not that the work has left the building — and anything it could not finish, or that is genuinely late or that you flagged yourself, is in the list above with the reason on it.

FinOps RoboticsAccountant agent

Checking your invitation…

FinOps RoboticsAccountant agent
—workspace
People

Who can sign in

Access is issued, never signed up for. You create the person; they choose their own password from a link that works once.

Invite someone

They set their own password. You never see it, and it never travels through a message you sent.

A new name opens a new client, kept completely separate from every other. Leave it as it is to invite a colleague into this one.

Waiting to be accepted

An invitation expires in seven days and can be withdrawn at any time.

Accounts

Removing an account removes the login. It does not remove anything the person did.

Nobody here can reset a password for somebody else, and there is no self-serve reset either. If an account is locked out, the way back in is a fresh invitation to a fresh account — which is slower on purpose, because every shortcut around a password is also a way in for somebody who is not you.

FinOps RoboticsAccountant agent
—workspace
Settings

Settings

How the agent looks to you. These are yours alone — they change nothing about what it does or what it is allowed to do.

Two-step sign-in

A second factor on your own account. It protects everything this agent can reach.

The agent's suit

Each of these was checked for contrast against the dark card it sits on, so it stays readable whichever you pick.

Green, amber and red are deliberately not themeable anywhere in this app. Posted, held and exception are not decoration — they mean something, and a colour that means something should not be a preference.

Preview

What you have picked, in the state the agent is in right now.

— —
FinOps RoboticsAccountant agent
—workspace
Setup · step 1 of 2

What should this agent do?

Tick the work you want done. What it needs connecting to follows from this — you will not be asked to connect anything that nothing on this list uses. You can change it later.

Nothing chosen yet Tick at least one job to begin.
FinOps RoboticsAccountant agent
—workspace
——
Setup · step 2 of 2

Wire the agent into your systems.

Connect what you have. Where a clean API exists we use it; where it does not — a bank with no feed, a BNPL provider that issues keys by email — there is a file route that reconciles exactly the same way.

0 of 7 connected Start with QuickBooks — everything the agent prepares has to have somewhere to land.

What happens after this

Connecting does not switch anything on. It gives the agent read access so it can start proving itself against work you have already done.

01
Rule set

We write your tolerances, coding rules and approval thresholds against the standard you report under, and you sign them off.

02
Parallel run

The agent prepares everything and posts nothing. You compare its output to your own for as long as it takes to trust it.

03
Posting rights

Once the output matches, you release posting — per process, under a named approver, and revocable in one click.

Connector

—