Process Automation
FyerX digitises operational processes that still depend on spreadsheets, shared inboxes and repeated data entry. We help the people doing the work choose which steps are stable enough to automate and which exceptions need a person with authority to decide.


When to bring in FyerX
One reason to review supplier onboarding is a change to payment details after the original reviewer has approved the supplier. It raises questions about supplier identifier, approval timestamp, bank-change flag and assigned owner, the groups affected and the action each can take when something goes wrong. Our starting point is the supplier registration and change request. We trace it from submitted registration to activated supplier record with the people who own those decisions. The result gives your operations process owner a specific first release, a testable operating outcome and a record of dependencies. For this example, the practical standard is simple: the operator can show who approved the final payment details.
Assessing real effort
Measure time spent on both the happy path and exceptions. Count the work moved to other teams as well as the work removed from the original team. A faster intake form can still leave the business worse off if downstream staff must repair incomplete data.
Process discovery
Observe a case from receipt to completion and identify where people rekey data or wait for permission. Ask experienced operators to show their spreadsheets and the exceptions missing from the written procedure. Bring the supplier registration and change request and its history to the design discussion. Check supplier identifier, approval timestamp, bank-change flag and assigned owner against the policy in effect at the time. For a case involving a change to payment details after the original reviewer has approved the supplier, ask how the team currently recognises that the decision is complete. Agree whether the person who changes protected details cannot independently release them.
Low-code workflows
Build an intake form, task queue and approval history in the agreed platform. Define delegation and escalation so a request can move when the usual approver is absent. Include supplier administrator, procurement approver and payment reviewer in the walkthrough. Each sees a different part of the supplier registration and change request. Ask them to trace submitted registration to activated supplier record and establish where authority to release a supplier for payment actually sits. Differences between the documented responsibility and the person carrying out the action belong in the scope.
Robotic process automation
Use RPA for repeatable steps with stable inputs and clear outcomes. Establish a queue for unexpected screens or missing values before scheduling unattended work. Work through a bulk import introducing a supplier already in a manual exception queue. Inspect the final submitted values, prior approval and amended decision before and after the event and ask the receiving team to explain the difference. A useful test includes duplicate registrations and conflicting delegated approvals, especially when the business consequence is a completed workflow with an unverified payment destination. Agree which information to keep and who will use it during a supplier payment cycle.
Illustrative engagement
Resolve a purchase exception
Starting point
Buyers spend time chasing the same approval when a purchase exceeds the receiving team's threshold.
Decision
Capture the thresholds and delegation rules. Test a split order and an absent approver before turning on reminders.
Deliverable
An approval queue with dates, delegates and a documented exception route.
Process controls and adoption
Retain evidence of decisions and train a named owner to manage the exception queue. Measure completed outputs alongside handling effort so partially processed cases do not appear successful. For operational handover, give the operations process owner a worked example from the supplier activation exception report. Reconcile the result against requests completed without a manual correction. Agree how to pause activation and request independent verification when the evidence falls outside the accepted range.
Testing the approval that changes mid-process
Consider a supplier onboarding request in which the applicant changes bank details after the finance approval. Decide which evidence the original approval covered and which change invalidates it. Make the workflow reopen the appropriate review without discarding the completed checks that are still valid. Include a test where the original approver has left the company. The operator should see who now owns the task and why a second review is needed. This avoids a queue that looks complete in the automation dashboard while finance still has to establish whether the payment information was independently checked.
Put a price on the exceptional cases
Expense approvals seem straightforward until the approver is on leave, the cost centre has closed or a receipt covers two projects. We sample completed and rejected claims with the operations team before proposing a flow. For each exception, we record how often it occurs in the sample, who can resolve it and how much effort the resolution actually takes. Some cases warrant an automated branch. Others belong in a clearly owned review queue because the next step depends on judgement.
For the pilot, we keep the existing human process available and compare the result on a controlled set of claims. Finance examines the coding, the approval evidence and the ledger entry, while the requester checks whether the status message explains what to do next. We also agree when an operator may stop or retry an item without paying it twice. The release decision considers time spent clearing exceptions as well as routine processing time. That comparison helps the sponsor decide whether to broaden the automation or change the underlying policy first.
What to bring to discovery
Bring an anonymised supplier registration and change request, a recent supplier activation exception report and an example of a change to payment details after the original reviewer has approved the supplier. Where the inputs contain sensitive information, supply synthetic equivalents that preserve the decision sequence. Ask the operations process owner to identify who may approve release a supplier for payment. Record supplier identifier, approval timestamp, bank-change flag and assigned owner with their meanings, including whether an empty value is permissible. Invite the people who use the final submitted values, prior approval and amended decision to describe the hardest discrepancy from the last cycle. The discovery log should capture the source evidence, responsible team and decision required.
Agreeing the first work package
Anchor the first work package in process discovery and choose a deliverable such as a decision table and exception queue design. Define the boundary from submitted registration to activated supplier record so both teams know what a completed item looks like. For planning purposes, list duplicate registrations and conflicting delegated approvals separately from ordinary cases and record whether each is included in release one. Material scope changes include a new supplier category, a different owner for supplier registration and change request or a dependency that changes a supplier payment cycle. Agree the cost and acceptance consequence of each before committing delivery capacity.
An acceptance exercise for your team
Give the operators a supplier who changes bank details between approval and activation. Ask the operations process owner to describe the expected business result before showing them the implementation. Introduce a change to payment details after the original reviewer has approved the supplier and follow the chain from submitted registration to activated supplier record. At each point, record the values of supplier identifier, approval timestamp, bank-change flag and assigned owner that matter to the decision. The test succeeds when the operator can show who approved the final payment details. If evidence from the final submitted values, prior approval and amended decision disagrees, stop at the first observable difference and establish who can resolve it. Keep the starting data and explanation with the supplier activation exception report. This example can be adapted to the rules and responsibilities of your organisation.
Designing a workable exception queue
Let an operator sort exceptions by the action needed and the deadline that matters. A request waiting for information from a supplier needs a different response from a failed system update. Provide sufficient context to act without exposing unrelated business or personal information.
Planning around the operating calendar
Build the release around a supplier payment cycle. For supplier onboarding, that means agreeing when the final submitted values, prior approval and amended decision are available, when the operations process owner can decide and what work would be interrupted by a late change. Select test material covering duplicate registrations and conflicting delegated approvals before reserving a business sign-off slot. Treat authority to release a supplier for payment as a release dependency. If a new supplier category is introduced at the same time, check whether the original baseline for manual touches and exception age per completed request still supports a meaningful comparison.
Exception ownership and recovery
One credible failure is a completed workflow with an unverified payment destination. The first diagnostic step is to inspect the final submitted values, prior approval and amended decision and identify the authoritative version of the supplier registration and change request. Next, determine whether the person who changes protected details cannot independently release them. For an incident involving an absent approver, an operator may need to pause activation and request independent verification. Agree that authority with the operations process owner ahead of a supplier payment cycle. Capture the resolution in a decision table and exception queue design, including how supplier administrator, procurement approver and payment reviewer can confirm recovery from their different perspectives. For repeat occurrences, compare the underlying fields rather than assuming every item in the exception queue has the same cause.
Handover and ongoing ownership
Put a decision table and exception queue design in the hands of the staff who will own supplier onboarding. Include a completed example from submitted registration to activated supplier record and a walkthrough for a change to payment details after the original reviewer has approved the supplier. Someone outside the delivery team should be able to locate the final submitted values, prior approval and amended decision, identify authority to release a supplier for payment and act when the supplier activation exception report shows a discrepancy. After the rehearsal, update ownership for supplier registration and change request and document where to propose changes to supplier identifier, approval timestamp, bank-change flag and assigned owner.
Planning your engagement
How to measure the outcome
Agree the measurement definition for manual touches and exception age per completed request before changing supplier onboarding. Start with requests completed without a manual correction, then review duplicate registrations and conflicting delegated approvals as a separate population if their expected treatment differs. A reliable baseline needs the reporting date, an owner for supplier registration and change request and a consistent definition of completion from submitted registration to activated supplier record. Test the supplier activation exception report with a case involving a change to payment details after the original reviewer has approved the supplier. If a new supplier category alters the population later, preserve the original baseline alongside the revised one. This gives the operations process owner an explanation for a change in the number and a decision about which improvement to fund next.
Delivery and support responsibilities
For an advisory phase, ask FyerX to focus on the decision behind process discovery. For an implementation, agree the behaviour of supplier registration and change request through submitted registration to activated supplier record and the evidence required from the final submitted values, prior approval and amended decision. For a team that already owns delivery, a bounded specialist assignment can focus on robotic process automation. Keep authority to release a supplier for payment with its named business or technology owner unless explicitly delegated.
What makes an automation expensive?
Volume matters, but a high-volume step with one reliable input can be simpler than a low-volume approval with six exceptions. Ask the operators for their last few manual interventions. We use those examples to estimate routing rules, exception handling, monitoring and the work that must remain with a person.
Frequently asked questions
Process Automation
How can we tell if a process is suitable for RPA?
Observe the work during both quiet periods and peak demand. Stable screens and predictable inputs support automation. Frequent judgement calls, unstable source data or a system due for replacement may justify process redesign first. Compare the effort of maintaining the robot with the work it can reliably complete.
Who handles the exceptions after automation?
Give each exception a reason, queue and named owner. An unreadable invoice, missing approval and changed bank account involve different decisions. Test the escalation path when the owner is away, and ensure an operator can correct data without inadvertently approving their own transaction.
What would you need to assess supplier onboarding?
Bring one supplier registration and change request, an example from the supplier activation exception report and the people responsible for the final submitted values, prior approval and amended decision. A useful discovery exercise follows submitted registration to activated supplier record under both ordinary conditions and a change to payment details after the original reviewer has approved the supplier. The resulting scope should identify the business decision, environment access and operating owner required for the first work package.
Can we begin with process discovery?
Yes. Define the first deliverable in terms of the operator can show who approved the final payment details. Agree with the operations process owner how to test it using the final submitted values, prior approval and amended decision. The first phase can stop after the decision and evidence are delivered, or continue into low-code workflows with scope and responsibilities already documented.
How does low-code workflows fit into delivery?
It addresses the point in supplier onboarding where the team must understand supplier identifier, approval timestamp, bank-change flag and assigned owner. Use a change to payment details after the original reviewer has approved the supplier to establish how information, permissions and ownership cross that boundary. The resulting acceptance case should demonstrate the person who changes protected details cannot independently release them and identify who takes over if the outcome is uncertain.
What happens to cases involving changed bank details?
Use supplier registration and change request as the starting reference and examine the final submitted values, prior approval and amended decision. The key question is whether the person who changes protected details cannot independently release them. Agree a treatment with the operations process owner, preserve evidence for the supplier activation exception report and make the authorised next action visible to the team. Include the case in later release checks, especially after a new supplier category.
Can approval continue when the usual approver is away?
Define the delegate and the scope of their authority before enabling automatic reassignment. If an item contains a sensitive change, it may require an independent reviewer even during an absence. Test the queue, notification and decision history using a delegated approval.
What should we expect at handover?
Expect the agreed delivery evidence and a decision table and exception queue design. A useful sign-off is for the receiving team to trace submitted registration to activated supplier record, read the relevant entry in the supplier activation exception report and respond to a change to payment details after the original reviewer has approved the supplier using the material supplied. Document ongoing responsibility for updates to supplier registration and change request before closing the engagement.
How will our team decide whether to go ahead?
Ask whether the operator can show who approved the final payment details. Check the final submitted values, prior approval and amended decision with the operations process owner and verify that authority to release a supplier for payment is available during a supplier payment cycle. If a critical dependency remains open, identify its effect on requests completed without a manual correction and the owner who can accept, resolve or defer it.
Which measures are useful after release?
Use manual touches and exception age per completed request alongside the supplier activation exception report. For supplier onboarding, reconcile a sample against requests completed without a manual correction and review the influence of duplicate registrations and conflicting delegated approvals. Confirm that a new supplier category or a new reporting definition has not changed the population before crediting an improvement to the work.
Who can operate the outcome internally?
Agree responsibilities among the supplier administrator, procurement approver and payment reviewer. Give the receiving operator an unfamiliar example involving an absent approver and ask them to investigate it through the final submitted values, prior approval and amended decision. Their ability to explain submitted registration to activated supplier record and identify authority to release a supplier for payment is a practical test of the handover.
Which approval rules should we automate first?
Start with stable rules that have an owner and an unambiguous result. Defer discretionary exceptions until the approver can explain how to handle competing conditions and who may override the decision.