Cashbook AI Concept comparison

PRD-112 · Internal notes on GST returns — design concepts

Three places to put internal team notes on a GST return: add a note, see which notes are still open, resolve them, and keep resolved notes as history. Each concept also shows how the GST returns list marks a return with open notes. Click a thumbnail to open the full concept; start on the list and click the first draft return (1 Jul - 31 Aug 2026). The second draft has no notes, so it shows the empty state.

Concept A — Notes tab

Open full ↗

The idea: a third tab, Notes, beside GST Return and Transactions. The header says "2 unresolved notes" and links to the tab. The list shows a small note badge in the Status cell.

  • 👍 Uses the page structure that already exists. The GST figures stay exactly as they are today.
  • 👎 A notes tab is one click away, so a preparer who ignores the header line can miss the notes.

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

Concept B — Notes rail

Open full ↗

The idea: notes always visible in a right-hand column beside the GST figures. The list gets its own Notes column.

  • 👍 Notes can never be missed, and the preparer can read a note while checking the box it talks about.
  • 👎 Narrows the GST figures on every return, even when there are no notes. Adds a column to a list PRD-110 is also changing.

Critic (1–5): Xero 3 · Hierarchy 3 · States 4 · Clarity 3 · Consistency 3 · Flow 4

Concept C — Callout + side sheet

Open full ↗

The idea: unresolved notes shown in a yellow box above the tabs, each with its own Resolve button. Adding a note and the resolved history live in a side sheet.

  • 👍 Most visible when there is something to act on, and invisible when there is nothing open.
  • 👎 Two places to look (box and sheet). A long note list pushes the GST figures down the page.

Critic (1–5): Xero 4 · Hierarchy 4 · States 4 · Clarity 4 · Consistency 3 · Flow 4

Optional add-on — first-open pop-up

Open full ↗

The idea: the old BankLink behaviour the client described. The first time each person opens a return with unresolved notes, a dialog lists them. It shows again after a newer unresolved note is added. It works with any concept above. The client called it "nice to have", so it is not in the recommended v1.

  • 👍 Impossible to miss a note.
  • 👎 Interrupts every first open, and needs a "seen" record per person per return.

Shared by all concepts — deregister warning

Open full ↗

The idea: deregistering from GST removes the draft returns after the last period. When those drafts carry unresolved notes, the existing warning gets one more line saying how many, and that the notes come back if the same period is created again. Nothing is blocked.

How to use this board

Walk each concept through the same lenses: information hierarchy (what's first / second / third), edge & empty states, click-vs-think cost, and the “simpler than Xero, same power” test. The chosen direction (or a blend) gets written up in DESIGN.md, then built high-fidelity by /cb-prototype.