Approval automation is often presented as a choice between two products. In practice there are at least five ways to run an approval, and they differ less in features than in where the decision record lives. That matters because the record is the point: an approval that cannot be reconstructed after the fact is a conversation, not a control.
This comparison is for a manager who already knows which processes need approval and wants to choose the operating approach. It avoids the cost build-up covered in our cost guide and concentrates on fit, control and the work each approach creates after go-live.
The five approaches
1. Email, chat and a spreadsheet register
The request arrives by email or messaging app, a manager replies "approved", and an administrator copies the decision into a spreadsheet. It is fast to start and requires no licence. It also fragments the evidence: the decision sits in one mailbox, the amount in another, and the attachment may be a photograph of a quotation.
This approach can be adequate for a small business with a handful of low-value approvals and one person who owns the register. It stops being adequate when approvals cross departments, when an auditor asks who approved an exception, or when the approver leaves and their mailbox is closed.
2. Low-code workflow platform
A workflow platform provides forms, routing, notifications, dashboards and an audit log, usually without custom code for the standard path. Many support BPMN notation, which gives business and technical teams a shared diagram of the process. Integrations are built through connectors or APIs.
This is often the best fit for repeatable approvals with a few branches and a moderate integration list. The trade-off is platform thinking: the process must be expressed in the tool's model, per-user or per-transaction pricing can grow, and complex exceptions may need custom code that the platform makes awkward to maintain.
3. ERP-native approval module
If the approval concerns a purchase order, invoice, payment, stock adjustment or credit limit, the ERP may already have an approval workflow attached to the transaction. The decision is recorded against the financial object, and the posting rules stay in one place.
This approach gives strong financial control and avoids duplicating master data. It is weaker for processes outside the ERP, such as marketing spend, legal review or HR requests, and changes can be slow because they touch a system with a controlled release cycle. It also tends to encode one company-wide threshold model, which may not fit every department.
4. Document management or finance suite
A document suite stores the quotation, invoice or contract and routes it for review and signature. Finance suites add matching, coding and payment release. The approval is tied to the document rather than to a generic request.
This works well when the evidence is the document and the decision is essentially "is this correct and authorised". It is less suitable when the decision depends on data spread across systems, such as a discount that must respect a customer's credit limit and a regional margin rule. Integration depth is the deciding factor.
5. Custom approval service
A custom build models the process exactly: roles, thresholds, delegation, exceptions, integrations and reporting. It can sit between existing systems and expose one API for requests and decisions.
Custom work fits processes that are unusual, high-volume or commercially important, especially where the approval logic is a competitive advantage. It also creates a software product that must be maintained, secured, documented and staffed. A custom approval service is a reasonable choice only with an owner and a support plan, not as a one-off project that ends at launch.
Comparison on the criteria that decide
| Criterion | Email and sheet | Low-code BPM | ERP module | Document suite | Custom build |
|---|---|---|---|---|---|
| Audit trail | Fragmented | Good, platform-defined | Strong on financial objects | Strong on documents | As designed |
| Exceptions | Undocumented | Configurable to a point | Rigid | Limited | Full control |
| Integration | Manual | Connectors and APIs | Native inside ERP | Document-centric | Any, at a cost |
| Change cost | Low until volume grows | Medium, licence-bound | High per release | Medium | Engineering time |
| Time to first process | Days | Weeks | Weeks to months | Weeks | Months |
| Ongoing owner | Administrator | Platform admin | ERP team | Finance operations | Software team |
Where each approach fits
Email and spreadsheet: choose only when approval volume is low, the decision is simple and one owner can produce the register on request. Write the register format first; if it cannot answer who, what, when and why, the approach is already failing.
Low-code BPM: choose when two to ten repeatable processes share a similar shape, the integration list is modest and the business wants to change rules without a release. Ask how delegation, escalation and out-of-office are handled before signing.
ERP module: choose when the approval is fundamentally a financial posting control and the transaction already lives in the ERP. Do not force non-financial processes into it just because the licence exists.
Document suite: choose when the document is the decision evidence and the main risk is version control, missing signatures or lost attachments. Check how it exposes status to the systems that need it.
Custom build: choose when the approval rules are distinctive, the volume is high, or the integration cannot be expressed in a platform. Budget for maintenance and an owner from the start.
Evaluation scorecard
Score each option from 0 to 3 on ten criteria, then weight the ones that matter for your process: audit completeness, exception handling, delegation and escalation, integration fit, mobile experience, language support, reporting, change effort, security and exit. A simple sum is less useful than agreement on the two or three criteria that would make a decision wrong. For most approval projects, audit completeness and exception handling deserve the heaviest weight.
Red flags in a proposal
- A demo that only shows the standard path and never an exception.
- No answer for what happens when an approver is unavailable or has left.
- An audit trail that shows the final status but not the previous value or the person who changed it.
- Per-user pricing that ignores contractors, seasonal staff and read-only users.
- Integrations described as "available" without an error-handling design.
- No export of requests, attachments and history on exit.
The decision record
Whichever approach you choose, document the process owner, the approval matrix, the exception rules, the audit fields and the review date. Then test one real request end to end, including a rejection, a delegation and an out-of-hours approval. The tool is secondary; the decision record is what survives an audit, a dispute or a change of staff.
If you need help mapping the decision rights before selecting a platform, start with Business Automation. The pricing page explains how discovery, build and support are scoped. For the cost drivers behind each approach, read approval workflow automation cost in Bangladesh.
Sources
- Camunda documentation, BPMN modeling, accessed 17 November 2026.
- Microsoft Learn, Get started with Power Automate approvals, accessed 17 November 2026.
- NIST SP 800-53 Revision 5, Security and Privacy Controls, accessed 17 November 2026.
- ISO 9001:2015, Quality management systems, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.