Approvals
Approvals in Orbit are one shared system, reused by every module that needs a sign-off step — not a separate implementation per module. A record enters an approval workflow, sits pending until its configured approvers decide, and only then takes effect.
What can require approval
Section titled “What can require approval”- Purchase Orders
- Sales Orders
- Payment/Receipt Vouchers
- Journal Entries
- Asset Transfers
- Asset Checkouts
- POS Void/Refund
- Payment/Receipt Voucher Void
- Sales Order Cancellation
An approval rule is configured per entity type:
- Threshold — an optional value above which the rule applies (e.g. only Purchase Orders over a certain amount need sign-off; smaller ones go through untouched).
- Steps — an ordered list of specific approvers. Each step is a named person, not a role or group, so a rule reads as an explicit chain: this person, then that person.
- Active/inactive — a rule can be turned off without deleting its configuration, useful for temporarily disabling a sign-off requirement.
Requests
Section titled “Requests”When a rule applies, submitting the record creates an approval request carrying the requester, a note, and one action per configured step. Each action resolves independently to Approved, Rejected, or Skipped; the request as a whole is Pending, Approved, Rejected, or Cancelled. Approvers see what’s waiting on them in their notifications, the same place mentions and assignments show up.
Where it shows up
Section titled “Where it shows up”Every module wires in the same way: the record’s own detail page shows its approval status inline, and the underlying request/decision UI is identical everywhere it’s used — approving a Purchase Order and approving an Asset Transfer are the same interaction, just against different underlying records.
See also: Users & Permissions for role/permission setup, and each module’s own page (Sales, Purchase, Assets, POS) for what triggers an approval in that module specifically.