Learning how to control expense reimbursements starts with one habit: review every claim once a month, against a written policy, before money leaves the bank. Done well, payments match what the business agreed to pay, the books close on time, and cash does not surprise you at quarter end. Skipping the review lets small errors pile up.

Why reimbursement claims pile up when no one reviews them

Reimbursements look harmless because each one is small. A team lunch here, a train ticket there, a software subscription paid on a personal card. Nobody sees the total until the month-end close, and by then the claims are approved, paid and sitting in the ledger with little context. A monthly review closes that gap.

The usual pattern is simple. An employee pays out of pocket, sends a photo of a receipt, and a manager approves it from a phone. Finance processes the payment on the next run. Nobody checks whether the expense fits policy, whether the project code is right, or whether the same receipt went in twice. The approval happened, so the process feels finished.

Start here: pull last month's paid reimbursements and sort them by employee and category. Look for three things: claims above what the policy allows, claims without an itemized receipt, and claims coded to the wrong account. For many owners, this first pull is the moment they see that the problem is not one bad expense. The problem is that nobody takes a second look.

Drift also comes from timing. A claim submitted two months late lands in a month with a different budget, so the expense shows up as a surprise. Late claims are harder to verify because the receipt has faded, the trip is forgotten and the business reason is fuzzy. A firm monthly submission deadline does more to fix this than any dollar limit.

There is a cash side too. Reimbursements leave the bank in lumps, often on payroll or on an extra payment run. If nobody tracks them in the forecast, the cash balance looks healthier than it is for a few weeks, then drops. Owners who review claims every month can see the lump coming and plan for it.

Write the reimbursement policy before approving any receipt

The policy is the yardstick for every review. Without one, the monthly review turns into a debate about each claim, and the person with the most seniority wins. Write the policy in plain language: what the company reimburses, who approves, what documents are required and how quickly claims must be submitted. Keep it short enough that employees will actually read it.

Cover the basics in writing:

Eligible categories, such as travel, client meals, software, supplies and training Approval limits by role, so routine items do not wait on the CEO Receipt standard: itemized, dated and showing the amount paid Submission deadline, with a rule for late claims How personal expenses are handled, including trips that mix business and personal days Rules for alcohol, gifts and anything else that needs extra scrutiny

The IRS expects most reimbursements to run under an accountable plan, which generally requires a business connection, substantiation of the expense, and return of any advance or excess within a reasonable period. A plan that meets these rules keeps reimbursements out of taxable wages. A plan that does not can turn reimbursements into income for the employee, which becomes a payroll problem as well as a bookkeeping one. Ask your accountant to confirm that your plan fits the rules.

Make the policy fit the people who submit claims. A sales lead who travels every week needs different rules than an office manager who buys supplies twice a year. For most small teams, two or three approval tiers are enough. A hypothetical company with a handful of managers might let department heads approve routine meals, while travel above a limit you set goes to the owner.

Date the policy and log every change with its reason. When a claim is disputed during the review, the version in force on the date of the spending decides the outcome. Without a dated version, every disagreement becomes a contest of memory, and the person who remembers best wins.

Set a monthly review calendar with clear owners

The review only works on a fixed calendar. Pick a submission deadline, a review date and a payment date, and keep them the same every month. A common pattern is to close submissions a few business days before the month-end close, review in the first week after close, and pay on the next scheduled run. The calendar gives everyone a date to plan around.

Assign owners by role. One person submits, one approves, one reviews and one releases the payment. In a small team, the reviewer and the payer can be the same person only if a second person checks the batch before it goes out. This is segregation of duties, a basic internal control that matters even in a company with only a few people on finance tasks.

Write the calendar as a checklist with owners and dates, and keep it on a shared page where each step can be marked complete. The calendar also tells the CEO when to expect the review summary, so the question "where are my claims?" stops appearing in chat every few days. Predictable timing reduces the number of follow-up messages more than any reminder does.

Who runs the review depends on the stage of the company. Owners of very small companies often do it themselves, at least at first. A bookkeeper can prepare the batch. A controller or a fractional CFO can own the review and the exceptions. What matters is that one named person signs off on each month's batch, so nobody is left wondering who is responsible.

Build in a rule for late claims. A claim that arrives after the deadline moves to the next month unless the manager explains the delay in writing and the reviewer approves it. This keeps the monthly picture clean without punishing the whole team for one missed deadline, and it gives people a reason to submit on time.

Check each claim against the policy, the receipt and the budget

The monthly routine is the same every time. Work through the batch in the same order, so the review takes less time each month and misses fewer problems.

Confirm the employee and the manager match the approval chain. Check that the receipt is itemized, dated and shows the amount paid. Confirm the category is allowed under the policy and the amount is within the limit. Look for duplicates by comparing merchant, date and amount across the batch and recent months. Match the business purpose to the project, client or department code. Compare the monthly total by category with the budget. Mark exceptions and send them back before payment is released.

Duplicates are the error that most often slips through. The same purchase gets submitted once as a receipt photo and once as a card statement line. Compare the merchant name, the date and the amount, not only the receipt number, because many systems generate different reference numbers for the same purchase. A duplicate caught before payment is a five-minute fix. After payment, it becomes a recovery task.

The budget check adds context. If travel for one team doubles compared with the prior month, dahengsi.com each claim might be valid while the trend is not. Flag the pattern for the manager instead of rejecting claims one by one. A review that only asks yes or no misses the story behind the numbers, Boston and that story is often what the CEO needs to hear.

For any claim above the threshold you set, require a one-sentence business reason. For any meal with a client or prospect, record who attended and why. Auditors and lenders ask for this later, and rebuilding it from memory a year on rarely works. A dinner with three people and no note is the kind of claim that turns into a dispute at year end.

Keep exceptions in a log: the claim, the issue, the decision and the date. Recurring problems from the same employee or vendor become a training point. A short note each month about the two most common errors does more good than a long policy memo nobody reads. Fix those two first, then add more checks once the team is consistent.

Compare reimbursements with company cards, budgets and cash

Reimbursements are one of several ways money leaves the business, and the review should sit next to the others. Company cards, direct vendor payments and reimbursements each carry different controls and different timing. The table below compares them so you can see where each kind of spending belongs in your process.

MethodWho pays up frontTypical controlWhere it shows in the cash forecast

Out-of-pocket reimbursementEmployeeReceipt and policy review before paymentIn the next payment run, often in a lump Company cardCompanyCard limits and monthly statement reviewWhen the card statement is paid Direct vendor paymentCompanyVendor approval and invoice matchingOn the invoice due date

Reimbursements are often the least visible of the three because they arrive as small amounts with no vendor on record. That is why the cash forecast should include a line for them. Base the line on recent months, then adjust for known events such as a trade show, a team offsite or a conference. The forecast is about the timing of cash, not only the size of the expense.

Card programs are where many small companies lose track. Employees spend on company cards, and reimbursements cover what the cards do not. If the same category runs through both, the monthly review should compare card statements with reimbursements to catch double counting. Pull both lists into one working sheet so the reviewer sees the full picture in one place.

Budget variance is the other link. When reimbursements sit outside the budget, a team can overspend without anyone deciding to. Put reimbursement categories into the budget with a monthly actual column, so the variance sits next to other costs. Planning tools such as Adaptive Insights can handle this once it is set up, and a well-built spreadsheet works for a small company.

For cash, the question is simple: after this month's payment run, how much cash is left, and what do the next three months look like? If that answer shifts because reimbursements jumped, the review has done its job. It shows the change before the bank statement does.

Adjust the review for startups, nonprofits, life sciences and agencies

The core method stays the same across segments, but the rules around it change. Startups, nonprofits, life sciences companies and agencies each have spending patterns that a generic policy misses. Founders in these segments ask similar questions, so the review should answer them directly rather than leave each team to work them out alone.

Startups often spend on founder cards, with reimbursements filling the gaps. At this stage, burn rate usually matters more than the fine details of the policy. Review reimbursements next to the monthly cash forecast, and confirm that founder expenses are not mixed with personal spending. If you plan to raise capital, investors will ask for clean expense records during due diligence, so the habit pays off twice.

Nonprofits that receive federal awards must follow the Uniform Guidance in 2 CFR 200, do i need a part-time CFO in Massachusetts which sets cost principles, including rules for travel. A meal or an airline upgrade may be allowable under one funder's terms and not another's. Tag each claim with its funding source during the monthly review, not at year end, when the records are harder to reconstruct and the cost may already be charged to the wrong grant.

Life sciences companies travel often to conferences, site visits and collaboration meetings, and claims frequently mix personal and business days. Require a short purpose note for each trip and separate any personal extension from the claim. Where sponsored research rules apply, the classification work looks like the nonprofit case: assign each cost to the right project before it is paid, not after.

Agencies face a specific question with client-rebillable expenses. A reimbursement may be recovered from a client or absorbed as overhead, and that choice affects revenue. Under ASC 606, whether a rebilled cost is presented as revenue or as a pass-through depends on a principal and agent analysis, which your accountant should document. Mark each claim as billable or non-billable during the review, so the choice is made once, in the right place.

Choose tools that support the review and know when spreadsheets stop working

You can run a solid review in a spreadsheet for a while. The question is when the spreadsheet starts costing more time than a system would. Warning signs include monthly batches with dozens of claims, several approvers working at the same time and a steady stream of duplicate or missing receipts. When those show up together, the manual process is the bottleneck.

Expense modules in accounting platforms such as QuickBooks, NetSuite and Sage Intacct can route approvals, store receipt images and map claims to accounts and projects. Before you choose one, check how it handles approval tiers, duplicate detection and audit trails. Features differ by product and by plan, so confirm details against the current vendor documentation rather than a summary from a salesperson.

Set a few rules when you configure any tool. Map each expense category to one account. Require a receipt attachment for every claim. Turn on approval steps that match your policy tiers. Export a monthly report that shows approved, rejected and paid claims, so the review has one place to start. These rules matter more than the brand, because a poorly configured system just makes mistakes faster.

A tool does not replace the review. It speeds up the checks. Someone still has to decide whether a dinner was a business dinner, whether a project code is correct and whether the amount fits the budget. Many small teams automate the routing and keep the exception review manual, and that split is a reasonable starting point.

Spreadsheets still work well for reconciliation. Export the paid batch, match it to bank transactions and card statements, and mark each difference. Keep the file in a shared folder with version history, so the reviewer can see who changed what. For teams not yet ready for a full module, one reconciliation sheet each month is often enough to keep the process honest.

Decide who owns the monthly review: owner, controller or fractional CFO

Who runs the review changes as the company grows. Founders often start by doing it themselves. As volume increases, a bookkeeper may take over the batch work. A controller owns the close and the internal controls. An accountant advises on tax treatment. A fractional CFO sets the review standard and reads the results for the cash and budget picture. Each role has a different scope.

The table below shows how the roles compare for this task.

RoleMain focus in the reimbursement reviewWhat it usually does not cover

BookkeeperRecords approved claims, codes them and reconciles them to the bankPolicy design and tax judgments ControllerOwns the close, the internal controls and exception sign-offLong-range forecasting and financing decisions AccountantTax treatment and accountable plan requirementsDaily batch handling and approvals Fractional CFOSets the policy and review cadence and links results to cash and budgetDay-to-day claim processing

A fractional CFO fits when the review raises questions about cash, budget or spending decisions, not just about errors. For example, the team may ask why reimbursements rose, and the answer may change hiring plans. Or a lender may ask for a clean expense history before renewing a credit line. A fractional arrangement brings senior input on a set schedule, which suits a company that needs guidance but is not ready for a full-time executive.

A fractional CFO should not replace the people who process claims. The CFO should not be the only approver, and should not do the bookkeeping unless the scope says so in writing. In the first conversation, ask who approves, who pays and who reviews, and write those answers into the calendar. Clear lines prevent the review from becoming one person's private job.

The question of when to move to a full-time CFO is separate. If the monthly review grows into weekly work across several functions, or the company needs a finance leader involved in daily decisions, the role may need to become full time. Watch for the moment when the review keeps surfacing decisions that no part-time arrangement can carry, because that is the signal the structure has outgrown the model.

The costliest mistake is paying claims nobody reviewed, and how to prevent it

The most costly mistake is paying claims that no one checked after the first approval. The manager approved the claim, the payment went out, and the review never happened. Over a year, the gaps add up to policy violations, tax exposure, cash surprises and a messy file for an audit or due diligence. It is rarely one big error. It is a steady pattern that nobody sees until someone asks for the records.

Prevent it by making the second look mandatory before payment. No batch is released until a named reviewer signs off on the list, the exception log and the cash impact. Build the sign-off into the payment step of your system, or add a checkbox to the spreadsheet that must be ticked before the bank file is created. The control works only when it blocks the payment, not when it sits in a folder.

Keep the review on the calendar even in quiet months. A month with few claims is when the habit is easiest to skip, and then the next busy month arrives unreviewed. A short check still counts, and it keeps the routine familiar for the person doing it. Consistency beats intensity here.

Report the results to the leader every month. Send a short note with the total paid, the top categories, the open exceptions and one change you recommend. When the CEO sees the number and the trend, the policy stops being a suggestion. Start with the next batch, not with a perfect system, and improve the process one exception at a time.

Knowing how to control expense reimbursements is less about strict rules than about the second look. Most claims are honest and simple. The goal is to make the rules easy to follow and the approvals easy to trust, so the business can see its spending before the bank does.