OrgExp SEE, SIGN, SETTLE
Product

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

OrgExp sits between somebody wanting to spend and the money actually leaving — and it is allowed to say no. Every line on this page is something you can watch happen in a demo. Ask us to show you any of it.

01

A real spend limit

Every approval is checked against what is left after other pending requests are held back — so two people are never told there is room for the same money. A request that would overspend is refused with the figure that refused it.

02

A record that stays put

One entry per approved line, dated and numbered, tied to the request that caused it. It cannot be duplicated and it cannot be deleted: a wrong entry is fixed by a compensating entry, so the history of a budget is the history of a budget.

Structured budgets

Categories and line items with their own figures and dates, built from reusable templates — so a new year is not a new week of typing.

Advances and settlements

A settlement names the advance it draws down, and only the difference charges the budget — because the advance already did.

Income that raises the ceiling

Money arriving raises what is available without rewriting the plan the budget was approved on. Off unless you allow it, with its own approvers.

Payment capture with proof

Method, date, reference and the slip itself. Registering a payment and approving one are different jobs held by different people.

Multi-level approvals

Steps in order, deadlines in working days, refusal reasons. Nobody sets up a path per request.

Escalation that is arranged, not hoped for

Working days only, holidays skipped, chains that vary by amount, deputies and backups for people who are away.

Approve from your phone

The decision where the approver is, with what is being asked for and what is left on the line in front of them.

Summaries and reporting

Daily and weekly digests of what is pending and overdue, and reporting on how long decisions actually take.

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.

01
A group is a tree, not a list.

Spend against your own company's budget or one above you. Never a sibling's — and a parent-company approver can still sign off a subsidiary's.

02
Approving twice is impossible.

Only a request that is waiting for a decision can be approved, so a second click cannot charge the budget twice.

03
A multi-line request cannot slip through.

Line two is checked against what line one just consumed, so a request that collectively overspends is refused on the line that breaks the limit.

04
Dates cannot be in the future.

Neither a spend request nor income can be dated forward.

05
A request is not counted against itself.

Which sounds obvious until it is not, and a legitimate request is refused for want of twice the budget.

06
Permissions are real, not hidden buttons.

Every right that matters — approving a payment, deciding a step, acting across companies — is checked where it cannot be worked around.

Adoption

You do not need all of it on day one

Three areas are the part you cannot do without. The other four switch on when you are ready, and turning one on later does not mean redoing your setup.

See what's included →
3 of seven areas, to start
01 Budgets core
02 Spend requests core
03 Approvals core
04 Income add later
05 Payments add later
06 Mobile add later
07 Assistant add later

See it refuse a request it should refuse

The fastest way to understand this is to try to overspend on purpose.

Start free trial → Talk to us
No card required · we set it up with you