Still chasing WhatsApp receipts to reimburse staff?

Every month it is the same scramble. Receipts arrive as WhatsApp photos and crumpled paper, somebody retypes them into a spreadsheet, a manager forwards an approval over email, and the reimbursement still takes ten days to reach the person who spent the money. The GST on those bills - input credit you are legally entitled to claim - mostly never gets captured, because nobody is going to chase tax breakups across forty receipt photos. None of this is hard work. It is just work that should not exist.

The Odoo Expenses module collapses that whole chain into one tracked flow: submit, approve, post, reimburse. This is the setup guide for an India SME - how to build the expense products and accounts, configure mileage and per-diem, capture GST input tax credit on the way through, and choose between reimbursing via payroll or as a vendor payment. It is written for the finance lead who is currently the human glue holding a spreadsheet process together and wants the system to do it instead.

Why the manual process actually costs you

The spreadsheet looks free because nobody bills for it, but it leaks in three places. First, time - every receipt is handled twice, once by the employee who sends it and once by finance who retypes it, and approvals sit in inboxes with no audit trail. Second, money - the GST input credit on travel, software, fuel and office supplies bought by staff is real cash you can offset against output GST, and a photo-and-spreadsheet process captures almost none of it. Third, trust - when reimbursements take ten days, people stop submitting small claims and start resenting the ones they do submit. Moving this into Odoo is not about software for its own sake; it is about recovering the time, the tax credit and the goodwill the manual process quietly burns.

Set up expense products and accounts first

Before anyone submits a claim, Odoo needs to know what categories of spend exist and where each one posts in your chart of accounts. In the Expenses module these are modelled as expense products - 'Travel - Air', 'Hotel', 'Fuel', 'Software Subscription', 'Client Meals', and so on. Each product is mapped to an expense account in the GL, so when a claim is posted the amount lands in the right place automatically instead of finance deciding the account by hand every time.

• Create one expense product per real category of spend - keep the list short enough that staff pick the right one without guessing.
• Map each product to its expense account so posting is automatic and your P and L breaks expenses down the way you actually report them.
• Set a cost or leave it open for the employee to enter the actual amount from the receipt.
• Attach the correct GST tax to each product - this is what makes input credit capture work, covered below.

This account mapping is the same discipline that keeps a clean ledger everywhere in Odoo, and it pairs naturally with getting your opening balances and first reports to reconcile when you go live. Get the products and accounts right once and every claim afterwards posts itself.

The submit, approve, post, reimburse flow

Once products and accounts exist, the day-to-day process is a four-step flow that replaces the entire WhatsApp-and-spreadsheet routine. Each step has a clear owner and leaves a record, so nothing sits in an inbox and nobody has to ask 'did this get approved?'

1. Submit. The employee creates an expense, picks the product (say 'Fuel'), enters the amount, snaps the receipt from the mobile app, and submits it - usually grouped into an expense report covering a trip or a month.
2. Approve. The manager sees the report, checks the receipt against the amount, and approves or refuses with a note. The approval is logged with a timestamp and a name, which is the audit trail the spreadsheet never had.
3. Post. Finance posts the approved report to the journal. Odoo creates the accounting entry - debiting the expense accounts, recording the GST input credit, and crediting the amount payable to the employee - in one click.
4. Reimburse. The employee is paid, either through the next payslip or as a vendor payment, and that payment is later reconciled against the bank statement.

The difference is measurable. Teams that move off the spreadsheet onto this flow typically close the monthly expense cycle in about 2 days instead of 10, and cut roughly 70 percent of the manual data entry, because the employee does the entry once on their phone and the accounting posts itself.

Receipts and mobile capture

The single behaviour change that makes this stick is killing the WhatsApp photo. In the Odoo mobile app an employee photographs a receipt the moment they pay, and the image is attached to the expense permanently - it travels with the claim through approval, posting and audit. There is no separate folder of photos to lose, no end-of-month reconstruction from a chat thread. For the finance lead, every posted entry has its source document one click away, which is exactly what you want when GST scrutiny or a statutory audit asks to see the bill behind a claimed input credit.

Capturing GST input tax credit on expenses

This is where Odoo pays for itself for an India SME. When staff buy fuel, software, hotel stays or office supplies from GST-registered vendors, the tax on those bills is input credit you can set off against your output GST - provided you capture it correctly and the supplier's invoice carries your GSTIN. Because each expense product carries its GST tax, posting a claim records the input credit automatically into the same GST ledgers your purchase bills feed. You are no longer choosing between reimbursing staff fast and claiming the credit - you get both from one entry.

For this to actually translate into a filed claim, the underlying receipt has to be a proper tax invoice in your business name, not a personal cash memo, and your GST compliance automation has to pull these expense-side credits into the return alongside vendor bills. The mechanics mirror the way you would match vendor bills against purchase orders to stop overpaying - the tax only counts when the document supports it. Done right, the input credit recovered on staff expenses across a year is rarely trivial for a growing D2C or services business.

Mileage and per-diem categories

Two categories need slightly different handling from a normal receipt-backed claim. Mileage - reimbursing staff who use their own vehicle - is best modelled as an expense product priced per kilometre, so the employee enters distance and Odoo computes the amount against your standard rate, with no fuel bill required. Per-diem - a fixed daily allowance for travel meals and incidentals - is a flat-rate expense product the employee claims per day on tour, again without itemised receipts. Setting both up as their own products keeps them clean in the books and stops staff from forcing a mileage claim through a 'Fuel' line that then demands a receipt nobody has.

Reimburse via payroll or as a vendor payment

Odoo gives you two ways to actually pay the employee back, and they behave differently in your books. Reimbursing via payroll adds the approved amount to the next payslip as a non-taxable reimbursement line, so it goes out with salary in one bank transfer - tidy if your team already runs Indian payroll in Odoo with PF, ESI, PT and TDS, because it rides the same monthly run. Reimbursing as a vendor payment treats the employee as a supplier and pays the claim separately, which is faster for urgent or one-off amounts and keeps reimbursements off the payslip entirely. Pick per situation: routine monthly claims fit payroll, while a large travel advance or an urgent payout is cleaner as a direct vendor payment.

Reconciling reimbursements and reporting

However you pay, the final step is reconciliation - matching the money that left your bank to the expense entries that authorised it. When the reimbursement clears, you reconcile that bank line against the employee payable Odoo created at the posting step, closing the loop. The same automation that handles your supplier payments handles this; setting up bank statement import and reconciliation models means these reimbursements match with little manual effort. On the reporting side, because every claim posted to a mapped account, you get a live expense report by category, by employee and by period without building anything - the analysis the spreadsheet promised and never delivered, available the moment a claim is posted.

This expense flow is one module of a wider system, and it is worth getting an Odoo consultant to wire it into your accounting and payroll rather than bolting it on alone, especially during a full Odoo implementation where expenses, GST, banking and payroll should all reconcile to the same ledger.

FAQ

How do employees submit expenses in Odoo?

From the Odoo mobile app or the web, an employee creates an expense, selects the expense product that matches the spend, enters the amount, photographs the receipt, and submits it - usually grouped into a report for a trip or a month. The receipt image stays attached through approval, posting and audit, so there is no separate folder of photos and no end-of-month reconstruction from a chat thread.

Can I claim GST input tax credit on employee expenses through Odoo?

Yes, provided the receipt is a proper tax invoice in your business name carrying your GSTIN, and you attach the correct GST tax to each expense product. When the claim is posted, Odoo records the input credit into the same GST ledgers your purchase bills feed, so it flows into your return alongside vendor-bill credits. It will not work on personal cash memos that lack your GSTIN.

Should I reimburse staff through payroll or as a vendor payment?

Both work in Odoo and the choice is about timing and book-keeping. Payroll adds the approved amount to the next payslip as a reimbursement line and pays it with salary - tidy for routine monthly claims. A vendor payment treats the employee as a supplier and pays the claim separately - faster for urgent or one-off amounts and it keeps reimbursements off the payslip. Pick per situation rather than forcing everything down one route.

How do I handle mileage and per-diem in Odoo Expenses?

Model each as its own expense product. Mileage is priced per kilometre, so the employee enters distance and Odoo computes the amount against your standard rate with no fuel bill needed. Per-diem is a flat daily rate the employee claims per day on tour, again without itemised receipts. Keeping them as separate products stops staff from forcing these through a receipt-backed line that then demands a bill nobody has.

The bottom line: the receipt photos and the reimbursement spreadsheet are not a process, they are the absence of one. Build the expense products and accounts, set the GST tax on each, and let the submit-approve-post-reimburse flow do the handling - claims posted on a phone, input credit captured automatically, and reimbursements reconciled against the bank without retyping a thing. Wire it up properly once and your expense cycle closes in two days instead of ten, every month after.