Amounts, dates, vendors, and line items sometimes need to be checked against the original invoice. In Busabase, how would you keep the source file, extracted values, and review status together? Can unreviewed entries be kept out of the final ledger?
Yes. There is already a useful starting point: Busa Invoice Sheet. On that page, choose Install this template and select your workspace. It installs an Invoices Base, a review App, sample rows, and an Agent manual. The App shows extracted invoice fields and line items with confidence notes, then lets a person correct a row, approve it, request changes, or block it.
The template's companion Agent workflow extracts a batch and imports it into the Invoices Base as Needs review. A reviewer checks the amount, date, vendor, line items, confidence and warnings in the App. Its export step produces CSV/JSON for approved rows only; it does not send anything to an accounting system or pay an invoice. In this template, the source filename and path are stored with the row, but the App does not upload the original invoice file. Keep that original in a location reviewers can open and include its reference when you ask the Agent to extract it. The template page includes the install entry and demo gallery.
If you need the original file *attached to the Busabase record itself*, add an attachment field to an invoice Base. This separate Busabase invoice example shows the source file next to the extracted values and a business status of Needs review:
For a further gate before an Agent's proposed edits become live records, give the Agent proposal-only access and review its Change Request in Home or Inbox → For review. That is a different review from the template App's Needs review / Approved business status. Here is what a field-by-field Change Request review looks like in the separate invoice example:
To keep unreviewed entries out of the final ledger, start with a saved view filtered to Approved. That is a display/export rule, not a permission boundary. If a downstream system must never see pending rows, use a separate Approved ledger Base and create records there only after finance verification. The current Busa Invoice Sheet template handles reviewed export, but does not create that separate ledger or enforce a Change Request on every extraction. We could extend the template for that stricter workflow. Is your final ledger another Busabase Base, or an external accounting system?
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in