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.

Want to try it?

Ask your Strawberry companion: “Gather the invoices, receipts, and payment evidence for this period, build a traceable register, and prepare the missing and ambiguous items for review.”

Skill

Organize invoices, receipts, and bookkeeping

Prepare the documents, register, and exceptions for the accepted reviewer without altering financial records.

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.

Run an AI-native ops teamConnect recurring finance administration with the wider operating system around it. How to review financial performance with AIUse accepted records to explain what changed and what needs attention. How to build a financial forecast with AICarry the accepted current picture into a forecast for cash, runway, and operating decisions.
Official Strawberry skill
Copy skill file Download skill file
name
organize-receipts-bookkeeping
description
Gather invoices, receipts, and payment evidence from approved email, vendor portals, files, and records; build a traceable transaction register; separate missing or ambiguous items; and prepare the next finance review or handoff. Use for recurring bookkeeping preparation without making payments, posting entries, or changing source records.

Organize Receipts and Bookkeeping

Turn scattered invoices, receipts, and payment evidence into a traceable register and clean review handoff. Prepare the records for the owner, finance team, bookkeeper, accountant, or other accepted reviewer; do not decide the accounting treatment or alter a financial record.

1. Define the handoff

Establish the company or entity, period, currencies, approved sources, destination, reviewer, and definition of complete. Learn the existing register fields, file naming, matching rules, and review or handoff format when they exist.

Useful approved sources may include email, vendor portals, billing tools, payment records, files, and an existing spreadsheet or accounting export. Work through visible, logged-in browser tabs when that is where the evidence lives. Suggest a connection only when it improves the chosen result.

2. Gather and record the evidence

Retrieve only the documents and records in scope. Preserve the source link, document date, vendor or payee, amount, currency, transaction reference, retrieval date, and original filename where available. Store or rename files only in the accepted destination and convention.

Build or update a reviewable register. Keep the original evidence available; do not turn a row in a spreadsheet into the only record of the transaction.

3. Match conservatively

Match a document to a payment or transaction only when identifiers, amount, currency, date, counterparty, and context support it. Do not force a match from amount alone.

Separate:

  • supported matches;
  • missing invoices or receipts;
  • ambiguous or partial matches;
  • possible duplicates;
  • unexpected vendors, payers, amounts, or dates; and
  • items that need accounting or tax judgment.

When the rules or volume are new, present a small, varied sample before processing the full period. Apply accepted corrections to the remaining work.

4. Check and deliver the handoff

Reconcile the register count and totals to the source set where possible. Check duplicates, date and currency consistency, links, filenames, and whether every exception is visible.

Deliver the organized evidence, register, and exception list with a short handoff note covering scope, sources, coverage, unresolved items, and questions for the accepted reviewer. Do not claim the books are complete or reconciled when only the supporting evidence has been prepared.

Use strawberry/finance/review-financial-performance after the accepted records are ready and the next question is what changed in the financial picture.

5. Make the next collection easier

After the user accepts the fields, sources, matching rules, and filing convention, preserve them as a reusable method. A Routine may retrieve documents from named sources on an agreed cadence and prepare the register and exceptions for review. It should stop when the company, account, period, source, destination, or matching confidence falls outside the accepted scope.

Reading a payment record is not permission to make a payment. Do not initiate, approve, schedule, or alter payments; post, reverse, categorize, or approve entries; change bank, ledger, payroll, invoice, or source records; or share the handoff beyond the accepted audience. Stop for review at MFA, new account access, an identity or entity change, or a broader sensitive-data scope.