Health and family

Expense claim approvals for a small team without ERP, in dollars

A simple expense claim approval process for a small US team without ERP: claim form fields, approval limits, status tracking and a worked example in dollars.

Editorial illustration for Expense claim approvals for a small team without ERP, in dollars

You can run expense approvals for a small team without ERP software by fixing three things: what every claim must contain, who approves at which amount, and one status column that everyone can see. A shared spreadsheet and a short written rule are enough for a team of ten or fewer. Dollars are used below, and the numbers are made up.

What must every claim contain?

  1. Date of the expense.
  2. Name of the person claiming.
  3. Amount and currency.
  4. Category, from a fixed list.
  5. What it was for, in one line.
  6. A receipt, photo or file name.

If a claim lacks any of these, it goes back to the claimant without comment on the amount. That keeps arguments about the form separate from arguments about the spend.

How do I decide who approves what?

Write limits as amounts. For example: claims up to $250 are approved by the team lead; claims above $250 and up to $1,000 need the lead and one more person; anything above $1,000 is agreed before the money is spent. These numbers are illustrations; choose limits that fit your own team and put them in writing.

ClaimAmountApproverReason
Client lunch$86.40Team leadUnder $250
Conference ticket$640.00Lead and second approverBetween $250 and $1,000
New laptop$1,450.00Agreed in advanceAbove $1,000
Total in the month$2,176.40--

Check: 86.40 + 640.00 + 1,450.00 = $2,176.40.

What does the status column look like?

  • Submitted: received, not yet looked at.
  • Query: sent back for more information.
  • Approved: ready to pay.
  • Paid: with the date and how it was paid.
  • Rejected: with a one-line reason.

Add a date next to each status change. A formula such as =COUNTIF($H$2:$H$300,"Submitted") on a side cell tells you how many claims are waiting.

How do I stop email from running the show?

  1. Ask people to submit only through the sheet or a form, not by email.
  2. Pick one day each week for approvals and tell the team which one.
  3. Pay approved claims in one batch, so you reconcile once, not every day.
  4. Keep receipts in a shared folder named by month.

When does a sheet stop being enough?

When claims pile up, receipts get lost or approvals happen in chat threads, you will want a tool with a proper queue. Check whether it supports approval steps and limits before you commit. SpendixAI is built around India and INR, is not offered here as a US product and is not a team approvals tool, since Pro covers one personal workspace.

What do I do with rejected or late claims?

Keep rejected claims in the sheet with the reason in one line, so the same claim is not resubmitted a month later. For late claims, set a window, say sixty days from the expense, and say it in writing before it matters. Make the rule apply to everyone.

Exceptions are fine if the approver writes the reason in the sheet, but they should be rare and visible.

Close each month with a count: how many claims came in, how many were queried and how many were paid. If queries are over a fifth of claims, the form or the rule is unclear and needs fixing, not the people.

How do I pay approved claims cleanly?

Pay once a week or fortnight, in one batch, and mark each line Paid with the date. Reconcile the batch total against your bank statement: if approved claims for the week add up to $2,176.40, the payments out should add up to the same. When they do not, find the gap the same day, while the claims are still in front of you.

Before you start

  • Claim form fields agreed.
  • Approval limits written down.
  • Status list fixed.
  • Weekly approval day chosen.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports