Suppliers & purchases · Guide 22 of 53
Employee expenses: claims, approval and reimbursement
Collect receipts and mileage, approve the accounting, and reimburse employees without turning staff into suppliers.
Employee expenses are three related events, not one: evidence supplied by the employee, an accounting decision by an approver, and cash settlement by treasury. IQ Books keeps those boundaries visible so a saved receipt cannot silently change the accounts and an approved claim cannot pretend the employee has already been paid.
Enable only when you need it
Go to Settings → Features and enable Employee expenses. IQ Books adds one Expenses destination and one dashboard signal. Turning it off hides that workspace and stops loading its data; it does not delete claims, attachments, journals, reimbursements or audit evidence.
The claim lifecycle
- Draft. Add ordinary expenses or mileage journeys, choose the account and optional project, then save. Attach receipt images or PDFs. Drafts are evidence only and do not touch the ledger.
- Submitted. The employee freezes the completed claim for review. An approver can return it with a reason; the claimant edits and resubmits the same record.
- Approved. Approval posts the expense and recoverable VAT, balanced to Employee Expenses Payable. The claim now appears under To reimburse.
- Partially paid / paid. One or more reimbursements debit Employee Expenses Payable and credit the chosen bank. The remaining amount stays visible until fully settled.
Expenses, mileage, VAT and currency
An ordinary line records its date, merchant, description, net amount and VAT treatment. Claims accept the plain VAT codes only (standard, reduced, zero, exempt, no VAT) — reverse-charge treatments belong on supplier bills, not employee claims — and the server independently caps the claimed VAT at the code’s rate. A running net / VAT / gross total updates at the foot of the editor as you build the claim. A mileage line records the journey, distance, miles or kilometres and the organisation’s rate; it carries no VAT by default. Both can be tagged to a project. Foreign claims use the recorded reporting-date exchange rate when approved. Mileage remains in base currency.
The HMRC car and van rate is filled in for the journey’s date: 55p a mile from 6 April 2026, 45p before. Past 10,000 business miles in a tax year the rate is 25p, and IQ Books applies it for you. A journey that crosses the line is split into the miles before it and the miles after, each at its own rate. If an earlier claim changes, later claims that are still open are re-priced to match; approved claims are never changed. Motorcycle (24p), bicycle (20p) and passenger (5p) miles keep their own rate and do not count towards the car and van 10,000.
Accrual VAT is recognised by the approval journal. Under cash accounting, personal-claim VAT enters the return as the employee is reimbursed; company-card claim VAT follows the company-paid expense date. Reversing an approval removes the original journal from the live ledger and preserves the reversal evidence.
Receipts read by RiQ
On My claims, drop or photograph a receipt (or use Add a receipt inside a claim). RiQ reads the shop, the date, the VAT and the total, and suggests the account. You check the line and choose which claim it goes on, an open one or a new one; the receipt is attached to the claim and marked against its line with a paperclip. Receipts not yet on a claim wait at the top of My claims.
Reading a receipt uses 10 of the organisation’s credits, not the claimant’s, up to 25 a day per person, and each receipt is read once. An owner or admin can switch it off in Settings → Features (Claimants can have receipts read); receipts can still be added, and the line is typed in. For an organisation that is not VAT registered, the whole amount on the receipt is the cost, VAT included, so the claimant is paid what they spent.
A receipt put on the wrong claim comes back with Put it back in Documents while the claim can still be edited: its line comes off (a draft claim that held only that receipt goes). Deleting a claim sends its receipts back to Documents rather than losing them.
Receipts and privacy
Attachments are AES-256-GCM encrypted at rest and checksum-verified on download. A submitter can access only evidence on their own claims. Expense approvers and admins can inspect all claims in the organisation. Evidence locks after approval; return the claim before asking the employee to replace it.
The expense policy
Under Settings → Features, with Employee expenses on, an owner or admin sets the Expense policy:
- Need a receipt for anything over an amount (£25 unless changed, or switched off). A claim with a line over it and no receipt cannot be submitted, or approved. Attach the receipt to the claim, or choose No receipt… on the line and say why (lost, or the same receipt as another line); the claimant or the approver can do this, and whoever approves the claim sees the reason. A receipt read by RiQ is marked against its line; any other receipt attached to the claim covers one line still without one, so correcting a line’s amount does not lose its receipt. A receipt counts once: its pages, or the same file attached twice, cover one line. Mileage needs no receipt. A foreign-currency line is measured in pounds.
- Limits per account: the most one line may cost on that account, for example meals. A line over its limit is pointed out to the approver, never refused.
A claim also shows when something looks claimed before: the same receipt file on another claim or on a supplier bill, or the same date, amount and merchant on another line of the claim, another claim or a bill (declined claims do not count). A claimant sees this only for their own claims and the bills; an approver sees every match, with which claim and whose. These do not stop an approval: they are there to be looked at. What RiQ found lists each submitted claim with something to check for whoever approves claims, and the push sent to approvers when a claim is submitted says how many things there are to check.
People and roles
Expense roles are deliberately separate from general bookkeeping roles. A submitter sees and edits their own claims. An approver reviews team claims and records reimbursements. An expense admin also manages roles and setup. Organisation owners and admins begin as expense admins; bookkeepers begin as approvers.
Secure reimbursement details
Bank details are stored as encrypted fields and ordinary reads return only masks. Saving or replacing details resets them to unverified. An owner or admin must check them against a trusted source outside the payment request before marking them verified. Plaintext details are never written to audit metadata.
Individual and batch reimbursement
Record an individual reimbursement when payment has already been made — the dialog pre-fills the outstanding amount and lets you pick the paying bank, date and reference. When that payment’s bank line arrives, Review offers to match it to the reimbursement so it is not counted twice (see confirming drafts). For a pay run, select approved claims, a date and a secure payment-file profile. Submission refreshes verified destinations and freezes encrypted snapshots. Owner/admin approval follows.
By default a claimant who is also an approver can approve their own claim, which suits a one-person business. Under Settings → Features → Approval controls you can require a different approver for expense claims, and separately for reimbursement batches, whenever segregation of duties matters.
Download either a UK bank-upload CSV or ISO 20022 pain.001 file, authorise it in your bank, then post the batch in IQ Books. Export does not mean the bank has paid it. Posting is all-or-nothing and idempotent: every reimbursement succeeds in one database transaction, or none do.
Corrections and audit evidence
A submitted or approved claim can be returned with a reason. If approval already posted, IQ Books first posts a linked reversal; active reimbursements must be reversed before the approval can be reversed. Reimbursement reversals restore the outstanding balance. Period locks apply to approval, reimbursement and reversal dates. Every change is organisation-scoped and audited.
What RiQ will and will not do
RiQ can explain the lifecycle, identify what is waiting and navigate you to Expenses. Asked, it can also say why a line has no receipt ("I lost the Travelodge receipt") and, for an owner or admin, change the expense policy ("receipts over £50", "limit meals to £30 a line"); each is shown for a yes first. It must not claim a draft is in the accounts or an exported bank file has been paid. Creating or verifying bank details, approving claims and payment batches, exporting instructions and posting reimbursements remain deliberate high-trust actions in the interface.