Enterprise / Operational Controls
Control payment operations without losing visibility.
First Digital Pay is designed to help enterprise teams identify payment activity requiring attention, understand its operational state and manage appropriate organizational actions around the payment workflow.
Organizational controls operate around the FDP transaction lifecycle. They do not replace FDP processing or required controls.
Availability varies by product, jurisdiction, configuration and eligibility.
Operations Queue
- PAY-2026-2311PO-52014
- Workflow state
- Awaiting review
- Payment state
- Created
- Required action
- Action required
- Responsibility
- Reviewer
- Updated
- Updated 29 Sep 2026, 11:42
- PAY-2026-2298INV-88120
- Workflow state
- Information requested
- Payment state
- Created
- Required action
- Information required
- Responsibility
- Finance
- Updated
- Updated 29 Sep 2026, 11:18
- PAY-2026-2290PO-51977
- Workflow state
- Awaiting authorization
- Payment state
- Created
- Required action
- Awaiting authorization
- Responsibility
- Authorizer
- Updated
- Updated 29 Sep 2026, 10:57
Illustrative example
Know what needs attention and what happens next.
- 01
Observe
Identify relevant payment activity.
- 02
Identify
Understand the state and reason attention may be required.
- 03
Assign
Associate organizational responsibility where appropriate.
- 04
Act
Record the applicable organizational action.
- 05
Record
Preserve the workflow event/history.
- 06
Continue
Allow the workflow to progress where applicable.
Recording an organizational action does not automatically cause FDP processing to continue. Processing follows its own lifecycle and required controls.
Bring operational exceptions into view.
- Action required
- An organizational action may be required.
- Information required
- Additional information may be needed within the applicable workflow.
- Awaiting authorization
- The organization's configured workflow may require authorization.
- Processing
- FDP processing remains underway.
- No action required
- The record currently requires no organizational action.
Conceptual states. Final state names remain subject to product review.
Two decisions. Two different responsibilities.
Organization
- Internal workflow
- Responsibility
- Review
- Authorization where configured
- Organizational action
First Digital Pay
- Payment processing
- Required controls
- Processing state
- Settlement relationship
- Record lifecycle
An organizational authorization records the customer's internal decision. It does not constitute FDP processing approval, compliance clearance or settlement approval.
Make responsibility visible.
An enterprise workflow may associate a task or step with an organizational responsibility, so it is clear who is expected to act.
Responsibility describes what someone is expected to do. Permission determines what the system allows them to do.
- Operations
- Monitors payment activity and routine workflow steps.
- Finance
- Reviews commercial and settlement context.
- Reviewer
- Examines a record before it moves forward internally.
- Authorizer
- Records the organization's internal authorization where configured.
- Technical
- Addresses integration or data questions.
Conceptual examples, not finalized roles or permissions.
Understand the action before it is taken.
An action detail view brings the workflow step, the responsibility and the separate payment, processing and settlement states together, so the organizational decision is made with context.
Action detail
- Payment reference
- PAY-2026-2290
- Commercial reference
- PO-51977
- Workflow
- Supplier payment review
- Current workflow step
- Authorization
- Responsibility
- Authorizer
- Requested action
- Record organizational authorization
- Payment state
- Created
- Processing state
- Not started
- Settlement state
- Not applicable
- Supporting information
- Invoice INV-88102, review note
Illustrative actions shown in this example: Review, Return, Authorize.
Illustrative example. Actions are shown for explanation only. An authorization would record an organizational decision only.
Every organizational action should leave context behind.
Workflow history is designed to be append-oriented: new events are added rather than earlier events being overwritten.
- Current workflow state
- Where the workflow stands now. Example: Completed.
- Workflow history
- The sequence of events that led there.
- 09:12Workflow created
- 09:14Responsibility assigned · Reviewer
- 09:41Review recorded
- 09:43Information requested · Supporting invoice
- 10:20Information received
- 10:52Authorization recorded · Organizational decision
- 10:53Workflow progressed
Illustrative example. Not a representation of legal immutability or regulatory audit compliance.
Route attention to the appropriate responsibility.
Assignment associates a record requiring attention with the organizational responsibility expected to act on it. How assignment is configured, and whether any part of it is automated, remains a product decision.
Workflow control does not rewrite transaction reality.
- Cancelling an organizational workflow is not necessarily the same as cancelling a payment.
- Withdrawing an authorization does not necessarily reverse processing that has already occurred.
- Cancelling a workflow cannot be presented as reversing a completed settlement.
- Transaction and workflow states remain distinct throughout.
One place to understand what needs attention.
Operations Queue · Showing all records
| Reference | Commercial ref. | Responsibility | Workflow state | Payment state | Settlement state | Attention reason | Updated |
|---|---|---|---|---|---|---|---|
| PAY-2026-2311 | PO-52014 | Reviewer | Awaiting review | Created | Not applicable | Action required | 11:42 |
| PAY-2026-2298 | INV-88120 | Finance | Information requested | Created | Not applicable | Information required | 11:18 |
| PAY-2026-2290 | PO-51977 | Authorizer | Awaiting authorization | Created | Not applicable | Awaiting authorization | 10:57 |
| PAY-2026-2277 | INV-88031 | Operations | Completed | Processing | Not yet allocated | Processing | 10:31 |
| PAY-2026-2264 | PO-51930 | Operations | Completed | Processed | Allocated | No action required | 09:05 |
- PAY-2026-2311Action required
- Commercial ref.
- PO-52014
- Responsibility
- Reviewer
- Workflow state
- Awaiting review
- Payment state
- Created
- Settlement state
- Not applicable
- Updated
- 11:42
- PAY-2026-2298Information required
- Commercial ref.
- INV-88120
- Responsibility
- Finance
- Workflow state
- Information requested
- Payment state
- Created
- Settlement state
- Not applicable
- Updated
- 11:18
- PAY-2026-2290Awaiting authorization
- Commercial ref.
- PO-51977
- Responsibility
- Authorizer
- Workflow state
- Awaiting authorization
- Payment state
- Created
- Settlement state
- Not applicable
- Updated
- 10:57
- PAY-2026-2277Processing
- Commercial ref.
- INV-88031
- Responsibility
- Operations
- Workflow state
- Completed
- Payment state
- Processing
- Settlement state
- Not yet allocated
- Updated
- 10:31
- PAY-2026-2264No action required
- Commercial ref.
- PO-51930
- Responsibility
- Operations
- Workflow state
- Completed
- Payment state
- Processed
- Settlement state
- Allocated
- Updated
- 09:05
Illustrative example. No live queue, filters or actions.
Controls surround the transaction.
Enterprise control layer
- 01Workflow
- 02Step
- 03Responsibility
- 04Action
FDP transaction layer
- 01 · INVCommercial reference
- 02 · PAYPayment
- 03 · PRCProcessing
- 04 · STLSettlement
- 05 · RECReconciliation
Conceptual. Workflow, payment, processing and settlement states remain separate.
Operational responsibility is only part of the control model.
Operational Controls identifies what needs attention and what organizational action may be required. Approvals & Access will address who is permitted to perform those actions within the FDP environment.
Explore Approvals & AccessBring structure to payment operations.
Tell us how your organization manages payment review, operational responsibility, settlement visibility and exceptions today.
Availability varies by product, jurisdiction, configuration and eligibility.