Skip to main content

BPA-02 Approvals and routing · Worldwide

Workflow Automation

Approvals that route themselves by value and category, remind the approver, escalate when the clock runs out, and pass to a delegate during leave. Plus the record of who approved what, which is the part auditors ask for.

  • Rules by value, category, cost centre, margin or vendor
  • Reminders and an escalation matrix when the clock runs out
  • Delegation during leave, recorded in the trail
  • Action from email or WhatsApp, without a desktop login

Reply within 1 working day · the first map is free

P J DivyaCo-Founder, CTO and CMO

Owns the routing matrix, the integrations and the launch.

Routing rule

01
Under the desk limit
Manager
02
Desk limit to department cap
Manager + Head
03
Above the department cap
+ Finance review
04
Not actioned in 48h
Escalate one level
05
Approver on leave
Delegate, recorded
  1. InputThe workflow as it really runs
  2. RulesApprovals and service levels
  3. BuildSystems connected end to end
  4. OutputEvery step visible and logged
PurchaseExpensesDiscountsLeaveDocumentsVendor onboarding
RoutingValue and cumulative
Per workflow1 to 3 weeks
Approve fromEmail or WhatsApp
TrailUneditable

10 Related

What sits either side of a workflow

Routing is the layer. These are the systems it routes between.

  • Purchase requisitions routed by value and category, with the budget checked before the approver sees it rather than after.
  • Expense claims with policy limits applied automatically, so only the exceptions reach a human at all.
  • Discount and pricing exceptions routed by margin rather than by amount, which is the rule most companies discover they wanted.
  • Credit limit changes with the customer's ageing and payment history attached to the request, not looked up separately.
  • Leave and attendance with cover confirmed before approval, and delegation of the approver's own authority handled automatically.
  • Document sign-off with version control, so nobody approves the draft that was superseded on Tuesday.
  • Vendor onboarding with document collection, verification and bank detail confirmation before the first payment can be raised.
  • Customer refunds and credit notes with the reason coded, so the pattern is visible at the end of the quarter.

Why delegation is not optional

An approver is away for roughly 15% of the working year once leave, travel and public holidays are counted, so a matrix with no delegate stalls one request in seven. 100% of approvals, delegations and escalations are written to the trail, and the escalation fires on 100% of breaches rather than when somebody notices.

10 Related

What sits either side of a workflow

Routing is the layer. These are the systems it routes between.

Routing dimensions, and when each one earns its place
Route byTypical ruleWhen it is the right choice
ValueUnder the desk limit to the manager, above it to the headThe default, and rarely sufficient on its own
CategoryCapital spend always to finance, whatever the valueWhere the type of spend matters more than the size
MarginAny quote below 18% margin to the sales headDiscount approvals, where value alone hides the damage
Cost centreThe budget owner, not the requester's managerMatrix organisations and shared services
Vendor riskA new or unverified vendor adds a compliance checkProcurement, where the risk is the counterparty
CumulativeThe fourth request this month from one requester escalatesCatching split purchases below a threshold

The rule that catches split purchases

Cumulative routing is the one dimension teams almost never ask for and almost always need. Four requests of 24,000 each in one month, all sitting just under a 25,000 threshold, is a pattern no single-request rule will ever see.

10 Related

What sits either side of a workflow

Routing is the layer. These are the systems it routes between.

  • The question: what happens when the approver is unavailable? Not "unavailable in theory", but on the Friday before a long weekend with a dispatch waiting.
  • The wrong answer: nothing happens, and the request waits. Two of those and the team goes back to WhatsApp, which is where the audit trail disappears.
  • The other wrong answer: it auto-approves. That converts a delay problem into a control problem, and the first time it approves something it should not have, the whole system is switched off.
  • What actually works: a named delegate per approver, set in advance, activated by the leave record or by the approver, with the delegation itself written into the trail. Plus escalation up the hierarchy after a stated time, so a request can wait but can never be forgotten.

The escalation was the part that changed behaviour. Once a pending approval started appearing on the director's Monday list, the queue emptied itself.

Head of procurementMulti-plant manufacturer

10 Related

What sits either side of a workflow

Routing is the layer. These are the systems it routes between.

  1. Step 1: Time the current path

    Request to action, measured rather than estimated, and where it waits. The waiting is almost always in one place and rarely the one people assume.

    2 to 3 days
  2. Step 2: Write the rule in a sentence

    By value, category, cost centre, margin or vendor, with thresholds as numbers. A rule that cannot be written in a sentence should probably not be a rule.

    2 to 3 days
  3. Step 3: Answer the absence question

    Delegates, escalation timings and what may never auto-approve. This is the decision that determines whether the system is used or bypassed.

    1 to 2 days
  4. Step 4: Build escalation and fallback first

    Reminders, escalation, a manual path and an alert to a named owner, before the happy path is wired at all.

    1 to 2 weeks
  5. Step 5: Hand over the rule editor

    An administrator on your side is trained to change thresholds and approvers without us, because a workflow you cannot edit is one you will abandon.

    1 day

10 Related

What sits either side of a workflow

Routing is the layer. These are the systems it routes between.

  • Every action carries the actor, the timestamp, the value, the rule that routed it and the channel it was actioned from, and none of it can be edited afterwards.
  • Delegated approvals show both people: the delegate who acted and the approver whose authority was used. An audit that cannot distinguish the two is not an audit.
  • Anything writing into the books is part of the accounting system, so it inherits the logging control an external audit already tests: an unalterable, timestamped record of each entry and each later change, which is control A.8.15 of ISO/IEC 27001. Retention is set per workflow rather than left indefinite.

10 Related

What sits either side of a workflow

Routing is the layer. These are the systems it routes between.

The rules are agreed with the people who will live inside them. That is the step most rollouts skip and then repeat.

  • P J Divya

    Co-Founder, CTO and CMO

    Connects the systems so the workflow is one path rather than four, and builds the escalation logic.

  • Chetan Ravi

    Founder and CEO

    Maps the workflow, negotiates the service levels, and gets the approval matrix signed.

  • Harith, Compliance Expert at ProTax

    Harith

    Compliance Expert

    Checks what the trail records: who approved what, when, and whether it survives an audit.

  • Harsh Jain, Legal Expert at ProTax

    Harsh Jain

    Legal Expert

    Reviews delegation during leave, sub-delegation limits and the authority behind each approval.

10 Related

What sits either side of a workflow

Routing is the layer. These are the systems it routes between.

  • Working hours

    Our day runs on UTC+5:30. The overlap window with your team is written into the scope rather than assumed, and everything outside it runs asynchronously.

  • How we communicate

    One written update a day on the channel you already use, a standing weekly call inside the overlap window, and a named person to escalate to. Nothing important is agreed only on a call.

  • Who you contract with

    ProTax Consultancy, the company behind ProTax, named in the agreement with its registration number. The governing law and the forum are agreed before you sign, not after a dispute.

  • Currency and payment

    Invoiced in your currency or in ours, your choice, and settled by bank transfer. Milestones are tied to deliverables you can see, never to elapsed time.

  • What you own

    Copyright in everything built for you is assigned on final payment: source code, design files, prompts, configuration and documentation. Third-party licences are listed by name so nothing is a surprise later.

  • Where data sits

    You choose the region your data is stored and processed in, and the answer is written down before the build starts, with who at ProTax can reach it and for how long.

Offset from our working day standard time

  • London-5:30
  • Dubai-1:30
  • Singapore+2:30
  • Sydney+4:30
  • New York-10:30
  • San Francisco-13:30

ProTax is a brand of ProTax Consultancy. The contracting entity, the governing law and the invoicing currency are all named in the proposal before you sign anything.

09 Questions

What sits either side of a workflow

Escalation matrix
The rule for what happens when an approval is not actioned in time: who receives it next, after how long, and whether it may auto-approve.
Delegation of authority
Approval rights passing to another person during absence, recorded so the trail shows who actually approved.
Maker-checker
A control requiring that whoever creates a transaction is not whoever approves it.
Straight-through processing
Written STP: a request meeting every rule that is released with no human action at all.
Service level
Written SLA: the time within which an approval is expected to be actioned, and against which a breach is measured.
Approval trail
The unedited record of actor, timestamp, value and routing rule for every action taken on a request.
GDPR
The EU and UK data protection regime. Article 83 sets administrative fines of up to €20 million or 4% of worldwide annual turnover, whichever is higher, which is why consent, retention and access control are build decisions here rather than paperwork.

09 Questions

What sits either side of a workflow

Workflow automation is the routing layer of a business: who a request goes to, in what order, on what rule, what happens when nobody acts, and what record survives afterwards. It is narrower than process automation and it is usually where a business should start.

Next step

Tell us the approval that holds things up most.

We will come back with the routing rules, the escalation matrix, the delegation design and a fixed quote. The first map is free and yours to keep.

Read by P J Divya, our CTO, not a form queue. Reply usually within one working day, in your time zone.

FROM THE PROTAX LIBRARY

Recent Articles & Guides

Practical reading on business records, tax filings and the decisions that come with running a company.

Newsletter

Stay ahead on compliance, tax & business updates

Get selected business and compliance updates by email. Once a month, no spam.

  • 100% privacy
  • 1 email / month
  • Unsubscribe anytime
Contact ProTax
Chosen by individuals and businesses

Get Help With Your Business

Tell us what you need help with. Our team will review your enquiry and explain the next steps.

Free Consultation No Obligations Expert Advice
FREE Consultation No obligation, no lock-in

Talk To ProTax

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
FREE Consultation No obligation, no lock-in

Request a Free Quote

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
Stop chasing approvals over email Rules reminders