An employee submits an expense, attaches a photo of a receipt and then waits. Finance cannot read the image clearly. The amount and category need correction. A manager approves the total but not the policy exception. The receipt is saved in one mailbox while the approved request lives somewhere else.
That gap between receipt and reimbursement is where expense processes become slow. Expense management for SharePoint and Microsoft 365 works best when every receipt, policy check and approval stays connected to the final reimbursement.
Why expense management needs a structured process
Where informal expense processes break down
Expense management touches the employee, manager, finance team and sometimes procurement or payroll. Each group may need different information, but the underlying request can remain the same.
- Multiple channels: receipts arrive in email, chat, shared drives and personal folders.
- Manual transcription: vendors, dates, amounts and categories are retyped from documents.
- Inconsistent policy: category limits and approval thresholds are applied differently.
- Limited visibility: employees do not know whether a claim is approved, paid or waiting for finance.
- Weak archives: finance must locate supporting documents across disconnected locations.
What a complete expense process should include
1. Create the right request
The employee chooses a template such as travel expenses, mileage or purchase reimbursement. The form collects the information needed for approval and reporting, while the expense table captures each line and receipt.
2. Capture actual expenses or allowances
Actual expenses use a manually entered amount with an attached receipt per row. Allowances use a configured rate and quantity, so the amount is calculated automatically. A template can support either approach or both.
3. Apply policy and approval rules
Expense categories can have compliance limits. Cost centres, vendors and departments keep reporting consistent. Automations can assign a request to finance when the total exceeds a threshold, block a policy violation or change a priority field.
4. Route the request to the correct reviewer
Approval paths can be sequential, parallel or mixed. For example, the line manager may approve every request, finance may review high amounts, and a department head may be required for selected categories.
5. Track reimbursement and preserve the record
The request lifecycle can distinguish between approved and paid. Finance sees which expenses are waiting for reimbursement. Successful document processing can export receipts to a standard SharePoint library, making the archive searchable and available to Microsoft 365 Copilot where licensed.
What changes when expenses are structured
A conference and hotel receipt
Before
The receipt is emailed to a manager with a short explanation. Finance asks for a clearer copy and the correct category. The employee retypes the vendor and amount, then checks again next week to see whether reimbursement has been processed.
After
The employee creates an expense request, attaches the receipt and confirms the extracted details. Policy and approval rules apply automatically. The status moves from approval to paid, and the searchable document stays connected to the request.
How Expenses Hub supports expense management in Microsoft 365
Expenses Hub is a SharePoint-hosted application available in SharePoint and Microsoft Teams. It combines request templates, expense tables, approval workflows, automations, budgets, categorisation, multi-currency support and reporting in the organisation's Microsoft 365 tenant.
- Configurable lifecycle: statuses from draft to approved and paid, with controlled transitions and permissions.
- Policy control: category limits, cost centres, departments, vendors and automatic rejection rules.
- Reimbursement tracking: checkbox or partial-amount reimbursement per row with a running total.
- Multi-currency support: automatic real-time exchange-rate conversion.
- Processing time measurement: understand how long requests take using working days and hours.
- Security and audit: role-based permissions and a full history of request changes.
Expense automation checklist
- Define templates for each reimbursement scenario.
- Agree expense categories and compliance limits.
- Set approval thresholds by amount, category or cost centre.
- Decide whether to use actual expenses, allowances or both.
- Configure reimbursement and payment statuses.
- Test receipts, exceptions, partial reimbursement and multi-currency entries.
Create a faster path from receipt to reimbursement
Expenses Hub brings the process into SharePoint and Microsoft Teams, where your team already works. Data remains in your Microsoft 365 tenant, and approval responsibilities stay visible.
Frequently asked questions
Does Expenses Hub require AI to process receipts?
No. AI document processing is optional. When enabled, it uses your own Azure Document Intelligence and Azure OpenAI resources to extract data and create searchable PDFs.
Can partial expenses be reimbursed?
Yes. Expense templates can use an Amount column for partial reimbursement while maintaining a running Amount to Reimburse total.
Can requests be blocked when they break policy?
Yes. Auto-rejection rules can prevent a request from being saved when configured conditions and messages detect a policy violation.
Can finance track reimbursement separately from approval?
Yes. The request lifecycle can include separate approved and paid statuses, with permissions and transitions configured for each.