Releases

3.20.1 current

24 September 2026

• No more "Customers to confirm". When JollyDrivers raises a new customer's first invoice in Xero, it finds the customer already in Xero by email, ABN, phone or exact name and uses them, or creates them when there is no match, and that is the end of it. Since 1.4.31 no invoice has waited for a confirmation, but a card still appeared afterwards asking you to confirm the customer, and a banner on every page said JollyDrivers could not raise their invoices until you did. Neither was true. The panel and the banner are gone.

• Customers are now found by their phone number. The phone check never actually searched phone numbers in Xero, so a customer with only a phone was matched on their exact name or created again. It now looks for the number however it was typed in Xero (0412 345 678, +61 412 345 678, and so on).

• A busy Xero no longer creates a duplicate customer. If Xero doesn't answer while JollyDrivers is looking for the customer, the invoice is refused with "try again shortly". Before, JollyDrivers could take that as "no match" and create the customer a second time.

• When more than one Xero contact matches (for example, two sharing an accounts@ email), JollyDrivers picks the one whose name, phone or ABN also match, instead of whichever Xero listed first.

3.20.0

24 September 2026

No changes recorded for this release.

3.19.1

24 September 2026

No changes recorded for this release.

3.19.0

24 September 2026

• A tip can now be recorded as a tip, not as part of the fare. A passenger who hands over $200 for a $50 job has given a $150 tip, and until now the only place to put it was the fare, so commission was taken from it, GST was charged on it, and the driver's running account said they were holding the operator's money. When Mark as paid is given more than the customer owes in total (the fare, any extras and anything bought for them), it asks whether the extra was a tip. Say yes and the fare is recorded as paid, with the tip beside it. A tip can also be recorded on its own at any time, including after the fare is paid, from the new Tips card on the trip. Every tip is the driver's in full, with no commission and no GST, and one recorded by mistake can be taken back out with a reason. Behind Features:Tips.

• Who has the tip is part of the record. A tip handed to the driver is theirs straight away. One that landed in the operator's account (their card terminal, or a bank transfer) is held for the driver until it is paid out, and every held tip must be paid out before 30 June. The new Tips page shows operators what they are holding for each driver, with a countdown through June and anything held from a past financial year flagged overdue. Drivers see what was handed to them and what is being held for them.

• A cut fare and a tip are shown side by side. If the fare was lowered after the booking was confirmed and a tip was then recorded, the trip shows both, so the operator and the driver can see whether part of the tip was really fare. The operator can move up to the amount of the cut from the tip back into the fare, and the driver sees that on the timeline. Otherwise the tip stays entirely the driver's.

• Tips reach Xero as tips, never as income. Operators nominate a Tips held for drivers account (a liability, BAS Excluded) on the Accounting tab. A card or transfer tip on a fare JollyDrivers invoiced in Xero gets its own document there, marked paid into the account the money landed in. A driver's statement bill passes held tips on to them in a BAS Excluded line, outside the taxable part of a recipient-created tax invoice. When an operator pays a tip on its own, the Tips page records it and says exactly what to enter in Xero.

3.18.0

24 September 2026

• A driver's AI assistant can now tell you everything booked ahead for one customer. Ask "when is Karen next travelling with me?" and customer_schedule lists every job still to come for that customer, soonest first, across every operator you drive for: one under way now, each pickup still ahead, and a round trip whose return is still to come even though its outbound has run. It gives the count, and says plainly when nothing is booked. Give it the customer from find_customer, or a name, mobile number or email; if two customers share a name it lists both and asks which, rather than picking one. Cancelled, declined, finished and draft jobs are left out. Two pickups either side of the border come out in the order they actually happen, not the order their clocks read.

• find_customer no longer calls a future booking someone's "last trip". It used to report whichever of the customer's bookings had the latest date, even one next week or one that was cancelled, so their next job could only be guessed from it. "Last" is now the most recent trip already taken, and each customer shows how many jobs are booked ahead.

• Times from a driver's assistant now say whose clock they are, e.g. "Fri 26 Sep, 9:00 am (NSW)". A pickup's time has always been the pickup's own local time, but nothing said so, and my_schedule described every time as Brisbane time. Across the border that is an hour's difference for half the year.

3.17.0

23 September 2026

• The front page now tells the story: rideshare, the right way up. A six-slide story (how rideshare has worked, the flip, and what changes for drivers, riders and operators), cards that turn over from "the old way" to "the JollyDrivers way" as you scroll, the life of a booking, a section on connecting your own AI assistant with example conversations, and a look under the bonnet. It is animated, but every word is in the page itself, so search engines and AI assistants read all of it. Anyone whose phone asks for less motion gets it standing still.

• The work behind it, counted by the code. The front page shows how many commits, merged pull requests, releases, automated tests and lines of source code have gone into JollyDrivers, and how many days since the first line. The figures are counted from the repository every time JollyDrivers is built, never typed in.

• A blog, at jollydrivers.com.au/blog, with the first two posts: Rideshare, the right way up and Bring your own AI. The latest posts also appear on the front page, and there is an Atom feed for news readers. A post can be written ahead and dated for the day it should appear.

• System Admin → Public site is a new page for everything the public sees: the contact details (moved here from Settings), JollyDrivers' social media accounts, and a launch countdown. Social links appear on the site only once an account's address is entered, and each must be on its own platform's site. The countdown shows on the front page only once a date is set, and disappears by itself when the moment passes. Every change is recorded in the settings change log.

3.16.0

23 September 2026

• jollydrivers.com.au now has a front page. The bare address used to open straight onto the sign-in card, and an AI assistant pointed at it read 87 words — some of them the "connection dropped" message the app keeps hidden. It now opens on a page that says what JollyDrivers does for operators, drivers and riders, how a booking goes from a chat to an invoice in the operator's own Xero, what JollyDrivers deliberately is not, how to connect your own AI assistant, and how to get in touch. It is plain HTML that any crawler or assistant can read without running the app, and it is laid out for phones first.

• Sign-in has moved to jollydrivers.com.au/signin. Nothing else about it changes. If you are already signed in, the bare address still takes you straight to your dashboard, and the installed app opens on the sign-in card as before.

• The public contact details are now set in System Admin → Settings → Public site — contact: an email address, an optional phone number, an introduction and an optional reply-time line. The email address follows the setting everywhere JollyDrivers publishes it — every public page, the summary for AI assistants (llms.txt) and the public AI endpoint — and every change is recorded in the settings change log with the name of whoever made it.

• Behind the scenes: the public pages' source files no longer answer at a second address (/public/about.html and the rest now redirect to the real page), and the front page's "Connect your AI" section only appears while the public AI endpoint is switched on.

3.15.0

23 September 2026

• An operator's AI assistant can now raise a booking's invoice in Xero — always as a draft. propose_raise_invoice works out exactly what the trip page's Request invoice would raise, using the same code, and writes nothing while doing it: the lines with their account codes, the total, the due date, and which Xero contact it goes to — or, plainly, that a NEW contact would be created, which stays in Xero once made. raise_invoice then raises that exact draft, once, within ten minutes, and refuses if anything about it has changed since. A draft sends nothing to the customer and can be deleted without trace; approve it with approve_invoice when it is right. If several Xero contacts could be the customer it refuses rather than guess, and a delivery's invoice is still raised from the trip page. Behind Features:McpOperatorWrites.

• A booking can no longer end up with two live invoices. The trip page only ever offered one, but the rule now lives where the invoice is raised, so no other way in can raise a second while the first stands; void it first and a new one can be raised as before.

• Raising an invoice now shows on the booking's timeline, naming who asked for it and whether it went in as a draft. Before, a single booking's invoice appeared with no line saying who raised it.

• Behind the scenes: a raise refused because an account code is blank no longer leaves a new saved bill-to behind for the customer.

3.14.0

23 September 2026

• An operator's AI assistant can now send the customer their confirmation. propose_send_confirmation works out exactly what the trip page's Send confirmation would send — the ride confirmation, or the completion notice or receipt once the trip is done — to the booking's own customer and passenger addresses, sent as the operator, with the same subject; it lists every recipient, the sender and what happens to the invoice (including, plainly, that a draft invoice is approved in Xero first and that neither the email nor the approval can be undone). send_confirmation then sends that exact plan, once, within ten minutes, and refuses if anything about it has changed since. It never takes an email address, so nothing a customer wrote can redirect a document. It is refused where the page's own checks would stop it — a booking not confirmed yet, a trip whose progress was never recorded, a completion notice whose invoice is not approved — and it is for passenger bookings; a task's confirmation is sent from the trip page. Behind Features:McpOperatorWrites.

• A confirmation sent from an assistant shows it on the timeline, with the admin's name beside the operator's when the admin was acting.

3.13.0

23 September 2026

• An operator's AI assistant can now approve a draft invoice. When JollyDrivers raised a booking's invoice in the operator's Xero as a draft, propose_approve_invoice shows it — the number, the total, the due date and every line — says plainly that approving cannot be undone (an approved invoice keeps its number for good and can only be voided afterwards), and says whether a completion notice to the customer is waiting behind it; approve_invoice then approves exactly that invoice, once, within ten minutes, and refuses if anything on it has changed since. Like the trip page's Approve button, a completion notice that was queued behind the approval goes to the customer straight after. Only a draft JollyDrivers raised itself can be approved this way. Behind Features:McpOperatorWrites.

3.12.0

23 September 2026

• An operator's AI assistant can now cancel a booking. propose_cancel_booking takes the reason from the same list as the trip page's cancel window (the booker cancelled, weather, a duplicate and so on) and an optional note, checks the booking exactly as the page's Cancel button does, and shows what would change — including, plainly, an invoice that cancelling does NOT void; cancel_booking then cancels it once, within ten minutes, through the same door as the page. The timeline shows "Cancelled by operator" with the reason. Nothing is sent to the customer or the driver, and it can be undone from the trip page's timeline. A completed trip is not cancelled this way: turning one into a cancellation settles its invoice, and stays with the driver and the admin. Behind Features:McpOperatorWrites.

3.11.0

23 September 2026

• An operator's AI assistant can now put a driver on a booking. propose_assign_driver finds the driver by name among the operator's active fleet and checks the job the way the bookings page does — the compliance verdict, a clash with the driver's other jobs for this operator, and a party bigger than the vehicle carries — and shows all three in the proposal instead of asking; assign_driver then makes that one assignment, once, within ten minutes. As on the bookings page it is for bookings with no driver yet, and only open ones. Nothing is sent to the driver or the customer; the job appears in the driver's trips. Behind Features:McpOperatorWrites.

• A driver can only ever be assigned from the booking's own operator's active fleet. The bookings page only ever offered those drivers, but the rule now lives where the assignment is written, so no other way in can put a driver from another business, or one who has left, on a job.

3.10.0

23 September 2026

• Operators can now cancel a booking and send the customer their confirmation from the trip page. Both buttons were the driver's and the admin's alone; an operator runs the book and the customer rings them, so they are the operator's too, in exactly the same windows — cancel on any booking that has not finished, and the confirmation (or completion notice, or receipt) from confirmed onward. Reclassifying a completed trip as a cancellation stays with the driver and the admin, because it changes an invoice already issued.

• When an operator cancels, the reason is kept. The trip page has always asked why, and for some time the answer went nowhere. An operator's cancellation now shows on the timeline as "Cancelled by operator" with the reason and any note beneath it.

• A confirmation now records who sent it. Every send used to be written as the booking's driver, whoever pressed the button; the timeline now names the person who actually sent it. Automatic sends are recorded as before.

• The send-confirmation window says what really happens: JollyDrivers emails it to the people listed, sent as the operator. It no longer says the operator will deliver it, no longer mentions a PDF, and no longer refuses to send when the operator has no notification email — that address has played no part in sending since JollyDrivers began sending confirmations itself.

• Creating a booking from an operator's AI assistant again says the confirmation is sent from the trip page — true now that operators have the button.

3.9.0

23 September 2026

• An operator's AI assistant can now accept or decline a booking that is waiting. Two new pairs of tools on an operator connection (or the admin acting as one): propose_accept_booking and propose_decline_booking find the booking in the operator's own book, check it exactly as the trip page's Accept and Decline buttons do, and change nothing — they show the booking, what would change and a proposal to approve; accept_booking and decline_booking then carry out that one proposal, once, within ten minutes, and refuse if the booking has changed in the meantime. Nothing is sent to the customer either way. The timeline records the operator's name "via AI assistant", with the admin's name beside it when the admin was acting. Behind a new switch, Features:McpOperatorWrites, off by default, which covers every operator change made from an assistant; accepting also still needs Features:OperatorAcceptance.

• Creating a booking from an operator's assistant no longer tells you to send the customer's confirmation from the trip page. An operator has no such button — the driver sends it from theirs — and the reply now says so.

3.8.0

23 September 2026

• An operator's AI assistant can now read the book. Four new tools on an operator connection (or the admin acting as one): bookings_board shows the bookings as the board does — today, upcoming or past, filtered by status, to unassigned jobs, or to jobs still owing money — with the driver and paid state on every line; booking_detail opens one booking by reference with route, driver, fare, what has been paid and the invoice if there is one; fleet_status lists every active driver with their vehicle and whether the app rates them available, on a trip, off duty or blocked out right now; unpaid_invoices lists open invoices oldest-due first, flags overdue ones, and adds the completed jobs that owe money with no invoice yet. Everything is read-only and scoped exactly as the operator's own pages are; assigning, accepting and invoicing from an assistant are still to come.

3.7.2

23 September 2026

• Operators can now let the JollyDrivers admin act as them too. The "Let the JollyDrivers admin act as me" switch appears on an operator's account page as well as a driver's, and act_as runs the admin's assistant in that operator's own book — bookings it makes land there, with the admin's name recorded beside the operator's. list_delegations says whether each person would be acted as a driver or an operator. The operator tools an assistant has today are the booking ones; the bookings board and invoices are still to come.

3.7.1

23 September 2026

• Drivers can now see everything the admin has done as them. Under the "Let the JollyDrivers admin act as me" switch on your account page there is a log of every action taken while acting — what was looked at, what was changed, when it started and stopped — newest first. Nothing in it can be edited.

• A Delegation Ledger for the admin, beside the Security Ledger: every stretch of acting as somebody, every call in it, filterable by person and by tool, with a shortcut from the user list for anyone who has granted access.

3.7.0

23 September 2026

• The JollyDrivers admin can now act as a driver from their own AI assistant. Three new tools on the admin connection: list_delegations shows every driver who has switched on "let the JollyDrivers admin act as me", act_as switches the connection to run as that driver — their trips, their passengers, their bookings — and stop_acting switches back. While acting, the admin's own tools are off, and every answer opens with "[as driver: John, by admin Jolly]" so there is never any doubt who is doing what.

• The driver is told, and everything is recorded. When acting starts the driver gets a text (or an email if there is no usable number), and every call made while acting — reads included — is written to a delegation ledger naming both people, the tool and what it answered. Stamps, texts, bookings and wishes made while acting carry the admin's name beside the driver's on their own trails.

• Acting ends by itself after 30 minutes without a call, when the driver turns the switch off, when the admin disconnects the assistant, or when delegation is switched off — and the next answer says why. It cannot be nested.

3.6.3

23 September 2026

• Drivers can now say whether the JollyDrivers admin may act as them. A new panel on your account page, "Let the JollyDrivers admin act as me", has one switch per admin. It is yours alone: the admin cannot turn it on, and you can turn it off at any time. Each change is kept as a dated record, so there is always an answer to "when did I allow this". Behind Features:McpDelegation, off by default. Acting itself is not switched on yet; for now the switch records your choice for when it is.

• The admin's user list shows who has allowed it, read-only, so they can see at a glance whose account they could act for once the tools arrive.

3.6.2

23 September 2026

• The trip timeline, the wishlist trail and "me too" can now record that an admin did something on a driver's behalf. Every stamp, booking, text and wish already names the account it ran under; each of those records has gained a place for a second name, the admin whose hand actually did it, and the timeline reads "John via AI assistant (by admin Jolly, acting as John)" when it is set. Nothing sets it yet — this is the second step towards letting the JollyDrivers admin act for a driver from their assistant (docs/mcp-admin-delegation-design.md), and every existing record is unchanged.

3.6.1

23 September 2026

• Every answer from a connected AI assistant now opens with who it is acting as — "[as driver: John]" — on every JollyDrivers tool, refusals included. Groundwork for letting the JollyDrivers admin act for a driver from their own assistant (design in docs/mcp-admin-delegation-design.md); nothing can act as anybody else yet.

• An assistant that reaches for a tool its connection cannot use is now told what context is missing rather than a bare "not for you": a driver connection is told which role to reconnect as, and the admin connection is told that acting as a driver is not switched on yet. Behind the scenes all fifteen tool classes now get their identity from one place, and a build check stops a new tool reading it anywhere else.

3.6.0

23 September 2026

• Every time in a customer's email now says which state's clock it is. A trip's pickup and arrival, the "as at" line on an itinerary, a delivery's collected and delivered stamps and its deadline all read like "6:30 PM (AEDT · NSW)". Before, the timezone only appeared when JollyDrivers could prove you might misread it — which is a fair rule on screen, where it knows where you are, and the wrong one in an email that could be opened anywhere. On an itinerary listing trips either side of the border it left two clocks an hour apart with nothing to tell them apart.

• A place with no street number — "Coolangatta Beach, Queensland" — no longer loses its state. Addresses like that come back from the map with the state spelled out and no postcode, and JollyDrivers could not read either, so it fell back to showing that stop in the pickup's clock. A Banora Point to Coolangatta trip therefore printed an arrival an hour out.

• Changing a stop to an address in another state now moves that stop's clock with it. A booking's timezone was worked out once and then kept, so editing a drop-off from Tweed Heads to Queensland left it still reading as New South Wales — permanently, and with nothing on screen to say so. One customer's itinerary went out with an arrival time an hour before it will happen. The five bookings already affected have been corrected. If a new address can't be placed, JollyDrivers now says so instead of quietly keeping the old state.

3.5.0

22 September 2026

• A customer's card can now find their other bookings saved under a different spelling of their name, and put the right name on all of them at once. Open the customer, choose Find bookings saved under another name, type the name they were saved under, and tick the ones that are really them. This is the bulk correction that was withdrawn on 3.4.1 for offering to relabel one customer's trips as somebody else's — it comes back on the card rather than firing by itself after a booking is corrected, it starts with nothing ticked, and it searches the name you type rather than guessing which names look close enough. Bookings already showing the customer's name are left out, since there is nothing to fix on those.

3.4.2

22 September 2026

• Behind the scenes: the release index — the depth layer an assistant reads behind this changelog — credited every release with the previous release's pull request, so the record of what shipped where pointed one release off all the way down. Each release now carries the pull request that actually delivered it, and nine releases that had none recorded now do.

3.4.1

22 September 2026

• Setting the travelling passenger now changes that one booking and nothing else. After recording who actually travelled, JollyDrivers went on to offer to apply the same person to every other booking still carrying the old name — 26 of them, all pre-ticked. On exactly the booking this feature is for, that old name is the booking customer's, so it was offering to relabel their own trips as their friend's. The step is gone.

3.4.0

22 September 2026

• A booking can now say who actually travelled, separately from who booked it. Some trips were recorded as if the booking customer had travelled themselves, when really they'd booked it for someone else. The Set travelling passenger action on the trip page now lets you correct that: search for or type who actually rode, and the booking customer stays exactly who they were — still the one who's billed — even on a booking that never had a saved card for them before.

3.3.2

22 September 2026

• The booking chat no longer asks "Ready to submit?" — it goes straight to the booking summary. Once the payment method is answered, the summary card appears with its Submit, Save as Draft and Cancel buttons; that card was always the real confirmation, and the extra question in front of it was where bookings were getting stuck on a blank last turn. A note can still be typed at any point, before or after the summary.

3.3.1

22 September 2026

• Corrected, and it was live for about an hour: the FAQ said JollyDrivers charges $3.30 on each settled booking when it is charging nothing. The fee was set yesterday with charging not starting until 2027, and the page took the amount from the setting but ignored the start date. It now says plainly that nothing is being charged yet, and from when — while still giving the price and the free-under-$30 rule, so nobody has to guess what is coming.

• Fixed: a date typed into Start charging from was read as UTC rather than Brisbane, so charging would have begun at 10am on the chosen day instead of midnight. Any booking settled that morning would have been free.

3.3.0

22 September 2026

• What JollyDrivers charges an operator for a booking is now a setting, not a number buried in the code. System Admin → Booking fee sets the standard fee and, if you want, a different one for a particular operator. Every change is dated and kept: a booking that has already settled keeps the fee that applied on the day, so changing the price never rewrites what was already owed.

• A small job can now be free outright. Set a figure and any booking below it is not charged at all — not a reduced fee, nothing. This replaces the old idea of capping the fee at 5% of the fare, which had the side effect of making the fee a percentage of every fare under $66. Flat above the line, free below it, and never a share of anybody’s fare.

• The fare that threshold is measured against is what the operator actually earned — the fare less tolls, airport access and the levy, which were only ever passing through. A $34 job carrying $6 of tolls counts as $28, and is free.

• Fees now accrue on a ledger once a booking has been paid in full, whether that was cash, a card on the operator’s terminal, a bank transfer or an invoice. Each line records the booking, what it was worked out from and what made it billable, so any figure can be traced back to the job that produced it. A booking that is refunded or deleted has its fee taken back off.

• You can count without charging. Set a date for charging to start, and every booking that settles before it is recorded at the fee it would have carried — owing nothing. Leave the date empty to charge straight away. This is not the same as setting the fee to $0.00, which records the booking as having been worth nothing: with a start date you keep the number, which is the whole point of counting before you bill.

• Nothing is being charged to anybody. No invoice is raised and no money moves — that part is not built. Accrual is also off until it is switched on, and a booking that settles before a fee has been set accrues nothing.

• Each operator now has a statement, month by month, on the same screen: how many bookings were charged, what they came to, how many were waived or not billed yet, and what was not charged. And a CSV download of every line, carrying the booking, the figure the fee was worked out from and why it came out the way it did — so the fees can be read, kept, or keyed into Xero by hand without waiting for anything to be connected.

• A booking that was waived records a line showing $0 and what it would have been, so what the free-below-the-line rule costs is a number rather than a guess.

• The fee on the FAQ now comes from the setting itself rather than from a sentence somebody typed. Change the fee and the public page changes with it — previously it could have gone stale without anyone touching it.

• Corrected: the FAQ said the fee is “held down to 5% of the fare”. With a free-below-the-line rule instead of a cap that is no longer what would happen, and two different claims about one fee could not both stay published.

3.2.4

22 September 2026

• Corrected: How it works still said card payments go through Stripe. They do not. A card is taken on the operator’s own terminal and recorded here against the booking — JollyDrivers does not process the card. It sat in a list beside Xero and Google Maps, which are live, so it read as a description of what happens to your customer’s money.

• Corrected: the same page promised drivers “the operator’s statement to you by email”. Earnings statements are live; the emailed one is not, and the sentence made one claim out of two.

• Corrected: it also still called peer checking of compliance documents “not live”. That was fixed on two other pages yesterday and missed here.

• Added: both the FAQ and How it works now say JollyDrivers is in closed beta, and where to write. The summary AI assistants read has said so for a while; the two pages a person actually lands on did not, so they read as an open door.

3.2.3

22 September 2026

• What JollyDrivers charges is now on the FAQ: a flat $3.30 including GST on each settled booking, never charged to the passenger. On a short run it is held down to 5% of the fare, so it can never be a large slice of a small job. Nothing is being charged yet — this is the price being stated plainly rather than a bill arriving.

• Corrected, and this one matters: several pages said JollyDrivers takes “no commission and no share of any fare” and one said “never a percentage of the fare”. That was wrong. The fee is flat, but the 5% cap means that on a small fare it is a percentage of it — the cap working in your favour, not a commission. The pages now say what is true: the fee never rises with the fare.

• Corrected: the public summary said peer checking of a driver’s compliance documents was “not yet live”. It has been live for some time.

• Corrected: the description of connecting your own AI said every tool is read-only. That is true of the sign-in-free one; the account endpoint can write, and now says so.

• And a test now refuses to let any of those sentences come back. Two releases ago the same wording was fixed in one file and left in five others, because the rule lived in a commit message rather than in the build.

3.2.2

21 September 2026

• Changed: two lines in the description JollyDrivers gives of itself were promises rather than descriptions — one about what JollyDrivers charges, one about where money sits. Both now say what the software does, which is the part anybody can check. Nothing about fares, invoicing or payments changed; only the words repeated back when somebody asks an AI what JollyDrivers is.

• The difference matters because those words are now answered automatically to people who have never signed in. “We take nothing from the passenger” is a commercial undertaking that could stop being true without anybody editing a file. “The fare comes from the operator’s own fare book” is a fact about how it works, and it stays true or the code changes.

3.2.1

21 September 2026

• Corrected: the note below about the map of what JollyDrivers can do said eleven jobs. There are twelve. It was counted off the list a driver sees, which leaves out the one only a platform admin has, and nothing was checked against the map itself. The entry below now says twelve.

• Worth saying why a wrong word got its own release. The map exists because the previous description of JollyDrivers went stale and nothing noticed. The checks added with it prove every part of JollyDrivers is described — they cannot prove the sentence about the map is right, and the very first one was not. Leaving it wrong on a page written to be read by strangers would have been the same failure in miniature.

3.2.0

21 September 2026

• New: ask an AI what JollyDrivers can do and the answer now comes from JollyDrivers itself. There has been a way for anyone’s assistant to ask that since September, but the answer was a paragraph somebody typed by hand, and nothing made it keep up. It now comes from a map of what JollyDrivers actually does — twelve jobs people are trying to do, from taking a booking to getting paid — and anything not fully live says so.

• The map cannot quietly go out of date. Every switch in JollyDrivers and every tile on your board has to belong to one of those jobs, checked on every build in both directions. Add something new and the build stops until somebody says which job it is part of. That is the whole point: the last document that tried to describe JollyDrivers went stale because nothing was checking it.

• Fixed, while we were in there: the check that decides whether a change needs a full build had two files fighting over one name, and the changelog lost. Every release since has been skipping the tests that read it. It does not any more.

3.1.0

21 September 2026

• New: the JollyDrivers changelog is public. Everything you are reading is now at jollydrivers.com.au/releases with no sign-in — so you can send somebody the link, and so an AI asked “is this thing still being worked on?” can answer without an account. That is a question anyone weighing up software asks early, and until today JollyDrivers had no way to answer it. The What’s new page inside the app is unchanged.

• The public page shows what this file says and nothing more. No commit numbers, no database changes, no list of internal switches — that record exists, it is useful, and it is deliberately not on a page anyone can read.

• Some older entries have been reworded, and it is worth saying why. A few quoted real invoice numbers and one real customer’s fare. One printed the word you type to confirm the most consequential thing an operator can do. Four described how our SMS provider proves to JollyDrivers that a message really came from it. None of that belonged in a file written for the people who use JollyDrivers, so it has been taken out of the file itself rather than hidden from one view of it.

• There is now somewhere to write to: hello@jollydrivers.com.au, on the About page and in the summary AI assistants read. Until today the one place that invited people to get in touch pointed them at a page with no way to do it.

3.0.3

21 September 2026

• New: paste a link to a JollyDrivers page into a message, a chat or a post and it now arrives with a title and a short description instead of a bare web address. Two of the three public pages had nothing to show, so they showed nothing — which is a poor first impression of a business you are asking somebody to trust with their bookings.

• The front page now says who JollyDrivers is in a form a machine can read, not only in words. Until today an AI arriving at jollydrivers.com.au had to fetch a second page before it could tell you what company it was even looking at.

• Those two descriptions of the business live in separate files, and nothing joined them up. They are now checked against each other on every build: if they ever drift into describing two different organisations with the same name, the build stops. That is the sort of thing nobody notices for a year.

• The summary an AI reads about what JollyDrivers can do now mentions that it can ask JollyDrivers questions directly, rather than only read about it.

3.0.2

21 September 2026

• New: you can now tell somebody to point their own AI at jollydrivers.com.au and get a real answer. JollyDrivers has had a sign-in-free way for an AI assistant to ask it questions since September — what JollyDrivers is, what an operator, a driver or a rider can each do, how it differs from a rideshare app — but nothing on the site said so, so the only people who could use it were the ones who had already been told the address. The summary for AI assistants, the About page and the crawler instructions now all print it. It needs no account, everything it answers is read-only, and it reads no bookings and no personal details.

• Fixed: the site map left out the front page entirely, and gave two pages a date older than the last time they actually changed — so a search engine or AI could be told nothing had moved when it had. The privacy page had no date at all.

• Fixed: the description that shows when you install JollyDrivers to a phone home screen still called it a “trip request platform for private hire and airport transfers”. That was written in April and describes a different product.

• The Stripe sample pages are no longer offered to crawlers. Nothing secret was on them, but they are scaffolding, not a description of JollyDrivers.

• And none of this is left to somebody remembering any more: a test now reads those files and fails the build if a public page goes missing from the site map, an entry loses its date, or the address stops being printed. Until today nothing in the test suite had ever read them.

3.0.1

21 September 2026

• Fixed: when somebody asked their own AI assistant about JollyDrivers, and it asked us how to connect, it was told that account access “is being built and is not yet live”. It has been live since September, running for a small pilot — so the question an interested operator or driver is most likely to ask was being answered with a no. It now says what is true: the address to add, that it is a pilot you ask to join rather than something open to everyone, and that riders cannot connect an assistant yet.

• The same answer promised “the same address” without ever giving one, anywhere. Both are now in it — the sign-in-free one any assistant can use, and the account one — and a test now holds them to the real endpoint, so renaming it fails the build instead of quietly sending the next person who asks nowhere.

3.0.0

21 September 2026

• JollyDrivers can now help build itself, and nothing it suggests happens until somebody says yes. That is a different kind of software from the one you were using yesterday, which is why the number jumped instead of ticking along. There is no version 2 — the shape changed here, not gradually.

• Your ideas now go somewhere. There is a Wishlist for the thing that isn't broken and has no date on it: the thought you had while doing something else. It is shared, so you can see that somebody already wished for the thing you were about to ask for and back theirs instead of raising it twice. How many people want something is the order the list is in, because on a list of ideas that is the only honest signal there is.

• And they come back to you. When something you asked for goes live, your own reports page says which release it went out in and what else came with it. An idea that was decided against stays on the list with the reason — that is the answer you are owed, and hiding it would only invite the same wish again next month.

• One person approves every idea before anyone builds it, and that cannot be delegated to a machine. An AI assistant connected to JollyDrivers can suggest an idea, read the backlog and do the work — but it cannot authorise its own suggestion, however it is asked. That approval happens inside JollyDrivers and nowhere else. Saying no to an idea needs no approval at all; only saying yes does.

• Every change an assistant makes says so. A decision made by an AI and one somebody typed themselves must never look the same a year later, so the record names both the person and the assistant they used.

• JollyDrivers now keeps a record of why it is the way it is — what each of its hundred-odd releases touched, what it came from, and, where somebody wrote it down, the reason. Where nobody wrote a reason down, it says so rather than guessing.

• Nothing in JollyDrivers runs off on its own. Every improvement above started with a person asking for it.

1.4.98

21 September 2026

• Fixed: the Status list on a report now reads in the order the work actually goes — New, Triaged, Planned, In progress, Resolved, Won't fix, Duplicate, Closed. Planned used to sit dead last, below the three statuses that mean it is over, and on a normal window it was below the fold entirely: you had to scroll past the endings to find the one that says "agreed, not started yet", which on a wishlist is the one you reach for most. Nothing about your existing reports changed — only the order they are offered in.

• While we were there, every other list in JollyDrivers that offers you a set of choices was checked for the same thing. Twenty-one of them, and this was the only one that had gone wrong.

1.4.97

21 September 2026

• New: a wish now has to be approved before anyone builds it. Anybody can still put an idea on the wishlist, and that has not changed. But a wish cannot be moved to In progress or recorded as Resolved until the platform admin has authorised it, on the report's own screen. There is an Approve this to be built button there, and until it is pressed nothing happens.

• This is the one thing a connected AI assistant cannot do for you. An assistant connected in the admin role can set every other status as you — so "only the admin can do it" would not have been a limit on an assistant at all. It could have suggested an idea, approved its own idea as you, built it and shipped it, and every line of the record would have read exactly as if a person had decided each step. Approving is deliberately available in JollyDrivers itself and nowhere else.

• Saying no still costs nothing. Declining a wish — won't fix, duplicate, closed — needs no approval at all. A gate that made refusing an idea as ceremonious as agreeing to one would just mean ideas sat unanswered.

• Bugs and change requests are not gated. Something already broken, or somebody already blocked, should not wait for a signature — least of all anything about money or safety. Only wishes, which are the kind that can breed.

• Approval is recorded with who gave it and when, and the person who suggested the idea is told: being informed that your idea was agreed to is better news than a status change. It can be withdrawn again, which is also recorded — an approval reconsidered is a normal thing, and a gate you cannot close again is one people stop opening.

• There is no setting to turn any of this off. A switch that disables the gatekeeper would not be a gatekeeper.

1.4.96

21 September 2026

• Fixed: an attendance job — a dog walked, a garden watered — was being called a delivery in four places. It isn't one. It carries nothing, goes nowhere, and has one stop rather than a route, and the words on screen now say so.

• The one that stopped you working: opening an attendance job to change its time or its price was refused with "A delivery needs at least one described item". An attendance job correctly has no items, so there was nothing you could do to satisfy that — the only way to edit one was not to. Creating one was always fine; only editing was blocked.

• Every list that shows jobs — your trips, the bookings board, deliveries, the calendar, the admin lists — described an attendance job in a delivery's words: "Delivered" when it was done, "In transit" while it was happening, "Awaiting operator" when nobody was waiting for anything. It now reads "Done", "In progress" and "Operator notified".

• The calendar's peek panel opened an attendance job under the heading "Delivery", and the edit window called it "Edit Delivery". Both now say Task.

• For anyone using a screen reader: the calendar announced every attendance job as "delivery number 000". It now says "task number 000" — and where JollyDrivers hasn't been told which kind of task a job is, it says the general word rather than guessing.

1.4.95

21 September 2026

• The wishlist now shows an admin a Work this link on each idea, straight through to the screen where a decision is made and recorded. The board itself is unchanged and still looks the same to everybody: it is one link, and only the platform admin sees it. Before this, an admin reading a wish had no way to reach the only screen that could act on it — you had to already know the queue existed and go and find the idea again by its reference, which is a thing you can only know if you built it.

1.4.94

21 September 2026

• Fixed, and found by using yesterday's release: when you connect an assistant as the JollyDrivers admin and ask it who it is, it was told about booking a job and looking up addresses — things that connection has no book for and cannot do — and was never told about the support backlog, which is the only reason it exists. It now describes the four things it can actually do, and says plainly that it cannot touch bookings, money, operators, drivers or settings.

• That answer also used to say "Drives for: no operator yet" to an admin connection. True, and it read like something had gone wrong rather than like the design. It now says the connection covers the support queue and has no book of its own.

• Fixed, on the audit trail: a wish added through an assistant was recorded as raised by you, with no mention that an assistant did it — while every other change an assistant makes says so. The promise on the connect screen is that everything is recorded as done by you through that assistant, and a record that keeps that promise for most of its lines and not the rest is worse than one that never made it. A wish you type on the wishlist page yourself is unchanged, and still says only your name.

• Fixed: "raised by a admin".

1.4.93

21 September 2026

• New for the platform admin, switched off for now: JollyDrivers' own support backlog can be worked through a connected AI assistant. Ask it what is outstanding and it answers worst first — how serious, how many people want it, how long it has sat — and it can read any report in full, with everything that has been done about it.

• It can also change a report: its status, how serious it is, what it is about, and what the person who raised it is told. Nothing it decides is written until you have been shown the exact words that person will read, and said yes. Closing something without a reason is refused outright, because a "Won't fix" with nothing beside it is the surest way to stop somebody ever reporting anything again.

• Working notes are different: a note only the JollyDrivers team sees is added straight away, with no approval step, and there is no way to ask for one that the reporter can see. Anything they read goes the long way round.

• This is the first time an assistant can act as the administrator, and it stays narrow. Choosing it is a separate option when you connect, so a driver or operator connection you already have gains nothing. It unlocks the support queue and nothing else on the platform — an admin connection can see fewer bookings than a driver's can, not more.

• The switch that allows it is a real off switch. Turning it off does not merely stop new connections: it is checked every time the assistant asks JollyDrivers for anything, so a connection already running stops working immediately. Losing the admin role does the same.

• Every change an assistant makes is recorded on the report as made by you through that assistant, by name. A change made by an AI and one you typed yourself must never look the same a year later.

• The page you see when connecting an assistant no longer promises it will never act as an administrator, because for this one option that would not be true. It now says exactly where that ends.

1.4.92

21 September 2026

• New: a Wishlist. Report a problem is for something that is broken right now; this is for the other thing — the idea you had while doing something else, that nothing depends on and nobody is waiting for. Write it down, say roughly what it is about, and it keeps.

• The wishlist is shared, so you can see that somebody already wished for the thing you were about to ask for and say "me too" instead of raising it twice. How many people want something is the only honest signal a list of ideas has, so it is the order the list is in. Who had an idea is not shown: it should be weighed on what it is.

• An idea that has been agreed to now says so — Planned — rather than sitting on "we've read it" for months, which is indistinguishable from being ignored. Ideas that were decided against stay on the list with the reason, because that is the answer you are owed and hiding it invites the same wish again next month.

• When something you reported goes live, your own reports page now says which release it went out in and links to what else came with it. It is checked against the changelog that shipped with the running app, so it can only ever name a release that actually exists.

• Report a problem still only offers "something's broken" and "I'd like a change". An idea for one day is a link to the wishlist rather than a third option: the page is open when something has already gone wrong, and that is the worst moment to be asked to sort your own thoughts into categories.

• Behind the scenes, and only visible to a connected AI assistant: JollyDrivers now keeps a second, deeper record of every one of its 98 releases — what each one touched, which change it came from, which switches and database changes it carried, and what it is broadly about. Ask your assistant how invoicing got to where it is, or what JollyDrivers has ever done about text messages, and it answers from that rather than from what it can infer. Where nobody wrote down why something was done, it says so instead of guessing.

• Your assistant can also read your own reports and the wishlist, add a wish once you have read it back and agreed, and back somebody else's. It cannot change a status, a severity or a decision — that stays with the JollyDrivers team, in the app, where it is recorded against a name.

1.4.91

21 September 2026

• New for admins, switched off for now: JollyDrivers can read the privacy mailbox itself, so a request someone emails in appears in the register without anyone typing it up. Each one keeps the date the sender wrote rather than the day it was noticed, which means its thirty days already count the time it spent waiting.

• It reads the mailbox and never changes it. Nothing is marked as read, moved or deleted on the mail server, so what you see in your own mail program is exactly as you left it. The trade is that a fault here can only fail to notice a message — never quietly file one away where you would not find it again.

• Nothing an email says turns into a privacy request on its own. Each message waits for you to say whether it starts a new request, belongs to one you already have, or is not a request at all — and every one of those can be undone. The address is published, so anyone can write to it, and a register that filled itself would be a register nobody could trust.

• Where a message mentions a request reference in its subject, that is shown as something to check rather than acted on. Whoever sent the email typed it.

• Only the deployment holding the real privacy mailbox will ever read it. A test or development copy of JollyDrivers refuses, and says on its own screen that it is refusing — so an empty list never has to be guessed at.

• Junk that reaches the privacy address keeps the record that it arrived, but its text is removed after about three months rather than the seven years real correspondence is kept for.

1.4.90

20 September 2026

• New for admins, switched off for now: a register for privacy requests — somebody asking to see what JollyDrivers holds about them, to have it corrected or removed, to stop being contacted, or to complain. Each one is recorded with the date it arrived rather than the day you typed it up, because a request that sat unopened in the mailbox for a week has already spent a week of the thirty days you have to answer it.

• The register counts those thirty days for you. It shows what is due and what is late, keeps a log of every letter and call either way, and records how you satisfied yourself the person asking was really them — the method, never a copy of their licence. Where a request needs longer you can extend it, but only by saying why and when you told them. Waiting on somebody does not stop the clock.

• The admin dashboard now says so when a privacy request is close to its deadline or past it. That warning appears whether or not the register itself is switched on: a deadline that has already passed is a fact, and a switch should not be able to hide one.

• Nothing is ever deleted from the register — a request raised by mistake is closed as withdrawn, which is itself worth keeping. After seven years the correspondence loses its words while the record that it happened, when, and with whom stays. A privacy register that kept every word for ever would be a poor advertisement for its own subject.

1.4.89

20 September 2026

• Fixed, the same mistake in the pay-link text message: on a group booking billed on one invoice, the text quoted a single trip's share while the link it carried opened the whole invoice. It now names what the customer actually owes. An invoice you recorded by hand is untouched — the figure you typed was already the whole thing.

1.4.88

20 September 2026

• Fixed: on a group booking where every trip is billed on one invoice, the pay button in the customer's email showed a single trip's share instead of the amount they actually owe — half the invoice, with the correct combined total printed further down the same email. The button, the plain-text version and the PDF now all carry the whole invoice. The invoice itself was always right; only what the customer was told to pay was wrong.

1.4.87

20 September 2026

• When you text a customer their pay link, you can now choose who it comes from — your own mobile, your business name, or JollyDrivers' number — from the senders set up for you, and the trip timeline records which one you used. Your own mobile is picked first, because a pay link is the kind of text somebody replies to. If nothing has been set up for you it goes from JollyDrivers' number, as before.

• Fixed: texting a pay link no longer refuses to send when the operator has no notification email set. JollyDrivers sends that text itself and never needs the operator's address — the check was left over from when Jolly Frog's system relayed it. The note box beside it no longer claims to go to the operator either; it is kept on the trip's record.

1.4.86

20 September 2026

• First step towards booking a job through a connected AI assistant, switched off for now: the assistant can turn words into a place JollyDrivers can put on a booking — a street address, a landmark, an airport by name or code, or "home" — and is told the state and time zone that place runs on. Your own saved places and JollyDrivers' airport list are checked before Google, so a regular run costs nothing to look up. When several places fit, the assistant asks which; it never guesses.

• The assistant can also work out which of your saved customers a name, mobile number or email means, and is given just enough to tell two people apart — the last digits of their mobile, their email's domain, and their last trip with you — never a full number. If nobody matches, it says a new customer will be created with the booking. Nothing is created by looking.

• The assistant can now build the booking up with you, in any order — addresses, a pickup time, a return, passengers, a flight, the customer, the fare, how they pay, and how the request reached you (including the customer's own words from a screenshot). After every detail it says what is still missing, in the order the booking chat asks. Times are read on the clock of the place they belong to: a pickup in NSW is NSW time, and when the trip crosses into Queensland the drop-off time is shown in Queensland time. When it has enough, it prepares the booking to read back to you — route, drop-off time, any clash with your other jobs, fare and customer — and nothing is created until you say so.

• When you agree, the assistant creates the booking — the same way the booking chat does: it lands in your operator's book under your name with you assigned, a new customer is saved to your address book only at that moment, the original message is kept on the booking, and the customer's confirmation goes out. A job that already happened is recorded as completed. The trip's timeline shows it was booked by you via your AI assistant. You can also ask for it to be saved as a draft to finish in the app instead.

• Operators can book through their assistant too: the job lands in your own book, confirmed, the same way the New booking page creates it. Name a driver from your fleet to assign them (the assistant checks that driver's calendar for clashes), or leave it unassigned for the app. Nothing is sent to the customer until you send it from the trip page.

• The assistant can look a flight up for an airport job — which of your airports it lands at or leaves from, when in that airport's own time, and the pickup time JollyDrivers would suggest (20 minutes after landing, or the time to be at the airport before a departure) — using the same flight tracking as the airport booking cards, so the same switch and the same allowance apply. Several legs on one number is a question, not a guess.

1.4.85

20 September 2026

• New for admins, switched off for now: each operator can be given their own JollyDrivers sending address from the Operators page. One button creates the mailbox, a second emails the operator a link that confirms it, and if the hosting panel can't be reached the card shows the steps to do it by hand.

1.4.84

20 September 2026

• Trip stages on the trip page now follow exactly the same rules as stages recorded through a connected AI assistant. One visible difference: if you skip a stage, it is filled in with a best guess and marked estimated as soon as you record a later one, not only when you complete the trip. Tap "On board" without having tapped "Arrived" and the arrival appears on the timeline straight away, marked estimated.

• Fixed: completing a task such as a dog walk no longer shows a warning that an operator notification failed. Nothing was being sent, and nothing was wrong.

• The completion and no-show messages no longer say the operator has been notified. JollyDrivers stopped sending those updates when Jolly Frog's system was switched off.

1.4.83

20 September 2026

• A connected AI assistant (such as Claude) can now answer questions about how JollyDrivers has changed, straight from this changelog: what is new, when something arrived or was fixed, and how a feature has grown. Every answer comes with the version and date it rests on.

• Drivers can record a trip stage through their connected AI assistant: on the way, arrived, on board, completed or no-show, now or at a time they say. The assistant shows exactly what it will record and only records it once the driver agrees. The same rules as the trip page apply: nothing in the future, nothing out of order, and any stage the driver skipped is filled in with a best guess and marked estimated on the timeline. Stages recorded this way show "via AI assistant" on the timeline. Delivery jobs still use the trip page.

1.4.82

19 September 2026

• Fixed: a booking group whose invoice is still a draft in Xero can now be marked paid in cash. The draft is deleted in Xero and every trip is marked paid. Before, the Mark as paid button stayed greyed out until the invoice was approved, even when the customer had already paid cash. Card and bank transfer still need the invoice approved first, because Xero won't take a payment on a draft.

1.4.81

19 September 2026

• Fixed: starting a booking from a customer's card now asks the same questions as choosing the customer from the list — how the request came in, and whether that customer is the one travelling (or who is). It used to go straight into the chat assuming the customer was the passenger, and recorded every such request as an SMS.

1.4.80

19 September 2026

• Drivers can send a passenger a ready-made update from the trip page (on my way, running late, I've arrived, meeting your flight, pickup reminder), choosing each time whether it comes from their own mobile or the company name. A connected AI assistant can prepare the same texts and send them once the driver approves. Being piloted before it opens more widely.

• A text JollyDrivers held back (for example on a test account) is now shown on the trip timeline as held back, not as sent.

• The About and How it works pages now say correctly that booking confirmations go by email. They previously said email and SMS.

1.4.79

19 September 2026

• Anyone can now read what JollyDrivers is before signing in: new About, How it works and FAQ pages, linked from the sign-in screen. They are written so that people, search engines and AI assistants asked about JollyDrivers get the real story.

• Behind the scenes: the groundwork for connecting your own AI assistant (such as Claude) to your JollyDrivers account, signing in the usual way. A driver's assistant will be able to answer "what's my next job?" and "what have I got this week?", seeing only what you already see in the app, and connected assistants appear on your Account page where you can disconnect them. Being piloted before it opens more widely; nothing changes for anyone else.

1.4.77

18 September 2026

• Behind the scenes: updates install more reliably. A file the upload tool could not send no longer leaves the site on its "back in a few minutes" page; it is sent another way instead. Nothing you use changes.

1.4.76

18 September 2026

• Fixed: customer emails (confirmation, completion and booking summary) now show each time in the local time of the state it happens in, matching the trip page. A Coolangatta to Murwillumbah trip in summer now reads "5:07 PM (AEDT · NSW)" at the drop-off instead of the Queensland clock's 4:07 PM. Delivery collected and delivered times follow the same rule.

1.4.75

18 September 2026

• Removed (behind the scenes): the retry queue that used to hold a message to Jolly Frog until it could be resent, and two leftover columns from the same era. The queue has been empty since Jolly Frog was switched off and nothing has written to it since. Nothing you use changes.

1.4.74

18 September 2026

• Removed: the code that built messages for Jolly Frog's old system — every message builder, the shared envelope and its version numbers, and the specification and example files they were written against. Nothing you use changes; none of it had run since Jolly Frog was switched off.

• Removed (admin settings): four more switches that only shaped those messages — State-aware wire, Consent receipt, Disbursement notice and Account reference round-trip.

• Changed (a driver's purchases on a trip): the card no longer talks about what the operator's system will pick up. It says the purchase is billed to the customer as its own line, at cost, with no GST.

1.4.73

18 September 2026

• New (attendance jobs): a job like a dog walk or a garden watering now offers the confirmation email and one-tap Complete, as a delivery does. Before, it offered neither.

• Changed (Mark as paid, cancel, change price): the wording no longer says the operator will be emailed. Cash voids the invoice in Xero, card and bank transfer mark it paid there, and a bank transfer still says it comes from the bank account, not the card terminal. Where JollyDrivers doesn't manage the invoice, it says to do it in Xero instead.

• Removed: the retry queue for messages to Jolly Frog's old system, with its "queued for delivery" and "retry delivery" buttons on the trip page, and its switch in admin settings. Nothing is queued now because nothing is sent.

1.4.72

18 September 2026

• Removed: the last messages to Jolly Frog's old system, the invoice or quote request, the request to void an invoice, and confirmations relayed through the operator. Invoices are raised and voided in your Xero, and confirmations go straight to customers, as they already do.

• Changed (Request invoice / Request quote): where an invoice can't be raised in Xero from JollyDrivers, or for a quote, you now get a clear reason instead of a request sent to a system that is switched off.

• Changed (Send confirmation): an operator whose confirmations aren't set to go straight to customers now gets a clear reason instead of a relay through its own system.

1.4.71

18 September 2026

• Removed: the booking and delivery messages JollyDrivers sent to Jolly Frog's old system: new booking, change, cancellation, status (en route, completed, no-show), and the same four for deliveries. Bookings still move to Sent and confirm exactly as before, and a retroactive cancellation still settles its invoice in Xero.

• Changed (trip timeline): those messages no longer leave "sent to operator" lines, because nothing is sent.

1.4.70

18 September 2026

• Removed: three notices JollyDrivers could send to Jolly Frog's old system: that an invoice had been raised in Xero, that a complaint or incident had been recorded, and that a booking had settled directly to the driver. Invoices are still raised in Xero and cases still land in the register, as before.

• Removed (admin settings): the Case notice and Direct settlement notice switches.

1.4.69

18 September 2026

• Removed: the option to have Jolly Frog's old system text a pay link on JollyDrivers' behalf. JollyDrivers sends the text itself, as it already does for you, and "Text the pay link" now shows whenever JollyDrivers' own texting is switched on.

• Removed: the group invoice request message to Jolly Frog. A group is billed as one invoice in your Xero, as it already is; an operator who can't raise invoices from JollyDrivers now gets a clear reason instead.

• Removed (admin settings): the SMS dispatch and Group invoice request switches.

1.4.68

18 September 2026

• Removed: the messages JollyDrivers sent to Jolly Frog's old booking system when a payment was recorded (cash, card, bank transfer, or a payment with no invoice) or an invoice's due date was changed. Payments on invoices in your Xero are still recorded there, exactly as before.

• Changed (Mark as paid): the confirmation no longer says the operator has been notified or asked to void the invoice when nothing was sent.

• Changed (Change due date): on an invoice that isn't in your Xero, it now says the due date can't be changed here, rather than claiming a change was sent.

• Removed (admin settings): the Cash reconciliation, Card reconciliation, Direct payment notice and Due date management switches. Those buttons stay on, as they already were. Bank transfer keeps its switch, which is now an ordinary release switch and still off.

1.4.67

18 September 2026

• Removed: five messages JollyDrivers could send to Jolly Frog's old booking system, which is switched off for good. None were switched on in production, so nothing you use changes. They are the attendance job notice, the driver assignment update, the fleet roster copy, the automatic invoice approval request and the invoice status refresh request.

• Removed (trip page): the "Notify operator" button on attendance jobs, which only sent that notice.

• Removed (admin settings): the five switches for those messages.

1.4.66

17 September 2026

• Removed (admin): JollyDrivers no longer checks the Jolly Frog protocol mailbox for replies, because Jolly Frog is switched off for good. The Protocol Log page loses its Poll Inbox button, auto-poll switch and last-poll panel, and the admin dashboard loses its "Inbox auto-poll" line. The log itself stays, with every message JollyDrivers has sent, including each customer confirmation.

1.4.65

17 September 2026

• Changed (admin settings): the driver accounting switches now keep their order. Driver ledger to Xero can't be turned on while Driver ledger is off, and Driver ledger can't be turned off while it is on, because card takings a driver collected would be booked to a clearing account that nothing ever clears. Turning on Commission RCTI without Driver ledger to Xero now warns that nothing will be issued.

• New: a step-by-step guide to switching driver accounting on, for when the first driver who isn't an owner-driver joins. Each of the four switches on the settings page points to it, and Driver ledger now warns to set a commission before opening anyone's ledger.

1.4.64

17 September 2026

• New (behind Commission RCTI, off by default): when a driver's bill goes to Xero as a recipient-created tax invoice, the driver is emailed their copy straight away. The email holds the whole tax invoice, so it works for drivers without a JollyDrivers login.

• New: the statement page shows that tax invoice to both you and the driver, exactly as it was issued, and it prints with the statement. You also see when and where it was emailed, or, if it wasn't, the date it must reach the driver by and a button to email it.

• Fixed (Driver ledger to Xero): retrying a statement whose payment step failed no longer sends the bill to Xero a second time.

1.4.63

17 September 2026

• New (behind Commission RCTI, off by default): a subcontractor's fleet page can record a recipient-created tax invoice agreement with them. The dialog shows the terms the ATO requires in full and records them only once you confirm the driver has agreed in writing. You can end the agreement there, and changing the driver's ABN ends it.

• Changed (Driver ledger to Xero): a driver's bill carries GST only when it is a recipient-created tax invoice, meaning the switch is on, the driver is a subcontractor with an ABN who is registered for GST, the agreement is recorded, and your ABN is set on Settings → Pricing. That bill is numbered RCTI-JD- and the statement number, and says on it that it is a recipient-created tax invoice, with both ABNs and that the GST is the driver's to pay. Any other bill carries no GST and no RCTI wording, even for a registered driver.

• New: the settings page warns when Driver ledger to Xero is on without Commission RCTI, because drivers' bills then claim no GST.

• Owner-drivers never get one, and their fleet page does not offer it.

1.4.62

17 September 2026

• New (behind Driver ledger to Xero, off by default): a closed driver statement becomes a bill in the operator's own Xero, from a contact JollyDrivers creates for the driver: driving services to the Driver payments account (with GST when the driver is registered), reimbursements to the customer purchases clearing account, adjustments alongside. If the driver collected passenger money in the period, the bill is paid from Driver collections clearing to that extent; a payout the operator records pays the rest from the bank account.

• Changed (same switch): a card payment recorded as received by the driver, on an invoice JollyDrivers raised, is now booked to Driver collections clearing instead of the terminal account, and "Mark as paid (card)" is offered again for drivers whose card takings go to their own account.

• New: two account mappings on Settings → Accounting, Driver collections clearing and Driver payments. Both refuse to post until set. Bills need a permission the Xero connection did not have, so the operator reconnects Xero once; the statement page says so and has a Post to Xero button for retries.

• New: a subcontractor's ABN and GST registration on their fleet page. The ABN goes on their Xero contact; registration decides whether their bill carries GST. Not said is treated as not registered.

• Owner-drivers: nothing is posted in either direction.

1.4.61

17 September 2026

• New (with Driver ledger): statements. On a driver's ledger card the operator closes a statement to the end of a chosen day; it freezes everything not yet on a statement with opening, movement and closing figures, and both sides can open it at any time. A correction to an issued statement appears on the next one; the issued one never changes.

• New: a statement page that prints cleanly, and "Email to driver" which sends it to the driver's address on file and records when it went.

1.4.60

17 September 2026

• New (behind Driver ledger, off by default): a running account between an operator and each driver. The operator opens it from a driver's fleet page, typing an opening balance if one exists. From then on each completed job posts the driver's share, anything they bought for a customer posts as a reimbursement, any payment recorded as received by the driver posts against them, and the operator records payouts and money handed back. The balance is the sum, shown to both sides with whose arithmetic it is.

• New: drivers get a Balance page, one card per operator, with the activity that made the figure. When the operator owes them they can request a payout to their PayID; when they hold the operator's money they can ask for an invoice to settle it. Requests move no money; the operator marks them paid or received with a reference, and that writes the ledger.

• New: on the fleet page the operator sees the same card with record-a-payout, record-money-handed-back, adjustment (with a reason) and refresh. Nothing is ever edited or deleted; a correction is a reversal that points at what it undoes.

• Changed: with the ledger on, the earnings page points at the Balance page instead of showing its own paid split, so a driver never sees two different "paid" figures.

1.4.59

17 September 2026

• New (behind Driver commission rates, off by default): each driver on the fleet page gets a Commission card. Set a rate for that driver — a percentage of their commissionable income, a flat amount per job, or both — from a chosen date, with the history kept underneath. Until one is set the operator default applies, and "Back to operator default" ends the driver's own rate from now.

• Changed: the commission line on a job, and a direct settlement, now use the rate in force when the job was completed, so a rate change never restates a job already done. A backdated rate says on the card how many completed jobs still carry the earlier figure; "Recompute fees" on a trip refreshes it.

• Changed: the operator default on Settings → Pricing is now recorded with a dated history as well as the live value.

1.4.58

17 September 2026

• New: "Mark as paid" now asks who has the money — the operator's account or the driver's own — for cash and card. It is preselected from what JollyDrivers already knows about the driver (the terminal declaration on their fleet page; cash defaults to the driver) and can be changed per payment. An owner-driver is not asked, and a bank transfer is always the operator's. The answer is kept on the payment and shown on the trip timeline as "received by the driver" or "received by the operator".

• Changed: a card payment recorded as going to the driver's own account can no longer be posted against the operator's invoice from the trip page. The money is not the operator's until the driver settles up; recording it in their books arrives with the driver ledger. The no-invoice card path and cash are unaffected.

• Groundwork: every payment recorded before today reads as "not recorded" for this question, never as a guess.

1.4.57

17 September 2026

• Changed: operator commission is now worked out on your income from the trip rather than on the whole price. A toll or airport fee that was absorbed into the price comes out before the percentage is taken, so a $100 fare carrying a $6.40 toll inside it commissions $93.60. Nothing already recorded is changed; the new figure appears the next time a trip's fees are recalculated.

• New: Settings → Pricing has two switches for whether commission applies to extras (baby seat and the like) and to the larger-group premium. Both are on, which is what always happened; switch one off and the driver keeps all of that charge.

• New (groundwork, nothing visible): each toll and airport line can now record who actually paid it, the driver or the operator. Every existing line is marked "unknown" and nothing reads it yet; it is the first step of the driver accounting work.

1.4.56

17 September 2026

• Fixed: delivery receipts now work whether they are configured per message or once for the whole account. An account-level receipt was arriving in a slightly different form and was being refused; it is now read correctly. Proven on a test text: the trip timeline showed "Text delivered to the customer's phone" within a second of the send.

1.4.55

17 September 2026

• New: the SMS inbox page now shows the last calls SMSGlobal made to JollyDrivers, including refused ones, so a missing delivery receipt can be traced without server logs. The first receipt after 1.4.53 never arrived even though SMSGlobal showed the text as delivered.

• Changed: the SMS webhooks now cope with providers that alter the address they are given, so a delivery receipt is no longer refused because of how the request was formed.

1.4.54

17 September 2026

• New: an SMS inbox for the platform admin. Every text that arrives on JollyDrivers's number is kept, matched to its booking where one can be found, and shown on that trip's timeline as "Customer texted back". The admin board shows how many are unread. Until now a reply that was not STOP went to the log and nobody saw it.

• Changed: the Direct Sms setting's warning no longer talks about importing the old operator system's list.

1.4.53

17 September 2026

• New: a text sent to a customer from the trip page now reports back. When the phone receives it the timeline says "Text delivered to the customer's phone"; when it never will (expired, undelivered, rejected) the timeline says so and why. Until now "sent" only meant the SMS gateway had taken the message. Needs delivery receipts switched on in the SMSGlobal account.

1.4.52

16 September 2026

• Changed: the SMS opt-outs page now says what actually happens. A STOP reply adds a number automatically; taking a number back off the list is done on the page by hand. The line about importing the old operator system's list is gone.

1.4.51

16 September 2026

• Fixed: the SMS reply webhook now accepts our provider's notifications however they arrive. Follow-up to 1.4.50.

1.4.50

16 September 2026

• Fixed: replies to the JollyDrivers SMS number (STOP / START) can now reach the opt-out register. The way our SMS provider delivers an incoming message did not match what JollyDrivers was expecting, so replies were being refused. Nothing was lost before this: the provider was never pointed at JollyDrivers until now.

1.4.49

16 September 2026

• Fixed: switching an operator's old booking system off ("My booking system is switched off" on Settings → Accounting) would also have stopped that operator's own customers receiving their confirmation emails. It now silences only the messages meant for the retired system. Found before the switch was ever used.

1.4.48

16 September 2026

• Fixed: a trip that had been billed as part of a group could not be invoiced on its own afterwards — asking for an invoice failed with a database error. Found while testing group consolidation.

1.4.47

16 September 2026

• Changed: settling a whole group by card is offered only when every trip's driver banks card takings into the business's account. One invoice settled by one payment can't be recorded when part of the money went somewhere else — set "Card takings" on each driver's fleet page.

1.4.46

16 September 2026

• New: a driver's fleet page now asks where their card takings land — the operator's account, or the driver's own. JollyDrivers records a card payment into the operator's Xero only when it knows the money reached the operator; otherwise it says so instead of recording it. An owner-driver needs no answer, since they and the business are the same party.

1.4.45

16 September 2026

• Fixed: "Mark as paid" by card or bank transfer was offered while the invoice was still a draft, on a trip and on a group. Xero does not accept a payment against a draft, so it would have failed. Approve the invoice first — the button says so now. Cash is unaffected: it retires the invoice instead of paying it.

1.4.44

16 September 2026

• New: a group's draft invoice can be approved from the group page. It used to say "Pending" with no way to act — you had to open one of the trips to find the approve button. It now reads "Draft in Xero" and has an "Approve in Xero" button of its own.

1.4.43

16 September 2026

• New: a small sync button on each invoice row checks that invoice against Xero on the spot. Opening a trip already checks once, but a void or payment made in Xero while the page sits open was not picked up until the page was opened again.

1.4.42

16 September 2026

• Fixed: a group where only some trips had an invoice called itself "already billed as one invoice", which hid the Consolidate button and left Request invoice greyed out — the group could not be billed at all from the page. It now counts a group as billed as one only when every trip is on that invoice.

1.4.41

16 September 2026

• New: "Consolidate into one invoice" on a booking group whose trips already have invoices of their own. It retires what is there — a draft is deleted and disappears, an approved invoice is voided — then raises one invoice covering every trip in date order. You see exactly which invoices go before anything happens, and a paid invoice is never touched (remove that trip from the group instead).

• Changed: adding bookings to a group no longer offers trips that are already paid. A paid trip has nothing left to bill and can't join a group invoice.

• Fixed: a group showed "Billed as one invoice" when only some of its trips were on that invoice. It now says so only when every trip is covered.

1.4.40

16 September 2026

• Fixed: asking for an invoice left the billing panel saying it was waiting for the operator, even though JollyDrivers had already raised the invoice in Xero — only a browser refresh showed it. The panel now updates on the spot.

• Removed: the "REFRESH · last updated…" row, from under the invoice card and from each leg on the group page. Opening the trip still checks the invoice against Xero, and now says so only when something actually changed.

• Removed: asking for a quote. Quotes were only ever raised by the operator's own system, which is being retired, so a quote request had nothing to answer it. Quotes already on a booking still show.

• Changed: "Request invoice" (was "Request billing artifact") opens with Invoice already chosen, and set to Draft — the invoice is raised in Xero for you to look over, and is approved automatically when a confirmation or completed notice goes out.

• Removed: the two pencil buttons either side of the price on the invoice card. Price and billing method are still editable from Edit trip.

• New: when an invoice is raised, a message names it and its state, for example "INV-0000 is approved in Xero, AUD 000.00" or "INV-0000 is a draft in Xero, AUD 000.00 — approve it to get a pay link."

1.4.39

15 September 2026

• Removed: the "invoice is out of date" notice on the trip page. It kept coming back; change an invoice's wording from the invoice lines window when you need to.

• Removed: the "Invoice header note" box, from the trip's billing card and from the passenger's own trip page. Drivers and operators write whatever they want on the invoice in the invoice lines window instead. A note already saved on a booking still prints on its invoices.

1.4.38

15 September 2026

• New: when a booking's pick-up date, time, addresses or reference change after its invoice was raised, the trip page says the invoice is out of date and lists what it no longer shows. "Update the invoice" opens the invoice lines on the fare line with those changes listed, for you to correct and save to Xero.

• Removed: "Reword with AI" and the saved example library are gone from the invoice lines window. It is now simply the editable description, saved straight to Xero.

• Changed: the description box shows 16 lines.

1.4.37

15 September 2026

• Fixed: "Reword with AI" now actually rewords. It used to hand back the same layout and ignore your direction; it now follows a direction such as "no route detail" or "all on one line", and with no example it writes a short, clean layout.

• Changed: when the booking's details have changed since the invoice was raised (a pick-up time moved, say), the suggestion lists exactly what using it would change on the invoice, rather than changing it quietly.

1.4.36

15 September 2026

• New: on an invoice's fare line, "Reword with AI" rewrites the description, either tidying the current wording or following an example you saved. The date, time, pick-up, drop-off and reference are checked to be copied exactly, and a version with any number that isn't on the booking is never offered. You read the suggestion and choose "Use this" before anything goes to Xero.

• New: "Save this wording as an example" keeps a description you like in a small library shared by the operator and their drivers, to follow on later invoices.

• Changed: the description box in the invoice lines window shows 10 lines instead of 6.

1.4.35

15 September 2026

• New: the invoice card on a trip has a lines button that shows each line of the Xero invoice — draft or approved — one at a time, with its amount alongside. A driver or operator can reword a line's description and save it straight to Xero. Amounts and everything else on the invoice stay as they are; a paid, part-paid or voided invoice opens view-only.

1.4.34

15 September 2026

• Changed: opening a trip now checks its invoice against Xero straight away, so a void, a payment or an approval made in Xero by hand shows on the page without pressing anything. This covers invoices the operator's old system raised too, as long as Xero is connected — they used to say "Waiting for updates…" from a system that no longer answers.

• Changed: the Refresh button reads Xero immediately when pressed, rather than asking you to wait out the cooldown. The nightly check now covers every open invoice in a connected Xero, not only the ones JollyDrivers raised.

1.4.33

15 September 2026

• Changed: under the "View & pay" button on confirmation and completed-trip emails, the note now reads "After payment access your paid tax invoice HERE!" with the pay link on HERE — customers were getting Square's card receipt and not realising the same link shows the paid tax invoice afterwards.

1.4.32

15 September 2026

• Changed: a booking a driver submits from a draft is now confirmed by JollyDrivers itself instead of sitting on "Sent" waiting for the operator system to reply. It is held instead, with the reason on the booking, when there is no price yet or a fatigue warning has not been acknowledged.

• New: an operator or admin can accept or decline a booking from the trip page ("Answer the booking"), including one that was left on "Sent" before this change. Settings → Booking Form → "Confirm my passenger bookings automatically" extends the automatic confirmation to bookings other people submit.

1.4.31

15 September 2026

• Changed: JollyDrivers no longer holds a customer's first invoice for you to confirm the Xero customer. It finds the matching Xero contact (by email, ABN, phone, then exact name) and uses it, or creates a new contact when nothing matches, then raises the invoice straight away — the way the operator system always did. The "Customers to confirm" panel on Settings → Accounting only shows invoices held before this change; confirm those to release them and it disappears.

1.4.30

15 September 2026

• New: when JollyDrivers raises the invoice in Xero, the request dialog asks whether to raise it Approved (as before, a live invoice with a pay link) or as a Draft to look over in Xero first. A draft shows as "Draft in Xero" on the trip, has no pay link yet, and gets a tick button to approve it. Sending a confirmation or a completed notice approves any draft on the trip first, so the customer's email always carries a working pay link; a draft that cannot be approved stops the send and says why. Voiding a draft deletes it in Xero rather than leaving a voided invoice behind.

• Changed: refreshing an invoice from Xero now also picks up the pay link when a draft was approved in Xero by hand.

1.4.29

14 September 2026

• New: a driver or operator can void an outstanding invoice from the trip page (the block icon next to it), with a reason. An invoice JollyDrivers raised in Xero is voided there on the spot; one raised by the operator's own system is refused with a note to void it there and refresh. The void is recorded on the booking, and once the only invoice is voided the "Request a new invoice" button comes back.

1.4.28

14 September 2026

• Changed: an invoice JollyDrivers raises in Xero now describes the trip the way your own invoices always did — flight banner, pickup time and zone, passenger and mobile, seats, extras, each stop, distance and ETA, the reference and the booking date — and carries the passenger-band item code (PAX-X / PAX-XL / PAX-MAX).

• Fixed: an invoice JollyDrivers raised in Xero after you confirmed the customer left no trace on the booking. The booking now shows when the invoice was held (and why), and once it is raised the operator's system is told about it and the booking records that, exactly as it does for an invoice raised straight from the trip.

1.4.27

14 September 2026

• Fixed: a customer waiting to be approved as a new Xero contact showed a greyed-out confirm button. The card now says no contact matched and offers "Approve as a new customer in Xero"; approving creates the contact and raises the waiting invoice.

1.4.26

14 September 2026

• Settings → Accounting → "Raise invoices from JollyDrivers" can now re-draft the invoices that were shadowed before JollyDrivers could draft the whole document. It builds the invoice JollyDrivers would have raised that day and checks it line by line against what is in Xero, so those early invoices count towards the switch-over bar — for it if they agree, against it if they do not.

1.4.25

14 September 2026

• My Trips: every booking in the list now shows the same invoice chip as the three cards at the top — "Invoice · Approved", "Invoice · Draft", "Invoice · Not issued" and so on — instead of the bare word "Invoice", so you can see whether an invoice has been raised without opening the trip.

1.4.24

14 September 2026

• Settings → Accounting gains the last switch for an operator whose own booking system is being turned off: once it is on, JollyDrivers sends that system nothing and takes over every invoice in Xero — refreshing, recording payments, voiding — including the ones the old system raised before the switch-over. It is offered only after "Raise invoices from JollyDrivers" is on, so invoicing can never fall between the two.

1.4.23

14 September 2026

• JollyDrivers can now text customers itself — pay links and receipts — from its own SMS number, instead of asking the operator's booking system to relay the text. Off until switched on. A new System Admin page, SMS opt-outs, holds every number that must not be texted: STOP replies land there automatically, START removes them, and the operator system's existing list can be pasted in.

• System Admin → Settings gains "Splash stays for at least", so how long the JollyDrivers mark shows while the app starts is yours to set. The splash itself has a new look: a sweeping ring around the mark, a soft halo, and the name settling in letter by letter.

1.4.22

14 September 2026

• Operators and admins can now accept or decline a booking on its trip page in JollyDrivers itself, and Settings → Booking Form gains a switch to confirm passenger bookings automatically the moment they are submitted. Auto-confirm holds back, and says so on the trip, when there is no price or the driver has an unacknowledged fatigue warning. Both are off until switched on; while your booking system still accepts bookings for you, leave them off.

1.4.21

14 September 2026

• When JollyDrivers raises one merged invoice for a booking group in Xero, the notice it sends the operator's system now names every trip on that invoice, so their records can show the invoice against each trip rather than only the first. Nothing changes until an operator is switched over.

1.4.20

14 September 2026

• Billing a booking group as one invoice now goes through the same door as a single booking: for an operator switched over to raising invoices in JollyDrivers, the merged invoice is raised in Xero by JollyDrivers itself, due on the day of the group's last trip, with each trip's share recorded against that trip. Nobody is switched over yet, so nothing changes today.

1.4.19

14 September 2026

• A JollyDrivers splash while the app starts up, in place of a blank page.

• The home menu, your trips list and the trip page now reveal their cards in sequence when you arrive.

1.4.18

14 September 2026

• On an invoice that JollyDrivers raised in Xero itself, changing the due date now changes it in Xero on the spot. Reclassifying a completed trip as cancelled now settles that invoice in Xero too: withdrawn when there is no fee, or credited for the difference when there is one. If the invoice was already paid, the credit sits on the customer's account and the refund is recorded in Xero by the operator. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.17

14 September 2026

• When a trip on an invoice that JollyDrivers raised in Xero itself is marked paid in cash, or its invoice is cleared so a group can be billed as one, JollyDrivers now voids that invoice in Xero on the spot instead of asking the operator's system to. A paid invoice is never voided. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.16

14 September 2026

• When a card payment is marked on an invoice that JollyDrivers raised in Xero itself, the payment is now recorded in Xero by JollyDrivers against your card terminal account, with the Square transaction as the reference. A part payment records the amount and leaves the invoice open. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.15

14 September 2026

• On an invoice that JollyDrivers raised in Xero itself, the trip page's Refresh button now reads the invoice's status straight from Xero and answers on the spot, instead of asking the operator's system and waiting. A payment made through Xero's online invoice, or keyed into Xero by hand, marks the trip paid the next time anyone refreshes — and every open one is checked overnight anyway. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.14

14 September 2026

• When a bank transfer is marked as paid on an invoice that JollyDrivers raised in Xero itself, the payment is now recorded in Xero by JollyDrivers, against your bank account, with the payer's reference. Invoices raised by the operator's system are unchanged. Nothing applies until an operator is switched over.

1.4.13

14 September 2026

• Settings → Accounting now has Raise invoices from JollyDrivers: it shows how many of your invoices JollyDrivers's comparison has agreed with, across everything you bill, and what is still short. Once the bar is met and the platform switch is on, you can switch over by typing the confirmation word it asks for. Switching back is one press. Nobody is switched over by this release.

• Confirming a customer on the review list now also raises any invoice that was waiting on that confirmation, once an operator is switched over.

1.4.12

14 September 2026

• When JollyDrivers raises an invoice in Xero itself, the operator's own system is now told about it straight away, so their records show the invoice and payments can still be recorded against it there. The pay link Xero provides is kept with the booking. Only applies once an operator is switched over, which none is yet.

1.4.11

14 September 2026

• JollyDrivers can now raise an invoice in an operator's own Xero organisation itself, instead of asking the operator's accounting system to. It is switched off for every operator and for the platform, and it stays off until the comparison evidence says it is safe. When it is on: the first invoice to each customer is held until you confirm the Xero customer, every invoice is authorised on creation and due on the day of the trip, and anything Xero refuses is shown to you in plain words rather than retried in silence.

1.4.10

14 September 2026

• Behind the scenes, JollyDrivers now works out for itself which Xero customer each invoice should go to — from a customer you have already confirmed, or by looking them up in Xero by email, ABN, phone or name — and records whether its answer matched the one the operator's system used. Nothing acts on it yet; it is the last piece of evidence before JollyDrivers raises invoices itself.

1.4.9

13 September 2026

• If a customer has been waiting more than a day to be confirmed, every portal page now says so at the top, with a link straight to Customers to confirm. Operators see their own; admins see every operator's. A customer left unconfirmed is an invoice JollyDrivers cannot raise, so it is not left to a screen you might not open.

1.4.8

13 September 2026

• Customers to confirm now catches up on invoices raised before the check existed: on first view it looks each one up in Xero once to find which customer it went to, so the cards for customers you have already invoiced appear without waiting for their next invoice.

1.4.7

13 September 2026

• Settings → Accounting has a new section, Customers to confirm. The first time a customer is invoiced, a card appears showing which Xero customer that invoice went to, and asks you once whether it is the right one. Confirm it and every later invoice for them resolves to that exact contact; mark it wrong and it will not be used again. Cards waiting more than a day are flagged. Admins see every operator's queue on Platform settings.

1.4.6

13 September 2026

• Groundwork for a one-time check per customer: JollyDrivers now keeps a review record for the first invoice raised to each customer of each operator, holding the Xero customer that invoice went to. Nothing is shown or held yet; the screen where you confirm or correct each one is the next step. Confirming will make that customer's invoices resolve to the same Xero contact every time without any matching.

1.4.5

13 September 2026

• When JollyDrivers reads an invoice back from Xero it now also records which Xero customer the invoice was raised for, and checks it against the customer JollyDrivers remembers for that bill-to. A mismatch is the one mistake nothing used to catch: a correct-looking invoice against the wrong customer. Groundwork for the review step that will let you confirm each new customer once.

1.4.4

13 September 2026

• After an operator's system raises an invoice, JollyDrivers now reads that invoice back from Xero and checks which of the operator's accounts each line actually posted to, against the account it would have chosen. This is a read only — JollyDrivers still creates nothing in Xero — and it is the last piece of evidence the shadow comparison was missing.

1.4.3

13 September 2026

• Behind the scenes, JollyDrivers now writes down the whole invoice it would have raised for a booking — every line, which of the operator's accounts each would post to, and the due date (the day of the trip) — at the moment it asks the operator's system to invoice. When that system's invoice comes back, the two are compared line by line and date by date. Nothing is sent to Xero and nothing about invoicing changes; this is the evidence that decides when JollyDrivers may raise invoices itself.

1.4.2

13 September 2026

• The Xero shadow comparison now records the invoice number (for example INV-0000) alongside each observation, so an admin reading the shadow log can see which invoice a row is about without looking it up by Xero's internal id. Rows recorded before this release keep a blank number.

1.4.1

13 September 2026

• When you press Connect to Xero and your organisation is greyed out on Xero's page, the Accounting tab now tells you why before you get there: Xero allows only two uncertified apps per organisation, and the fix is to disconnect one you no longer use under Xero's Settings → Connected apps. Nothing else about connecting has changed.

1.4.0

13 September 2026

• Operators can connect their own Xero organisation to JollyDrivers, and say which line of their own accounts each thing they bill should be recorded against — passenger fares, deliveries, tasks, a recovered passenger levy, purchases made for a customer, and the accounts payments land in. It is on Settings → Accounting. JollyDrivers never sees a Xero password: you approve it on Xero's own pages, and you can revoke it from your Xero account at any time.

• Nothing on that screen is ever filled in for you, and a missing account is never guessed — a code that is right for another business would put your income somewhere your accountant did not choose, and that is the kind of mistake found at BAS time rather than by an error message. The screen says plainly which gaps stop an invoice being raised and which do not.

• Groundwork for JollyDrivers to raise an operator's invoices itself, rather than asking their accounting system to. Before that happens for anybody, JollyDrivers now writes down what it would have put on each invoice and compares it against the one their system actually raised — on real bookings, until the differences stop. Nothing about how invoices are raised changes yet, and nobody sees anything different.

• All of the above is off for every operator until it is switched on deliberately.

1.3.1

12 September 2026

• A page left open no longer dies after a few minutes. If the connection drops — a tunnel, a locked phone, or just leaving a tab alone while you do something else — JollyDrivers now holds your place for 15 minutes instead of 3, and reconnects the moment you come back to the tab. Where it cannot be saved, the page refreshes itself instead of leaving you on a grey "could not reconnect" screen with your work behind it.

• The booking chat is the one exception, on purpose: it will not refresh itself out from under you, so a conversation you were part-way through stays on screen to read.

1.3.0

12 September 2026

• Operators can now set the name customers see on their emails and the address customer replies go to, on Settings → Branding. Each operator gets its own JollyDrivers sending address behind the scenes; nothing changes in what customers receive until it is switched on for that operator.

• Groundwork for JollyDrivers to send booking confirmations to customers directly, as the operator, instead of handing them to the operator's own system to forward. Off for every operator until it is switched on deliberately.

1.2.1

11 September 2026

• The calendar now shows every trip at the pickup's own local time, in the state it happens in. A Byron Bay pickup at 9:00 reads 9:00, not the Queensland 8:00 it also is, and the day view labels each entry with its state when the two clocks are in play.

• Calendar invitations — the ones emailed to drivers, and the download — now say which state's time they are in, and a cross-border trip ends in the other state's time. Google, Outlook and Apple file the event under Australia/Sydney or Australia/Brisbane instead of "UTC".

• Blockouts ask which state they are in, so a border driver's "Tuesday 9–5" is the right 9–5. It defaults to the state of your last blockout or last pickup, so the usual case is one tap.

• The passenger's Add to Google Calendar link now names the pickup's state, so a Queensland passenger booking a New South Wales pickup no longer gets an entry an hour out in summer.

• Behind the scenes: every release now has to carry a new version number and a description before it can go out, and the app reports the changelog's version rather than a fixed one.

1.2.0

10 September 2026

• You can tell us about a problem, or ask for something to work differently, from Report a problem on your home board. Add a screenshot, a booking number, and we'll come back to you — My reports shows what you've raised and where each one got to.

• When you're making a booking and it clashes with something already in the calendar, you can now stop. Before, the only choices were to carry on anyway or move the pickup time; leaving the page was the only way out of a clash you couldn't work around.

1.1.0

10 September 2026

• Portal pages now stop at a comfortable width on large monitors instead of stretching all the way across the screen. On a 32" display the content sits in a readable column with the JollyDrivers logo and your account menu lined up with it.

• There is now a changelog — this page. It shows which version you are on and what changed in each release.

• Behind the scenes: JollyDrivers can now tell you exactly which build it is running, which makes a bad deploy obvious in seconds instead of taking a morning to find.

1.0.0

8 September 2026

• JollyDrivers went live at jollydrivers.com.au.

• Booking, trips, invoicing, driver and vehicle records, compliance documents and the operator messaging protocol all running in production for the first time.