Stop typing receipt details into spreadsheets by hand

It is Friday afternoon. A fuel receipt is in the glove box, two supplier receipts are on WhatsApp, and another is fading inside a wallet. Someone still has to copy the merchant, date, VAT, total, and KRA details into a spreadsheet before the records are useful.

For many owner-managed businesses, that person is the owner or the one administrator already handling customers, stock, suppliers, and payments. The problem is not one receipt. It is repeating the same careful typing every week and then correcting avoidable mistakes.

Snapsheet changes the first part of the job. It reads standard KRA ETR and eTIMS details from receipt photos and PDFs, then prepares records for a person to review and export. The goal is not to remove the check. It is to spend less time typing and more time checking the details that matter.

I would not begin with the box of receipts from last year. That is how a small test turns into a rescue mission. Begin with five receipts you understand, compare the old work with the new workflow and learn where your real problems are.

This is part one of a three-part receipt workflow. Next, learn how to stop chasing missing receipts at month-end.

Quick answer for a busy owner

• Start small: use five receipts from one completed week.
• Capture well: take clear, complete photos or keep the original PDFs.
• Extract first: let Snapsheet prepare its standard Kenyan receipt fields.
• Check the draft: compare every important value with the source receipt.
• Export: download the reviewed records as Excel or CSV.
• Measure: compare the time and corrections with your normal manual process.

You do not need to redesign your entire expense process. A five-receipt test is enough to show whether the workflow can remove useful work from your week.

Why manual receipt entry becomes expensive

Typing a receipt looks like a small task until you count every step. Someone opens the image, zooms in, finds the correct spreadsheet row, copies several fields, checks the decimal points, and names or files the source. If the photo is cropped or the print has faded, the person stops and asks a question.

The same work returns when a field was missed, a receipt was entered twice, or the accountant cannot match a row to its source.

Automation helps most when it removes this repeated preparation. It does not make an unclear receipt clear, explain why the purchase was made, or decide how the expense should be treated. Those responsibilities stay with your business and accountant.

Decide what a useful result means before the test

“We used AI on our receipts” is not a business result. Decide what you want the five-receipt test to prove.

For a business owner, a useful result could mean:

• the administrator prepares the records without typing every field;
• the owner reviews only exceptions and larger amounts;
• every exported row can be traced back to a source receipt;
• missing context is discovered during the week rather than at month-end; or
• the same number of checked records takes less staff time to prepare.

Write down your current process in one or two sentences. For example: “Jane receives receipt photos through WhatsApp, types eight fields into Excel, and asks me about anything she cannot identify.” After the test, describe the new process just as simply.

This prevents the team from judging Snapsheet only by how quickly a result appears on screen. A fast extraction that nobody checks is not a successful workflow. The result must be accurate enough for its intended use after a person has reviewed it.

Step 1: Choose five receipts you understand

Pick five receipts from a week that is already complete. Use familiar purchases so you can quickly recognise a wrong merchant, date, or total.

Choose a useful mix:

1. one clear paper receipt;
2. one original receipt PDF;
3. one receipt with several line items;
4. one receipt with VAT or other KRA details you normally record; and
5. one difficult photo, if poor images are common in your business.

Before using Snapsheet, note how you handle these receipts today. If you usually type them manually, time that process or estimate it honestly. Also count how many corrections you make. This gives you a fair comparison after the test.

Step 2: Make each source readable

Good extraction starts with a source a person can read. For a paper receipt, place it on a flat surface in good light. Keep all four edges in the photograph and check that fingers, shadows, folds, or glare do not cover important text.

Open the photo before sending it. Can you read the merchant, date, total, and KRA details without guessing? If not, retake it while the original is still available.

For a digital receipt, use the original PDF when possible instead of a screenshot forwarded several times through WhatsApp. Keep the original file in an approved business folder, not only in an employee's personal chat or camera roll.

Only upload documents your business is permitted to handle, and follow your own privacy and record-retention rules.

Step 3: Let Snapsheet prepare the receipt record

Open Snapsheet and process the five receipt photos or PDFs. There is no field-selection step. Snapsheet extracts a fixed set of standard KRA ETR and eTIMS details, which may include:

• merchant name, date, and time;
• seller and buyer KRA PINs;
• subtotal, VAT, total, and currency;
• line items and payment details; and
• ETR serial, invoice number, signature, and verification link.

The resulting record is a draft. Faded thermal paper, glare, cropping, unusual layouts, and poor image quality can all affect what is read. A confident-looking value can still be wrong, so do not skip the source check.

Step 4: Review every receipt in the same order

A fixed review order makes the check faster and easier to teach. For each receipt:

1. Match the record to the correct source image or PDF.
2. Check the merchant, date, and total amount.
3. Check VAT, KRA PINs, ETR identifiers, and other tax details you need.
4. Review important line items and payment information.
5. Add a category, tag, purchaser, project, or business purpose where needed.
6. Mark anything you cannot confirm for follow-up.

Do not correct an unreadable value by guessing. Ask the purchaser, find a clearer source, or leave the question visible for the appropriate reviewer.

The person doing this work does not have to be the owner. An administrator can prepare the records while the owner or finance lead checks exceptions and larger amounts.

A worked five-receipt example

Imagine a Nairobi-based supplier testing the workflow with these documents:

1. a fuel receipt for a delivery vehicle;
2. a PDF from a packaging supplier;
3. a hardware receipt with several line items;
4. a client-site parking receipt; and
5. a faded receipt for office supplies.

The administrator uploads the five sources and reviews the extracted records. The first three match clearly. The parking receipt needs a business-purpose note because the document does not say which client visit it supported. The faded office-supplies receipt has an unclear invoice number, so the administrator marks that field instead of guessing.

The owner does not need to reread every obvious detail. They confirm the delivery vehicle, the client visit, and the unclear exception. The finished export contains five reviewed records, while the source folder still contains the five original documents.

That is a useful result even though one field remains unresolved. The workflow has made the uncertainty visible and sent it to the right person.

Step 5: Export a spreadsheet you can actually use

After reviewing the records, export them as Excel or CSV. The export includes every receipt field Snapsheet holds. You can filter which records to include by date, category, tag, or individual selection before downloading.

Use a consistent file name such as receipts-2026-08-reviewed.xlsx, and keep the source receipts with the export. If your accountant needs the scans together, you can also prepare an audit-pack PDF.

Snapsheet prepares KRA-ready receipt data. It does not file a KRA return, guarantee compliance, decide whether an expense is deductible, or choose its accounting classification.

Step 6: Check the batch before calling it complete

Finish the five-receipt test with a short control check:

1. Count the source receipts and exported records.
2. Recheck the largest total and any value with a decimal point.
3. Look for repeated merchant, date, and total combinations that may be duplicates.
4. Review every record marked for attention.
5. Ask a second person to compare at least one record with its source.

Now compare the result with your starting point. How many minutes did extraction, review, and export take? How many corrections were needed? Was it easier to find missing information?

The useful measure is not whether software touched the receipt. It is whether your business produced a checked record with less repetitive work and fewer avoidable corrections.

Common ways the first test goes wrong

The technology is only one part of the workflow. Watch for these process mistakes:

Uploading a large backlog first

A pile of 200 old receipts creates too many questions at once. Start with five current documents, agree on the review method, and expand only when the team can repeat it confidently.

Treating extraction as final approval

An extracted total can look convincing and still be wrong. Keep the source visible and require a human check before export or handover.

Measuring upload speed instead of finished work

Count the time from collecting the source to producing a checked export. Include corrections and follow-up. That is the real work you are trying to improve.

Losing the source after export

A spreadsheet row is easier to use when the team can find the receipt behind it. Keep a consistent source folder or audit pack for the same period.

Giving every question to the owner

The owner should not become the new bottleneck. Agree on which exceptions an administrator can resolve, which need the purchaser, and which should go to the accountant.

What to track for the next four weeks

If the five-receipt test works, repeat it weekly for one month. Track the number of receipts, total processing minutes, corrections after review, unclear sources, missing business-purpose notes, and possible duplicates.

Do not turn this into a large reporting exercise. A simple weekly note is enough. At the end of four weeks, ask whether the business is producing checked records earlier, whether the owner is answering fewer routine questions, and whether month-end starts with fewer gaps.

Those answers tell you whether to keep the workflow, change it, or stop using it.

Turn the test into a repeatable habit

Your first batch will usually reveal a process problem beyond typing. Perhaps receipt photos arrive late, the business purpose is missing, files live in personal WhatsApp chats, or nobody owns the final review.

Fix the smallest repeated problem first. Choose one collection place, one processing time, and one person responsible for open questions. That is how a useful five-receipt test becomes a receipt process your team can maintain.

The point is not to celebrate that AI read a receipt. The point is to give somebody back the time they used to spend copying it—without losing the care that makes the record trustworthy.

Continue to part two: stop chasing missing receipts at month-end.