---
title: "Exception Routing vs Reporting in IFS Cloud"
date: 2026-08-26
description: "A report tells you twelve POs are unconfirmed. A decision tells you which three need a call today. Why IFS Cloud exception routing beats reporting."
author: "Dariusz Mysliwiec"
categories:
  - name: "Blog"
    url: "https://www.ifs-erp.com/blog.md"
---

# Exception Routing vs Reporting in IFS Cloud

Independent IFS Cloud practice · Supply Chain

 
## The difference between a report and a decision and why IFS Cloud should route, not report

 **Key takeaways**

 
- A report tells you twelve purchase orders are unconfirmed. A decision tells you which three need a phone call today — most supply chain reporting only ever delivers the first.
- Volume is not value: forty pages, eighty line items, a dashboard with six charts — the recipient scans it, sees nothing on fire, and moves on.
- A report that requires interpretation is a task you have handed to someone who did not ask for it. A decision that arrives pre-qualified is a gift.
- **Exception routing in IFS Cloud** puts the right three lines in front of the right person at the right time, and never asks them to hunt.

 A report tells you twelve purchase orders are unconfirmed. A decision tells you which three need a phone call today. Most supply chain reporting confuses the two. It delivers volume — forty pages, eighty line items, a dashboard with six charts — and the recipient scans it, notes that nothing is obviously on fire, and moves on. The value was never in the forty pages. It was in the three lines that needed action. But those three lines were buried among thirty-seven that did not, and the person who could have acted on them never saw them at all. Good exception handling does not report. It routes. It puts the right three lines in front of the right person at the right time, and it does not ask them to hunt. This article looks at why reporting defaults to volume, what interpreting a report actually costs, and how to route exceptions in IFS Cloud instead of reporting them.

  ## 1.Why does reporting default to volume?

 Reports are easy to build comprehensively and hard to build selectively. Comprehensiveness is a query: pull every open order, every line, every field. Selectivity requires someone to decide, in advance, which combination of conditions actually matters — and that decision feels like a risk, because leaving something out looks like a mistake later, while leaving everything in never does. So the safe choice, repeated across every dashboard and every export, is to include everything and let the human sort it out.

 The human, of course, is usually the same person the report was meant to save time for. They open it between two other tasks, scroll for a pattern, and either catch the three lines that matter through sheer familiarity with the data, or miss them because today was a busy day. The report did its job — it reported. Nobody decided anything, because nobody was asked a specific question.

  ## 2.What does interpretation actually cost?

 Handing someone a report instead of a decision does not save work. It moves the work, unpaid and unscheduled, onto whoever opens the report next.

 
- **Hidden hunting time.** Every minute spent scanning eighty rows for the three that matter is a minute not spent acting on the three that matter.
- **Diffused ownership.** A report sent to a distribution list is a decision nobody personally owns; everyone assumes someone else already checked it.
- **Delay by design.** A weekly or monthly report means the three-line decision waits for the report’s schedule, not for the moment it actually became urgent.
- **Fatigue that hides the signal.** A recipient who scans forty pages every week and finds nothing eventually stops scanning carefully — exactly when a real exception finally appears.

 A report that requires interpretation is a task you have given to someone who did not ask for it.

  ## 3.How do you tell the difference in IFS Cloud?

 The test is simple: does the output name a person and a next action, or does it name a data set? A Quick Report that lists every open purchase order is a data set — useful, but still a report. A rule that filters that same data set to the handful of orders past a defined threshold, and sends only those to the buyer responsible, is a decision arriving pre-qualified. The mechanics of both are covered in [Quick Reports, Custom Fields and Custom Events compared](https://www.ifs-erp.com/blog/quick-reports-custom-fields-custom-events), and the trigger-and-action pattern behind routing specifically is the backbone of the [SCM automations for IFS Cloud](https://www.ifs-erp.com/blog/automate-scm-processes-ifs-cloud).

 Most instances already have the report. What is usually missing is the second step: a Custom Event that reads the same underlying data, applies the threshold that defines “matters today”, and sends the result to one named recipient instead of publishing it for everyone to interpret.

  ## 4.Reporting versus routing

 The two are built from the same data. The difference is entirely in what happens between the data and the person who has to act on it.

 
|   | Reporting | Routing |
| --- | --- | --- |
| Output | Every row that matches the query | Only the rows past the threshold |
| Recipient | A distribution list | The named person who can act |
| Interpretation needed | Yes, every time it is opened | None — the filter already did it |
| Timing | Fixed schedule, regardless of urgency | As soon as the threshold is crossed |
| Fails when | The reader is busy or fatigued | Never sleeps |

 Keeping the report is often still worth it — it is the audit trail and the occasional deep dive. Routing does not replace it; it removes the requirement that a human read the whole thing to find the part that matters.

  ## 5.How do you turn a report into routing safely?

 Start from a report you already trust, not from a blank page.

 
1. **Pick one existing report.** Choose the one that is opened most often and interpreted the same way each time — that repetition is exactly what routing should absorb.
2. **Name the three-line question.** Write down, in one sentence, what the reader is actually looking for when they scan it. That sentence becomes the filter.
3. **Run the filter in dry-run.** Log what it would have sent for two or three cycles and compare it to what a human actually flagged from the full report.
4. **Route to one named person.** Replace the distribution list with the specific role who owns the action, so the alert cannot be assumed to be someone else’s job.
5. **Keep the report as the record.** Let routing carry the urgency and the report stay as the audit trail and the place to check the wider picture.

 The routing layer is built inside the IFS Extensibility Framework — standard Custom Events, Workflows and PL/SQL — so it sits alongside your existing reports without modifying them or the core, and survives the next upgrade untouched.

 [Book a 30-min call](https://www.ifs-erp.com/book-a-call) [See SCM Automation Pack](https://www.ifs-erp.com/scm-automation-pack)

  ## 6.Frequently asked questions

 What is the difference between exception reporting and exception routing? A report lists everything that matches a query and leaves interpretation to whoever reads it. Routing applies the interpretation in advance — a threshold, a filter, a named recipient — so what arrives is already a decision, not a data set to search through.

   Should we stop building reports altogether? No. Reports remain valuable as an audit trail and for the occasional deep dive. The change is to stop relying on a report as the primary mechanism for surfacing something urgent, and to route the urgent cases separately.

   How do we decide what counts as the “three lines that matter”? Watch what an experienced person actually flags from the full report over a few cycles, then turn that pattern into an explicit threshold. The dry-run period exists precisely to test that the filter matches what a human would have chosen.

   Is this update-safe? Yes. Routing is built with standard Custom Events, Workflows and PL/SQL inside the IFS Extensibility Framework, sitting alongside existing reports rather than modifying the core — nothing here is at risk from the next R1/R2 release.

  ## 7.About the author

 **Dariusz Myśliwiec** — 25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally — you talk to the consultant who builds it, not a sales layer.

 **Selected clients:** Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.

 IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

  ## Turn your busiest report into a routed decision

 Pick the report your team dreads opening and I will show you, on a dry-run, what routing it would actually send — and to whom. On a 30-minute call we will map the first threshold together — fixed price, dry-run before anything sends.

 [Book a 30-min call](https://www.ifs-erp.com/book-a-call)