Xero Partnership Guide: How to get listed in the Xero App Store

Anyone offering an integration with Xero becomes a Xero app partner, and until this year that mostly meant a listing and a share of what you sold through it. Xero has replaced the arrangement. In their words, they are “retiring our current revenue share model (comprising Xero App Store Subscriptions and Commercial Billing)” and introducing five tiers instead.

So the commercial question moved. It used to be what percentage Xero takes of your revenue. It is now a flat monthly fee plus a usage bill, and both are driven by numbers you control at design time rather than at sales time.

The migration ran on a published schedule. No new apps entered the old models after 4 December 2025, apps created between then and 2 March 2026 started on an interim arrangement, and existing apps moved from 2 March 2026 with 30 days notice each.

The ladder is Starter, Core, Plus, Advanced and Enterprise. Every tier carries a connection ceiling and a monthly fee, and a connection is one customer organisation attached to your app through a valid OAuth grant.

This is the part that changes how you build rather than what you pay. Xero meters data in one direction only. Ingress, everything you send into a customer’s organisation, is marked Unlimited on all five tiers. Egress, everything you read back out, has a monthly allotment and a price per gigabyte after it.

Posting a thousand invoices costs nothing. Reading them back to check what happened is the part with a meter on it, and that inverts the usual instinct that writes are the expensive operation.

The practical consequence is that sync design and cost control became the same conversation. A delta query instead of a full read, a cache instead of a re-read, an event instead of a poll: each one used to buy you headroom against a rate limit and now also lowers an invoice.

If the listing is why you are here, this is the sentence that matters. Xero writes: “To be listed on the Xero App Store, you will need to be in the Plus tier or higher.” The pricing table says the same thing in a second place: Starter and Core are marked Not Applicable, Plus and Advanced Optional, and Enterprise Required.

That is one rung later than a Core-tier plan would suggest, and it is the difference between a 35 AUD monthly fee and a 245 AUD one before your first listing view.

Two prerequisites sit underneath the listing and they arrive at different rungs. App certification is required from Plus upwards. A security assessment is required from Advanced upwards, and Xero notes it as initial and annual, so it is a recurring commitment rather than a one-time gate.

Certification also has product requirements that are easy to miss because they live in your interface rather than in your integration: showing the name of the connected organisation, showing the connection status, offering a disconnect button and handling the case where the customer disconnects from Xero’s side.

Some capabilities are not bought with code, they are bought with a tier. Three of them decide architecture, so they belong in the plan rather than in a discovery call.

• The journals endpoint, from Advanced. It returns the complete set of journal entries for an organisation, including the ones Xero generates automatically from invoices, bills and payments. It also needs a security assessment and use case approval.
• Bulk connections, from Advanced. One user connects many organisations in a single authorisation flow, which is the difference between onboarding a practice and onboarding each of its clients.
• Rapid sync, from Plus. Xero lifts the standard limits for the first 30 minutes of a new organisation connection. That is exactly the window in which the first full import runs.

Nothing about the tier change alters how you build against Maesn. The data model is the same, the interface is the same, and the systems beyond Xero stay one configuration step away. What changed sits on the other side of the line.

• The app is yours, so the tier is yours. You register it under your own product name, which is what your customers read on the consent screen, and the connection ceiling, the certification and the monthly fee belong to that app. We run the partner process with you and we cannot hold it for you.
• Xero bills you directly. The tier fee and any egress overage are charged by Xero to a card you register with them. They are independent of what you pay Maesn.
• Reducing egress is shared work. Which objects you read, how often and with what filter is your product decision. Making that decision once instead of once per system is ours. QuickBooks has reached the same place from a different direction, and the cross-vendor view is the accounting integration partnerships guide.

What the connection itself involves, from the tenant id on every call to the token cycle behind it, is on the Xero API page.