Approvals that don't slow you down

Every business needs some approvals. A purchase above a certain amount, a discount larger than usual, a week of leave, an expense claim. Approvals protect your money and your team.

But approvals done badly become the bottleneck everyone complains about: requests waiting in someone's inbox, people approving their own requests to get things done, and nobody knowing who is holding what.

Set limits, not rules for everything

Decide which amounts need a second look and which do not. A small purchase within budget can go straight through; a large one needs one approval; a very large one needs two. The fewer requests that need a person, the faster the important ones get attention.

Never approve your own request

The person who asks should not be the person who approves. For money that leaves the company — payments, large purchases, manual journal entries — a second person should always look.

Keep things moving when someone is away

Approvals stall when the approver is on leave. Let managers hand their approvals to a delegate while they are away, and make it visible who is covering.

Make decisions easy

Show the approver what they need to decide in one place: the amount, the budget left, the reason and the history. A good approval takes seconds, not a meeting.

Approvals in Kluvan today

Approvals already work inside the apps where the money is:

• Procurement: purchase requests go through approval steps, with two approvals above your limit and firm budgets.
• Trade: wholesale orders can need approval, with an optional second person and no self-approval.
• HR & Payroll: leave and other requests reach an approvals inbox, with delegation while a manager is away, and payroll runs with two-person controls.
• Books: manual entries above your threshold need another person's approval.

One approvals inbox for every app — with deadlines and escalation — is coming soon in Workflows.