Canonical: https://deeplight.ae/insights/agentic-workflows-in-practice
[Reading guide](https://deeplight.ae/llms.txt): company facts, services, published articles and optional visual assets.
Author: Sam Patel
Published: 2026-06-16
Format: Markdown representation of the public HTML page. Interactive controls and diagrams are available in the HTML version.

[All Insights](https://deeplight.ae/insights)

# Agentic workflows in practice

Practice 16 June 2026 5 min read

By Sam Patel

Follow three workflows from their evidence to a recorded decision: an invoice exception, a new starter’s onboarding and a customer request. Each shows what agents prepare and what people decide.

## In short

- [**Agents prepare, finance decides** In an invoice exception, agents bring the evidence together and prepare a resolution. A finance reviewer decides what happens next.](https://deeplight.ae/insights/agentic-workflows-in-practice#section-1)
- [**Agents plan, a manager approves** Agents check the starter’s details and draft the onboarding plan. The hiring manager approves access before anything is provisioned.](https://deeplight.ae/insights/agentic-workflows-in-practice#section-2)
- [**A prepared answer, checked by a person** Agents triage the request and draft an answer from approved knowledge. A service adviser checks it and decides whether it can be sent.](https://deeplight.ae/insights/agentic-workflows-in-practice#section-3)
- [**Test the whole workflow** Test representative and difficult cases, and measure routine effort and exception handling separately.](https://deeplight.ae/insights/agentic-workflows-in-practice#section-4)

## Invoice exceptions

A useful agentic workflow starts with a specific piece of work. Here, an invoice does not match the purchase order or goods receipt. Agents bring the evidence together and prepare a resolution. A finance reviewer decides what happens next.

Invoice exceptions are a common problem for finance teams. A mismatch holds up payment until someone traces the invoice, purchase order and receipt by hand. The workflow below shows where agents take on that preparation and where a person keeps the decision; the distinction between preparing work, making a decision and carrying out an approved action matters at every step.

Workflow · Invoice exceptions

### Evidence moves forward.
Finance keeps the decision.

- Invoice
- Purchase order
- Goods receipt

Starts with Invoice mismatch flagged

Outcome Resolution recorded

Ownership and operation

Access · Evaluation · Monitoring · Release

1. Agents Document agent
   Read the evidence
   Hands over: Source-linked comparison
2. Agents Reconciliation agent
   Explain the mismatch
   Hands over: Draft resolution with evidence
3. People Finance reviewer
   Review the resolution
   Hands over: Recorded finance decision
4. Systems Workflow automation
   Update the record
   Hands over: Closed or escalated exception

Exception

Request more evidence or escalate

Finance can ask for further evidence or escalate the case.

- Shared intelligence platform
  Models · Agents · Tools · Knowledge
- Data and distributed systems
  Accounts payable · ERP · Document store

Keep source references and the finance decision with the case. Update only permitted fields. An unresolved discrepancy remains an exception.

The agent cannot authorise payment or change supplier bank details. A changed supplier bank account is held for the existing verification process.

### The controls belong in the workflow.

The comparison uses the invoice, purchase order and goods receipt. Reconciliation adds the agreed matching rules. Finance receives the draft resolution and supporting documents; automation receives an approved resolution. Each handover carries the evidence needed for the next task.

Invoice exceptions, step by step: what each step works from, does, may not do and hands over.

| Step | Works from | Work | Control | Hands over |
| --- | --- | --- | --- | --- |
| 01 · Document agent Read the evidence | Invoice, purchase order and goods receipt | Extract the references and compare line items against the source records. | Uncertain fields stay flagged, with their source document attached. | Source-linked comparison |
| 02 · Reconciliation agent Explain the mismatch | Comparison and agreed matching rules | Identify a price, quantity or missing-receipt exception and draft the next action. | Apply the agreed rules; an unresolved discrepancy remains an exception. | Draft resolution with evidence |
| 03 · Finance reviewer Review the resolution | Draft resolution and supporting documents | Accept the explanation, request more evidence or escalate it. | The agent cannot authorise payment or change supplier bank details. | Recorded finance decision |
| 04 · Workflow automation Update the record | Approved resolution | Update the permitted case fields and notify the responsible team. | Keep the decision and source references with the case. | Closed or escalated exception |

## Employee onboarding

Coordinate HR, IT and the hiring manager around one new starter, with people approving access and resolving exceptions.

Workflow · Employee onboarding

### From signed offer to a ready first day.

Starts with Signed offer received

Outcome First-day plan confirmed

Ownership and operation

Access · Evaluation · Monitoring · Release

1. Agents Intake agent
   Check starter details
   Hands over: Validated starter brief
2. Agents Planning agent
   Prepare the plan
   Hands over: Draft onboarding plan
3. People Hiring manager
   Approve access
   Hands over: Approved access request
4. Systems Workflow automation
   Coordinate tasks
   Hands over: Tracked tasks and first-day summary

Exception

An access request outside the approved role goes to the hiring manager and IT owner.

- Shared intelligence platform
  Models · Agents · Tools · Knowledge
- Data and distributed systems
  HR system · Identity provider · Service desk

Employee onboarding, step by step: what each step works from, does, may not do and hands over.

| Step | Works from | Work | Control | Hands over |
| --- | --- | --- | --- | --- |
| 01 · Intake agent Check starter details | Signed offer and starter record | Check required fields and flag missing or inconsistent information. | Missing details return to HR; the agent does not invent them. | Validated starter brief |
| 02 · Planning agent Prepare the plan | Starter brief and approved role template | Draft the HR, equipment and induction tasks for the agreed start date. | Use the approved role template and retain the source for each task. | Draft onboarding plan |
| 03 · Hiring manager Approve access | Proposed access and equipment | Review the proposed entitlements and any exceptions. | A named person approves access before provisioning. | Approved access request |
| 04 · Workflow automation Coordinate tasks | Approved access request and onboarding plan | Create the permitted tasks and collect their completion status. | Only agreed system actions; failed tasks go to the service desk. | Tracked tasks and first-day summary |

## Customer requests

Connect incoming requests to approved knowledge and case history, so service teams review a prepared answer rather than start from scratch.

Workflow · Customer requests

### A useful response, with the context behind it.

Starts with Customer request received

Outcome Reviewed response sent

Ownership and operation

Access · Evaluation · Monitoring · Release

1. Agents Triage agent
   Triage the request
   Hands over: Categorised case brief
2. Agents Response agent
   Prepare an answer
   Hands over: Source-linked draft response
3. People Service adviser
   Review the response
   Hands over: Approved response
4. Systems Workflow automation
   Complete the case
   Hands over: Response and case history

Exception

A request for a refund outside policy is escalated rather than promised by the agent.

- Shared intelligence platform
  Models · Agents · Tools · Knowledge
- Data and distributed systems
  Shared inbox · CRM · Knowledge base

Customer requests, step by step: what each step works from, does, may not do and hands over.

| Step | Works from | Work | Control | Hands over |
| --- | --- | --- | --- | --- |
| 01 · Triage agent Triage the request | Incoming request and permitted case history | Identify the request type, urgency and missing information. | Sensitive or out-of-scope requests go to the responsible specialist. | Categorised case brief |
| 02 · Response agent Prepare an answer | Case brief and approved knowledge | Retrieve relevant guidance and draft an answer with its sources. | Do not make commitments unsupported by the approved policy. | Source-linked draft response |
| 03 · Service adviser Review the response | Draft answer, sources and uncertainty flags | Check the answer, edit it and decide whether it can be sent. | A person handles exceptions and approves the customer response. | Approved response |
| 04 · Workflow automation Complete the case | Approved response | Send through the agreed channel and update the case record. | Write only to permitted fields and retain the review decision. | Response and case history |

## Test the whole workflow

Start with an operational owner, a clear problem and a process the team can describe. Map the inputs, outputs, decisions and handovers before choosing a model. Agree which records an agent can read, which tools it may use and which actions need a person’s approval.

Then test representative cases alongside the difficult ones: missing evidence, uncertain fields, failed integrations, exceptions and work that should stop. Check whether the proposed answer is grounded in its sources, whether the right person receives the exception and whether every system action stays within its permission.

Compare the whole workflow with the current process, including the review and operating work left to people. Measure routine effort and exception handling separately. A faster draft is useful only if the resulting decision and record are dependable.

Our [workflow mapping guide](https://deeplight.ae/insights/mapping-operational-workflows) explains how to capture that baseline. The [simulation guide](https://deeplight.ae/insights/simulating-agents-in-workflows) includes a calculator for exploring capacity assumptions. Those assumptions need measured inputs and representative tests before they can support a delivery decision.

## Turn an example into a delivery brief

A useful brief names the work, its owner, the available evidence, the permitted actions and the decisions people keep. It also describes how to recognise a successful outcome, how exceptions will be handled and what happens when a tool or integration fails.

Deeplight’s practitioners help organisations do this as [tailored professional services](https://deeplight.ae/services/agentic-workflows). The design, platforms and models follow the organisation’s needs. Foundry supports how we organise the engagement and agent-assisted work.

[Talk to us](https://deeplight.ae/contact)

## Put this thinking to work

[**Programmes** Choose an AI use case or build and test one.](https://deeplight.ae/services/programmes)

## Explore the offer

[**Discovery**](https://deeplight.ae/services/discovery) [**Accelerate**](https://deeplight.ae/services/accelerate) [**Agentic workflows**](https://deeplight.ae/services/agentic-workflows)

## Related reading

[All Insights](https://deeplight.ae/insights)

Strategy

### [Mapping operational workflows: find the steps where agents pay off](https://deeplight.ae/insights/mapping-operational-workflows)

Read the article

Strategy

### [Simulating agents in a workflow: price each step before you build](https://deeplight.ae/insights/simulating-agents-in-workflows)

Read the article
