Prepare a client’s month-end handover.

Define what belongs in this batch

Begin with a small, named client batch. Keep a separate note of the period and documents you expect, especially when files arrive through different channels. Receipt Workbench can organise selected files; it cannot know whether a client has supplied every receipt.

Use a clear client label and check it on each document. The beta accepts up to 25 PDF, JPG or PNG files, with a 10 MiB individual limit and 50 MiB batch limit. Each PDF may contain up to five pages. Keep separate receipts in separate files.

Separate a readable file from a reviewed record

Successful reading means text was obtained, not that the fields are correct. Compare the merchant, document date, total and currency with the original preview. For a multi-page invoice, inspect all pages before confirming its total.

If the date could mean two different days, or a dollar sign leaves the currency uncertain, resolve the question before confirmation. The month folder follows the reviewed document date. It is an organisational choice, not a decision about which accounting period should receive an entry.

Keep exceptions visible

Imagine a fictional four-file batch for Cedar Studio: an office invoice, a delivery receipt, a second copy of that receipt and a password-protected PDF. Confirm the first two after checking them. Inspect the duplicate warning before explicitly excluding the extra copy. Obtain an authorised unlocked replacement for the protected PDF, or record it separately as outstanding and exclude it.

The resulting download would contain two document copies and two CSV records. It would not prove the client’s month is complete. The excluded files are not in that package, so tell the recipient what remains unresolved using your existing communication process.

When a supported file passes its format checks but OCR fails, a manual-entry option may be available. Read the source yourself, fill every required field, then confirm. Unsupported or invalid files cannot bypass the checks through manual entry.

Inspect the finished package

Download only after every file is confirmed or explicitly excluded. Open the ZIP and check that the client folders and months make sense. Compare the document count with the CSV rows, then open a few source copies and follow their paths from the list.

For example, a reviewed October invoice appears under Cedar Studio/2026-10/. The CSV retains its original filename alongside the new path. Keep your original files; the downloaded documents are copies, and the tool does not rename files on your device.

Download a fictional handover ZIP (30 KB). This sample contains two reviewed document copies in September and October folders, plus manifest.csv and README.txt. Open the CSV and follow each archive_path to its file. The ZIP is ready to inspect without uploading a receipt.

Share through your approved process

The ZIP is not encrypted. Use a storage and sharing method appropriate for the records and the client. Download before refreshing or closing the workbench: the beta does not save your batch or edits between visits.

This checklist follows the current product workflow and limits. See the privacy explanation, the filename guide and the CSV review guide for related checks. The tool does not post transactions or determine tax treatment.

Compare this with your month-end routine

If you prepare receipt batches for clients, try the fictional files first. Then choose a small batch you already have permission to process. Aim for the same result in each workflow: reviewed copies organized by client and month, with a list that lets you find each file.

1. Time your usual method and the workbench separately. Start when the files are ready and stop when you have checked the handoff. Include any time spent fixing names, folders or CSV rows.
2. Check that every file you intended to include is present and that a CSV row leads to the right copy. Note anything you had to correct or leave out.
3. Share what happened if you choose. It helps to know whether you regularly prepare files for clients, roughly how long each method took, and what you had to fix. If you remember where you first heard about the workbench, you can mention that too. Keep receipts, attachments, filenames and client details on your own device.