Expense policy: rules enforced at creation, not explained after approval

A policy written in a PDF on the intranet gets broken without anyone noticing. 4expenses turns the rules into checks that run the moment an employee files the expense: a ceiling per category, a mandatory document above a threshold, exceptions that must be approved explicitly.

The rules that can be enforced automatically

Ceiling per category

Accommodation, meals, transport, fuel — each category can carry its own limit, per day or per event. The employee sees the ceiling before spending, not in a rejection at settlement time.

Mandatory documents, per category

The categories that require a supporting document are set explicitly: on those, a report cannot be submitted without an attachment. The rule is configured once and applies uniformly across departments.

Block or warn, your choice

For each rule you decide whether a breach blocks submission or merely warns and flags the line for the approver. Controls that are too rigid produce workarounds; controls that are too permissive produce nothing.

Exceptions approved explicitly

When an over-ceiling expense is justified, it passes through an extra approval step and stays marked as an exception. Exceptions can be counted at month-end, so the rule does not erode quietly.

The same rules on phone and web

Policy is evaluated server-side, so a report filed from a phone on the way back goes through exactly the same checks as one entered at a desk.

The policy is versioned and dated

When ceilings change, expenses already recorded stay judged against the policy in force on their own date. Otherwise a January report becomes "non-compliant" purely because the rule changed in June.

What separates a respected policy from an ignored one is not the wording but the timing of the check. Enforce the rule at creation and the employee learns it before spending; enforce it at settlement and the only outcome is an argument about money already spent.

Frequently asked questions about expense policy

Yes. Ceilings can be configured per category and per organisational structure, so a sales team that travels constantly is not held to the same figures as a department that never does.

Write the policy once, then let it do the work

Ceilings per category, documents mandatory above a threshold, exceptions counted — on web and on mobile.