One terminal total, three different revenue streams
Open a fitness studio's point-of-sale settlement report and it typically shows one running list of transactions for the day — a protein bar here, a ten-session personal training package there, a day pass sold to a visiting friend of a member somewhere in between. The terminal itself doesn't distinguish between these categories in any way that's useful for finance reporting; it simply records that a card was charged a certain amount at a certain time.
Before an owner can answer a basic question — is personal training revenue actually growing relative to retail, is day pass volume trending up or down seasonally — every one of these needs to become the same thing: category, item, amount, date, in one consistent structure. Doing that by hand, one settlement report at a time, is the kind of repetitive work that eats a bookkeeper's afternoon every single month without fail.
Why a POS settlement report is harder to use than it looks
A settlement report looks like a simple document — item, amount, time — and that simplicity hides real variation once you look at more than a handful of transactions.
Every terminal formats its report differently
A cloud-based POS export, a printed end-of-day summary and an emailed PDF all represent the same underlying sales completely differently.
Item descriptions are often abbreviated or generic
A settlement report might list "PKG10" or "Item #4471" rather than a readable description, leaving the actual category to be inferred from context.
Multi-session packages aren't always flagged as such
Some systems record a ten-session PT package as one lump sale, others record each session as it's redeemed — the same underlying revenue can look structurally different depending on the system.
Tips and gratuity aren't always broken out
Some terminals record a tip as a separate line, others fold it directly into the total charged, making it hard to see actual service revenue versus gratuity at a glance.
None of these four are a sign of anything being done wrong at the front desk — they're the normal shape of how different point-of-sale systems independently record a sale, and they're exactly why a single rigid spreadsheet template rarely survives contact with more than one terminal type for long.
What this doesn't do, stated up front
Doesn't calculate net deposit or match against the bank
It reads the sales recorded on the settlement report. Matching those sales against a bank deposit and membership dues is the job of membership dues and POS matching, a separate step.
Doesn't connect to a POS terminal or inventory system
There's no API, no login, no integration. You export or download the settlement report yourself, the same way you already do, and upload it.
Doesn't track remaining inventory or session counts
Confirming how many sessions remain on a member's package, or how much retail stock is left, stays your point-of-sale or inventory system's job.
Doesn't process a refund or void a transaction
Those actions happen at the terminal. This reads the settlement report after the fact, whatever it shows.
What's left is narrow, and it's exactly the part that consumes a disproportionate amount of time every single month: turning a blended terminal report into a clean, category-separated spreadsheet.
What gets read
| Field | Source |
|---|---|
| Item description, category | Settlement report line item |
| Amount, date and time | Settlement report |
| Package versus single-session flag | Settlement report, where distinguished |
| Tip or gratuity, where present | Settlement report |
| Location | Settlement report header |
Five fields, read consistently regardless of whether the source is a cloud export or a printed end-of-day summary.
The categories it actually separates
| Category | Typical examples |
|---|---|
| Personal training | Single sessions, multi-session packages, semi-private training |
| Retail | Apparel, supplements, water and snacks |
| Day passes and drop-ins | Single-visit passes, guest passes, class drop-ins |
| Other services | Locker rental, towel service, nutrition consults |
Four distinct categories, each read from whatever description or code the settlement report actually uses — the terminal's own labeling stops mattering once it's categorized.
A day's POS settlement, separated
A busy Saturday at a mid-size studio, with sales across all four categories.
| Category | Item | Amount |
|---|---|---|
| Personal training | 10-session package | $650.00 |
| Retail | Protein powder, shaker | $58.00 |
| Day pass | Single-visit pass | $25.00 |
| Personal training | Single session, drop-in | $75.00 |
Four completely different sale types, one consistent output structure — ready to feed directly into monthly revenue reporting or into a broader dues and POS matching process without anyone re-typing a single line.
How it works
Upload settlement reports in whatever format they arrive
Cloud export, printed scan or emailed PDF — mixed formats in one batch are fine.
Each line is read and categorized
Retail, PT, day pass or other, with a confidence level per line.
Ambiguous items flagged
An unclear description or an unrecognized code is marked for a quick manual confirm.
Export
Excel, CSV or JSON — one row per sale, categorized and dated, ready for revenue reporting.
Personal training packages sold over multiple visits
A multi-session personal training package is typically sold once, as a single upfront charge, but delivered over several weeks or months as the member redeems individual sessions. Some POS systems record only the initial sale; others also log each redemption as its own zero-dollar entry, which can look confusing on a raw settlement report if the two aren't distinguished clearly.
Reading the initial package sale as the revenue event, and treating redemption entries as informational rather than additional revenue, keeps the reported PT revenue accurate rather than double-counted or understated depending on which reporting convention a specific terminal happens to follow.
Day passes and drop-in visitors
A day pass sold to a visiting friend of a member, or a drop-in class fee charged to someone not on a recurring membership, is a small transaction individually but can add up to a meaningful revenue category for a studio in a high-traffic location or near tourist areas. Because these sales don't connect to any recurring member record, they're easy to undercount if the only revenue tracking that exists is built around the membership roster.
Reading day passes as their own category, separate from both recurring dues and other POS sales, keeps this genuinely separate revenue stream visible for its own trend analysis.
Tips and gratuity on training sessions
Where a studio allows tipping on personal training sessions or other services, a settlement report sometimes breaks the tip out as its own line and sometimes folds it directly into the total charged. Confusing the two can either overstate service revenue or understate what actually needs to be passed through to the trainer, depending on the studio's compensation structure.
Reading a tip as its own field where the settlement report distinguishes it keeps base service revenue and gratuity pass-through cleanly separate in the export.
What happens after POS sales are separated
A categorized POS export is the raw material for two downstream processes: revenue reporting, which needs retail, PT and day pass totals broken out for a meaningful trend view, and deposit reconciliation, which needs the same sales matched against what actually settled in the bank alongside recurring dues. Once POS sales exist in one consistent structure, feeding them into either process — or into a broader reconciliation that checks both at once — becomes straightforward in a way that working from raw, mixed-category settlement reports directly never is. The detail of matching POS sales against the bank deposit once they're categorized is covered in membership dues and POS matching.
For a studio also tracking recurring membership dues from the same merchant batches, the same output feeds naturally into a broader bank reconciliation workflow, described in more detail on the gym bank statement to Excel page.
Who this is for
Studio owners tracking revenue mix
Retail, PT and day pass trends visible on their own, instead of blended into one terminal total.
Bookkeepers serving fitness clients
Clean, categorized POS data ready to feed straight into monthly revenue reporting.
Multi-location studio operators
One consistent categorization process regardless of which POS terminal each site happens to use.
Studios growing a specific revenue category
A clear, separated trend line for the category being actively grown, like personal training.
This isn't a point-of-sale terminal or inventory system
Worth being precise about the boundary. This doesn't process a sale, track inventory, or connect to any POS platform. There's no login to any client system. What it reads is the settlement report after the fact — whatever format it arrives in — turning it into structured, categorized data.
Moving from a spreadsheet built by hand
Most owners and bookkeepers reaching for this have someone manually re-typing settlement report lines into a spreadsheet every single month, guessing at categories based on abbreviated item descriptions — a task that scales linearly with sales volume and doesn't get meaningfully faster with practice, since every report still has to be read and categorized individually.
The transition doesn't require changing how the POS terminal itself works. A reasonable first step is running one month's worth of settlement reports through and comparing the output against whatever the manual process already produced, to confirm the categorization matches before relying on it for a full reporting period.
Most studios making this switch report the biggest relief isn't the raw time saved, though that's real, but finally being able to answer a question like "is PT revenue actually growing" with a real number instead of a guess based on a general sense of how busy the trainers have looked lately.
How often to process settlement reports
Matching your processing cadence to your revenue reporting schedule is the simplest rule that actually works — monthly for most studios producing a monthly revenue report. Processing settlement reports right before each reporting cycle, rather than in occasional large batches, keeps the volume manageable and keeps any flagged, unclear entries fresh enough to resolve quickly.
What accuracy actually looks like
Accuracy is best understood as a confidence distribution across settlement lines rather than a single number. Clean digital exports with clear item descriptions read at very high confidence consistently. Reports with abbreviated codes or handwritten summaries vary more — a clearly labeled one reads just as reliably, while a cryptic or smudged one produces a larger flagged tail needing manual confirmation.
In practice, a studio with a modern digital POS terminal typically sees 90% or more of lines land at high confidence, with the remainder split between a quick confirm and genuinely ambiguous entries that need a look at the original terminal record regardless of what tool is used.
Seasonal shifts in retail and day pass volume
Many studios see retail sales spike around New Year's resolution season and day pass volume rise during summer tourist months, while personal training packages often sell more heavily right after a membership sign-up surge. Reading POS sales in categorized form makes these seasonal patterns visible as a genuine trend rather than an impression based on how busy the front desk seemed on any given day.
A studio that tracks category-level seasonality over a couple of years can plan retail inventory purchasing and PT staffing more deliberately around known peaks, rather than reacting to each season's demand after it's already underway.
The same seasonal view also helps set expectations internally — a January retail dip after a strong December, or a summer lull in PT package sales while members are traveling, can look alarming compared to the prior month if nobody has a categorized multi-year baseline to compare against. Seeing that the same dip showed up at the same point last year, and the year before that, turns a worrying-looking number into an expected, already-understood seasonal pattern rather than a fresh cause for concern each time it recurs.
Privacy
Uploads go over TLS, encrypted end to end.
Processing runs on EU-hosted infrastructure.
Original documents are deleted immediately after extraction.
POS sales data is never used to train AI models.
Full details are on the security page.