Glofox bookings in. Moloni invoices out. Nothing typed twice.
This is the pair that runs today. Memberships and packs are sold in Glofox, the money moves, and the certified document appears in Moloni under the rules your accountant signed. This page describes the mechanism in full, because the mechanism is the proof.
From a charge in Glofox to a document in Moloni
Step 1
The charge is read
The engine reads each completed charge from Glofox with its member, its revenue line and its amount. A charge that never completed never reaches the invoicing side.
Step 2
The rules decide
Member identity and NIF are checked, the VAT rate for that revenue line is confirmed against the signed mapping, and the charge is matched against every document already issued. A duplicate stops here.
Step 3
The document is raised
Clean charges become invoice receipts in your own Moloni account. Anything the rules cannot confirm is held in a review queue with the reason written next to it.
Every revenue event Glofox produces
Memberships
Recurring membership billing is the core of this pair. Each successful collection raises its document in Moloni for the gross amount paid, on the member record the NIF check confirmed.
Class packs and drop ins
Pack purchases and single visit payments post as their own revenue lines, each carrying the VAT rate your accountant confirmed for that line.
Retail
Product sales keep their own VAT treatment, separate from service revenue. Retail at the standard rate never inherits the rate of a class line by accident.
Guests without a Portuguese NIF
Visiting clients with no Portuguese tax number are documented under Consumidor Final, number 999999990, with country attribution, exactly as your accountant signs off before go live.
What happens when it is not clean
A refund
A refund never edits or deletes the original document. A credit note is issued in Moloni against it, for the refunded amount, and both documents stay in the ledger and in the run log. Your accountant sees the full story, not a gap.
A cancelled booking
No charge means no document. If a booking was charged and then cancelled with a refund, the credit note path above applies. If the charge stands, the document stands.
A no show
A no show that was paid is revenue, and it is documented like any other paid visit. A no show that was never charged produces nothing, because documents follow money.
A failed payment
A failed collection raises no document. When the member pays later, through a retry or a new payment at the desk, that successful charge is the one that gets documented, once.
A duplicate
Every issued document carries the reference of the charge behind it. A retry, a repeated event or a second read of the same charge matches that reference and stops. The same charge is never invoiced twice.
Missing or invalid data
A charge with a missing NIF, an unmapped revenue line or no confirmed VAT rate is held, not guessed. It lands in the exception list with a plain reason, and it posts only after the data or the mapping is fixed.
The tax rules run before the document exists
Each revenue line carries the VAT rate your accountant confirmed for it. The engine checks the rate, the member NIF by Modulo 11, and the document type before anything is issued in Moloni. A line with no confirmed rate is held. Nothing posts because it looked close enough.
Payment provider fees never change the document. The invoice is raised for the full gross amount the client paid, and the fee appears as its own line in the reconciliation, classified under the account code your accountant agrees before go live. Gross and payout both stay visible, which is what a clean audit needs.
What your accountant receives
The close pack
The month, assembled: documents issued, credit notes, the exception list with reasons, and the reconciliation between Glofox charges and Moloni documents.
The SAF-T file
Moloni produces the SAF-T (PT) export your accountant files, built from documents that were checked before they existed.
The run log
Every cycle is logged: what was read, what posted, what was held and why. Your accountant gets the log, not a story.
Your data first, commitment after
Send 30 days of exports from Glofox. We run the mapper over your own month and read back what posts cleanly, what gets held, and what the bridge covers. Your accountant reviews the mapping and signs it before anything is built into your live accounts.
Scope and price are agreed after the export review. No payment until your accountant signs off. We work in your accounts, not a copy of them.
Straight answers
Do I need to change my booking or invoicing software?
No. The bridge connects the Glofox and Moloni accounts you already run. Your front desk and your accountant keep their own tools and logins.
Are the invoices certified?
Yes. Documents are created inside Moloni, an AT certified invoicing platform, in your account, with ATCUD on every document and the SAF-T export your accountant files.
Who approves the tax rules?
Your certified accountant reviews and signs the mapping of revenue lines, VAT rates and account codes before the first live run. The engine enforces that signed mapping and holds anything outside it.
What does my accountant have to change?
Nothing about their tools. They receive the close pack, the exception list and the SAF-T file, and they keep working in the portal they already use.
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.