Mindbody runs the studio. Moloni carries the fiscal record.
Mindbody is where larger studios live, and it is also where Portuguese invoicing usually falls back to manual exports. This bridge is the same engine pattern that runs Glofox to Moloni in production today, connected to Mindbody through its developer programme, with access granted by you and revocable by you.
Your grant, your accounts, your data
Step 1
You grant access
The integration is registered in the Mindbody developer programme. You activate it for your site from your own Mindbody API integrations screen. No password of yours is ever shared or stored.
Step 2
Sales are read
Completed sales are read from Mindbody with the client, the pricing option or contract behind them, and the amount paid.
Step 3
Documents are raised
Charges that pass the checks become invoice receipts in your Moloni account. Charges that fail a check wait in a review queue with the reason attached.
Mindbody revenue, mapped to Moloni lines
Contracts and memberships
Recurring contract payments document gross, per collection, on the client record confirmed by the NIF check. A declined collection documents nothing until it succeeds.
Pricing options and packs
Each pricing option maps to its Moloni revenue line with the VAT rate your accountant confirms for it. New options are mapped before they go on sale, or their first sales are held for review.
Retail
Product sales carry the standard rate treatment and stay separate from service revenue in the mapping, the documents and the close pack.
Guests and visitors
Drop in guests with no Portuguese tax number are documented under Consumidor Final, number 999999990, with country attribution, under the treatment your accountant signs off.
Answered before you ask
Refunds and returns
A refund raises a credit note in Moloni against the original invoice receipt. Originals are never edited or deleted, so the audit trail stays complete.
Frozen or cancelled contracts
A frozen contract collects nothing and documents nothing. A cancelled contract keeps the documents for the collections that already happened, and the credit note path covers any refunded part.
Duplicates
Every Moloni document carries the reference of the Mindbody sale behind it. A repeated read or a retried event matches that reference and stops before a second document can exist.
Multi site groups
Each Mindbody site maps to its own Moloni document series, so locations never share numbering, and the close pack reports per site and in total.
What your accountant receives
The close pack: invoice receipts and credit notes in Moloni, the exception list with reasons, and the reconciliation between Mindbody sales and Moloni documents, with card and payment fees shown as their own line so documents stay gross. The SAF-T (PT) export comes out of Moloni as usual.
Straight answers
Is Mindbody to Moloni already running somewhere?
The production pair today is Glofox to Moloni, live at one Lisbon studio. This page describes the same engine pattern applied to Mindbody, connected through the Mindbody developer programme. We would rather say that plainly than imply a listed app that does not exist yet.
What access do you need in Mindbody?
An activated integration under the developer programme, granted by you for your site, scoped to the sales and client data the bridge reads. You can revoke it from the same screen at any time.
Who approves the tax mapping?
Your certified accountant, before go live. Contracts, pricing options and retail each carry the VAT rate and account code they confirm.
Monoja · Lisbon, Portugal · All pairs · Live today: Glofox to Moloni, in production at one Lisbon studio. Every other pair is built per studio on the same engine pattern.