Run the queue, not a folder hunt
A firm-level view should show last import, matched count, review count, unresolved count, and last reconciliation by client. From there a bookkeeper can jump directly to the exceptions rather than opening every file to see whether work remains.
The summary should avoid exposing unnecessary transaction values. Operational counts are usually enough to route work across the team.
Keep client context scoped
A bank description that identifies one customer's legal entity may mean something else in another workspace. Source payer names, invoice references, date evidence, and reviewer decisions should remain attached to the correct client and import.
Organization roles and row-level policies should prevent one client workspace from reading another. Server checks must enforce the same boundary even if a user edits a URL.
- Separate client workspaces
- Mapping preview on every import
- Inspectable payer evidence
- Portfolio counts without merged financial records
Make handoff easy to review
An audit log should record the source file, automated reasons, reviewer, decision, and final applications. Exports can then accompany the bookkeeping close package and show what remains unmatched.
For messy first files, a client can send them through an authenticated support workflow. Do not expose financial uploads through an unprotected public form.