The approval black hole
You know the scene. A purchase order for $18,000 in raw materials is sitting in someone's email. The vendor's holding pricing until Friday. The approver is in back-to-back meetings. Nobody knows it's stuck because nobody can see it.
Multiply that by twenty documents a week and you've got a shadow process eating your margins. Rush fees. Lost discounts. Production waiting on materials that were ordered — technically — six days ago.
SAP Business One has had the fix for this since forever: approval procedures. The problem is most companies either never turn them on, or they configure them once, badly, and conclude "approvals don't work for us."
What approval procedures actually do
Strip away the SAP terminology and it's simple: when someone creates a document that matches your rules, SAP B1 parks it as a draft and notifies the approver. The approver gets a clear approve/reject decision — in the client, in the web client, or on mobile. Approved? The document posts. Rejected? It goes back with a reason.
The rules are where the magic is. You can trigger approvals on:
- Amount thresholds — POs over $5,000 need a manager; over $25,000 need the controller
- Document types — every outgoing payment, every sales discount over 10%
- Departments or warehouses — different rules for different parts of the business
- Gross profit deviation — a quote with margin below your floor gets flagged automatically
That last one is my favorite. It catches the "we'll make it up on volume" quotes before they become "we lost money on volume" regrets.
Designing approvals that don't suck
Here's where implementations go wrong: they copy the org chart into SAP B1 and call it a workflow. The result is a five-deep approval chain for a $200 office supply order, and everyone starts working around the system within a month.
Rules I give every client:
Match the control to the risk. A $500 PO and a $50,000 PO are not the same decision. Tier your thresholds so small stuff flows and big stuff gets eyes. Most companies need two tiers, not seven.
One approver per tier, with a backup. Approval chains where "any of these three people" can approve sound flexible. In practice, all three assume someone else will do it. Name one primary and one backup. The backup only gets pinged if the primary sits on it past your SLA.
Put a clock on it. SAP B1 can escalate or notify on aging approvals. A 48-hour rule — approve, reject, or it escalates — keeps things moving. Without a clock, approvals go where emails go to die.
Let the system do the nagging. The approver shouldn't need to remember to check. SAP B1 alerts, the web client dashboard, and mobile notifications exist for exactly this. Turn them on.
The mobile factor
This is the part that changed everything for approvals: the SAP Business One mobile app and web client let approvers clear documents from anywhere. The plant manager approves a PO from the floor. The owner approves payments from the airport.
If your approvers are still required to be at their desks running the full SAP client, you've built a workflow around 2010. The approvals work fine — the access model is the bottleneck.
What good looks like
A client of mine — mid-size distributor, about $30M — went from "approvals take 3-5 days" to "approvals take 3-5 hours." Same people. Same authority levels. The difference was entirely: clear thresholds, named approvers with backups, 48-hour escalation, and mobile access.
Their controller told me the best part wasn't the speed. It was that for the first time, she could SEE every pending approval in one place. No more "oh, I didn't know that was waiting on me." Visibility is the real product; speed is the side effect.
Frequently asked questions
Can SAP Business One approvals handle multi-level chains?
Yes. You can chain approval stages — e.g., department head, then controller, then CFO — with each stage conditional on the previous one. Keep chains short; every level you add is latency you're choosing.
Do approvers need the full SAP Business One client?
No. Approvers can work from the SAP Business One web client or the mobile app. This is the single biggest lever for approval speed — meet approvers where they already are.
What happens if an approver is on vacation?
Set up substitute authorizers. SAP B1 lets you define backup approvers who receive the approval requests when the primary is unavailable. Define these BEFORE vacation season, not during it.
Can I require approvals on sales discounts?
Absolutely — and you should. Discount-percentage thresholds on sales quotations and orders are one of the highest-ROI approval rules. It stops margin erosion at the source instead of discovering it in the month-end review.
