LedgerVault first stop (PRD-119) — design concepts

The idea: two outline buttons on the Cashbook header (Connect to LedgerVault, Bulk import from LedgerVault), LedgerVault in the app switcher, and a table-centric LedgerVault dashboard with a status column per product, a Transfer or Open action per row and a ⋯ menu for the trial balance and Disconnect.

• 👍 every organisation and its next action are visible in one table, nothing to open first
• 👎 two similar-looking buttons next to each other; the franchisee must know which one they want

Critic (1–5): Xero n/a · Hierarchy 4 · Clarity 4 · States 4 · Flow 4 — recommended

The idea: the same table for the central team with a Branch filter, checkboxes and a sticky Transfer bar; progress and a per-organisation result dialog.

• 👍 works like a spreadsheet, filter and tick, scales to hundreds of rows
• 👎 needs the Branch filter to be set right or you transfer into the wrong branch

Critic (1–5): same concept; see Concept A

The idea: a LedgerVault hub card on the Cashbook dashboard carries the counts and both actions, so the header keeps one primary button; LedgerVault shows organisations as cards grouped by next step (Not in Cashbook yet, In Cashbook) with a full drill-down page per organisation.

• 👍 the dashboard explains LedgerVault before you click, and "Not in Cashbook yet" is the first thing a franchisee sees
• 👎 cards take more space than rows; the hub card pushes the cashbook list down

Critic (1–5): Xero n/a · Hierarchy 4 · Clarity 4 · States 5 · Flow 4

The idea: organisations grouped by branch, each group with its own "Transfer all waiting" button plus per-card ticks.

• 👍 a whole branch in one click, and the branch is always obvious
• 👎 long page with many branches; selecting across branches is clumsy

Critic (1–5): same concept; see Concept B

The idea: one LedgerVault button on the Cashbook header opens a two-choice panel (connect more / import connected) with counts; LedgerVault is master–detail: organisations on the left, the selected one's product status and stored trial balance on the right.

• 👍 one button, one decision, and the trial balance is never more than one click away
• 👎 the panel adds a step before every action; master–detail is cramped on small screens

Critic (1–5): Xero n/a · Hierarchy 4 · Clarity 5 · States 4 · Flow 3

The idea: a four-step wizard for the central team: branch, organisations, confirm, done.

• 👍 one decision per step; impossible to transfer into the wrong branch
• 👎 slower for someone who does this all day; one branch per run

Critic (1–5): same concept; see Concept C