“Why does reimbursement take three weeks?”

Expense claims workflow

Claims routed by reporting line, coded on submission, and paid from the same record.

Where the delay comes from

Not the approval — the assembly. Claims arrive as forms or emails, somebody codes them, somebody else approves, and a third person schedules payment.

Each handover is a wait, and the person owed money has no way to see where it is.

A claim carries its category and cost centre on submission, so coding is not a separate step. Approval routes by reporting line from Nest, with delegation set on the record so leave does not stall it.

Approved claims post to the ledger and into the payment run without being re-keyed.

How the path works

What changes for the claimant

They can see where the claim is without asking, which removes most of the chasing.

And because petty cash usually exists because reimbursement is slow, fixing this generally removes the need for the float as well.

Nine days, and the ninth is your first close.

Other journeys

Expense claims workflow, answered.

Bring the journey that hurts most.

We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.