Who this is for: studio operators (admin panel) · Product: Podyx V2
Purchases is the money view of your studio. Where Sessions shows you the operational side, who is booked and when, Purchases is the ledger of every transaction that has happened on your account. When your accountant asks a question, this is the tab you open.
🎥 Watch the walkthrough
🔧 Where to find it
Operations → Purchases
⚠️ Money amounts are called Subtotal and Total
Amounts are named the way they are named at checkout. Total price is Subtotal, and Total price (VAT) is Total. You will see those two names across the Purchases lists and detail pages, in Session details, and in the client's Purchase history.
The purchases CSV export uses the same names: its header row reads Subtotal and Total. The values and the column order are unchanged — only the header text is different.
⚠️ Anything that reads those files by column name needs updating: a spreadsheet whose formulas point at a named column, a Zap or other automation that maps the export, an accountant's import template. An export that silently loses a column mapping is the kind of thing nobody notices until month end. Run one export now and check whatever consumes it on the other side.
💡 Sorting Individual purchases by Subtotal or Total follows the amounts shown on screen, refunded bookings included — so the order of the rows matches the numbers in them.
💳 Amount paid and Amount due
A purchase nobody has paid yet reads Amount due rather than Amount paid. That covers a cash Pay Later booking waiting on your approval, a payment link that has not been paid, and a payment that failed.
A booking that was cancelled, declined or expired and was paid at the studio shows no amount due at all — not in the CMS, and not in the client's account. A cash booking that never happened used to show the client a figure they did not owe, which is the kind of thing that comes back to you as an awkward email. There is nothing to clear up: affected bookings read correctly now.
💡 The label itself now tells you whether money has actually arrived — something an Amount paid row showing a figure on an unpaid booking never did.
🛠 Filter by what was bought
Individuals. One-off session purchases.
Bundles. Multi-session packages.
Subscriptions. Including whether each one is currently active.
💡 On the Individual tab, the Approved and Declined filter chips appear only for studios that actually use Pay Later — including studios migrated from v1 that take cash. If you are card-only, those chips stay hidden rather than sitting there matching nothing.
📄 What each status means
Status | What it means |
Pending | A payment link was sent from the admin booking flow and has not been paid yet |
Approved by client | Used in the pay later flow, where the booking request had to be approved |
Paid automatically | Payment completed by the client on your website |
Manual | The booking was created by an admin |
Refunded | The booking was cancelled and gave back everything it held — including when part of it went to the client's wallet through an earlier session edit |
💡 A booking whose money came back partly as a refund and partly as wallet credit still reads Refunded, because nothing is left on it. Open the purchase to see how much went each way — the wallet part is listed as a refund to the wallet.
Subscriptions have a Manual status and a matching filter of their own, for a private subscription granted to a client without a payment link. A subscription in that state used to be listed as Active; it now reads Manual, so you can tell at a glance which subscriptions were granted rather than bought.
Sessions your team granted by hand on a bundle or subscription are listed on the purchase page under Manually granted sessions, separate from the sessions the client paid for — so a goodwill session never looks like part of what was bought.
💡 For how manual subscriptions and manual session grants work, see Subscriptions — that article is the canonical home for them.
🧮 Tax on older bookings
Bookings made before 6 August 2026, and bookings carried over from the previous Podyx, show the tax that was genuinely charged at the time rather than a figure recalculated at today's rate. A staff booking from the previous Podyx no longer has tax added twice — a 120.00 booking with 20.00 tax reads 120.00, not 140.00 or 144.00 — and a previous-Podyx booking with a price override lists the tax paid on top of that price.
⚠️ These corrections apply to the bookings already affected, with nothing to backfill on your side. Figures on an old purchase may therefore differ from what you saw before, and from an export you took earlier. The figures you see now are the correct ones — if you are reconciling against an older export, that is the explanation for the difference.
💡 For the fuller explanation of how tax is worked out and displayed, see Tax, VAT & Currency — that article is the canonical home for it.
📆 Session value on a multi-month subscription
A session booked from a multi-month subscription shows its share of the whole term, not of a single month. Take a 6-month plan with 10 sessions a month, sold for 4,800: that is 60 sessions over the term, so each session shows 80 — not 480. The Dashboard uses the same figure, so revenue per session reads the same wherever you look.
⚠️ Sessions booked before this change keep the old per-session figure until Podyx runs a one-time correction on them. There is nothing for you to do. Until then, an older multi-month subscription session may show a higher figure than a newer one from the same plan — that is the explanation if you spot the difference.
✂️ A session cancelled after a paid edit
If a session was edited into a more expensive booking, paid for by card, and then cancelled, the purchase shows the correct refunded, remaining and paid amounts. Those three used to be able to disagree after exactly that sequence — which is the moment a client is most likely to be reading the numbers over your shoulder.
❌ Sessions cancelled from a booking
When a session is cancelled from a cash booking, its value comes off what is left to collect. The session page, the purchase page and the client's purchase breakdown show it as Cancelled sessions and Remaining active value, so you collect for the sessions that are still going ahead and not for one that was dropped.
On the Purchases list and on the member page, the Sessions column reads N of M for a booking that has lost sessions — for example 2 of 3. Hover over it to see the detail.
💡 A booking reading N of M is still live for the sessions it has left. Only a booking that gave back everything it held reads Refunded.
When the last session is deleted. Deleting the last session of a paid booking keeps its purchase, payment history and add-on purchases here in Purchases, so the money is never lost from your records. The session page, the Sessions list and the Calendar warn you before a delete removes the booking — see Sessions.
👛 Refunds to the client's wallet
When money goes back to a client as wallet credit rather than to their card, it is recorded where you would look for any other refund. A booking's Payment history in the CMS shows a Refunded to wallet row, and Purchase details shows the refund to the wallet alongside the rest of the money on that purchase.
💡 If a client says they were never refunded, check for a Refunded to wallet row first. The money may be sitting in their wallet as credit, ready for their next booking — see Credits.
↩️ When a refund fails after it looked successful
A refund taken through Square appears on the purchase as soon as Square accepts it, rather than hours later when Square has finished processing it. The record matches what you just did, so you are not left wondering whether a refund went through — or issuing it a second time.
A refund can be reported as successful by the payment processor and still fail later, most often because the client's card has since been closed. When that happens, Podyx takes the refund back off the payment's refunded total and alerts your studio, so the ledger stops counting money the client never actually received.
⚠️ If you get one of these alerts, the client has not been refunded. Contact them and arrange the refund another way — a bank transfer or a new card — then record what you did.
⏱️ Payments that arrive after a booking expires
Some payments land after the booking they were for has already expired. Podyx refunds these automatically, and those refunds run promptly.
When a payment goes through after the booking has already closed, the client is told what actually happened — and is promised a refund only when one is genuinely on its way, rather than being shown a "Payment failed — retry" message that explains nothing.
⚠️ If an automatic refund of this kind fails permanently, your studio receives an email asking you to refund the client by hand. Treat that email as a to-do: the money is still with you until you send it back.
🔍 Open a transaction
Open any purchase to see the full ledger entry: the transaction details, the Subtotal and the Total, the date and time of purchase, exactly what was bought, and the associated Stripe data. Session purchases show the net amount, tax charged, and tax-inclusive total. Add-on purchases show the same breakdown with tax and gross rows listed separately. It is the complete story of a single payment in one place.
Credits and card together. Purchase details, and the Money card on the session page, show the correct amounts for bookings that mix credits and card: refunds on such bookings, credits returned when a session is cancelled, and admin bookings partly paid with credits. This applies to older bookings too.
When a member of your team adds an additional service to a booking without sending a payment link, the purchase records it as collected outside Podyx and it appears in Purchases as a staff sale. Money taken at the desk shows up in your records rather than vanishing from them.
Add-on refunds on the client's page. A client's Purchases tab and Recent purchases show any recorded add-on refund next to the original total, so you can see what was charged and what went back without opening each purchase.
💡 On a package booking whose only paid extra was later removed, the breakdown no longer carries a leftover row of zero figures — the extra simply drops out.
ℹ️ Opened a purchase from a client's page? Back returns you to that client's Purchases tab, not to the main Purchases list.
🟢 The Completed badge on a session
Inside Purchase Details, a session whose time has already passed is badged Completed — but only when the purchase itself is confirmed.
Previously the badge went by the clock alone, so a pending or expired purchase could show its sessions as having taken place. The record then read as though a session had been delivered when it was never paid for and may never have happened at all.
💡 Completed now means two things at once: the session actually ran, and the purchase behind it actually went through. That makes it something you can rely on when reconciling, rather than a date check you have to verify by hand.
A cancelled session's card on the CMS session page says that it was cancelled, so the status is visible there too and not only on the purchase.
🏷️ Purchases made with a promo code
When a booking was bought with a promo code, the purchase page shows the whole chain rather than just a final figure: the original price, the promo code used, the discount applied, tax, the total, any credits used, and the amount paid. You can see exactly how a number was arrived at without reconstructing it yourself.
⚠️ Subtotal is the price before tax and Total is the full price of the purchase with tax included — neither is what the client handed over. That figure has its own row: Amount paid, or Amount due where nothing has been paid yet. If you have been reading the Total as the amount collected, read Amount paid instead — on any purchase where credits were used, they are different numbers.
🔒 A redeemed promo code is shown in full only to team members whose role lets them manage promo codes. Everyone else sees the first two letters with the rest masked, for example SU******. The discount amount stays visible to everyone.
🧾 Invoices
If a purchase has a generated invoice, you can download it straight from the purchase record. You can also view all invoices in one place and export them as a ZIP file, which is the fastest way to hand a month or a quarter to your accountant.
An add-on bought after the booking shows its own invoice in the Purchases list, and in the client's purchase history, rather than a dash.
Once a purchase has an invoice, the purchase page stops offering Generate invoice, so you cannot issue a second invoice for the same transaction by accident.
💡 One purchase, one invoice — which is what your accountant and your client both expect to find.
📤 Export to CSV
ℹ️ CSV export is a Premium plan feature.
Export the purchase list to CSV for reporting, reconciliation, or anything you want to do in a spreadsheet outside Podyx. The money columns are headed Subtotal and Total; if a spreadsheet, automation or import template of yours still looks for Total price or Total price (VAT), point it at the new names.
🧠 Why it matters
Month-end stops being a hunt. Every transaction, with VAT, in one filterable list.
You can see what actually sells: one-offs, bundles or subscriptions.
Chasing unpaid money is easy. Filter to pending and you have your follow-up list.
Paid and unpaid are readable at a glance, because an unpaid purchase says Amount due rather than Amount paid.
You only chase what is still owed, because a session cancelled from a cash booking comes off the remaining active value.
Money taken at the desk is still recorded, because a service added without a payment link appears as a staff sale collected outside Podyx.
Wallet refunds are on the record, so a refund that went to credit is never mistaken for one that never happened.
Discounts are auditable, because every promo code purchase shows its full breakdown.
A completed session means a delivered session, because the badge only appears on confirmed purchases.
Old bookings show the tax that was actually paid, so historic records match what the client was charged.
✅ Summary
Sessions answers "who is coming in." Purchases answers "what did we earn, from what, and has it been paid." Use the filters to separate one-offs, bundles and subscriptions, check statuses to find unpaid balances, read the amounts as Subtotal and Total — the same names used at checkout and in the CSV export — and re-point any spreadsheet or automation that still reads that export by the old column names, read Amount paid rather than Total when credits are involved and treat Amount due as money that has not arrived — a cancelled, declined or expired booking paid at the studio shows none — sort Individual purchases by Subtotal or Total knowing the order matches the figures on screen, look for the Manual status and filter on a subscription granted without a payment link where one used to read Active, find sessions your team gave by hand under Manually granted sessions, read a multi-month subscription session as its share of the whole term — older sessions keep the old figure until Podyx's one-time correction, with nothing for you to do — expect a session cancelled from a cash booking to come off the Remaining active value and the Sessions column to read N of M, expect a paid booking whose last session was deleted to keep its purchase, payment history and add-on purchases, read Refunded as a booking that gave back everything it held even when part went to the wallet, find wallet refunds as Refunded to wallet rows in a booking's Payment history and in Purchase details, see recorded add-on refunds next to the original total on a client's Purchases tab, trust Purchase details to show the right amounts on bookings that mix credits and card, expect an additional service your team added without a payment link to appear as a staff sale collected outside Podyx, trust the Completed badge in Purchase Details because it now appears only on a session that ran under a confirmed purchase, expect bookings from before 6 August 2026 and bookings carried over from the previous Podyx to show the tax actually charged — which may differ from an older export, and is the correct figure — act on any alert or email telling you a refund failed because those clients still need their money, find the invoice for an add-on bought after the booking on its own row, and export invoices as a ZIP when it is time to do the books, knowing a purchase that already has an invoice will not offer to generate another.
Related: Sessions · Invoicing · Payments & Refunds · Credits · Promo Codes · Clients
