Try this skill in Strawberry

Organize Receipts and Bookkeeping

Strawberry can log in to vendor portals and billing pages in the browser to download invoices that never arrive by email.

Setup

  • Which company and period, and where the receipts usually turn up, e.g. email, vendor portals, or a shared folder.
  • Where the register and files should go, and any existing naming or column conventions.
  • Who reviews it: the owner, a bookkeeper, or an accountant.

Worth knowing

  • Keep a link to the original document for every row. The spreadsheet shouldn't become the only record.
  • Only match a receipt to a payment when more than the amount agrees, e.g. date, vendor, and reference.
  • List missing receipts, possible duplicates, and anything that needs an accountant's judgment separately, rather than guessing.
  • This prepares the books. It never makes payments or changes accounting records.

Invoice and receipt collection is a good example of work that is simple in theory and tedious in practice. The evidence may be split across email, vendor portals, payment records, downloads, and a spreadsheet that only makes sense to the person who assembled it.

Strawberry can work through those sources in the visible, logged-in browser, keep each document connected to its origin, and prepare a register another person can review. The useful result is not autonomous bookkeeping. It is a cleaner review with fewer missing documents and fewer forced matches.

Decide what the reviewer needs

Start with the company, period, currencies, approved sources, destination, and reviewer. If the owner, finance lead, bookkeeper, or accountant already uses a register, filename convention, or exception format, keep it. A new template is not an improvement when it creates more translation at the end.

Keep the source beside each row

The browser matters because many documents are not sitting in one export. Strawberry can inspect an approved inbox, follow the vendor link, use the logged-in portal, retrieve the right invoice, and return to the register without losing the path. You can watch the work, correct it, or take over at an access boundary.

Keep for each itemWhy it helps
Vendor, date, amount, currency, and referenceSupports matching without relying on one ambiguous field.
Document and source linkLets the reviewer trace the row back to the evidence.
Match state and noteSeparates supported matches from missing, ambiguous, or duplicate items.
Retrieval date and original filenamePreserves what was found before files are organized or renamed.

Review the exceptions, not just the completed rows

A confident-looking match can still be wrong. Amount, date, currency, counterparty, and transaction reference should support one another; amount alone is not enough. When the rules are new, a small set with a clean match, missing document, duplicate-looking item, and ambiguous case is more useful than processing the entire month before anyone reviews the judgment.

  • Keep unmatched items visible instead of forcing completion.
  • Flag questions that need accounting or tax judgment.
  • Reconcile the register count and totals to the available source set where possible.
  • State the coverage and gaps in the handoff note.

Make the recurring work safer

After the reviewer accepts the sources, fields, filing convention, and matching rules, the companion can carry those choices into the next period. A Routine can collect from named sources and prepare a new register and exception list, stopping when the company, account, period, destination, or matching confidence changes.

This workflow does not make or approve payments, post entries, change invoices, or declare the books complete. Those are different actions with different ownership and risk.