Skip to content

Status

Overview

SARA uses short status codes to represent the current state of a record. Statuses drive what actions are available, who can edit the record, and how it appears in lists and filters. This page documents the system-wide status catalog and how statuses behave across the interface.

For how statuses relate to record lifecycles, see: Workflows & Pipelines


How statuses work in SARA

Every record in SARA has a status. Statuses serve three purposes:

  • Visual indicator — Each status is displayed as a colored badge in the data table, making it easy to scan a list and identify records that need attention.
  • Filter criteria — Status filter badges at the top of each record list let you narrow the view to specific statuses. These filters are dynamic and only show statuses that exist in the current dataset.
  • Action control — The actions available in a record's row action menu depend on its current status. For example, a record in COMP (completed) status typically cannot be edited, while one in INPG (in progress) can.

Note

Each transaction uses only a subset of the statuses listed below. The specific statuses, transitions, and rules for each feature are documented in that feature's Workflow page.


Status catalog

Record lifecycle statuses

These statuses represent stages in a record's lifecycle — from creation through completion or cancellation.

Code Name Typical use
PEND Pending Records awaiting action or review
INPG In progress Records actively being worked on
COMP Completed Finished records (typically read-only)
CANC Cancelled Voided records that are no longer active
FINA Finalized Fully closed financial or administrative records
APPR Approved Records that have passed an approval step
REJC Rejected Records returned or denied during review
WAIT Waiting Records on hold, awaiting an external input or dependency

Catalog and master data statuses

These statuses are used for catalog-type records (customers, suppliers, assets, accounts) that have a simple active/inactive lifecycle rather than a workflow pipeline.

Code Name Typical use
ACTV Active Record is in use and fully operational
INAC Inactive Record has been deactivated (soft delete)

Domain-specific statuses

Some transactions use statuses that are specific to their business domain. These statuses are defined and documented in the corresponding feature's workflow page.

Code Name Used in
TCLS Technical closure Projects
OPEN Open Reconciliation periods, unresolved alerts
CLOS Closed Reconciliation periods
CONF Confirmed Import batches confirmed by operator
DISC Discarded Import batches rejected by operator
RESV Resolved Alerts that have been addressed
IGNR Ignored Alerts explicitly dismissed
UNMT Unmatched Transactions not yet linked
MATC Matched Transactions fully linked
PAID Paid Payment records
IQUO In quotation Purchasing
APDR Pending direction Purchasing
MODI Modified Purchasing
DELV Delivered Logistics, purchasing
UNDL Undelivered Logistics, purchasing
INST In stock Inventory
RETN Returned Inventory, purchasing
DELN Delivered & notified Logistics
PWCR Paid with credit Finance
APFI Pending finance Finance

Status catalog reconciliation

The status catalog is being standardized across SARA. Some statuses listed above may be renamed, consolidated, or reclassified as this process continues. When in doubt, refer to the feature-specific workflow documentation for the authoritative status definitions in each transaction.


How statuses appear in the UI

  • Status badges — Displayed as small colored labels in the data table's status column and in the filter area. Colors provide a quick visual cue (e.g., green for active/approved states, red for inactive/cancelled, yellow for pending/in-progress states).
  • Status filter badges — Checkbox toggles at the top of each record list. Only statuses with at least one matching record are shown. Selecting a badge filters the table to show only records with that status.
  • Row action menu — The dropdown button on each row typically shows the current status as its label. Clicking it reveals the actions available for that record given its status and your permissions.

For the full description of these UI elements, see: Common Features


Statuses and permissions

What you can do with a record depends on both its status and your permissions. For example:

  • A record in INPG may be editable only by users with the edit permission.
  • A record in PEND may show an Approve action only for users with the relevant approval permission.
  • Records in COMP, CANC, or FINA are typically read-only for everyone.

For details on how permissions work, see: Permissions & Access


FAQs

Why don't I see a status filter for a specific status? Status filters are dynamic — they only appear when at least one record in the current dataset has that status. If no records match, the filter badge is hidden.

Can a record go back to a previous status? It depends on the transaction's workflow. Some workflows allow returning a record to an earlier status (e.g., rejection sends a record back to INPG), while others are strictly forward-moving. Check the feature's workflow page for the specific rules.

What happens when a record is cancelled? Cancelled records (CANC) remain in the system for reference and audit purposes but are no longer part of active operations. They are typically read-only.