Your whole quarter sits in four numbers, and you open any one of them to the order underneath it. Gross, platform fees, refunds, net: on the Australian financial year, in Sydney time, and you download the files your bookkeeper wants.
The finance hub is on from your first order. You pay the published per-cart fee, plus a one-time A$29 ex GST to set up your payout account, and that’s the lot.
Bayside Runners · FinancePreview
Gross sales
A$18,540.00
214 paid orders
Platform fees
A$912.15
ex GST
Refunds
A$342.00
Processed in period
Net to organiser
A$17,194.63
Gross − fees and their GST − refunds
April to June: the BAS quarter now closed, and the one the exports below are cut to.
Example account · demo figures
A$17,285
Net for the quarter
214
Orders, each with an invoice
6
Files your bookkeeper knows
3
Quarters ready for the BAS
Open any order to its invoice.
The order ledger filters in place, the moment you touch it. Any row opens to the split an accountant asks for, so “what was this A$95.94?” is one click.
01
Four ranges, one tap
This quarter, last quarter, this financial year, all time: Sydney-dated, on the Australian financial year. The numbers above the ledger match the rows below it.
02
A numbered invoice, per order
Sequential per club, issued at payment. The fee split, the GST where GST applies, the provider reference and the full refund history all hang off it.
03
Filters live in the URL
Search by purchaser, narrow to one event, then paste the view straight into an email to your committee. It opens on what you were looking at.
Order · Bayside RunfestPart refunded
ANYRUN-A007-000412
Paid 28 Jun 2026 · Aisha K.
10K entry × 1A$65.00
Event tee × 1A$25.00
Platform fee, ex GST · runner-paidA$5.40
GST on the feeA$0.54
Total paidA$95.94
Not charged
GST on this order
stripe · pi_3PqK…A2
Provider reference
ProcessedA$25.0002 Jul 2026 · event tee
Six files your bookkeeper already knows.
Finance exports · Apr–Jun 2026Console filenames
01
Order ledgerWorking papers
anyrun-bayside-runners-order-ledger-2026-04-01-to-2026-06-30.csvThe master sheet: every order with its type column, the full fee split, GST and the provider reference. Reconcile anything against it.
02
Xero sales invoicesXero
anyrun-bayside-runners-xero-sales-invoices-2026-04-01-to-2026-06-30.csvHeaders byte-exact to Xero’s own template. Import tax-inclusive, GST on Income, account 200, dates DD/MM/YYYY.
03
Xero bank statementXero
anyrun-bayside-runners-xero-bank-statement-2026-04-01-to-2026-06-30.csvImport against your AnyRun clearing account: income positive, fees and refunds negative, so it reconciles to zero.
04
QuickBooks bank transactionsQuickBooks
anyrun-bayside-runners-qbo-bank-transactions-2026-04-01-to-2026-06-30.csvThe three-column upload QBO expects. For the GST side, paste the sales-summary journal beside it.
05
GST / BAS summaryThe BAS
anyrun-bayside-runners-gst-bas-summary-2026-04-01-to-2026-06-30.csvG1 gross sales and 1A GST per BAS quarter. Refunds keep their columns and are reported separately from sales.
06
Itemised feesWorking papers
anyrun-bayside-runners-itemised-fees-2026-04-01-to-2026-06-30.csvPlatform fees, split entrant-paid against organiser-absorbed. The expense side of the story, per order.
07
Sales-summary journalClipboard
The seventh is not a file. Gross, fees, refunds and net for the period as plain text: one button copies it, ready to paste as a journal entry.
These are files.
CSVs you hand to whoever does your books. A file opens in any ledger, keeps working without a key to babysit, and leaves with you. Bank feeds and the Xero API push live outside AnyRun.
We log every export: who pulled which file, over which range, when.
We show the totals. Your accountant owns the treatment.
GST handled, BAS ready.
Your entry prices include GST where it applies to you. Our fee is charged ex GST, and the tax on it is a separate line. When your club is registered for GST, G1 and 1A sit in quarterly rows for you, and when it isn’t the GST column stays at zero.
GST / BAS summary · by quarterPreview
Gross sales, GST and refunds for each BAS quarter, as the export writes them
Quarter
Orders
G1 gross
1A GST
Refunds
Jan–Mar 2026
129
11,020.00
1,001.82
180.00
Apr–Jun 2026
214
18,540.00
1,685.45
342.00
Jul–Sep 2026
48
4,210.00
382.73
65.00
Figures in A$, with our fee shown ex GST beside its own GST line. Checkout, the drill-down and the export run the same arithmetic, so the three agree.
Quarters, made native
BAS quarters and Australian financial years are native. The range presets and every export speak the same calendar.
Refunds keep their column
A refund keeps its GST column and is reported separately from sales. The quarter reads the way the ATO reads it.
Credits are an expense
Credits your club buys are money you pay us. They are not revenue you earned, and they touch neither G1 nor 1A.
Give away the books, keep the keys.
The person who does your books gets a seat, and everyone else on race day gets a separate one. Your bookkeeper sees the money, and a runner’s phone number and date of birth stay with you. The owner login stays with the owner, and the CSVs stop being an email chain.
Invite to Bayside RunnersPreview
Email
otto@brandtbookkeeping.com.au
Role
AdminStaffCoordinatorTimerAccountant
Send invite
Sees money. Settings stay closed.
Can reach
The finance hub, over any rangeThe ledger, and every invoice under itSix exports and the journalThe refund queue, read-onlyThe audit log’s financial slice
Cannot reach
Entries, results and timingVolunteers, media and commsEntrant personal detailsRefund decisions: they see the queueEvent settings, pricing, publishing
Six roles × what they can touchEnforced on every screen
What each of the six console roles can reach, area by area
Role
Finance
Refunds
Entries
Crew
Comms
Audit
Owner
✓
✓
✓
✓
✓
✓
Admin
✓
✓
✓
✓
✓
✓
Staff
—
—
✓
✓
✓
—
Volunteer coordinator
—
—
—
✓
—
—
Timer
—
—
✓
—
—
—
Accountant
✓
○
—
—
—
$
✓ full · ○ sees the queue, cannot decide · $ financial slice · no access
The seat decides what loads. Someone without finance can’t reach the money by pasting a URL, and it cuts every way: coordinators get the roster, timers get timing.
“Processed” means the money moved.
A refund marked done that the runner has not received is how a platform ends up in the group chat for the wrong reasons. Here the order of operations is a rule the system enforces.
01
The runner asks from their account
It lands in your queue with the order already attached to it.
02
Approve arms a confirm
A second click with the dollar amount printed on it, so the refund you send is the one you meant.
03
The provider moves the money first
If that call fails the request stays open. The books say done once the money has moved.
04
Then, and only then, processed
The runner is told of the decision either way, and the audit row is written.
Refund requests · Bayside RunfestPreview
Aisha K.10K entryA$65.00Requested
The console’s two-step confirm, playable: try approving it.
What a refund returnsEngine maths
10K entryA$65.00
Platform fee, ex GSTA$4.18
GST on the feeA$0.42
Runner paidA$69.60
Back on the same cardA$65.00
The A$4.18 fee and its A$0.42 GST are the only part that stays, and both were on the checkout page before anyone paid.
Money leaves fingerprints here.
Your money actions land in an append-only log: who, what, when. The log only ever grows, and the accountant seat reads its financial slice while an entrant’s details stay with the organiser.
Optional analytics cookies. We'd like to load Google Tag Manager (it carries Google Analytics, our advertising measurement and Microsoft Clarity) to understand how AnyRun is used. Until you accept, none of it is loaded at all; "necessary only" keeps it that way, and we don't sell your data. Details in the Cookie Policy.
