Benefits budgets and expense reimbursements without the Slack-DM chaos

Receipt photos in a DM are a system — a bad one

Most small IT companies do offer benefits — a learning budget, sport, equipment — and do reimburse work expenses. What they don't have is a flow. The real one looks like this: the budget lives in a spreadsheet one person understands; requests arrive as DMs to HR or the founder; a receipt photo lands in a thread; someone replies "ok"; and the accountant hears about all of it at month-end, as a forwarded screenshot.

Every failure mode of that setup is predictable:

• "Did we approve this?" — the approval was a chat message, so nobody can tell approved from merely mentioned.
• Paid twice, or never — the same receipt forwarded in two threads, or an "ok" that no one turned into a transfer.
• Budgets nobody reconciles — the spreadsheet says one thing, the bank statement another, and the difference surfaces in December.
• The unanswerable employee question — "how much of my learning budget is left?" requires archaeology instead of a page.

None of this is anyone's fault. DMs are just the wrong tool for money.

What a lightweight benefits + expenses flow needs

You don't need an ERP. You need five things, each small:

• Named budgets people can see. Per-category annual allowances (learning, sport, equipment) with a self-serve "how much is left" — a benefit nobody can check is a benefit HR re-explains in DMs.
• One intake path. A request carries the amount, the category, and the receipt file in a single submission. No receipt, no request — attached at submit time, not chased at month-end.
• An explicit approval that leaves a record. Who approved, when, and — for rejections — why. "Ok" in a thread satisfies none of those.
• A paid step separate from approval. Approval means "the company owes this"; paid means "it left the account". Collapsing the two is how items get lost between yes and money.
• Policies that fire before the money is spent. Per-category limits and rules should warn at submission, not become an argument after the fact.

Add an audit trail on top — money records are exactly the kind of thing you want answerable a year later.

The flow: budget → request + receipt → approve → reimburse

The whole pipeline is four stages:

1. Set the budgets. Define categories with an annual allowance and eligibility rules (many companies gate benefits until probation ends). Publish them where employees can see their own remaining balance.
2. Request with the receipt attached. The employee files amount, category, a short description and the receipt in one go. The balance is visible before filing, so "would this even fit my budget?" answers itself.
3. Approve or reject, with a reason. The approver sees the request next to the remaining budget and any policy warnings. Rejections carry a reason back to the requester — silence is how trust erodes.
4. Reimburse and close. The accountant works one queue of approved items, pays through the normal channel (payroll or a transfer), and marks each item paid with a reference. A paid item stops being anyone's open question.

The point isn't ceremony — each stage is a few clicks. The point is that every item is always in exactly one known state: pending, approved, paid, or rejected. That single property kills the DM archaeology.

Separation of duties: requester, approver, payer

Small-company informality is fine for lunch orders and fatal for reimbursements. Three rules, all cheap:

• Nobody approves their own request. Not HR's own gym receipt, not the admin's conference ticket. Whoever files it, someone else signs it.
• Money approvals shouldn't sit with line managers. Time-off is a manager's call — they own the delivery plan. Reimbursements are different: a manager approving the team dinner they attended, or gear for their own project, is precisely the awkward case. Route money to the HR/finance side.
• Approval and payment are two acts, ideally two people. The approver commits the company; the payer moves the money and records the reference. If one person wears both hats today, keep the steps separate anyway — the structure outlives the headcount.

At ten people this can feel bureaucratic. It's three clicks — and it matters the first time an amount is questioned, an auditor asks, or a dispute needs the record rather than someone's memory.

How Helia HR does this

The Benefits & Expenses pack ($1.50/employee/mo — see pricing) implements the flow end to end:

• Annual benefit budgets per category — you define the categories and allowances, with an optional "after probation" eligibility gate. Every employee sees a live balance: used, pending, remaining.
• Requests with the receipt attached — the file uploads to private storage and stays tied to the request; the approver has it one click away.
• Expense reimbursements for out-of-pocket spend — category, amount in its original currency, date incurred, receipt. Travel, equipment, client meals, training and more.
• Receipt OCR that pre-fills the numbers — it reads the photo or PDF and drafts the vendor, total, currency and date, leaving a field blank rather than guessing. A human confirms before anything counts. It's part of Helia AI, and the workspace owner can switch it off globally or per feature.
• Expense policies that warn early — per-category limits and vendor rules lint every submission; the warnings appear at submit time and again in front of the approver before sign-off.
• Separation of duties by design — approve, reject and mark-paid live with the HR/admin chain (deliberately not line managers), nobody can action their own request, and the state machine only moves forward: a rejected or already-paid item can't quietly become payable again.
• A structured queue for the accountant — approved-not-yet-paid items in one list, closed by marking paid with a payment reference. Every transition is audit-logged and the requester is notified.
• Payroll pickup — approved-but-unpaid reimbursements flow into the monthly payroll export automatically, and drop out once marked paid. Nothing falls between the tools.

New workspace? The getting-started guide covers the setup order.

FAQ

Shouldn't the line manager approve their team's expenses?

It's common, and it's the weakest link in most setups — managers approve spend they're close to (their team, their project, sometimes their own dinner). Keeping money approvals with HR/finance while managers keep time-off is a cleaner boundary, and it's the one Helia ships.

What about receipts in a different currency?

Expenses keep their original currency. When figures need to come together — in the payroll export or reporting — they're consolidated to your reporting currency with an explicit flag if a rate is missing, rather than silently converted or silently dropped.

Does the OCR decide amounts on its own?

No. It drafts vendor, total, currency and date from the receipt, and it's instructed to leave a field blank rather than guess. A person confirms before the amount counts against anything — and the owner can turn the feature off entirely.

What counts against a benefit budget?

Approved and paid requests consume the budget. Pending requests are shown separately as an "if approved" figure, so both the employee and the approver see the true remaining amount before the next yes.

How does the money actually reach the employee?

Helia doesn't move money. The accountant pays through the normal channel — payroll or a bank transfer — and marks the item paid with a reference. Until then the approved amount rides along in the payroll export so it can't be forgotten.