Parkcore Blogging Site

One Click to “Have They Paid?”: Why Full Payment History Belongs on the Booking Screen
Parkcore's Payment History report lets staff pick any pitch or any owner and see that pitch's or owner's complete financial record in one view — every booking or invoice, what's been paid, what's outstanding — without a date range to narrow it first, because the whole point is seeing everything. Both views export to CSV, and both can also be exported as a branded PDF for sharing.

One Click to "Have They Paid?": Why Full Payment History Belongs on the Booking Screen

Quick answer: Parkcore's Payment History report lets staff pick any pitch or any owner and see that pitch's or owner's complete financial record in one view — every booking or invoice, what's been paid, what's outstanding — without a date range to narrow it first, because the whole point is seeing everything. Both views export to CSV, and both can also be exported as a branded PDF for sharing.

Every business that's ever run a customer account of any complexity eventually discovers the same expensive gap: the question "has this person actually paid us?" sounds like it should have an instant answer, and in a disorganised system, it never quite does. Retail banking solved this generations ago by insisting every account have a single statement — not three ledgers that someone has to reconcile in their head. The lesson generalised far beyond banking: anywhere money changes hands more than once with the same person, that person deserves one place where the running total lives, not a scavenger hunt across every system that's ever touched their account.


Holiday parks run two parallel versions of this problem — guests booking pitches, and owners paying site fees — and until recently, Parkcore answered "have they paid?" the same way most park software still does: look at the booking, look at the invoice, do the sum yourself.

What actually shipped

Payment History is a new section in Reports with a simple toggle at the top: Pitch or Owner.

Pitch mode lets staff pick any unit — park-owned or privately owned — and see every booking that pitch has ever had, most recent first, with guest name, dates, status, total, deposit paid, and outstanding balance. Summary tiles above the table show the total booked, total taken, and total outstanding for that pitch at a glance, so the headline numbers don't require scanning a table first.


Owner mode does the equivalent for an individual owner's invoices — every invoice ever raised against them, paid or outstanding, with the same kind of summary tiles rolling it up into one picture. Crucially, this isn't scoped by date range unless staff want it to be; the default is the complete history, because "how much has this owner paid us, ever" is a more useful question most of the time than "how much did they pay us between two arbitrary dates."


Both views export to CSV for anyone who wants to work the numbers further, and both also generate a branded PDF — useful for anything from an internal finance review to something that needs to go to an owner or accountant looking clean rather than like a database export.

"Have They Paid?"

Why "have they paid?" deserves to be a one-click answer

Picture the moment this actually gets used: a guest calls asking why they've been sent a balance reminder they're sure they've already cleared, or an owner queries an invoice they believe was settled months ago. In a fragmented system, answering that confidently means checking the booking record, then the payment record, then maybe a separate invoicing tool, then doing the arithmetic by hand while the guest or owner waits on the phone. Every one of those extra steps is a moment where staff sound less certain than they should, on a question that's entirely answerable — the information already exists, it's just scattered.


Payment History collapses that into the thing it should always have been: pick the pitch or the owner, look at one screen, answer confidently. That's a small-sounding change that shows up in a very specific, very human way — the tone of a phone call where staff clearly know the answer, versus one where they're visibly hunting for it.

Pitch and owner are kept deliberately separate

One decision worth explaining, because it's not obvious from the outside: a privately owned pitch's booking history and its owner's site-fee invoices are shown separately, not blended into one combined view. Selecting a pitch in Pitch mode shows only that pitch's bookings — it won't also pull in the owner's own site-fee invoices, because those are a different kind of financial relationship answering a different kind of question. To see an owner's invoice history, switch to Owner mode and select them directly. It's a small distinction, but conflating the two would make both views noisier and less trustworthy for the specific question each is actually meant to answer.

What this shows — and what it honestly doesn't, yet

It's worth being precise about what this report actually displays, because the distinction matters if it's ever relied on for something it isn't quite built for yet. Payment History shows financial status — what's been taken in total, what's still outstanding — using Parkcore's existing booking and invoice records.

It's one row per booking in Pitch mode, one row per invoice in Owner mode. It is not, today, an itemised log of individual payment events: if a guest paid a deposit on one date and the balance on another, this view shows the combined total taken and the current outstanding balance, not two separately dated entries. For the vast majority of "have they paid, and how much do they still owe" questions, that status-level view is exactly what's needed — but a genuinely itemised payment ledger, with every individual transaction dated and listed, is a different and larger piece of work, flagged as a natural next phase rather than built into this first version.

Who can see it

Payment History is available to admin, manager, and accountant roles — the same access level as Parkcore's other financial reports. If a park wants reception to be able to answer "has this guest paid their balance" directly at the desk without escalating to a manager, that's a deliberate access decision worth raising, since it's a slightly wider circle than Parkcore's financial reporting has typically used.

Key takeaways

- Payment History lets staff pick any pitch or owner and see their complete financial record in one view, not scoped to a date range by default.

- Pitch mode covers bookings per unit; Owner mode covers invoices per owner — kept separate so each answers its own specific question cleanly.

- Summary tiles show totals taken and outstanding at a glance, above a full table of the underlying records.

- Both views export to CSV or a branded PDF, ready for internal use or sharing with an owner or accountant.

- The report shows financial status (totals taken and owed), not yet an itemised log of individual payment events — a fuller payment ledger is a planned future phase.

payments

Frequently asked questions

No — the default view shows a pitch's or owner's complete history. Date range filtering is available for Pitch mode when a narrower view is useful, but omitting it returns everything.

Pitch mode shows a specific unit's booking history only. Owner mode shows an individual owner's invoice history only. The two are kept separate deliberately — a privately owned pitch's bookings don't pull in that owner's site-fee invoices, and vice versa.

Not yet. Today's report shows financial status — totals taken and outstanding — based on existing booking and invoice records, rather than a dated log of each separate payment. An itemised payment ledger is a planned next phase.

Admin, manager, and accountant roles today, matching the access level used across Parkcore's other financial reporting.

No — it's a fast, confident answer to a specific operational question at the desk or in a review, not a replacement for full accounting. Both views export cleanly to CSV for anyone who needs to take the numbers further into dedicated accounting software.

Parks wanting an instant, confident answer to "have they paid?" can find Payment History inside Reports in Parkcore now, for both pitches and owners.


Leave a Reply

Your email address will not be published. Required fields are marked *

Steve Richards headshot

Bio for Stephen Richards: Born in Colwyn Bay North Wales, Steve's introduction it Computers was at secondary school in 1974. That first year, Machine Code was hand written onto gridded paper and sent to Connah's Quay Technical College where is was copied to punch card and then entered into a mainframe computer. The results printed out were sent back for the following week!

Steve left School in 1976 joining the Royal Air Force to work on RADAR and communications equipment. His last 5 years involved working in an Automatic Test Equipment (ATE) department on the System Management Team and also writing models for Microchips. It was a good job that he had kept up with computers which had become rather a passion by the time he started in ATE.

During that time the main Mainframe we replaced in a £3.9 million upgrade reducing the run time of the biggest ATE program from just under 2 weeks to the time it took for a finger to come off a depressed return key!

Leaving the RAF after 18 years service Steve worked for a Charity (Apex Leicester Project) before returning to electronics at Sonatest in Milton Keynes which after 3 or 4 years led to a Job at Telematica the then development arm of Trafficmaster PLC (Tm). Eventually brought in-house at Tm he worked moved into the IT Support Team with his last project moving email from a Linux Box to Microsoft Echange for the 300 users in the company each of whom typically had 5 email addresses.

In 2006 Steve left to start his own company back in North Wales, Computer Technical Solutions was an MSP and moved to become an MSSP following another of Steve's passions Cybersecurity. Officially retiring in 2025, by May 2026 that overactive mind started thinking about all of the software he had seen not just for MSSPs but also for his clients that was either extremely expensive or that didn't exist with a complete answer to the needs of the SME.

By August 2026 two significant pieces of software have been created. Netmon the Network Monitoring Software and the second release Parkcore aimed at Caravan/Lodge Holiday Parks..... And so it begins!