Journal voucher: recording adjustments your auditor can follow
A journal voucher documents a manual accounting entry — what was posted, why, and who approved it. What it must contain, when you need one, and the controls that stop errors.
An expense claim process is judged on one number: how long between submitting and being paid. Everything else — forms, policies, receipts — exists to make that number small.
An expense claim is somebody spending their own money on the company's behalf and asking for it back. That framing matters, because it explains why slow reimbursement damages goodwill out of proportion to the amounts involved: a colleague who waits six weeks for a taxi fare is not being difficult, they are lending the company money without agreeing to.
A workable process is short: a written policy people can actually recall, a claim form with the fields the books need, and a payment cycle that runs regardless of who is busy.
Say in the policy what happens without a receipt, because it will happen. A stated rule — a small limit for lost receipts with a written explanation, nothing above it — is fairer and faster than deciding case by case, and it stops the awkward conversations that make people stop claiming at all.
In Ettex, the claim itself fits Ettex Forms — a short form with the seven fields above and a file-upload question for the receipt, submissions landing in a searchable, timestamped inbox with a live summary and export to CSV or XLS. The accounting side lives in Ettex Books: a chart of accounts structured the way accountants expect, categories and auto-categorisation rules, notes and documents attached to any entry so the receipt sits with the transaction, multi-currency with rate tracking for foreign spend, bank reconciliation to match the payment when it goes out, instant search across all periods, and P&L and ledger export as PDF, CSV or XLS.
Rates only answer part of the question. A travel policy states what class of travel is allowed, how far ahead to book, which booking route to use and what happens when someone books outside it.
Claimant, dates, amount and currency, category, business purpose, what it relates to, the receipt, and the approval.
On a published cycle — monthly at worst, ideally with the next payroll or payment run. Predictability matters as much as speed.
Have a stated rule: a modest limit with a written explanation, nothing above it. Deciding case by case is slower and feels arbitrary.
Not for a small team — a form, a category list and a payment cycle cover it. Software pays off with volume, multiple approvers, or card feeds worth reconciling automatically.
With the rest of your financial records, for whatever retention your jurisdiction requires — usually years, and the receipt must stay attached to the entry.
An expense claim process is a promise about money someone already spent. Publish the rules, approve on a rhythm, pay on a cycle — the paperwork exists to protect that promise, not the other way round.
A journal voucher documents a manual accounting entry — what was posted, why, and who approved it. What it must contain, when you need one, and the controls that stop errors.
Consolidated accounts present a group as one entity. Who must prepare them, what gets eliminated, and the reconciliations that decide how long it takes.
Fund accounting tracks money by the restrictions attached to it. Who needs it, how restricted funds work, and the reporting it makes possible.