Migrating from ApprovalMax to DueReason
ApprovalMax gates spend inside Xero, QuickBooks or NetSuite. See what moving the same approval step to DueReason's signed, agent-native grant changes.
Updated · 8 min read
In short
- ApprovalMax is a multi-level approval layer bolted onto Xero, QuickBooks Online or Oracle NetSuite - bill-to-PO matching, budget controls and segregation of duties, built specifically for accounts payable and receivable.
- It is the closest finance-approval-specific alternative to DueReason's payments and refunds workflow, but it stays inside one accounting system, with no agent or pipeline story and no signed, independently verifiable grant.
- DueReason's payment and vendor-onboarding actions cover the same spend and vendor sign-off whether or not an accounting system is involved at all, and a signed grant is checked by whatever system pays the invoice, not just assumed from a click.
- DueReason has no native bill-to-PO matching or budget-control UI of its own - bring the accounting integration you already have and add DueReason for the decision, the record and the agent-native surface around it.
If your finance team already approves bills and payments inside Xero, QuickBooks Online or Oracle NetSuite, there is a good chance it is through ApprovalMax: a dedicated approval layer that bolts onto the accounting system itself rather than sitting beside it. This walks through what that gets you today, and what changes if you move the same approval step to DueReason.
What ApprovalMax does today
ApprovalMax sits on top of an accounting system - Xero, QuickBooks Online or Oracle NetSuite - and adds what accounting software on its own usually lacks: multi-level approval chains for bills, purchase orders and payments, bill-to-PO matching, budget controls, and segregation of duties so the person who enters a bill is not the one who approves it. It is built specifically for accounts payable and receivable, and it reads and writes back to the accounting system's own records once a chain of approvers has signed off.
That scope is also its boundary: the approval only exists in service of the accounting system it is wired to. There is no published agent, pipeline or API story for having a script or an AI agent file and track a request the way it does for a person clicking through Xero or NetSuite, and the workflow itself does not extend to a decision that has nothing to do with accounts payable - a production deploy, an access grant, a piece of content going out.
What happens after someone clicks approve
A multi-level chain in ApprovalMax pauses a bill or payment until the assigned approvers sign off, then releases it back into the accounting system to be paid or posted. What is not published is a signed, independently verifiable object the paying system checks before money moves - the trust sits in the approval chain having run inside the same accounting system that will act on it, the same shape Power Automate's Start and wait for an approval action has, which the Power Automate migration guide covers in more detail if that is the comparison you are also making.
The same shape in DueReason
DueReason's Payments and refunds template covers the same ground - before money leaves the organization, it asks first, and larger amounts route to Finance with the invoice attached and then to management - but it is not tied to any one accounting system. Install the template from Settings → Templates, and an agent paying an invoice, a pipeline issuing a refund, or a person filing one by hand all go through the same request form and the same approver groups. A separate Vendor onboarding template covers the segregation-of-duties half of what ApprovalMax does: Procurement checks a new vendor, and anything above a spend threshold also needs management sign-off with the vendor's registration document.
Whichever path a request takes, once it is decided DueReason issues a signed, single-use grant bound to the exact payload - the amount, the payee, the invoice reference - which whatever pays the bill verifies before it moves money, rather than trusting that the right chain ran somewhere upstream.
What changes, not just what moves
- A grant the paying system checks, not an approval trusted at the source. Once approved, DueReason's grant is bound to a hash of the exact payload and verified by whoever acts on it, so a changed amount or payee after approval is refused rather than paid.
- A hash-chained ledger, not an accounting system's own activity log. Every step of a request - filed, each answer, the payment reported back - is a ledger event from the start, checkable on its own without opening the accounting system that happened to host the approval.
- An agent-native surface, not just a human clicking through the accounting UI. The same payment and vendor-onboarding actions are reachable from
@duereason/sdk, the MCP server, the GitHub Action or the REST API, so a pipeline or an agent can request and wait for the same approval a person would otherwise click through. - Not bound to one accounting system. The payment and vendor-onboarding actions work the same way whether the spend touches Xero, QuickBooks, NetSuite or nothing at all - an agent-initiated refund with no accounting-system record behind it yet still gets the same approval step.
Moving one approval step over
- Install the Payments and refunds template (and Vendor onboarding, if ApprovalMax's segregation-of-duties checks on new vendors matter to you) from Settings → Templates - this creates the approver groups and the routing in one step.
- Recreate the people on each approval level - the first sign-off, Finance, management - as members of the template's approver groups, in place of ApprovalMax's approval chain configuration.
- For requests filed by hand, the console request form replaces clicking through ApprovalMax's own approval screen: pick the action, attach the invoice, write a reason.
- For requests your accounting system or an automation already raises,
requestApproval()andwaitForApproval()from@duereason/sdk(or the no-code webhook recipe if you would rather not write a backend) replace the point where ApprovalMax's chain used to pick up the bill. - Replace whatever read ApprovalMax's outcome back into the accounting system with a check of
decided.statusand a verification ofdecided.grantbefore the payment is made - the step that actually moves money should check the grant, not just the approval status.
What has no direct equivalent
DueReason has no native bill-to-PO matching and no budget-control UI built into an accounting-system integration - it answers one question (is this specific payment or vendor approved, by whom, with what evidence) rather than reconciling bills against purchase orders inside Xero, QuickBooks or NetSuite. If matching and budget enforcement inside the accounting system itself are the main reason you run ApprovalMax, keep that integration for the matching and add DueReason around the decision and the agent-native path into it, rather than expecting a native replacement for the accounting-side reconciliation.
Questions
- Does ApprovalMax really have no agent or API story?
- No published one found in this pass: ApprovalMax's own marketing describes multi-level approval chains, bill-to-PO matching and budget controls inside Xero, QuickBooks Online and Oracle NetSuite, but nothing describing an agent, pipeline or general API filing and tracking a request the way a person clicks through the accounting system.
- Can I keep ApprovalMax for bill-to-PO matching and still use DueReason?
- Yes. DueReason does not reconcile bills against purchase orders or enforce a budget inside Xero, QuickBooks or NetSuite - that stays whatever your accounting integration already does. Use DueReason for the approval decision, its signed grant and its agent-native surface alongside it, not as a replacement for the matching itself.
- What does ApprovalMax cost, compared to DueReason?
- ApprovalMax does not publish a flat price list - pricing is split per accounting-system integration (separate Xero, QuickBooks Online and NetSuite plan pages) and partner pricing is available on request, so treat any number you see elsewhere as unverified until quoted directly. DueReason is free today for one organization with up to five members, all core features included.
- Do I need to involve engineering to move a manual approval chain over?
- No. Installing the Payments and refunds template and adding people to its approver groups is a console-only setup, the same as filing a request from the console form; engineering is only needed once you want a script, a pipeline or an agent to request approval through the API instead of a person using the form.
- Can I self-host instead of using the hosted product?
- Yes. Self-hosting runs on one Postgres database and one pre-built image started with Docker Compose, with no accounting-system-specific setup - the same payment and vendor-onboarding actions work the same way whether you use the hosted product or run it yourself.
Move your payment approval to DueReason
Install the Payments and refunds template and point requestApproval() and waitForApproval() at the spend you already gate - no accounting-system lock-in required.
Create your accountSources
- ApprovalMax: approval workflows for Xero, QuickBooks Online and NetSuite
- ApprovalMax pricing (split per accounting-system integration)
- @duereason/sdk: requestApproval and waitForApproval reference
This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.