Why Expense Policies Fail, and What to Write Instead

Expense policies do not fail because people are careless. They fail because most of the rules in them cannot be checked by the person who has been told to check them. Write rules that an approver can verify from the claim in front of them, and enforcement stops being a matter of willpower.

Almost every small business expense policy contains the same four defects, and they compound. The rules are unenforceable, so approvers stop reading. Card slips get accepted because the itemised receipt is missing and the claim has to be paid anyway. Claims arrive months late and land in the wrong fiscal year. And coding gets deferred to whoever closes the books, by which point the reason for the spend has evaporated. None of these are exotic. All four are fixable by changing what the document says.

The 60-second version

A rule an approver cannot verify is decoration. Replace "must be reasonable" with something checkable from the claim itself.
Card slips do not support an input tax credit. ETA s. 169(4) requires the prescribed information before you file [3].
Late claims become wrong-year expenses. Expenses belong to the period incurred, not the period submitted [6].
Code at submission, not at year end. The submitter is the only person who knows why.
Six years is the baseline retention period from the end of the last tax year the records relate to [1].
Write the exception process, not just the rule. Every policy gets broken; the question is whether breaking it is recorded.

Why do written rules and actual behaviour drift apart?

Take the most common line in any expense policy: "expenses must be reasonable and necessary." Now imagine you are the person approving a $180 dinner. What do you compare it against? There is no benchmark in the document, no threshold, no named criterion. The approver either applies a private standard that differs from everyone else's, or approves it because refusing would require an argument they cannot win with the policy in hand.

Multiply that across a dozen similarly vague clauses and the policy stops being a decision tool. It becomes a document you point to after something has already gone wrong, which is the least useful moment.

The test for any rule you write: what would the approver look at to verify it? If the answer is information that is on the claim, the rule works. If the answer is information that lives in someone's head, in a booking system, or in the past, the rule does not work no matter how sensible it sounds. "Book the lowest available fare" fails this test. "Flights over the pre-approval threshold need written approval before booking" passes it, because the approval either exists or it does not.

Rewrite in that direction and the policy shrinks. Most of what gets cut was never being enforced anyway.

Why is a credit card slip not good enough?

A terminal slip proves a payment happened. It does not prove what was bought, and for GST/HST it carries almost none of the information the law requires.

Section 169(4) of the Excise Tax Act prohibits claiming an input tax credit unless the registrant has obtained the prescribed supporting information before filing the return [3]. What counts as prescribed is set out in the Input Tax Credit Information Regulations, and the requirement scales with the size of the purchase: small amounts need less, larger ones need more, including the supplier's GST/HST registration number [4]. The current tiers are set out in CRA Guide RC4022 [7], and they are the numbers to check rather than a figure remembered from a policy template.

For income tax the problem is different but no less real. Section 18(1)(a) permits a deduction only for outlays made for the purpose of earning income [5]. A slip showing "RESTAURANT - $180.00" does not establish that purpose; the itemised receipt plus a note naming who was there does.

So write the rule as two documents, not one: the itemised merchant receipt is the supporting document, and the card slip is evidence of payment. Where the merchant genuinely cannot produce an itemised receipt, require a contemporaneous note of what was purchased attached to the claim. Our article on CRA receipt requirements goes through the tiers in detail, and the six-year retention rule for digital receipts covers what happens to those images afterward.

This is the point where a policy usually meets reality: the receipt is in a coat pocket, and the claim is already three weeks old. Capture at the moment of purchase is the only durable fix. MapleExpense accepts a photo of the receipt or a forwarded vendor email and pulls the merchant, date, total, and tax off it, which means the itemised document is attached to the claim from the start rather than requested later and never produced.

What goes wrong when claims arrive after year end?

An expense belongs to the period in which it was incurred. Section 9(1) of the Income Tax Act computes business income as the profit for the year [6], and profit means matching the costs of a period to the revenue of that period. Submission date has no bearing on it.

When a claim shows up after the books are closed, you have three unattractive options. Accrue it if the year is still genuinely open. Record it in the current year and accept that two years are now slightly misstated. Or amend, if the amount justifies the cost of doing so. Most small businesses take the second option and never say so out loud, and for small amounts that is defensible - but it stops being defensible when the pattern is systematic and the amounts are not small.

The worse outcome is the claim that never arrives at all. An employee who missed the deadline by two months and assumes the claim will be refused simply eats it, and the company deducts nothing. That is a real deduction lost to an administrative silence.

Two things fix most of it. A submission deadline short enough that claims land inside the reporting month - thirty days is the usual answer, and the reasoning is set out in building an approval workflow for a small team. And an explicit year-end cut-off, announced before year end, stating the last date claims for the closing year will be accepted and what happens to anything later. Pair that with the timing decisions covered in year-end expense timing and working capital, so the cut-off is a deliberate date rather than the day your accountant asks for the file.

Should coding happen at submission or at year end?

At submission, and this is the single change with the largest effect on data quality.

The person submitting a claim knows why the money was spent. That knowledge has a half-life of about a week. When coding is deferred to year end, a bookkeeper is inferring purpose from a vendor name and an amount, months later, with no way to ask. That is how a client lunch becomes office supplies, how a tool purchase that should have been capitalised gets expensed, and how the meals line ends up understated in a way that quietly misstates the s. 67.1 limitation.

Deferred coding also destroys the usefulness of monthly numbers. If categories are only correct once a year, you cannot run a budget, you cannot see a cost trend, and the management reporting you are paying for is decorative until the annual cleanup. Our notes on expense categorisation practices and on GIFI codes cover where the categories should map to.

The objection is always the same: submitters are bad at coding. They are. The answer is not to take coding away from them, it is to make the choice small. MapleExpense proposes a category and the matching GIFI code from the receipt and the vendor history, and learns from the corrections, so the submitter is confirming a suggestion rather than navigating a chart of accounts. Confirmation at submission beats reconstruction in March.

So what should the policy actually say?

Six sections, on one page.

Who approves whom. Names, not titles, in a company this size.

What needs permission first. The pre-approval threshold, the two categories that always need it regardless of amount - recurring charges and capital purchases - and how permission is given.

What a valid claim contains. Itemised receipt, business purpose in a sentence, names of attendees for meals, category selected. Spell out that a card slip alone is not a receipt.

Deadlines. The routine submission window, and the hard year-end cut-off date.

What is never reimbursed. A short, specific list. Specific beats comprehensive; three real examples are worth more than a page of categories.

The exception process. Every policy gets broken. State who can authorise an exception and require that it be recorded on the claim. A policy with no exception route is not stricter, it is just one that gets broken silently.

Then review it once a year against what actually happened. If a rule was bypassed all year and nothing bad resulted, the rule was wrong. If a rule was followed and you still ended up with a mess, you are missing one. A policy that never changes is not stable; it is unexamined. When you do get examined, the consistency of the process is a large part of what makes it defensible - a point we take further in preparing for a small business audit.

Frequently asked questions

Why do expense policies fail in small businesses?

Expense policies fail mainly because they contain rules that nobody in the company has the information or authority to enforce. A rule such as "expenses must be reasonable" gives an approver nothing to check against, and a rule such as "book the lowest available fare" requires the approver to know what fares were available at the time of booking, which they do not. A policy only works when every rule in it can be checked by the person you have asked to check it, using information they actually have in front of them.

Is a credit card slip enough for a business expense in Canada?

A credit card slip is usually not enough. For income tax purposes CRA expects a supporting document that shows what was purchased, not just that a payment occurred. For GST/HST, section 169(4) of the Excise Tax Act bars an input tax credit unless the registrant has obtained the prescribed supporting information before filing, and the Input Tax Credit Information Regulations require details including the supplier's name and, above specified amounts, the supplier's GST/HST registration number. A terminal slip carries none of that, so the safe rule is to require the itemised merchant receipt and treat the card slip as evidence of payment only.

What happens to an expense claim submitted after the fiscal year end?

An expense belongs to the period in which it was incurred, not the period in which someone got around to submitting it. If a claim arrives after the books for that year are closed, you have three options: accrue it if the year is still open for adjustment, record it in the current year and accept that both years are slightly wrong, or amend the return if the amount is material. The practical defence is a submission deadline short enough that claims land before the year closes, plus an explicit cut-off communicated before year end.

How long do I have to keep expense receipts in Canada?

The general rule under section 230 of the Income Tax Act is that records and supporting documents must be kept for six years from the end of the last tax year to which they relate. Some situations extend that period, including unfiled or late-filed returns and outstanding objections or appeals. Electronic images are acceptable provided they are readable and retained in an accessible form. CRA Information Circular IC78-10R5 sets out the retention and destruction rules, including how to request permission to destroy records early.

Should expenses be categorised when they are submitted or at year end?

Categorise at submission. The person submitting the claim is the only one who knows why the money was spent, and that knowledge decays within days. Coding at year end means a bookkeeper is guessing the purpose of a transaction from a vendor name and an amount, months after the fact, which is how meals end up in office supplies and how capital purchases end up expensed. Submit-time coding also means your monthly numbers mean something, rather than becoming accurate only once a year.

What makes an expense rule enforceable?

An enforceable rule is one where the approver can tell, from the claim in front of them, whether the rule was followed. Compare "meals must be reasonable" with "meal claims must name the people present and the business reason". The second can be checked in five seconds against the claim itself; the first requires a judgement nobody has been given criteria for. When you write a rule, ask what the approver would look at to verify it. If the answer is information the approver does not have, the rule is decoration.

Do I need a written expense policy if everyone follows the rules anyway?

Yes, for two reasons that have nothing to do with current behaviour. First, a written policy is what lets you apply a rule consistently when it becomes inconvenient, which is the only time a policy is ever tested. Second, the policy is part of the record that supports the deduction: it evidences that expenses were incurred for business purposes under a defined authorisation process, which is materially easier to explain to CRA than a pattern of individual decisions made from memory.

Sources cited in this article

Income Tax Act, s. 230
Requirement to keep books and records with supporting documents, and the retention period that runs from the end of the last tax year to which they relate.
https://laws-lois.justice.gc.ca/eng/acts/i-3.3/section-230.html
CRA Information Circular IC78-10R5, Books and Records Retention/Destruction
CRA policy on how long records must be kept, acceptable formats, and early destruction requests.
https://www.canada.ca/en/revenue-agency/services/forms-publications/publications/ic78-10.html
Excise Tax Act, s. 169(4)
Prohibits claiming an input tax credit unless the registrant has obtained the prescribed supporting information before filing the return.
https://laws-lois.justice.gc.ca/eng/acts/e-15/section-169.html
Input Tax Credit Information (GST/HST) Regulations, SOR/91-45
Specifies the supporting information required, scaling with the amount of the purchase, including the supplier's registration number above prescribed thresholds.
https://laws-lois.justice.gc.ca/eng/regulations/SOR-91-45/
Income Tax Act, s. 18(1)(a)
An outlay is deductible only to the extent it was made for the purpose of gaining or producing income from the business.
https://laws-lois.justice.gc.ca/eng/acts/i-3.3/section-18.html
Income Tax Act, s. 9(1)
Income from a business is the profit for the year, which is what requires expenses to be matched to the period in which they were incurred.
https://laws-lois.justice.gc.ca/eng/acts/i-3.3/section-9.html
CRA Guide RC4022, General Information for GST/HST Registrants
Current documentary requirements for input tax credits, including the amount tiers that determine how much supplier information is needed.
https://www.canada.ca/en/revenue-agency/services/forms-publications/publications/rc4022.html
CRA, Keeping records
CRA guidance on record formats, electronic records, and where records must be kept.
https://www.canada.ca/en/revenue-agency/services/tax/businesses/small-businesses-self-employed-income/setting-your-business/keeping-records.html

All sources verified 2026-09-23. Spotted a link that has moved? Email [email protected] and we will correct it.