What happens if a request would overspend?

It is refused at approval, with the numbers: what was requested and what was available. Available is what is left after other requests already waiting for a decision are held back — so two people cannot each be told there is room for the same money.

Can I top a budget up without rewriting it?

Yes. Register it as income and the available amount rises; the planned figure the budget was approved on does not move. Income needs its own approval, and a budget has to allow income before any can be registered against it.

Whoever the budget names, in the order it names them. Nobody sets up a path per request — the people who must sign it are read from the budget the spend is charged to, at the moment it is raised. Each step has a deadline.

What happens when an approver is on leave?

The step escalates — to a named person, to whoever is available in a group, or up the management chain. Public holidays come from the calendar you already keep, and personal leave is picked up too.

OrgExp SEE, SIGN, SETTLE

Budgets · Approvals · Spend · Payments

Every spend approved before it happens

The budget holds, the chain signs, the record stays put.

OrgExp holds the budget, sends the request to the people who must sign it, checks what is actually left, and keeps a record of the decision that cannot be edited away. What is left is a number, not an opinion.

Start free trial → See how it works

On the web and on your phone · approvals wherever your approvers are

The record recorded

{{ e.code }}

{{ e.date }} · {{ e.line }}

{{ e.value }}

entries cannot be duplicated or deleted
a wrong entry is fixed by a compensating entry

FY26-OPS-TRAVEL OPERATING 01 Apr 26 — 31 Mar 27

Planned

500,000

Income

50,000

Spent

{{ spentText }}

Available

{{ availText }}

          {{ pendingCount }} pending·
          {{ reservedText }} reserved·
          {{ freeText }} free to commit
        

{{ message }}

Available is planned + income − spent. Pending requests are held back but not yet charged — which is the number a spreadsheet never has. Illustrative figures.

Nobody overspends by accident

A request is checked against what is left after other pending requests are counted. Approve the one that fits; the one that does not is refused with the figure that refused it.

Every approval has a name and a time on it

Steps in order, each with a deadline, each decided by the person it went to. Refusals carry a reason. None of it is reconstructed from an inbox six months later.

The record cannot be quietly corrected

Entries cannot be duplicated or deleted. A wrong entry is fixed by a compensating entry, which means the history of a budget is the history of a budget.

One request, three desks, one record

The person raising it sees what is genuinely left. The approver sees where the request is and what happens if they sit on it — on their phone, if that is where they are. Accounts works a queue, with the slip attached.

New spend request draft

Budget line item

FY26-OPS-TRAVEL — Travel & field visits

Amount

25,000

Type

Advance Settlement

Allotted on this line5,50,000

Held by others15,000

Available to you1,25,000

Who signs it EXP/26/0117

{{ s.role }}

Sits past the deadline → escalates to whoever is free in Treasury. Weekends and your holiday calendar are not counted.

Payments to approve · 1

{{ p.ref }} · {{ p.proof }}

{{ p.amount }}

{{ p.state }}

Approve Cancel registered ≠ paid

Illustrative figures.

The flow

Declare it, request it, approve it, pay it

Four documents, in one direction, each one leaving a record the next one depends on. Nothing here is reconstructed from an inbox later.

{{ s.n }}

Read the full walk-through →

Product

Budgets that hold. Approvals that route. A record that stays put.

Every line below is something you can watch happen in a demo. Ask us to show you any of it.

{{ c.n }}

The guards

The parts you only care about in month three

None of these are settings somebody has to remember. They are refusals built into the product.

{{ activeGuardNum }} of 06 refusals

What's included

Start with the core. Add the rest when you want it.

Budgets, spend requests and approvals are the part you cannot do without. Everything else is there when you are ready for it, and switching it on later does not mean redoing your setup.

core

Which areas you get depends on the plan →

Optional

Ask what's left without opening anything

The assistant answers budget questions in a chat. It answers as you — you see exactly what you would see in the app and nothing more — and anyone it cannot identify gets no answer at all.

What's left on FY26-OPS-TRAVEL?

Available 1,40,000. Of that, 15,000 is held by one waiting request — so 1,25,000 is free to commit.

And the group travel budget?

That one isn't yours to see.

answered as you · 14:06

What OrgExp is not

We built the part everyone skips — the moment before the money leaves, when something has to decide whether it may, using a number that is correct at that instant.

The questions everyone asks first

Priced per organisation, not per transaction — you are not charged for approving things.

See the plans →

Find out what your budgets are actually doing

Declare one budget, raise one request, and watch the figures move.

Start free trial → Talk to us

No card required · we set it up with you