FleetbaseFleetbase
Back to blog
Blog articleJune 24, 20263 min read

Fleetbase 0.7.48: Fleet-Ops REST Coverage, Revenue Lifecycle Safeguards, and Settlement Status

Fleetbase 0.7.48 is a release with a strong financial-integrity backbone. It significantly expands public REST and export coverage across Fleet-Ops, tightens how active revenue is calculated, introduces transaction settlement status, and adds a set of Ledger safeguards that keep your revenue records accurate even as orders and invoices change state. It also brings telematics hardening, new map layer settings, and a round of navigation polish. Here's what's new. Fleet-Ops REST, exports, and me

Written byShiv Thakker
Fleetbase 0.7.48: Fleet-Ops REST Coverage, Revenue Lifecycle Safeguards, and Settlement Status

Fleetbase 0.7.48 is a release with a strong financial-integrity backbone. It significantly expands public REST and export coverage across Fleet-Ops, tightens how active revenue is calculated, introduces transaction settlement status, and adds a set of Ledger safeguards that keep your revenue records accurate even as orders and invoices change state. It also brings telematics hardening, new map layer settings, and a round of navigation polish.

Here's what's new.

Fleet-Ops REST, exports, and metrics

This release meaningfully broadens how you can get data in and out of Fleet-Ops. We've added public REST endpoints for devices, equipment, fuel transactions, parts, sensors, and work orders, all with UUID-safe resource resolution. If you're building integrations on top of Fleetbase, these surfaces give you clean, predictable access to far more of the operational model.

Export coverage has expanded dramatically too, now spanning contacts, devices, drivers, equipment, fleets, fuel reports, issues, maintenance, orders, parts, places, sensors, service areas, service rates, telematics, vehicles, vendors, and work orders. Whatever you need to pull out for reporting or analysis, the odds it's covered are now much higher.

On the metrics side, we've added a shared active revenue query so earnings, revenue trend, and average order value calculations ignore deleted or inactive orders and invoices, and standardized active revenue transaction status handling for reporting and accounting consistency. The result is numbers you can trust. We also fixed sensor status and type filters so option labels render correctly.

Ledger and settlement

The financial layer is where 0.7.48 does some of its most important work. We've added transaction settlement status support across Core API and Ledger, including migrations and model and resource helpers, so you can track where a transaction sits in its settlement lifecycle.

Backing that up is a new set of Ledger revenue lifecycle safeguards covering cancelled and deleted orders, deleted or inactive invoices, transaction voiding, restore handling, and reversal journal creation. When records change state, your ledger stays correct rather than drifting. For cleaning up existing inconsistencies, there's a new dry-run-first Ledger repair command, so you can preview what would change before anything is written.

This release also advances payments: GNU Taler gateway support, invoice QR checkout, public invoice payment flow improvements, and local Taler testing utilities, along with new invoice and transaction filters for settlement and review workflows.

Telematics and device workflows

Connectivity gets another round of hardening. We've strengthened Safee and AFAQY telematics sync, including sensor identity sync, device status bootstrap, and safer provider error handling. Connectivity screens gain device event details and improved device event navigation, and we've fixed vehicle attachment navigation along with the device, sensor, and vehicle filters those screens rely on.

For mapping, we've added Google Maps view layer settings to Fleet-Ops map configuration, including settings to enable the Google Traffic Layer and Transit Layer for richer operational context on the map.

Shared UI and Console polish

A number of refinements make day-to-day use smoother. We've fixed sidebar navigator initial active-parent sync so module root pages no longer open deeply nested menus too early, and added permission-safe sidebar filtering that respects visible permissions and visible child requirements. There's new recently-offline badge styling, improved currency lookup and formatting utilities, internal bulk delete REST registration support in Core API, better handling for reused organization invite codes, and GET support for custom HTTP SMS gateways.

Bug fixes worth noting

This release also clears out several issues, including active revenue metrics counting inactive or deleted revenue sources, Fleet-Ops sensor filter option rendering, Safee and AFAQY telematics sync edge cases, Fleet-Ops vehicle attachment navigation, sidebar navigator initial sync and related lint issues, and reused organization invite code handling.

What's in this release

Version 0.7.48 updates Console to 0.7.48, Fleet-Ops to 0.6.56, Core API to 1.6.53, Ledger to 0.0.6, and Ember UI to 0.3.38. New API surfaces include Core API settlement status support for transactions, internal bulk delete REST routing, Fleet-Ops public REST endpoints and request/resource contracts for device, equipment, fuel transaction, part, sensor, and work order resources, Fleet-Ops export classes for additional operational resources, a Ledger revenue lifecycle service, repair command, settlement filters and Taler gateway integration, and Ember UI sidebar navigator visibility controls and currency utility improvements.

Upgrading

bash

# Pull latest version
git pull origin main --no-rebase
# Update docker
docker compose pull
docker compose down && docker compose up -d
# Run deploy script
docker compose exec application bash -c "./deploy.sh"

As always, if you run into anything, join us on GitHub Discussions or drop by #fleetbase on Discord.

Ready to put these ideas into practice?

Explore the platform, docs, and open-source modules behind the workflows we write about on the Fleetbase blog.

Explore Fleetbase