Replacing Excel for Expense Claims in Charities

Charities organisations may use Excel for expense claims because it is quick to adapt and can hold the information the team needs without waiting for a new software project. In this setting, teams often balance programme delivery, fundraising, volunteers, administration and reporting with limited appetite for heavy software overhead.

That flexibility is useful, but the spreadsheet can gradually become more than a file. It may start coordinating employee or contractor expenses that need receipts, coding, review and a clear reimbursement status. At the same time, fundraising, finance and programme tools may cover some standard needs while Excel remains the flexible bridge for organisation-specific processes.

This guide is about recognising that point and choosing the proportionate next step. The answer may be a better workbook, an existing software product, an extension to a system already in use, or a custom app built around the actual workflow.

How expense claims is usually handled in Excel

Expense spreadsheets usually contain claimant, date, category, description, amount, tax or coding information and a total, while receipts are attached separately. Typical information can include claimant, expense date, category, description, amount, receipt and approval status.

In charities, the workbook often sits inside a wider process rather than operating on its own. work may happen across offices, community locations, events and remote settings. Small teams can still have complex handoffs when one person covers several responsibilities and information arrives from many sources.

That surrounding work matters because a spreadsheet may be perfectly capable of storing the rows while still being a poor place to coordinate every decision, hand-off and update.

Where the spreadsheet starts to break down

The useful question is not whether Excel can technically hold more data. It is whether the team is doing increasing amounts of manual coordination around the workbook.

Common failure points for expense claims include:

• receipts are separated from the line they support
• claims arrive in different spreadsheet versions
• policy checks are manual and inconsistent
• approvers review totals without enough line-level context
• finance consolidates approved claims by hand

The sector adds its own practical pressure. Forms, supporting documents, programme notes, approvals or funding-related records may need to stay with the underlying work item. Management may need views by programme, fund, owner, activity, location or status.

Signs you have outgrown Excel

A spreadsheet is more likely to be acting as an operational system when several of these are true:

• claimants email spreadsheets and receipt bundles separately
• finance repeatedly asks for missing evidence
• approval is recorded in email
• old templates keep circulating
• reimbursement status is not visible to the claimant
• one person has become the keeper of the workbook and the rules around it
• staff maintain side lists, emails or messages because the spreadsheet does not cover the whole workflow

These are not arbitrary limits. A workbook with many rows can be completely manageable, while a smaller file can be difficult if it has to coordinate several people, permissions, decisions and external systems.

When Excel is still suitable

Excel may still suit a small organisation with infrequent claims, a single reviewer and straightforward reimbursement handling.

It is also worth improving the workbook before replacing it if the main problem is inconsistent structure. Controlled lists, clearer ownership fields, protected calculations, better naming and a single shared location can remove a surprising amount of friction.

Excel can remain valuable after part of the workflow moves into an app. Teams may still use it for flexible analysis, modelling, ad-hoc reporting or data exports where a grid and formulas are the right tool.

What a better workflow could look like

A replacement should not copy the spreadsheet cell by cell. It should make the real route through expense claims clear and give each person the information and actions they need.

1. Capture each expense with its evidence

Keep the date, category, amount, description and receipt together from the start. For charities, this should reflect that teams often balance programme delivery, fundraising, volunteers, administration and reporting with limited appetite for heavy software overhead.

2. Check the claim before submission

Prompt for missing fields or evidence while the claimant can still correct the entry. The design should make sense for programme staff, fundraisers, administrators, volunteers, finance teams and managers, rather than assuming one office-based owner.

3. Submit the claim for approval

Create a clear submitted version so the reviewer knows which lines form the claim. This is especially useful where small teams can still have complex handoffs when one person covers several responsibilities and information arrives from many sources.

4. Approve or return specific items

Record queries and decisions against the relevant expense rather than exchanging corrected spreadsheets. Where evidence is part of expense claims, forms, supporting documents, programme notes, approvals or funding-related records may need to stay with the underlying work item.

5. Hand approved claims to finance

Provide a consistent approved output for reimbursement or accounting without rebuilding totals manually. The resulting data should support the views people actually need: management may need views by programme, fund, owner, activity, location or status.

What is different about expense claims in charities

For expense claims in charities, the important design problem is to collect complete claims and receipts, apply policy and approval rules, and prepare approved data for finance or payroll. In this sector, small teams often coordinate staff, volunteers, beneficiaries, programmes and restricted resources with lighter systems and a high reliance on adaptable spreadsheets. That means the app cannot be designed from spreadsheet columns alone. It has to fit programme staff, volunteers, operations teams, managers and finance staff, because the replacement should reduce coordination overhead without introducing a platform that is harder to maintain than the spreadsheet it replaces. A common failure pattern is that receipts are separated from claims, coding is inconsistent and returned claims lose the reason for correction.

Failure patterns specific to this setup

• The replacement still fails if it does not keep claimant, expense type, date, amount, coding, evidence, approver and decision together while preserving the sector context needed for programme, responsible person, funding or project context, approval, evidence and next action
• The replacement still fails if it does not test the workflow with programme staff, volunteers, operations teams, managers and finance staff rather than assuming the person who maintains the spreadsheet represents every user
• The replacement still fails if it does not make the live status and hand-off explicit so expense claims does not continue in email, messages or a second spreadsheet after the app is introduced
• The replacement still fails if it does not confirm the interface reflects the operating reality that the replacement should reduce coordination overhead without introducing a platform that is harder to maintain than the spreadsheet it replaces

Practical details to design around

• Keep claimant, expense type, date, amount, coding, evidence, approver and decision together while preserving the sector context needed for programme, responsible person, funding or project context, approval, evidence and next action.
• Test the workflow with programme staff, volunteers, operations teams, managers and finance staff rather than assuming the person who maintains the spreadsheet represents every user.
• Make the live status and hand-off explicit so expense claims does not continue in email, messages or a second spreadsheet after the app is introduced.
• Confirm the interface reflects the operating reality that the replacement should reduce coordination overhead without introducing a platform that is harder to maintain than the spreadsheet it replaces.

Where the system boundary should sit

For expense claims in charities, CRM, donor, finance, case-management and volunteer systems should remain authoritative where they already own core records. reimbursement, posting and payroll calculations should remain in finance or payroll systems unless there is a clear reason otherwise. The replacement should own the awkward workflow gap and the decisions around it, while referencing trusted identifiers from those systems instead of creating another master-data source.

Approval design lens

For expense claims in charities, the difficult part is rarely storing the rows. It is deciding who can submit, what information makes a request complete, who has authority to decide, what happens when something changes, and which approved data moves onward. A useful replacement should make those decisions visible rather than hiding them in email.

What good looks like

• Employees can submit a complete claim with the evidence required.
• Policy checks and approver ownership are visible before finance receives the claim.
• Returned claims keep the reason and correction history.
• Approved claims can be exported or handed off without rekeying the same details.

The process should also pass the combination-specific proof points below:

• Prove with real charities examples that a standard claim and a returned claim both reach finance with complete evidence and no duplicate entry.
• Confirm programme staff, volunteers, operations teams, managers and finance staff can complete their part without maintaining a parallel spreadsheet or private side list.
• Verify identifiers and downstream hand-offs respect the agreed system boundary rather than duplicating records owned elsewhere.
• Review exceptions from the pilot and add only those that occur often enough to justify product logic.

Questions to answer before replacing the spreadsheet

• Which expense rules actually require validation?
• What evidence is mandatory for each claim type?
• Who approves and when does project or department coding matter?
• What does finance need from an approved claim?

These questions should be answered with the real workbook, users and surrounding systems in front of you. They are more useful than choosing software from a feature list before the awkward parts of the workflow are understood.

A more specific hypothetical scenario

Consider a charities team where receipts are separated from claims, coding is inconsistent and returned claims lose the reason for correction. A focused replacement is introduced for expense claims. programme staff, volunteers, operations teams, managers and finance staff work from one current record containing claimant, expense type, date, amount, coding, evidence, approver and decision, with the relevant programme, responsible person, funding or project context, approval, evidence and next action. The first release is considered useful only when a standard claim and a returned claim both reach finance with complete evidence and no duplicate entry. This is a hypothetical example, not a customer case study.

This scenario is illustrative and is not a customer case study.

What not to build

• Do not replicate accounting posting or reimbursement logic unless it genuinely belongs in the workflow.
• Do not collect sensitive information that finance does not need.
• Do not automate edge-case policy decisions that still need human judgement.
• Do not duplicate a function already handled well by an existing system merely to make the new app look more complete.
• Do not move every old spreadsheet column into the new system unless it has a clear operational purpose.

Comparing the realistic replacement options

The cheapest-looking option is not always the lowest-cost operating model. Compare the amount of coordination, configuration, duplicated entry and compromise each option leaves behind.

Option	Why it can look attractive	The tradeoff to examine
Keep or improve Excel	Familiar, flexible and already paid for	Excel is cheap and flexible, but receipts, policy checks, approval and finance hand-off often live outside the file.
Buy an off-the-shelf product	Established product and a defined implementation route	Expense platforms are a strong default for standard policies and card-led workflows. They may be excessive or inflexible for a small bespoke process with unusual coding or approval rules.
Extend an existing core system	Keeps more data inside a platform the business already uses	Accounting or payroll products may already accept expenses, but their employee-facing workflow may not fit the way claims are gathered and reviewed.
Build a custom app	Designed around the workflow the business actually follows	A focused app can match the organisation’s actual claim types, coding and approvals without introducing a broader expense platform than the team needs.

For expense claims in charities, the system boundary matters particularly strongly. For expense claims in charities, CRM, donor, finance, case-management and volunteer systems should remain authoritative where they already own core records. reimbursement, posting and payroll calculations should remain in finance or payroll systems unless there is a clear reason otherwise. The replacement should own the awkward workflow gap and the decisions around it, while referencing trusted identifiers from those systems instead of creating another master-data source.

A specialist product or existing module is still the right answer when the workflow genuinely fits it. The custom-app case becomes stronger when the spreadsheet exists precisely because the surrounding software cannot represent the organisation's rules, calculations, approvals, hand-offs, evidence or reporting without workarounds. In that situation, buying another generic product can leave the business paying for software while Excel continues beside it.

The Spreadsheet Assessment is the lower-commitment way to test that fit before agreeing a build. The recommendation can still be to keep Excel or use existing software if that is genuinely the better route, but the assessment is designed to identify whether the spreadsheet is filling a business-specific gap that deserves its own app.

What to include in a replacement system

A sensible first version should concentrate on the parts of expense claims that people use repeatedly. Useful capabilities may include:

• line-level expense entry
• receipt attachment
• controlled categories
• submission state
• approval and return
• claim totals
• approved export

For charities, the design should also account for the way work is actually performed. Work may happen across offices, community locations, events and remote settings. Access and screen design should reflect programme staff, fundraisers, administrators, volunteers, finance teams and managers rather than assuming every user needs the same view.

Features should earn their place. If a rare exception can remain manual without creating risk or confusion, it may be better to leave it out of the first release and keep the core workflow simple.

Hypothetical example

Consider a hypothetical charity managing several programmes with a small central administration team where claimants send a spreadsheet and a set of receipt files to a manager before finance combines approved claims. The spreadsheet is useful because it fills a gap, but staff have to keep the file synchronised with the work happening around it.

A replacement could change that flow so claim lines, receipts, approval and reimbursement status can stay connected throughout the process. The exact screens and rules would depend on the organisation, but the important shift is that the record becomes part of the workflow rather than a document someone has to update after the workflow has happened.

This is an illustrative scenario, not a customer case study and not a claim about a particular organisation.

Migration checklist

Before replacing the spreadsheet, work through the details that make the current process function:

• keep only open claims in the new workflow unless history is genuinely useful
• agree expense categories and coding
• test missing-receipt and correction paths
• reconcile the first approved export
• retire old templates after cut-over
• map the people and hand-offs involved in charities
• identify information that already comes from another system and should not be re-entered unnecessarily
• preserve important calculations and business rules with representative test cases
• decide what old data genuinely needs to move and what can remain archived
• agree a clear cut-over point so the spreadsheet and app do not become competing operational records

The Spreadsheet Assessment is designed to work through this kind of detail before a build is agreed. It looks at the spreadsheet together with the process around it so the recommendation can distinguish between what should stay, what should change and what a first useful version would need.