Skip to content

Insight Connecting your tools 5 min read

Power Automate approval workflow: licences, limits and checks

By Renzo Demartini, Chartered Accountant ·

Drafted with AI, reviewed and spot-checked by me.

Bill 7731 for $1,100.00 appears in SharePoint. A second copy meets the duplicate check and stops. The owner approves the original bill’s evidence. A draft bill appears in Xero. Payment stays unapproved. Approval moves the bill on, not the money.
Where to startA$990

Workflow Audit

Where an existing feature is enough, and where Zapier, Make or n8n earns its place.

  • n8n
  • Zapier
  • Employment Hero
  • SharePoint
See the workflow automation audit
Fixed price · AUD · No GST

Your supplier bill sits in SharePoint while approval disappears into email. A Power Automate approval workflow can coordinate that handover,1 but the connection to Xero needs its own checks and licences.2

The short answer: use a cloud flow to collect approval, then create a draft bill in Xero. The design below is a proposal on sample data, and it has not been deployed or measured.

Approval workflow · SharePoint bill → draft in XeroDemonstration

The bill the owner approved. Bill 7731 from Supplier A (sample) sits in SharePoint with its PDF. The owner approved $1,100.00 against that version.

Then the flow creates a draft in Xero. The flow writes a draft bill and returns its Xero ID. The draft is not approved for payment.

SharePoint · Bill 7731Approved

Supplier A (sample)

Approved by the owner

  • Materials$800.00
  • Delivery$200.00
  • Assumed GSTSample assumption$100.00
Approved total
$1,100.00

Approval is recorded against this document version.

Xero · Draft billDraft

Supplier A (sample)

Created by the flow

  • Materials$800.00
  • Delivery$200.00
  • Assumed GSTSample assumption$100.00
Draft total
$1,100.00

The Xero ID is saved before the tracker is marked complete.

Rules compare the two. The same checks every time: duplicate, approved version and total. Any difference stops the bill.

Checked by a rule Approved bill

Checked by a rule Xero draft

Supplier

Approved bill: Supplier A

Xero draft: Supplier A

Materials

Approved bill: $800.00

Xero draft: $800.00

Delivery

Approved bill: $200.00

Xero draft: $200.00

Assumed GST

Approved bill: $100.00

Xero draft: $100.00

Total

Approved bill: $1,100.00

Xero draft: $1,100.00

  • Bill 7731 is not already in the tracker
  • Draft total equals the approved total
  • Document unchanged since approval

A person reviews the coding. The bookkeeper approves the coding or sends the bill back. Payment is a separate decision.

Messages · Bill 7731

Draft bill Coding approvedReturned with a reason

Approve the coding for bill 7731?

Totals agree. Coding is the bookkeeper’s decision.

Coding approved, still a draft.Returned with the reason recorded. The bookkeeper approves the account coding. The bill stays a draft until an authorised person approves payment.The bill goes back to the owner with the reason. Nothing is posted or paid.

Xero · Bill 7731Draft

Supplier A (sample)

  • CodingApproved by the bookkeeper
  • PaymentAwaiting an authorised person$1,100.00

Payment is released by an authorised person.

SharePoint · Bill 7731Returned

Supplier A (sample)

  • StatusReturned to the owner

Nothing is posted or paid.

End of the day Each bill in SharePoint is checked for a duplicate and approved by the owner. The flow then creates a draft bill in Xero. It never approves coding, posts or pays.

These are demonstrations. They use sample data and simulated Claude steps. Nothing connects to your accounts, sends a message or changes a record.

Check the connection first

Publisher and status

The connector is published by Magnetism, a third party, and is in Preview.

Power Automate class

Microsoft lists it as a Premium connector, so a Premium licence applies.

Separate subscription

Magnetism needs its own licence after a 7-day trial. Microsoft’s licence does not cover it.

Connector throttle

Up to 100 calls per connection every 60 seconds. A limit, not a promise of throughput.

Microsoft lists “Xero Accounting - Magnetism (Preview)” as a Premium connector. Magnetism publishes it and requires its own subscription after the trial.2 Its Xero App Store listing describes the sign-in step, where you allow access to your Xero organisation.3 Confirm the exact bill fields before building, because “Some Xero API endpoints and fields may not be available from the Connector”.2

Budget the whole workflow

A Premium licence costs A$268.80 a year; a Process licence costs A$2,694.00

A$ a year, ex GST · orange: per bot

Annual figures are Microsoft’s monthly rate times 12. They are alternatives, not cumulative purchases.

Source: Microsoft Power Automate pricing, Australia, read 31 October 2026. Excludes GST.

These Australian prices were read on 31 October 2026. They exclude GST and are monthly rates paid yearly, at A$22.40 a user for Premium and A$224.50 a bot for Process.4

Automated flows use the flow owner’s licence context, and instant flows use the invoking user’s. An instant flow with a premium connector needs Premium for every user who runs it, unless it has a Process licence. “Users who respond to approval requests don’t need a Premium license.”5 Add Microsoft 365, Xero, Magnetism, build and support to your budget. The automation cost guide separates those costs.

A worked example on sample data

Bill 7731 with its lines, the approved total, the draft total and the difference
Bill 7731, Supplier A (sample) Amount
Materials $800.00
Delivery $200.00
Subtotal $1,000.00
Assumed GST $100.00
Approved total $1,100.00
Draft total $1,100.00
Difference $0.00

Sample data, not a client’s. For bill 7731, record approval against the document version, and treat a changed amount as a fresh review. Store the Xero identifier the flow returns before the tracker is marked complete. Xero’s API describes creating sales invoices or purchase bills in one call.9 Test the connector’s draft status and field mapping before enabling writes, and keep payment authorisation separate.

Make failures visible

Duplicate

Hold the second copy and compare it with the original before anything is created.

Rejected

Return the bill to the requester, with the reason recorded.

Timeout

Escalate to the owner well before a pending approval times out.

Failed write

Search Xero for the bill before retrying, because it may already exist.

I would give every stopped bill an owner and a reason. A flow run can last 30 days, and “After 30 days, any pending steps time out”.6 Escalate earlier, because silence must never become approval, and search Xero after a failed response because the bill may already exist.

A checklist before you build

Connect safely

The connection points at the right Xero file. The sign-in has the access the flow needs, and no more.

Draft the bill once

Every bill field lands where you expect it. The same bill sent twice creates one draft.

Handle a stop

A rejected bill goes back to the requester with the reason saved. A named person is chased before the run limit.

Recover and own it

Xero is searched for the bill before anyone retries. One person fixes the flow when something changes.

This is a working checklist, not a claim about your savings. If you only need a notification when a list changes, SharePoint’s own list rules may be enough.7 Power Automate handles processes across apps and services, and desktop flows automate tasks on the web or the desktop.8 Compare the upkeep with an n8n workflow, and stop if required fields fail testing or nobody owns recovery.

The full checklist, eight checks
  1. Correct organisation. The connection points at the right Xero file, not a demo or an old one.
  2. Permissions checked. The sign-in uses an account that has the access the flow needs, and no more.
  3. Draft mapping tested. Every bill field, including tax and the account code, lands where you expect it.
  4. Duplicate replay blocked. The same bill sent twice creates one draft and holds the second copy.
  5. Rejection recorded. A rejected bill goes back to the requester with the reason saved beside it.
  6. Timeout assigned. A named person is chased well before the run limit ends a pending approval.
  7. Failed write reconciled. Xero is searched for the bill before anyone retries a failed request.
  8. Support owner named. One person fixes the flow when Microsoft, Magnetism or Xero changes something.

Where a person stays in charge

Rules check

Matching, totals and the duplicate check, the same way for every bill.

Claude drafts

An exception note, if the design includes one. It writes only.

You decide

The owner approves spend, the bookkeeper approves coding and posting, an authorised person pays.

I keep calculations and duplicate checks in rules. Claude may draft an exception note if the design includes one, but it does not approve, post or pay. The Supplier Bill Approval build starts from A$3,900 (AUD, no GST charged).10

Start with a free fit check by email at the foot of this page, to document the approval boundary and the recovery owner first. The Workflow Audit, A$990 (AUD, no GST charged), is the next step.10

Questions

Is Xero included with Power Automate Premium?

Premium covers premium connectors. Magnetism’s connector subscription is separate.25

Does every approver need Premium?

Microsoft says people who respond to approval requests do not need Premium. Invoking an instant premium flow is a different licensing case.5

Can an approval wait indefinitely?

No. The documented run limit is 30 days, including pending approval steps.6 Design escalation and recovery before that limit.

Sources

Not sure which to fix first?

Get a free fit check by email and I will say whether it is worth automating. No call needed. The next step is a A$990 workflow audit: the top 3 things worth automating, with a fixed quote for each.

Get a free fit check by email

If you would rather have it built

Each topic has a fixed-price build behind it. The audit tells you which one is worth doing for your business.

Need more than one workflow? For strategy, board work and larger custom builds, I work through renzodemartini.com.

More insights

Start with a free fit check by email

A free fit check by email first. The A$990 Workflow Audit is the next step, credited to your build.

Get a free fit check by email The next step after the fit check: the A$990 Workflow Audit

Get a free fit check by email

Send the form with your software, the workflow, your team size and your timing. I reply by email, usually with a question or two, and tell you whether it's a fit. No call needed. If it is, the next step is the A$990 Workflow Audit.

Sending saves your details in HubSpot so I can reply. No mailing list. No payment is taken. How your enquiry is handled.