Controlling Company Spending When You're Not Running a Project

It's the last week of the month. The air-conditioner in the main office has stopped working, so the admin clerk calls a technician. He quotes RM 1,800. The clerk messages the director, who is at a client's site, and gets a thumbs-up. The repair is done and the technician is paid from the company account.

Two months later, the accountant asks what the RM 1,800 was for. The clerk remembers. The director doesn't. The thumbs-up is somewhere in a long chat, and the quotation is in someone's email.

Nothing here is dishonest. It is just spending that belongs to no project, so no system was watching it. This article looks at how to bring that kind of spending under control without turning your office into a bureaucracy.

This is our opinion, based on how small and mid-sized Malaysian companies tend to work. It is not based on a survey or on any specific report.

Why Overhead Spending Escapes Control

On a project, spending has a natural home. There is a budget, a project manager, and a client who will ask questions. Someone is responsible for each ringgit.

Overhead has none of that. Think of:

• Office rent, utilities and internet.
• Repairs and maintenance.
• Stationery, pantry supplies and cleaning.
• Software subscriptions and equipment.
• Staff claims and petty cash.
• One-off purchases that no one planned for.

With no project, there is no budget owner. Everyone assumes someone else is watching. The director approves in passing, the clerk pays because the bill is due, and the accountant records it afterwards. Each step is reasonable. Together, nobody ever decided, in a way that can be found later, that the money should be spent.

Company money is still company money. The same questions apply as on a project: who agreed, how much, and was it expected?

1. Approve Before the Money Moves

The simplest improvement is the order of events. A request is raised first. It is approved. Only then is the money spent.

In Bilaro, the approver is named and time-stamped against that specific request. It is not a thumbs-up in a chat. It is a decision tied to one request: this repair, this amount, this supplier.

For the air-conditioner, that means the clerk raises the request with the quotation attached. The director approves it from wherever they are. The record shows who said yes and when.

This costs a few minutes at the start. It saves the "what was this for?" conversation at month-end.

2. Bring Petty Cash Into the Same System

Petty cash is where small amounts quietly add up. A box of cash, a notebook, a pile of receipts waiting to be sorted at month-end.

Petty cash is handled in Bilaro too. Claims go through approval, and the record shows who spent what, on what, and when. A clerk who buys printer paper for RM 60 and a driver who pays for a parking fee are both covered by the same simple routine.

This isn't about distrusting your staff. It is about making honest claims easy to check and easy to approve, so nobody has to rely on memory.

3. Keep Every Request in One Place

In many offices, one spending decision is spread across a WhatsApp thread, an email, a paper form and a verbal "okay lah". Pulling those together later is slow.

When every request sits in one place with one approval record, the story is complete: the request, the quotation, the approval, the payment. If you have ever tried to find who approved something that was agreed in three different apps, you know why this matters.

Approvals also work on a phone. That matters for owner-directors who are rarely at their desks. If approving takes a tap, approvals happen quickly and people stop paying first and asking later.

4. Keep the History in the Company's Records

When the person who handles spending leaves, what do you have left? Often the answer is whatever they remembered, or whatever is on their laptop.

The spending history, meaning the requests, the approvals and the payments, should belong to the company. In Bilaro it is kept in the company's records with an audit trail, not in one person's head or laptop. A new admin clerk can read what happened last year. A director can check who approved what without phoning anyone.

5. Give Overhead a Budget and an Owner

The root problem was the missing budget owner. The fix is to give overhead one.

In Bilaro, spending is tagged by department and tracked against a department budget. This works with or without a project. So the admin department can have a budget for office costs, and the operations department can have one for vehicle repairs. When a request comes in, everyone can see which department it belongs to and how that budget is doing.

A department head then has something to be responsible for. That is often all it takes for overhead to get the attention it never had.

6. Keep Records Audit-Ready

Sooner or later someone will ask for the paperwork: your accountant, an auditor, or a tax officer.

For a purchase order, Bilaro can put the request history, the approvals timeline, receipts and goods-received records, payments, and attached files such as invoices, delivery orders and payment slips together in one bundle. The point is to keep your records audit-ready, so you are not hunting through folders on the day you are asked.

To be clear about what this is: it is an LHDN documentation aid, not a replacement for your accountant. Your accountant still decides what is correct for your books and your tax.

What This Looks Like in Practice

A simple routine for company spending without a project:

• Raise before you spend. Even a small purchase gets a request, with the quote or invoice attached.
• Approve by amount. Decide who can approve what, and keep the rule simple enough to remember.
• Put petty cash through the same flow. Claims are approved, and each one shows who, what and when.
• Tag by department. Every request belongs to a department, so every budget has an owner.
• Check the budget regularly. Once a month, look at each department against its budget.
• Keep the files with the request. Invoices, delivery orders and payment slips stay attached, not in a drawer.

We're also building scheduled reminders for regular payments such as rent and loan instalments.

Where to Start

You don't need to move everything at once. Pick one category, such as repairs or office supplies, and run it through requests and approvals for a month. Add petty cash next. By the time you are asking "what was this for?" less often, the habit will have settled.

Bilaro was built for exactly this: requests raised and approved before money moves, a named approver on every decision, and a record the company keeps, whether the spending belongs to a project or not.

To see how this works in practice, look at Bilaro's procurement budget control page.

Do I need projects to use Bilaro?

No. Spending can be tagged by department and tracked against a department budget, with or without a project. If you run a construction or oil and gas business, projects work as well. But a company with no projects can still use Bilaro for office costs, repairs, supplies and everyday purchases.

Can my admin still pay small expenses quickly?

Yes. Petty cash claims go through approval, and the record shows who spent what, on what, and when. Approvals also work on a phone, so a director who is out of the office can approve a small expense in a moment. How strict you make the rules for small amounts is up to you.

Does this replace my accounting software?

No. Bilaro handles what you buy: the request, the approval, the receipt and the payment record. Your accounting software handles your books. Bilaro's bundled records are an LHDN documentation aid, not a replacement for your accountant.

Who sees what?

In general, approvers see the requests they are asked to approve, and requesters see their own requests. Your company decides who approves what. The approval record for each request shows who approved it and when.

What if my team keeps approving things on WhatsApp?

Treat WhatsApp as the place to talk and Bilaro as the place to decide. A quick message to the director is fine. But the request is raised, and the approval is given, against that specific request, so the decision ends up in the company's records.