Approval

What it is

Approval is AgFlow's credit authority module: the mechanism that defines, phase by phase, who within the company has the authority to approve (or reject) an operation, and up to what value that authority applies. It is the governance step that ensures no credit decision moves forward without review from someone qualified to decide on that amount.

How it works in practice

When a phase in the process requires approval, the company configures an authority level — a list of people authorized to decide, tied to a value limit. Two decision logics are available:

Horizontal: any approver on the list can decide alone. A single "yes" (or "no") from any authorized person is enough to move the phase forward. This model favors speed — useful when several managers share the same authority and no double-check is required.

Vertical: the decision follows a hierarchical sequence — each approver in the chain must weigh in, in order, before the operation can advance. This model favors control — useful when the value of the operation calls for multiple levels of validation, from analysts up to leadership.

A company can combine multiple authority levels within the same phase, each covering a different value range — for example, a horizontal authority for smaller operations and a vertical one, with more approvers, for operations above a certain threshold.

Why it matters

Without an authority module, the risk is obvious: someone without the right authority (or without visibility into the risk involved) approves a credit decision on their own that should have passed through more eyes. Approval exists to close that gap — it is the final checkpoint before a credit is actually granted, ensuring the level of scrutiny applied to each decision is proportional to the value and risk of the operation. This protects the company from undue exposure and gives every credit decision a clear, traceable record.

Simplified example

{
  "title": "Rural Credit Authority",
  "continueAfterRejection": false,
  "approvers": {
    "type": "alternative",
    "hierarchy": [
      { "level": 1, "quantity": 1 }
    ]
  }
}

This snippet is illustrative only: type also accepts the value cumulative, which activates the vertical model, and each hierarchy level normally carries the full list of approvers authorized at that level. For the complete technical specification of this domain — every field, conditional rules, and full examples — see the 🇺🇸 English tab.

What it is#

How it works in practice#

Why it matters#

Simplified example#

What it is

How it works in practice

Why it matters

Simplified example