RBTERP

Guides › Approvals and Workflows: Who Signs Off What

Approvals and Workflows: Who Signs Off What

RBTERP team · · 3 min read

How to design approval rules for purchases, payments and other documents: approval levels, amount limits, delegation, escalation and maker-checker.

RBTERP Purchasing screen: Control what you buy and what you owe

Purchasing in RBTERP, with a sample company and fictional data.

An approval is a second pair of eyes before money leaves or a commitment is made. Too few approvals and mistakes or fraud slip through. Too many and work stops while documents wait in someone's inbox. A good workflow puts approvals where the risk is, and nowhere else.

Where approvals earn their keep

Ask, for each document type: what is the worst thing that could happen if the wrong person made this alone? If the answer is small, you probably do not need an approval.

Designing the rules

Levels

Approvals can come in levels. A department head approves first, then finance, then a director. Each level starts only when the one before it is complete.

Conditions

Most documents do not need every level. A rule such as *director approval only above 100,000* keeps small items moving and puts senior attention on large ones.

Who approves

An approver can be a named person, anyone holding a role such as department manager, or anyone holding a permission such as finance management. Roles and permissions are better than names: when someone leaves, the rule still works.

Quorum

Some decisions need more than one approver at the same level, such as two directors for a very large payment.

Maker-checker

The person who made a document should not approve it. This one rule, called maker-checker or segregation of duties, prevents a large share of internal fraud. Build it in, so nobody has to remember it.

When the approver is away

Approvals in RBTERP

Approvals and Workflow: your inbox, all approvals, workflows, delegations and notifications
Approvals and Workflow: your inbox, all approvals, workflows, delegations and notifications

RBTERP has one approval engine for every module's documents, under Approvals in the sidebar.

Start simple

  1. Begin with one workflow: supplier bills, approved by someone other than the person who entered them. See approving supplier bills.
  2. Add an amount threshold for payments once the first one runs smoothly.
  3. Review the approval statistics after a month. If documents wait days for approval, the rule is too broad or the approvers too few.

More guides

Purchasing

Approving Supplier Bills Before They Are Paid

Why supplier bills need a second person's approval, what the approver should check, and how to set up bill approval without slowing payments.

16 November 2026 · 3 min read

See RBTERP working with your own business

Pick a plan and request it, or tell us about your company and we will help you choose.