Replace Expense Spreadsheets with a Reviewable Process

The approach

The first step is not choosing a new form. Identify what the spreadsheet currently records, who supplies each field, and how a request becomes an approved and reconciled expense. A replacement process should keep receipts and business purpose with each transaction, make exceptions visible, and give finance a traceable outcome. This is an operating-model guide, not a claim that one product automatically performs every step.

A practical process

Map the current handoffs

Take a recent reporting period and trace five ordinary expenses plus two exceptions. Note who enters the amount, who checks the receipt, who decides the cost center, who approves payment, and who posts the final amount. Identify the exact columns and attachments needed for accounting, including dates, vendors, currency, business purpose, and project or department. Keep the original records until the new process is reconciled.

Define one complete expense record

Specify the fields and evidence required for each type of spend rather than collecting every possible field on every submission. A corporate-card transaction, employee reimbursement, and cash advance have different reconciliation paths. Attach supporting documents to the relevant item and state how a missing receipt or ambiguous business purpose is handled. A reviewer should not have to reconstruct context from an email thread.

Assign decisions and exception paths

Separate the employee's submission, the manager's policy decision, and finance's accounting review. Decide which situations need a second reviewer—for example, a requester approving their own expense, a duplicate-looking charge, or a change in project coding. Document who can correct a record after approval and whether the change requires renewed review. This prevents an apparently complete spreadsheet from hiding unresolved decisions.

Pilot and reconcile before retiring the sheet

Run a small real period through the proposed workflow in parallel with existing controls. Compare submitted totals, reimbursements, card statements, and general-ledger entries. Investigate differences by transaction, not by adjusting a grand total until it matches. Save the decisions and update the instructions before rolling the process out to more teams. Retire the spreadsheet only after finance can retrieve the evidence and reproduce the close.

Worked example

A field team submits mileage, vendor purchases, and two company-card charges in one week. Under the old method, a manager marks a spreadsheet row approved while the missing mileage route sits in an email. In the new process, the mileage record stays open with a named owner; the card charges are matched to their statement entries; and the vendor purchase retains its receipt and project code. Finance reconciles each path separately before posting, so the approved total does not conceal the unresolved mileage claim.

What to avoid

• Do not import an unreviewed spreadsheet and treat the migrated rows as approved evidence.
• Do not use one approval status to mean both policy approval and accounting reconciliation.
• Do not discard attachments or correction history when changing systems.

Related resources

• Expense management guide
• Expense approval workflows
• How to organize business receipts
• Month-end expense reconciliation