Your organisation's expense policies carry limits and rules. Chronon checks a new expense against them as you save it, so problems surface now rather than a week later in an approval queue.

The policy does not cover that category

You are over a limit

Policies can carry a daily, monthly, or annual limit. Chronon adds up what you have already claimed in the window and refuses the expense that would break the ceiling. The message tells you which limit and by how much.

What to do:

• Check whether an earlier expense in the window is wrong and should be corrected.

• Split a genuinely mixed spend into its real categories, each under its own limit.

• If the spend is legitimate and over the limit anyway, talk to your approver before submitting — an approver can accept it, but nobody can make the limit not apply.

A pre-approval is required

Some policies require a pre-approval before the spend. If yours does, raise the request first — see Request a cash advance and Raise a trip request — and link it on the expense.

A receipt is required

The policy requires a receipt and none is attached. Attach one, or use a policy and category that does not require one, if such a pairing genuinely fits the spend.

Policy validation runs again when the report is submitted, not only when the expense is saved. An expense that was fine in March can fail in April because later expenses filled up the monthly limit ahead of it.