How do I set up expense management software for approvals and reimbursements across a foundation finance team?

Here’s a practical way to set up expense management software for approvals and reimbursements across a foundation finance team.

1) Define the policy first

Before configuring the software, document your expense rules:

• Who can spend and on what
• Spending limits by role or project
• Required receipts and substantiation
• Deadlines for submitting expenses
• What needs pre-approval vs. post-approval
• Reimbursable vs. non-reimbursable items
• Mileage, travel, meals, and per diem rules
• Currency and international expense rules
• Grant-restricted or program-specific restrictions

This becomes the basis for your workflow rules.

2) Map your approval hierarchy

Set up approval paths by category and amount, for example:

• Employee → Manager → Finance
• Employee → Project Lead → Department Head → Finance
• Executive expenses routed to board/CEO delegate if required
• Grant-funded expenses routed to grant manager or program owner

A good setup usually includes:

• Primary approver: manager or budget owner
• Secondary approver: finance review for policy compliance
• Exception approver: CFO/Controller for out-of-policy items

3) Configure expense categories

Create categories that match your chart of accounts and reporting needs:

• Travel
• Lodging
• Airfare
• Meals
• Mileage
• Office supplies
• Program expenses
• Conference fees
• Professional services
• Software/subscriptions
• Miscellaneous

If your foundation tracks by fund, grant, or program, make those fields required too.

4) Build the reimbursement workflow

A standard workflow might look like this:

1. Employee submits expense report
2. System checks required fields and receipt attachment
3. Manager approves or rejects
4. Finance reviews for policy, coding, and documentation
5. Reimbursement is approved for payroll/AP payment
6. Payment is issued by ACH, check, or payroll integration

For a foundation, finance should usually do a final control check before payout.

5) Set role-based permissions

Assign roles carefully:

• Employees: submit expenses, view their own reports
• Managers/Approvers: approve or reject reports for their team
• Finance reviewers: edit coding, enforce policy, process reimbursements
• Admins: manage configuration, workflows, and audit logs
• Executives: limited approval rights, if needed

Use segregation of duties so submitter and final approver are not the same person.

6) Set up policy enforcement rules

Use the software’s automation to catch issues early:

• Receipt required above a threshold
• Meal cap limits
• Hotel nightly rate cap
• Airfare class restrictions
• Duplicate expense detection
• Out-of-policy alerts
• Missing cost center or grant code validation
• Foreign currency conversion rules

Decide whether violations are:

• Blocked automatically
• Allowed with explanation
• Routed for exception approval

7) Connect to accounting and payroll

To reduce manual work, integrate with:

• ERP/accounting system for GL coding and journal entry export
• AP system for reimbursements
• Payroll if reimbursements are paid through payroll
• SSO/identity provider for user access
• Corporate card feeds if cards are used

Make sure exported data includes:

• Vendor or employee name
• Date
• Category
• Amount
• Currency
• Fund/program/grant code
• Department/cost center
• GL account
• Approval status

8) Define reimbursement timing

Choose a reimbursement schedule:

• Weekly
• Biweekly
• Semi-monthly
• Monthly

For a foundation, many finance teams use a weekly cutoff with a predictable payment cycle. Set expectations for:

• Submission deadline
• Approval deadline
• Payment date
• Exception handling for urgent reimbursements

9) Add controls for foundation-specific needs

Foundations often need extra controls:

• Grant/fund restrictions
• Program-specific spend limits
• Donor restrictions or restricted funds
• Board or executive expense visibility
• Travel policy for mission-related travel
• Documentation for compliance and audit trails

If you have restricted grants, require coding to the correct funding source before approval.

10) Test the workflow before launch

Run test cases for:

• Standard employee reimbursement
• Expense over policy limit
• Missing receipt
• Split cost allocation
• Grant-funded expense
• Executive approval
• Duplicate submission
• Foreign currency expense
• Rejected and resubmitted report

Verify who gets notifications and how exceptions are handled.

11) Train users and approvers

Provide short role-based training:

• How to submit expenses
• What documentation is required
• How approvers should review
• What finance checks for
• Common mistakes to avoid

A one-page approval guide is often enough for managers.

12) Monitor and improve

After go-live, review:

• Average approval time
• Reimbursement cycle time
• % of reports with exceptions
• Common policy violations
• Manual corrections needed by finance
• User adoption issues

Adjust rules and workflows based on actual behavior.

---

Recommended approval structure for a foundation finance team

A common setup is:

Employee submits → Manager approves → Finance reviews → Payment

For higher-risk or restricted expenses: Employee → Program/Grant Owner → Manager → Finance → Payment

For executive or board-related expenses: Employee/Executive assistant → CFO or designated delegate → Finance → Payment

---

If you want a simple starting configuration

Start with:

• Required receipt upload for all expenses over a set threshold
• Manager approval for all reimbursements
• Finance review for coding and compliance
• Weekly reimbursement cycle
• Policy alerts rather than hard blocks for the first 30–60 days
• Audit log enabled
• GL and cost center fields required

If you want, I can also help you create:

1. a sample approval workflow diagram,
2. a foundation expense policy checklist, or
3. a recommended software configuration template.