An HR and admin lead at a post-merger nonprofit with fewer than forty people described the current state without romance. Employees fill Excel expense forms. Receipts go missing. Someone says they will do it later. Payroll already runs through a separate system. The assumption hanging in the air was that employee reimbursements must hitch to that payroll connector to get paid.
Then the realisation: pay reimbursables as payables, separate from payroll. Their reaction was immediate. That is something I have not thought of. It does make sense, and it is way better, actually.
The direct answer: accountable business expense reimbursements are usually payables with receipts, not payroll earnings. Riding them inside payroll confuses employees, mixes tax categories, and forces HR tools to pretend they are AP.
This matters most if you are a nonprofit or association on Excel expenses today, if HR owns the form but Finance owns the coding, and if you assumed a payroll connector was the only way to repay staff.
The second problem after "we will just add it to the next pay run"
Payroll is built for earnings, deductions, and taxable benefits. Accountable reimbursements for business expenses, when reasonable and receipted, are a different object in CRA guidance: a repayment of expenses incurred for employment duties, supported by records, generally not treated as income when they meet the conditions in CRA employers' materials such as T4130 and the travel expense topics on Canada.ca.
Stuffing those repayments into payroll creates practical failures even when tax theory is handled carefully.
Employees stop understanding the payment. Is this pay? Is this a benefit? Why does the net look weird next to my salary?
HR becomes the chase function for receipts that Finance will recode anyway.
Finance loses a clean AP audit pack: invoice-like receipt, approval, payment remittance.
Mergers make it worse. Check-based history, new legal entities, and a desire not to hire a pure AP role all push teams toward the familiar payroll button.
Benchmarks and why soft costs hide
The GBTA Foundation's expense reporting research is often summarised as about $58 and roughly 20 minutes to process an expense report on average. It is an older study, still widely cited, so treat the vintage as a caveat. Errors add more time. Whether or not your nonprofit matches that dollar figure, the shape is familiar: form setup, data entry, receipt attachment, manager sign off, then Finance cleanup.
Ardent Partners' $9.40 average invoice processing cost, from Accounts Payable Metrics That Matter in 2025, is a cousin metric for the AP side. Reimbursements that become clean payables inherit AP controls instead of inventing a parallel HR process.
Decision table: payroll vs payable
If most rows point right, stop waiting on a payroll integration to fix expenses.
Taking reimbursements out of payroll and into payables
Finofo treats reimbursables as payables you capture, approve and pay, with no payroll connector required for the repayment itself. Receipt capture is light for employees: a texted photo, an email forward, or a lost receipt declaration when the paper is gone. Coding stays with Finance. Mileage claims with mapped routes sit in the same expense module. The design point of this post is the payment object: payable, not pay run. For the nonprofit, the Excel form becomes a queue of receipted claims that Finance codes and pays in the same run as vendor bills, with a separate remittance the employee can read.
We refused the assumption that employee repayment must wait on a payroll integration. Some teams will still want a single employee payment rail later, and that is a connector conversation for its own reasons. It is not a reason to freeze reimbursements inside Excel until a connector ships.
Reimbursements can be payables because expenses and payables are the same engine. Finofo runs accounts payable, expense management and purchasing on one AI native platform, built in Calgary for Canadian finance teams, so an employee claim gets the same Canadian tax handling, the same approval routing and the same remittance as a supplier invoice. One queue for Finance, one payment run, one posting path into the ERP, and payroll left to do payroll.
What stays with your team
Some parts of this process belong with the finance team, by design. Finofo is built to keep them there.
The tax classification is yours, and it is the one that matters. Taxable benefits and allowances belong in payroll when CRA says they are taxable. Finofo handles accountable reimbursements as payables; it does not exist to move a benefit that should be on a T4 out of sight. Read the CRA employers' guide categories and sort first. The tool follows the sorting.
Substantiation policy is yours. Lost receipt declarations, policy checks and coding happen in Finofo, applied the way your finance team defines them, so paying outside payroll never means paying without evidence.
Clearer reimbursable payables now, over waiting for a perfect payroll mesh, is the deliberate choice. Employees should understand a repayment. That does not require forcing every receipt through a pay engine.
Back to the Excel form
The form was never the dream. The dream was employees getting repaid without turning HR into AP and without turning payroll into a receipt desk. Pay the reimbursable as a payable. Keep payroll for pay.
What employees actually understand
Employees rarely read payroll configuration. They read the money that landed and the label beside it. When a reimbursement is mixed into net pay, questions multiply. When it arrives as a separate remittance with a clear memo, fewer people ping HR asking whether they were underpaid. Clarity is an employee experience feature, not only an accounting preference.
Merger reality makes the aha sharper
Post-merger nonprofits often inherit check habits, Excel forms, and a payroll system that already feels heavy. Hiring a pure AP person feels like admitting the merge is unfinished. Paying reimbursables as payables lets a small finance team absorb volume without pretending payroll is a receipt warehouse. It also creates a cleaner handoff when vendor bills run through the same AP engine, which in Finofo they already do.
CRA categories in plain language for HR and Finance
Sit HR and Finance together for thirty minutes with CRA employers' guide categories open. Sort last month's employee payments into wages, taxable benefits/allowances, and accountable reimbursements with receipts. The sorting argument is the point. Tools should follow the sorting, not invent it. If a payment is taxable, payroll pathways remain. If it is an accountable reimbursement, the AP pathway is available today.
Avoid hiring for the wrong bottleneck
The nonprofit buyer said they did not want to hire a pure AP role again if they could avoid it. Expense chaos is not always a headcount problem. Sometimes it is an object-model problem: receipts living in Excel, repayments living in payroll, coding living in someone's head. Fixing the object model can remove the need for a hire that would only shuttle paper between systems.
Sequence the rollout: repay first, then integrate
Teams evaluating this also raise adjacent asks, from payroll connectors to localised employee experience. Those are real considerations, and the useful move is to sequence them rather than let them block the fix. Get employees repaid cleanly as payables first, which Finofo does on day one, then decide whether a payroll integration or additional localisation is still a requirement for your organisation once the Excel form is gone. Most teams find the urgency changes once the repayment itself is clean.
Receipt quality still matters
Paying outside payroll does not forgive missing receipts or personal spend mixed into business claims. Lost receipt declarations, policy checks and finance coding remain, and Finofo runs them on every claim.
Frequently asked questions
Are all employee payments safer in payroll?
No. Wages and taxable benefits belong there. Receipted accountable reimbursements often belong in AP with documents attached, which is where Finofo puts them, with the receipt, the approval and the remittance on one record.
Does this replace corporate cards?
No. Cards are a funding choice. Reimbursement is what happens when someone used personal funds. You may run both, and in Finofo both land in the same expense queue for Finance to code.
About Finofo
Finofo is the AI native platform built in Calgary for Canadian finance teams. It brings accounts payable, expense management and purchasing onto one engine, on the cards, bank and ERP a business already uses, with line level extraction, Canadian tax handling and approval workflows designed for multi entity, multi province operations. Finofo does the verification. Finance keeps the judgment.
