The AI drafts. A human confirms. Nothing posts to the ledger on its own.

The bridge that runs your month-end
with you.

One close board. Every entry, every owner, every file in one place. It reads what your month sends it, drafts the journal entries with the work shown, and waits for a person to say post.

the bridge · July 2026
Standard journal entries 1 of 5 confirmed
TaskDayStatusOwnerAmountNote
Intangibles AmortizationDay 1CLOSEDBThe board412,600.00Carried from prior month, confirmed
Bi-Weekly Payroll AccrualDay 1DRAFTCTController196,480.25Email support received
ASC 842 Lease AmortizationDay 2DRAFTCTController438,905.10Lease amortization schedule prepared
Revenue Recognition AdjustmentDay 2REVIEWCFCFO Waiting on support details
Bonus AccrualDay 3OPENCTController Accruing to annual plan target
This board is live. Open an entry to see what it drafted, what it checked, and the file it read.
31entries
$39.5Mtied both ways
155lines, largest entry
every monthconfirmed by a working controller
The close, day by day

Five working days, and what
the board does in each

The accounting does not change. What changes is who does the fetching, who does the retyping, and whether the state of the close lives in a person's head.

WD-2gather

Your month arrives the way it always does

An export, an email, a working paper, a screenshot. Nobody changes how they work, and nothing has to be uploaded to a portal first.

the board reads it
WD-1prepare

Last month's entries carry forward, empty

Every account and every side arrives in place, with last month's figure beside each line as reference. The amounts stay blank, because a figure that is typed for you is a figure nobody checks.

the board carriesyou still do the accounting
WD 1draft

It drafts the entry and shows its work

Each line traces to a document number and a source file. It refuses to export until it balances, and it names the line that is short.

the board drafts
WD 2review

A person opens it, sees the checks, and confirms

The state lives on the row, next to the entry and its backup. The request never travels away from the work it is about.

a person confirms
WD 3post

It posts, and the ledger's own number comes back

Derived from the file, never typed. If the period is not loaded, nothing claims to be posted.

the board postsonly after you say so
What it does

Built for the way a close actually arrives

Not a portal your team has to be trained into. They keep sending what they already send, and the board does the reading.

01

Drop anything on its entry

Excel, CSV, PDF, a screenshot of a portal. Ten plus formats through one reader.

02

Or just email it in

Forward it to the intake address. The board files it against the right entry.

03

Roll-forward that tells the truth

Accounts and sides carried. Amounts left blank, on purpose.

04

Guards that hold, not guess

Wrong entry, wrong tab, wrong period: it holds and says which.

05

QC with four honest states

Closed, draft, review, open. No fifth state that means nothing.

06

Close package on demand

Every entry, every check, every source file, in one download.

Connections

How your data reaches the bridge

Two families of ledger, two ways the numbers move, one board in the middle. Reading a system beats parsing its export, and the board does both.

How your data reaches the bridge Four tiers left to right. Cloud ledgers, desktop ledgers and everything else feed two intake paths, a direct API pull and a single file reader. Both converge on the bridge, which drafts the entry and shows its work. A person reviews and confirms, and only then does anything go back, either posted by API or handed back as an import file. Cloud ledgers QuickBooks Online, NetSuite, Xero, Sage Intacct, Dynamics 365 Desktop ledgers QuickBooks Desktop and Enterprise, Sage 50, anything that exports Everything else Payroll registers, bank exports, ops reports, working papers, PDFs, screenshots Direct pull API, on a schedule One reader drop it, or email it in 10+ formats, guarded THE BRIDGE drafts the entry shows its work A person reviews and confirms Post by API cloud ledgers, after confirm Post by import file .IIF or CSV, imported by a person live connection file exchange a person Two ways in, one bridge, one human gate, two ways back.
Either path, same rule. A live connection changes how the numbers arrive, never who approves them. The confirm stays human on both sides.
The assistant

It sits beside the board, and it shows its work.

Drop the register on it. It reads what arrived, drafts the entry, names the file behind every figure, and stops when the support is not there. Nothing reaches the ledger until a person says so.

the board

Running on a loop. Click anything inside the frame to take over.

31entries on the bridge, Preclose through Day 3
3,912posted lines tied to the penny by the QC layer
10+file formats read through one converter, screenshots included
100%of postings confirmed by a named person, on the record
Get started

See your own close
on the bridge.

Bring one month. We read it, draft the entries, and show you the work behind every number. You decide what posts.

No connection to your ledger required to start.