Built for GCC delivery operators

Hisbuu Driver Operations

Run driver onboarding, daily submissions, partner reconciliation, bank proof, payouts, assets, and admin controls from one focused operations platform.

Admin and driver portals
Single-tenant installs
English and Arabic driver UI
Managed or self-hosted rollout
4 admin rolesSuper admin, admin, finance, and supervisor access.
Native, web, and APIiOS/Android driver app, web fallback, and token-based endpoints.
Client-owned dataSeparate database and environment per operator.
Arabic readyDriver-side language switching and RTL support.

Where fleet operations usually break

Hisbuu is designed around the daily work that spreadsheets, WhatsApp threads, and month-end catchups fail to control.

Cash proof gets scattered

Drivers send screenshots in chats, bank deposits arrive later, and finance has no clean audit trail.

Partner data does not line up

Aggregator reports, driver submissions, and bank records rarely land in the same place or format.

Compliance is hard to see

KYC documents, expiry dates, assigned assets, and driver status need active follow-up.

Payouts become manual

Monthly earnings, adjustments, advances, shortages, and approvals turn into fragile worksheets.

A platform for the full driver lifecycle

The current Hisbuu build covers the modules operators need from first driver record to final payout slip.

Driver records and KYC

Create drivers, track civil ID, license, vehicle registration, expiry dates, approvals, and document sides.

  • Bulk driver upload support
  • KYC review queues

Driver daily submissions

Drivers submit orders, cash deposited, transaction references, remarks, and proof files from the native app or web/PWA fallback.

  • Pending, approved, and rejected states
  • Resubmission path for corrections

Partner data comparison

Upload partner daily data and compare it against driver submissions to find missing days, order gaps, and cash differences.

  • Partner daily import flow
  • Summary and detail review screens

Bank and settlement proof

Track bank transaction logs, settlement remittances, and proof files so finance can validate actual cash movement.

  • Bank Muscat parser support
  • Settlement targets and proofs

Payout cycles

Build monthly payout cycles with earnings, incentives, deductions, advances, shortages, and printable driver slips.

  • Finance-focused approval flow
  • Driver payout history

Assets and adjustments

Manage assigned equipment, salary schemes, positive and negative adjustments, recurring expenses, and other income.

  • Asset expiry awareness
  • Configurable adjustment categories

Settings and integrations

Configure branding, lookups, commission rates, Bunny CDN storage, WhatsApp messaging, projects, cities, zones, and types.

  • White-label ready settings
  • Installer profile support

Controls and audit trail

Role gates, CSRF helpers, activity logs, secure uploads, and session controls support day-to-day governance.

  • Permission-aware admin actions
  • Operational activity logging

Deployable per client

Each operator can run a separate install with its own database, environment, branding, admin account, and optional demo seed data.

  • CLI and browser installer
  • Migration runner for upgrades
Daily operating loop

From driver activity to finance-ready payout

Hisbuu connects the work that usually happens in separate tabs: driver proof, partner reports, bank validation, review, and monthly payout.

Reconciliation snapshot Needs review
Driver submission34 orders, OMR 186.500 deposited
Partner daily file35 orders, OMR 190.000 expected
Bank transactionReference found, amount short by OMR 3.500
1

Onboard the driver

Create the driver profile, collect KYC, assign project, city, zone, vehicle details, and equipment.

2

Capture daily submissions

Drivers submit order count, cash deposit, bank reference, remarks, and screenshots from their phone.

3

Compare against partner and bank records

Operations reviews missing submissions, mismatched order counts, cash gaps, and bank validation status.

4

Close the payout cycle

Finance combines monthly earnings, adjustments, advances, shortages, and approvals into driver payout slips.

Built around teams

Different views for different responsibilities

Hisbuu does not treat everyone as the same admin user. It separates operational, financial, supervisory, and driver work.

Super Administrator

Full control

Owns setup, users, settings, integrations, lookups, role access, and client-level configuration.

Finance Administrator

Money movement

Handles partner uploads, reconciliation, settlement proof, commission rates, adjustments, and payout cycles.

Supervisor

Daily review

Checks driver submissions, follows missing days, reviews proof files, and keeps operations moving.

Driver

Mobile-first

Uses the native driver app, web/PWA fallback, or API-backed workflows for submissions, KYC documents, assets, adjustments, and payout history.

Rollout options that match your operation

Pricing and scope depend on driver count, hosting preference, branding, integrations, migration work, and support needs.

Pilot

Start with a focused fleet

Validate the submission and reconciliation workflow with a controlled driver group before wider rollout.

  • Core driver and admin setup
  • Initial partner data mapping
  • Demo-led operator training
Managed rollout

Launch for the whole operation

Move the core workflows into daily use with branding, settings, users, migrations, and support.

  • White-label portal and lookups
  • Driver imports and KYC workflow
  • Payout and finance configuration
Dedicated install

Own environment, deeper controls

Run Hisbuu in a dedicated environment with separate database, optional self-hosting, and tailored integrations.

  • Client-specific database and env
  • CDN and WhatsApp settings
  • Upgrade and migration support

Questions operators ask first

Short answers for the decisions that usually come up before a demo.

No. Cash and bank proof are major strengths, but the platform also manages driver records, KYC, partner data, payouts, assets, expenses, settings, and admin controls.

Yes. The staging build supports per-client environment settings, database setup, branding values, superadmin creation, and optional integration settings during install.

Hisbuu supports both the native Hisbuu Driver app and a browser-based web/PWA experience. The native app can be provisioned to the right company workspace by QR code, while the web portal remains available when a browser fallback is easier.

Current integration points include driver API endpoints, partner data import workflows, Bank Muscat parsing, Bunny CDN storage configuration, and WhatsApp messaging settings. Deeper aggregator sync can be scoped per rollout.

Yes. Hisbuu has bulk upload paths and install tooling. In a rollout, we map existing driver records, projects, cities, zones, document types, and payout structures before going live.

We quote based on fleet size, hosting model, migration effort, branding, support, and integration requirements. That keeps the commercial plan aligned with the actual operation instead of an outdated public rate card.

Ready to see Hisbuu against your workflow?

Share the size of your fleet and we will walk through the modules that matter most: driver onboarding, daily proof, reconciliation, and payout close.

Demo first, rollout scope after the workflow is clear.