Missing Transaction Documentation: A Month-End Checklist

What is missing transaction documentation?

Missing transaction documentation is the set of company charges that do not yet have enough supporting proof for finance review. The gap may be a missing receipt, an invoice that has not been attached, a document that belongs to a different transaction, or an unclear purchase that still needs context.

Before month-end close, build one exception list from the charges finance already reviews. Separate complete records from missing or uncertain ones, record exactly what each exception needs, assign a follow-up owner, and return resolved records to the accounting workflow.

This missing transaction documentation checklist focuses on company charges and their invoices or receipts. It is not a replacement for bank reconciliation, expense policy, or an accounting decision about accruals and cut-off.

For the matching process itself, read How to Match Transactions to Invoices and Receipts. You can also use the month-end receipt collection guide to improve employee follow-up.

A quick status framework

Use three statuses so incomplete work stays visible:

A file attachment alone is not the completion test. IRS recordkeeping guidance describes invoices, receipts, statements, and proof of payment as supporting documents. It also notes that companies may need a combination of documents to substantiate all elements of an expense. Review whether the available proof supports the payee, amount, date, payment, and business context rather than only checking that a file exists. (IRS)

Month-end checklist for missing transaction documentation

1. Define the review period and population

Start with the close period and the company charges finance expects to review. Use the card or accounting data already in the workflow rather than beginning from a separate spreadsheet of remembered purchases.

Confirm which accounts, entities, cards, and transaction dates are in scope. This prevents the missing-document list from mixing current-period charges with older items or transactions owned by another process.

2. Confirm the transactions reached the accounting workflow

Check that the period’s relevant bank and card activity is present in the accounting system or the connected review flow. A missing transaction is different from a transaction with missing proof.

QuickBooks includes account reconciliation and organized documentation in its month-end accounting checklist. Xero defines bank reconciliation as comparing business records with bank activity and investigating missing entries or discrepancies. Use those workflows to confirm the books and bank activity; use this missing transaction documentation checklist to confirm that each charge has the proof finance needs. (QuickBooks, Xero)

3. Gather proof from the places it already arrives

Search the sources where invoices and receipts normally appear:

• shared finance or AP mailboxes;
• employee Gmail accounts where permitted;
• Google Drive folders;
• direct uploads;
• vendor portals;
• purchase-confirmation or billing emails.

Collecting from known sources first keeps follow-up focused. Do not ask every employee for every receipt when finance may already have many of the documents.

4. Check whether the proof supports the charge

For each proposed match, compare the available evidence:

• vendor or merchant;
• transaction amount;
• document total;
• currency;
• transaction, invoice, receipt, or email date;
• invoice number or order reference;
• line items or service description;
• sender and surrounding email context.

No single field proves the relationship in every case. If the evidence conflicts or several documents could match, keep the item uncertain rather than forcing a completed status.

5. Classify each documentation gap

Use a specific reason instead of one generic “missing receipt” label:

• no document found;
• invoice found, receipt missing;
• receipt found, invoice missing;
• wrong document attached;
• vendor does not align;
• amount or currency conflicts;
• date is unclear;
• duplicate or multiple possible documents;
• one document may cover several charges;
• business purpose or owner is unclear;
• accounting decision required.

A useful exception reason tells the next person what to investigate. It also separates collection work from decisions that belong with the controller or accountant.

6. Record the minimum exception details

At this stage, turn missing transaction documentation into one clear row or review item for each unresolved charge:

Controller-oriented close guidance consistently recommends named ownership, deadlines, and visible open-item status rather than leaving incomplete work undocumented. (Finance Alliance)

7. Assign one owner and one next action

Avoid broad messages such as “Please submit any missing receipts.” Assign the exception to the person most likely to resolve that specific charge and state what is needed.

Examples:

• “Send the invoice for the August 28 software charge.”
• “Confirm whether this receipt covers one charge or several.”
• “Review the currency difference before marking the item complete.”
• “Decide whether this needs an accounting adjustment rather than another document search.”

The controller can own the exception queue without personally chasing every item. Department owners, cardholders, AP, procurement, or the vendor may own the next action.

8. Recheck only the unresolved exceptions

Once finance separates complete transactions from missing and uncertain items, work from the exception list. Reopen a completed record only when new evidence conflicts with it.

This is the practical advantage of an exception-first process: finance spends review time on the charges that still need a document or decision instead of checking the full transaction population repeatedly.

9. Keep the accounting system as the source of record

The exception tracker should support the accounting workflow, not become a competing ledger. Preserve the original transaction source and keep the final document connection available to the accounting team.

With ClearSpend, QuickBooks or Xero can remain in the workflow while finance collects proof and reviews what is missing. The goal is to return ready records to the existing process, not replace it with another disconnected tracker. See transaction matching for the product workflow.

10. Close with open items documented honestly

Do not hide an unresolved charge inside a completed status. If an item remains open at the close deadline, record:

• what is missing;
• what the team has already checked;
• who owns the next step;
• the expected resolution date;
• whether a controller or accountant must make a separate close decision.

This missing transaction documentation checklist organizes documentation follow-up. It does not determine the accounting treatment for an unresolved expense, cut-off question, or accrual. Route those decisions through the company’s existing review and approval process.

Common missing transaction documentation scenarios

The card statement shows the charge, but there is no receipt

Treat the statement as transaction evidence, not automatically as complete proof of business purpose. Search email, Drive, uploads, and the vendor before assigning follow-up. IRS guidance notes that companies may need a combination of supporting documents to substantiate an expense. (IRS)

An invoice exists, but the amount is different

Check currency, tax, tips, credits, partial billing, and whether the invoice covers more than one transaction. If visible evidence does not explain the difference, leave the item uncertain.

Several documents could match one transaction

Use invoice numbers, order references, dates, line items, sender context, and totals to distinguish them. Do not select a document only because the vendor matches.

The employee or vendor has not responded

Keep the item assigned and open with the original request date and next follow-up date. If the close deadline arrives first, escalate the item for a controller or accounting decision rather than inventing documentation.

What controllers should review before sign-off

Before treating the missing transaction documentation review as complete, confirm:

• every in-scope charge has a visible status;
• every missing or uncertain item has a specific reason;
• every exception has one owner and next action;
• resolved items retain the supporting document connection;
• finance separates accounting questions from document-collection tasks;
• unresolved items remain visible with an expected resolution date;
• completed records are ready for the existing QuickBooks or Xero workflow.

ClearSpend’s CFO and controller workflow supports clearer finance review without replacing the systems the team already uses.

Frequently asked questions

What is missing transaction documentation?

Missing transaction documentation is the absence of adequate supporting proof for a company charge. The missing item may be a receipt, invoice, payment evidence, or purchase context needed for finance review.

What should a missing invoice tracker include?

At minimum, track the transaction, documentation status, exception reason, owner, next action, due date, and resolution note. Keep the tracker connected to the accounting workflow rather than using it as a separate ledger.

Is a bank statement enough when a receipt is missing?

A statement confirms that a transaction occurred, but it may not explain the business purpose or provide every detail finance needs. Review the payee, amount, date, proof of payment, and purchase description. A company may need a combination of supporting documents.

Is document matching the same as bank reconciliation?

No. Bank reconciliation compares bank activity with the accounting records. Transaction-to-document matching connects a company charge with its supporting invoice or receipt.

Can ClearSpend work with QuickBooks or Xero?

Yes. ClearSpend keeps QuickBooks or Xero in place while connecting transactions with invoices and receipts and surfacing unresolved items for review.

Sources

• IRS: What kind of records should I keep? — types and elements of supporting documents for business records
• QuickBooks: Small Business Accounting Checklist — organized documentation and month-end reconciliation tasks
• Xero: How to do a bank reconciliation — distinction between bank reconciliation, missing entries, and organized supporting records
• Finance Alliance: Month-end close checklist — task ownership, deadlines, and missing-document follow-up