Finance & Accounting

Spend approvals that survive an audit

Thresholds, delegations and segregation of duties, written once in plain language and enforced on every request.

Request a demo

What this usually looks like today

Approval limits live in a policy document nobody reads and a spreadsheet nobody trusts.

Month-end close stalls because three requests are sitting in someone's inbox, unread.

When an auditor asks who approved a $40,000 invoice, the answer is an email thread.

Workflows

What finance & accounting teams run in Branchsolve

Each of these is a description away. None of them is a template you have to adopt.

Purchase requisitions

Amount and cost centre decide the chain. Under the limit approves on submission with the reason recorded.

Capital expenditure

Business case, payback period and asset class collected up front, then routed to controller, CFO and — above a threshold — the board sponsor.

Vendor onboarding

Tax forms and banking details as required attachments, with procurement and finance reviewing in parallel.

Expense exceptions

Only out-of-policy claims route for judgement. Everything inside policy clears without a queue.

Journal entry sign-off

Preparer submits, reviewer approves, and the requester can never approve their own entry.

Credit and write-off authority

Escalates by exposure, with the customer balance collected on the form so the condition can read it.

Routing

Thresholds you can see before you commit

Branchsolve derives the boundary cases from the workflow’s own rules and shows you where each one lands. Nobody types this table out — it falls out of what you described.

Purchase requisition

$99Approved on submission
$100Manager
$1,000Manager, then Finance
$10,000Manager, then Finance, then CFO
$10,000 with a contract…plus Legal, reviewed in parallel

Questions we get from finance & accounting teams

Can we enforce segregation of duties?

It is enforced by the engine, not by configuration. A requester can never approve their own request, and nobody can decide twice on the same pass.

What happens when an approver is on leave?

A step can carry an SLA. On breach it can remind or escalate to additional approvers. Auto-approve and auto-reject exist too, but they require an explicit second confirmation before they can be published.

Will this connect to our ERP?

Not yet as an automatic write. A workflow can include a step that says 'create the PO in the ERP', which a person marks complete — so the process is honest about the handoff instead of pretending it does not exist.

Your process doesn’t have to be on this list

If you can describe it, Branchsolve can run it. Bring the one that causes the most arguments.