INVARIANCE | Arc
MenuClose
Commitment Authority

Who or what may bind the organization to this commitment?

Payments, purchases, contracts, and trades can create obligations. Authority Control evaluates each proposed commitment against the authority the organization has established before it takes effect.

The problem

A technically valid commitment may still fall outside the authority granted for it.

The expected person can use an approved device, complete a workflow, and provide a valid signature while exceeding the authority delegated for the result. Those checks remain valuable. They do not, by themselves, settle whether this commitment falls within the organization’s established limits.

The commitment passes every existing check while the authority question remains unresolved.
What each check answers

Valid identity, access, and workflow can leave the authority question unresolved.

  • IdentityWas this the expected actor?
  • AccessCould the actor use the system?
  • WorkflowWere the required system steps completed?
  • Signature or instructionIs the artifact or instruction technically valid?
  • AuthorityCould this actor bind the organization to this consequence?

The first four can all be valid while the fifth still requires a determination.

A worked example

Illustrative example: a purchase outside delegated scope.

Proposed commitment · non-budgeted vendor obligation

A procurement manager proposes a vendor commitment above the role’s delegated amount and outside its budgeted categories. The identity, access, and workflow checks pass. Authority for the proposed commitment still requires resolution.

  • IdentityValid. The expected actor, authenticated as themselves.
  • AccessValid. The role is entitled to reach the commitment path.
  • WorkflowValid. Required steps completed and recorded in the system of record.
  • AuthorityAdditional authority required. The amount and the non-budgeted category both fall outside what this role holds.
DeferIn this example, the commitment waits for resolution through the organization’s review process.

In this illustrative configuration, Defer leaves the authority question unresolved for the organization’s existing review process. A durable record preserves the determination.

Illustrative configuration only. The organization’s own thresholds would control.
How it fits what you run

Existing commitment systems stay in place.

Commitment systems continue to create, approve, and execute obligations as designed. Authority Control adds the organizational question of whether this person or system has authority to create this particular obligation.

ERPProcurement systemsTreasury platformsTrading systemsContract systemsE-signatureIdentity and access managementPrivileged access managementApproval workflows
Existing systems remain the execution points. The determination arrives before the commitment binds.