Turn policy into rules
A policy that exists only as a document will be ignored. Express it as rules: categories, limits per category or per day, required receipts above a threshold, and restrictions on certain spending. Make the rules visible to employees as they enter the expense, with warnings instead of surprises at approval. Keep the policy short and consistent, and revise it when it clashes with real practice, because rules people routinely break need attention.
- Categories mapped to accounts and tax treatment.
- Limits and receipt thresholds stated clearly.
- Warnings at entry, not only at approval.
Capturing receipts and entry
The best time to capture an expense is when it happens. Mobile capture lets employees photograph receipts and attach them to draft expenses. Reduce typing through defaults, saved templates, and imported card transactions. The easier it is to submit as you go, the fewer end-of-month batches of forgotten items. Confirm with your accountants what receipt evidence is required in your jurisdictions.
Corporate cards and reconciliation
Corporate card transactions can be imported and matched to employee expense lines, which removes duplicate entry and helps detect personal spending. Define how unmatched transactions are chased and what happens when employees do not submit. Reconcile card statements to the ledger regularly, and set rules for lost receipts and disputed charges so cases are handled consistently.
Financial close automation →Mileage, per diems and travel
Mileage and per-diem allowances follow rates and rules that vary by place and tax authority. Store rates as maintained data with effective dates, and confirm the correct treatment with your advisors. Link travel expenses to trips or projects where useful, so costs can be billed to clients or analyzed by purpose. Foreign-currency expenses need rate handling that employees do not have to think about.
Approvals and audit
Route approvals to managers by default, with additional review for high-value or unusual items, and finance review for specific categories. Provide approvers with the information they need to decide quickly, including flagged policy exceptions. Audit a sample of approved reports regularly, and review patterns such as round-number claims or repeated items. Visible auditing deters misuse and reassures leadership.
NetSuite roles and security design →Reimbursement, project billing and reporting
Approved expenses should reimburse on a predictable schedule, ideally integrated with payables. For professional services firms, billable expenses flow to client invoices, so coding must be accurate at entry. Reports should show spend by employee, category, department, and project, along with policy exceptions and cycle times. Insights from this data often reveal opportunities, such as negotiating travel rates.
Revenue and billing solutions →Making it stick
Make the experience pleasant for employees, since they are the real users. Fast mobile entry, quick reimbursement, and clear explanations of rejections build goodwill and compliance. Share summary results with managers each quarter, such as the most common policy exceptions and the average time to reimburse, so the process improves over time. A short annual refresh of the policy keeps categories and limits aligned with how the organization actually travels and buys.
Decisions to settle before configuration starts
- Policy rules. Define categories, limits, and receipt thresholds.
- Card strategy. Decide whether corporate cards are imported and how matching works.
- Approval chain. Set approvers and escalation for exceptions.
- Billable expenses. Specify how client-billable items are coded and invoiced.
A realistic first 90 days
- Days 1 to 30. Review the policy, define categories and accounts, and decide on the card approach.
- Days 31 to 60. Configure rules, approvals, and mobile capture, and test with a pilot group.
- Days 61 to 90. Roll out to all employees, connect reimbursement, and publish the first exception and cycle-time reports.
Pitfalls to avoid
- A policy nobody reads. Build rules into entry screens.
- Batching at month end. Capture on the day to prevent lost receipts.
- Rubber-stamp approvals. Show exceptions to approvers and audit samples.
- Poor coding. Wrong categories distort reporting and client billing.
