How to Set Expense Policy Rules and Approval Routes

Why expense policies are ignored

Most companies have an expense policy: receipts above a certain amount, a daily meal limit, no weekend spending without a reason, claims within so many days. In practice the policy lives in a PDF, and approvers are expected to remember it while clicking approve on a busy afternoon.

The result is uneven. One manager rejects a claim without a receipt, another approves it. Duplicates slip through because the same receipt is claimed twice a month apart. Large claims go to the wrong approver, or wait for someone on holiday.

A policy that is checked automatically, before a claim reaches an approver, and an approval route that follows clear rules for amount, category and department, make approvals faster and more consistent.

Why this happens

• The policy lives in a document, not in the system.
• Approvers apply different standards.
• Duplicate receipts go unnoticed.
• Large claims reach the wrong approver.
• Approvals wait while an approver is away.

Biznsbook addresses this through expense policy rules, approval stages by amount, category and department, route preview, approval delegation in Expense Management, posting card spend to the card account and clearing payments in bank reconciliation.

Small gaps in expenses rarely fail loudly. They show up later as numbers nobody can explain. Recording each step where it happens removes the guesswork.

Step-by-step: Set Expense Policy Rules and Approval Routes

Written for finance teams and office managers handling company card spend in Biznsbook Expense Management.

1. Add policy rules. In Expense Settings → Settings → Policies, add rules: maximum per claim, daily limit per person, receipt required above an amount, duplicate window, maximum age, weekend spend.
2. Choose an action per rule. Each rule can warn, require a justification, or block. Warn only flags the claim for approvers; Require justification stops it until the claimant writes a reason; Block stops submission until the claim is fixed or a settings manager overrides it.
3. Build approval stages. In Settings → Workflow, add stages: role, named users, reporting manager, department head, or finance sign-off (always last). Scope them by amount, category and department, choose parallel or any-of, and set escalation.
4. Preview the route. Use Route preview to see who a claim of a given category, amount and claimant would go to before staff submit real claims.
5. Set up delegations. In Settings → Delegations, name a delegate, the dates and optionally a category, so approvals continue while someone is away.
6. Add budgets. In Expense Settings → Budgets, create monthly, quarterly or annual budgets by category and optionally department, cost center, project and work order; the alert threshold defaults to 80%.
7. Let claims flow. On Submit, policy checks run first, then budget checks; the claim then follows its route, and approvers see only claims at their stage.

Review results after the first full monthly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: The policy lives in a document, not in the system. Repeating this each month usually shows up first in claims approved against the policy.
• Mistake 2: Approvers apply different standards. Repeating this each month usually shows up first in claims approved against the policy.
• Mistake 3: Duplicate receipts go unnoticed. Repeating this each month usually shows up first in claims approved against the policy.
• Mistake 4: Large claims reach the wrong approver. Repeating this each month usually shows up first in claims approved against the policy.
• Mistake 5: Approvals wait while an approver is away. Repeating this each month usually shows up first in claims approved against the policy.

Each of these turns into a question finance cannot answer quickly. Fix the process on the record rather than in email threads or spreadsheets.

Best practices that hold up as you scale

• Add policy rules — In Expense Settings → Settings → Policies, add rules: maximum per claim, daily limit per person, receipt required above an amount, duplicate window, maximum age, weekend spend.
• Choose an action per rule — Each rule can warn, require a justification, or block.
• Build approval stages — In Settings → Workflow, add stages: role, named users, reporting manager, department head, or finance sign-off (always last).
• Preview the route — Use Route preview to see who a claim of a given category, amount and claimant would go to before staff submit real claims.
• Set up delegations — In Settings → Delegations, name a delegate, the dates and optionally a category, so approvals continue while someone is away.

Import every statement as soon as it arrives and keep the number of unmatched lines at zero before month end.

How Biznsbook supports this workflow

expense policy rules is part of Biznsbook and works on the same records as the rest of expenses, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

approval stages by amount, category and department is part of Biznsbook and works on the same records as the rest of expenses, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

route preview is part of Biznsbook and works on the same records as the rest of expenses, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

approval delegation is part of Biznsbook and works on the same records as the rest of expenses, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

Company cards need Enable Corporate Cards in Settings and the Manage Expense Reimbursements permission; bank matching needs Finance Management.

Suggested implementation timeline

1. Week 1: Set up expense policy rules and the permissions the people involved need.
2. Week 2: Run the real process in Biznsbook only, with no side spreadsheet, for one team or site.
3. Week 3: Review what was recorded with the people involved and tighten the rules where they disagreed.
4. Month 2: Roll out to every team or site.
5. Ongoing: Reviewing policy and routes each quarter.

Related guides

Cluster hub: Accounting guides. Module: expense management. Also see scan receipts into claims.

How budgets, routes and categories interact

Budget checks run at submission: they warn when a claim is near or over budget, and block it when it is over budget and the category has a maximum amount. Spend is counted once, when a claim is finally approved, and given back if it is cancelled. A claim line counts against the most specific matching active budget.

A claim with lines in several categories goes through each category's own stages and the all-category stages for its other lines. If a category does not require approval, or no stage applies, the claim is approved at once on submission.

Stages that name specific people can be actioned only by them or their delegates; a role stage by anyone with that role; a reporting-manager or department-head stage by that person, or the fallback role when HRMS has none with a login. Overdue approvals escalate through a scheduled job, weekly by default.

A rejected claim needs a reason. The claimant fixes it and resubmits from Self Service or the Expense module, and it restarts the route from the beginning, so every approver sees the corrected version.

Metrics to track monthly

• Unmatched statement lines
• Draft claims still missing details
• Card account balance against the statement
• Card payments not yet cleared in the bank

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Manual workarounds vs Biznsbook

Compare common manual workarounds with Biznsbook expense policy rules and the related capabilities.

Reviewing policy and routes each quarter

Each quarter, look at which rules fire most often and whether their action is right: a warning nobody reads may need to require a justification, and a block that is always overridden may be too strict. Check that delegations have ended for people who are back, and use Route preview after any change to stages.

Write the card policy (what can be bought, receipt deadline) into your expense policy.

Frequently asked questions

How this differs by industry