Contractor Bookkeeping: A Receipt Review Routine

A receipt photo tells you what a document looked like when you captured it. It does not necessarily tell the next person which job the purchase belongs to, whether another copy was already entered, or why the amount differs from the record they are reviewing.

Start by making those questions visible. Keep the source document, record the facts you know and flag what still needs checking. That gives the person responsible for your books a clearer starting point than a folder full of unexplained pictures.

This guide covers preparing purchase records for bookkeeping review. It is not a complete accounting system, a bank-reconciliation procedure or tax advice. Your qualified adviser should determine accounting treatment, required records and retention, deductions and filing obligations. A completed checklist does not establish that your books or taxes are correct.

Agree on what the reviewer needs

Before reorganizing a year's worth of receipts, ask the person who reviews your records how they want to receive them. Agree on a storage location, a way to identify each document, the relevant job or business reference, and where unanswered questions should go. Use your existing approved process if one is already in place.

Try that arrangement on a small group of recent purchases. Can the reviewer open the original document, understand your note and tell what remains uncertain? Resolve those problems before applying a new naming system everywhere.

The IRS overview of business records explains that supporting documents should be organized and that more than one document may be needed to support a purchase or expense. It does not make your receipt folder a substitute for the books themselves.

A sensible review packet connects the original source to your explanation. “Materials” is a start, but “replacement fittings purchased for job DEMO-R10; one item may have been returned” tells the reviewer what to investigate. Keep the uncertainty in the note instead of silently treating the entire purchase as settled.

Capture the source without changing what it says

Use a readable photo, scan or original digital file through your approved storage method. Check that the document is complete: the vendor, date, item detail and total should not be cut off or hidden by glare. If there are several pages or a separate payment document, retain the connection between them.

Keep the date printed on the source distinct from the day you uploaded it. A picture taken on Friday does not establish that the purchase happened on Friday. If the date cannot be read, mark it unclear and request a better copy; do not replace it with today's date merely to finish the entry.

Keep any transcription beside the source. If software reads a number from an image, compare the extracted fields with the document before treating them as checked. This is a review step, not a claim that a particular app offers reliable extraction or that software can settle an ambiguous purchase.

Record only information the reviewer needs, and store it with appropriate access. A receipt may contain account details or other private information. Do not put it in a public job gallery or broadly shared team chat. Preserve required originals and follow the record-retention instructions for your business; do not discard a document just because a photo exists.

Add job context without guessing at the allocation

Record the job reference when it is known. If the purchase was for general stock, several jobs or another purpose, say that. A supply-store name alone does not establish which job used the materials.

For a mixed purchase, describe the known item-to-job connections and the unresolved portion. Do not assign the entire amount to the most convenient job to clear the list. The person responsible for costing or bookkeeping should decide the allocation using the appropriate records and method.

Keep purchase, receipt of goods and use on a job separate. Buying a box of fittings does not prove that the whole box was used at the next visit. If you need to reconstruct what happened on site, refer to the contractor job-notes checklist. For current quantities, location and usable stock, use the contractor inventory checklist.

Those records answer different questions. Link them where useful, but do not manufacture a job-use record from a purchase receipt or a stock count from a bookkeeping entry.

Check whether the purchase is already represented

One purchase can leave several documents: a supplier invoice, a receipt, an emailed copy and a payment record. Finding another document is a reason to compare the records, not automatically a reason to add another expense.

Compare the source identifiers, vendor, dates, amounts and item details. Two documents with the same total might still describe different purchases. Two versions with different dates might relate to the same purchase and its later payment. Record what supports a proposed connection and what does not match.

Check for an existing record before you create a new one. QuickBooks Online's bank feed matching guide draws the same line: match a downloaded transaction to a record you already have, or add it as new. Pocket Boss sends invoices and recorded payments to QuickBooks Online one way, so a payment that is already there should be matched, not entered a second time.

If the relationship is uncertain, leave a question for the reviewer. Do not delete financial entries, force a match or change a completed reconciliation to make the screen look tidy. A possible duplicate in the review list is not a confirmed duplicate transaction.

Use a review sheet that leaves open questions visible

Here is an invented example, not a customer case or an accounting record. DEMO-R10 and the document identifiers are fictional. The review happens on September 10, using permitted source documents already available to the people involved. The listed amounts are document totals, not approved job costs or tax deductions.

On a narrow screen, scroll the example sideways. Keyboard users can focus the table area and use the arrow keys.

Do not add these four rows to get “total expenses.” Two rows describe copies of the same receipt, one lacks supporting detail, and another concerns a return. The table's purpose is to explain what needs review, not to decide the final entries or calculate profit.

Before sending this packet, assign each open question to the person who can answer it and agree on the next check. The example does not assume that the purchaser has responded, an allocation has been approved or a refund has arrived.

Send the records and the exception list together

Keep unresolved items in the same handoff as the documents. A separate message saying “there were a few problems” can easily lose its connection to the affected receipt.

For each open item, include the source reference, the specific question, any supporting facts, who is checking it and the next agreed follow-up. If you received an answer verbally, record who supplied it and when, then identify whether the answer is confirmed or still needs supporting information.

A short handoff could read: “September purchase packet is ready for review. R10-01 needs an item allocation check, R10-02 is another source copy and needs a check against the books, R10-03 needs item detail and purpose, and R10-04 needs refund follow-up. These are open questions; no final treatment is implied.”

Confirm that the intended reviewer can access the files through the approved method. Sending a link is not proof that it opens for them. Do not share credentials or expose unrelated customer, employee or financial records to solve an access problem.

Keep “prepared,” “received for review” and “review completed” distinct. When the reviewer makes a decision, record that actual decision through your normal process. Do not mark every item resolved simply because the packet was sent.

Improve the routine using the problems you actually find

Choose a review rhythm that fits your transaction volume and the person handling the records. There is no universal number of minutes that makes bookkeeping complete. Start with a manageable batch and pay attention to which facts repeatedly go missing.

If job references are often unclear, improve the purchase note. If images are unreadable, change how people capture them. If several copies arrive through different channels, agree on how the review list should connect them. Adjust the process around a recurring problem rather than adding fields nobody uses.

When considering operational software, use the PocketBoss financial-tracking overview as a starting point for evaluating the product. Confirm the current capture, access and export behavior you need before relying on it. This routine does not establish a product feature, a completed accounting integration or a replacement for professional bookkeeping.

The immediate goal is a set of readable source records and clearly assigned questions. That is something you can check. Whether the books are complete, the treatment is correct or the records support a particular filing requires the appropriate review beyond this worksheet.