Run a weekly expense reconciliation routine for a support assistant

Set the cut-off and the source of truth

Choose a weekly cut-off and the system that holds the authoritative expense record. Every claim should trace to that system rather than to a chat message or a personal note. Announce the cut-off to the client and the team so receipts arrive before the review. A clear cut-off turns a month-end scramble into a short weekly task.

Decide how late receipts are handled and who may approve an exception. Some expenses are legitimate but arrive after the cut-off, and the routine needs a place for them. Record the late item with its reason and the approver. The exception path should not become the normal path.

Match receipts to the card statement

Start from the card or bank statement and match each line to a receipt and a business purpose. Work in one direction so a missing item cannot hide. Mark the transactions that have no receipt and the receipts that have no transaction. Both lists are useful, because a receipt without a charge may indicate a duplicate or a personal purchase.

Check the amount, the currency, the date, and the merchant against the statement. A receipt that rounds differently may still be correct, but a different merchant is a question. Note the exchange rate source for foreign currency. Matching on amount alone misses the errors that matter.

Download the statement once and work from that saved copy so the review is repeatable. A live statement that changes during the week can make a matched line look missing. Save the extract with the week's folder and note the period it covers. The reviewer should be able to reproduce the match from the saved file.

Classify the expense before coding it

Ask the assistant to write the business purpose in plain words before choosing a category. A purpose such as client site visit for the monthly review is easier to audit than a label such as travel. Then apply the client's chart of accounts. The purpose explains the claim while the code organizes it.

Separate client-billable expenses from internal costs and record the client or project reference. A billable expense without a reference creates a delay at invoicing. Check the client's policy on mark-ups and reimbursable categories. The classification should match the contract, not the assistant's best guess.

Handle missing and duplicate receipts

For a missing receipt, ask for a bank or card record and a short written explanation before approving. The record shows the payment happened, while the explanation gives the purpose. Mark the claim as incomplete until both exist. Do not let a verbal reminder stand in for the document.

Check for duplicates by matching the date, the merchant, and the amount across the week and the prior week. A receipt photographed twice or a claim submitted in two systems can create a double payment. Record the duplicate and the resolution. The check takes a minute and prevents a correction that takes much longer.

Give the traveler a simple way to submit a receipt at the moment of purchase, such as a photo with the business purpose in the caption. A receipt that arrives a month later is harder to recall and easier to lose. Set the expectation that the photo is part of the purchase routine. The weekly review then becomes a confirmation rather than a hunt.

Route exceptions to a named approver

Name the person who can approve an out-of-policy expense and the limit of their authority. Send the exception with the receipt, the purpose, and the policy clause it departs from. The approver should see the whole case in one place. A chain of forwarded messages slows the decision and loses the evidence.

Set a response expectation for approvals and a fallback when the approver is away. An expense that waits two weeks for a signature often becomes a reimbursement complaint. Record the approval in the expense system rather than only in email. The system of record should show who approved and when.

File the week's evidence

File the matched receipts, the statement extract, the coding, and the approvals in one folder for the week. Use the client's naming convention and keep the files readable without the assistant. The folder should let a reviewer reconstruct the claim without asking for anything. That standard is what makes an audit quick.

Record the review date and the reviewer in a short log. Note the exceptions, the missing items, and the follow-up owner. Keep the log with the folder rather than in a personal inbox. A week that is fully documented is closed and should not need another pass.

Review the trend once a month

Once a month, count the missing receipts, the duplicates, and the late claims by category. Look for a pattern in one merchant, one card, or one traveler. A recurring gap usually points to a process or a tool rather than a careless person. Fix the cause before adding another approval step.

Ask the assistant which part of the routine takes the most time and which rule causes the most questions. A small change to the intake form or the cut-off can remove most of the rework. Test the change for a month and compare the counts. The routine should get shorter as the evidence improves.

Share the monthly count with the client in plain language and name the one change the team will make. A short, specific update is easier to act on than a long report. Ask the client to confirm any policy change before the next cycle. The review then closes with an agreed improvement rather than a list of complaints.