← All posts
Manager reviewing a purchase approval on a laptop in a small business office

SAP Business One Approval Procedures: Stop Approving Purchases by Email

Why Email Approvals Are Broken

Every small to mid-size company I work with starts the same way. Somebody needs to buy something. They send an email with the quote attached. The manager replies “looks good” from their phone at a soccer game. Accounting prints the email and staples it to the PO. Six months later nobody remembers why that $8,000 server was approved or who actually said yes.

The problems stack up fast. Emails get buried. People go on vacation. The thread forks when someone hits reply-all by mistake. Version control disappears. And good luck pulling a clean audit trail when the tax folks come knocking. SAP Business One has a better way built in. Approval procedures turn that messy back-and-forth into a structured process that lives inside the ERP.

Stack of purchase orders and a stamp on a desk

What Approval Procedures Actually Do

Approval procedures in SAP Business One are simple rules you define once. They watch for certain conditions on documents like purchase orders, purchase quotations, or goods receipts. When those conditions are met, the document gets locked until the right person approves it.

The system sends a notification inside SAP, not another email. Approvers see a clear list of pending items on their dashboard. They can approve, reject, or add comments without leaving the software. Every action is timestamped and tied to a user. When the approval chain finishes, the document is released automatically. No more guessing.

Think of it as guardrails instead of traffic lights. The process does not slow down good purchases. It just makes sure the wrong ones never move forward without the right signatures.

How to Set Up Your First Approval Procedure

Setting these up takes about twenty minutes once you know the steps. Start in the Approval Procedures window under Administration > Approval Procedures > Approval Templates.

  1. Give the template a clear name like “PO Over 5K – Needs Manager Approval.”
  2. Choose the document type. For purchases, select Purchase Order.
  3. Define the conditions. You can use amount, department, vendor, item group, or any combination. Example: Total > $5,000 OR Vendor = “Expensive Supplier Inc.”
  4. Set the approval stages. Add one or more approvers in sequence or in parallel. You can even route based on who created the document.
  5. Decide what happens on rejection. Usually the document returns to draft so the originator can fix it.
  6. Activate the template and test it with a sample PO.

Keep your first rules simple. Over-complicating them on day one is the fastest way to get everyone to ignore the system.

Common Setup Mistakes and How to Avoid Them

I see the same errors every time I help a new customer. First, making the thresholds too low. If every $200 office supply order needs the CFO’s approval, your CFO will stop using the system. Start higher and tighten later.

Second, putting too many people in the chain. Three approvers maximum for most purchases. More than that and things sit.

Third, forgetting to train the team. Just turning on approval procedures without telling people what changed guarantees confusion. Spend fifteen minutes in the next staff meeting walking through the new dashboard alert.

Fourth, ignoring the “originator can approve” checkbox. Sometimes the person who creates the PO should not be allowed to approve it. Turn that off when it makes sense.

Real-World Rules That Actually Work

Here are four approval templates I have seen work well for distributors and light manufacturers.

  • Anything over $2,500 requires the department manager.
  • Capital equipment over $10,000 routes to the controller and then the owner.
  • Purchases from new vendors need purchasing manager review regardless of amount.
  • Recurring service contracts above $1,000 per month get flagged for finance.

You can combine these. The system lets you stack multiple templates on the same document type. One PO can trigger two different approval stages if it meets both sets of conditions.

The key is to make the rules reflect how your business actually thinks about risk. What matters more, the dollar amount or the type of spend? Let the system do the remembering instead of your memory.

If your SAP Business One setup needs a tune-up, here is how I help SAP Business One customers.

Stop the Email Madness for Good

Moving purchase approvals into SAP Business One is one of those small changes that quietly improves everything. Your audit trail becomes automatic. Managers spend less time hunting through inboxes. Buyers know exactly where their POs stand. And you stop losing visibility on spending the moment someone hits send on an email.

It is not complicated technology. It is just better process. Once you see how clean the approval queue looks on Monday morning, you will wonder why you ever let email control your purchasing.

Take one afternoon this week and build your first two templates. Start small, communicate the change, and adjust as you go. Your future self, and your accountant, will thank you.

Frequently Asked Questions

Can I set up approvals for specific departments only?

Yes. SAP Business One lets you include department as a condition in the template. You can also assign different approvers based on which department created the document. This keeps the process from becoming one-size-fits-all and respects how different teams operate.

What happens if the approver is out of the office?

You can define a substitute approver in the system or set up escalation rules that move the request to the next person after a set number of days. Most companies start with a simple substitute setup and add escalation later once they see how people actually use it.

Do approvals work on mobile?

The SAP Business One mobile app shows pending approvals and lets users approve or reject with a couple taps. It is not as full-featured as the desktop version but it is good enough for most quick decisions when someone is traveling or on the road.

How do I know the approval history later?

Every approval and rejection is logged in the document history and in the approval summary report. You can pull a clean list anytime showing who approved what, when, and any comments they left. This makes year-end audits and internal reviews much less painful.

Share this post X Facebook LinkedIn
David Strausser

Written by David Strausser

David is CEO of Dead Brands, LLC and Head of Sales (contracted) for Quaint Business Solutions — an ERP veteran of over a decade across SAP Business One and Odoo. Ex-General Manager (Northeast) at Vision33 and VP of Business Development at SEIDOR. Dad, guitarist, Eagles fan.

Keep reading

Let's talk about your business

Running on spreadsheets, QuickBooks, or an ERP that fights you? Grab a free 30-minute call — I'll tell you straight whether SAP Business One or Odoo is the right move, and what it really costs.

Book a Meeting with Me

Shop the brand

Take a piece of the bite with you

Dead Brands white v-neck — white v-neck shirt with the official Dead Brands crowned skull logo
View all in the store →