Expense management in Project Operations

For services businesses, employee expenses on customer engagements are both a billing input and an operational cost — they need capture, policy enforcement, reimbursement, and project posting all coordinated. Expense management in Project Operations covers the cycle.

The expense report. A submitter creates an expense report holding multiple expense lines for a date range or project context. Each line has:

• Date — when the expense occurred.
• Category — Travel, Meals, Lodging, Equipment, Mileage, Other.
• Amount and currency — the expense itself, with currency.
• Description — narrative.
• Project / task / customer — the billing context.
• Billable flag — should this be billed to the customer? Defaulted from policy, can be overridden.
• Receipt attachment — image or PDF of the receipt.
• Merchant — the vendor name (often extracted automatically from receipt OCR).

Expense categories and policies. Expense categories map to GL accounts for accounting. Each category carries policy rules:

• Per-diem limits — daily caps per category (e.g. €40 lunch).
• Pre-approval requirements — certain categories need approval before incurring (large equipment).
• Documentation requirements — receipts mandatory above threshold.
• Allowed billable status — some categories never billable to customers (e.g. private travel).

Submitting an out-of-policy expense triggers an exception flag for approver attention.

Receipt OCR and AI Builder. A modern pattern: take a photo of the receipt with the mobile app, AI Builder's receipt-reading model extracts merchant, date, amount, line items, and auto-populates the expense line. The submitter reviews, adjusts, and submits.

Approval workflow. Submitted expense reports route through approval:

1. Direct manager — first reviewer.
2. Project manager — for project-billable expenses.
3. Finance — for high-value or out-of-policy expenses.

Approval can be parallel or sequential per the configured policy. Each step records the approver, timestamp, comments.

Mileage. A specific category for travel by personal vehicle, calculated as kilometres × rate. Configurable rates per country, per period. Integrated with GPS-tracked mileage capture in the mobile app — the journey from customer A to customer B logs automatically.

Credit cards. Corporate credit card statements can import into Project Operations, with each transaction either auto-matched to a submitted expense or flagged for the submitter to attach a receipt and categorise.

Billing integration. Approved expenses marked billable flow into the project's billable plan. The next project invoice run can include billable expenses, either as separate line items or aggregated into a single "expenses" line, configurable per contract.

Reimbursement integration. Approved expenses generate payables to the employee — either through HR / payroll for direct reimbursement, or through AP as a vendor invoice. The integration with the customer's payroll or AP system handles the actual payment.

Reporting.

• Expense by project, by customer, by category — for project profitability.
• Per-employee expense trends — for compliance and cost control.
• Policy violations — frequent out-of-policy patterns.
• Pending approval ageing — to keep approvals moving.

Common pitfalls.

• No receipt discipline — submissions with missing receipts complicate audit. Configure receipts as required.
• Wrong project context — expenses posted to wrong project hide true profitability. Train staff.
• Slow approval cycle — expenses pending approval for weeks demoralise submitters and complicate cash flow. Set service-level expectations on approvers.
• Billable / non-billable defaults wrong — over-billing customers or under-billing your own organisation. Verify policies.

Limits. Sophisticated corporate-card programs with complex feeds, multi-card reconciliation, and audit-grade compliance may layer specialist tools like Concur, Coupa, or Expensify integrated with Project Operations. For mainstream services businesses, the built-in expense management is sufficient.