Prepaid wallets and tiered tariffs: Gulf-style fleet billing models

Why postpaid billing struggles in the fleet market

The traditional subscription model is familiar: deliver the service for a full month, issue an invoice, wait for payment. It works where collection cycles are short and disciplined. In the fleet market it collides with a different reality: a customer running dozens of vehicles with a budget stretched across fuel, maintenance, and payroll; a relatively small service provider with no collections department; and a service whose absence is only felt when it is suddenly needed — so the tracking line item naturally drifts down the payment queue.

The result is a familiar chain: invoices age, collection calls consume the team, the cut-off decision keeps being postponed because the customer is "big" or "promised to pay" — until the provider finds itself financing its customers involuntarily, and often accepting settlements with discounts that eat the margin. The problem is not the market's ethics; it is the model's design. A system that allows debt to form will produce debt, every time.

The irony sharpens when you remember that Gulf markets have known and culturally accepted prepayment for decades: the prepaid SIM is the default rather than the exception, and prepaid service cards are familiar in every sector. The Gulf customer is not puzzled by loading a balance and consuming it; he is only puzzled by being cut off without warning. What is needed is not changing the market's culture — it is designing a system that warns clearly and then executes fairly.

The prepaid wallet: automatic suspend and release

The alternative that has long since taken root in Gulf markets — from prepaid telecom SIMs to service cards — is prepayment: the customer's wallet is topped up with balance, service costs are deducted from it periodically, and as the balance approaches zero the customer is notified through their preferred alert channels. If it runs out, service is suspended automatically; the moment the wallet is topped up, the suspension is released automatically — no one intervenes at any step.

The value of this design lives in the repeated word "automatically": no employee decides when one customer is cut and another indulged, no courtesy hardens into debt, and no customer is surprised, because the rule is declared on day one and applied to everyone equally. It is also fairer than it first looks: the disciplined customer no longer subsidizes, through his own prices, the defaults of others — and the relationship stays clean because money is settled by the system, outside personal phone calls. On the Pixa platform, this machinery — wallet, automatic suspend, automatic release — is built into the core of the billing layer, not bolted onto it.

The cornerstone of customer acceptance is the early warning, not the suspension itself. Low-balance alerts go out through the platform's five alert channels — WhatsApp, SMS, email, app push, and browser notification — plus the internal notification center, so no one can claim they did not know. The customer who received three messages before the suspension tops up on time; the rare customer who ignores them all is precisely the one who would have become a write-off under the postpaid model.

The tiered tariff engine: a price that grows with the customer

The second question after "how do I collect?" is "what do I charge?". One flat price per vehicle regardless of fleet size looks simple but loses on both ends: it overweights the small owner relative to the value consumed, and pushes the large fleet into one-off negotiation or out the door. One-off negotiation, in turn, breeds a chaos of contracts where nobody remembers why a given customer got a given price.

A tiered tariff engine solves this with a published rule: one tier for the first band of vehicles at one price, the next band at a lower unit price, and so on upward. The large fleet gets its appropriate unit price without a private negotiation, and the whole price book remains a single rule the system applies automatically — one a salesperson can explain in a minute. Three principles keep the ladder itself balanced: make each tier wide enough that customers do not hop between tiers with every vehicle added or removed; keep your margin intact even in the smallest tier, since it usually holds the most customers; and publish the thresholds so the customer knows in advance what he gains by growing his fleet with you — turning the ladder into a growth incentive rather than a mere price sheet. The table puts the two models side by side:

The tax invoice: ZATCA compliance through ERPNext

Prepayment does not abolish the invoice. Saudi organizations need compliant tax invoices for everything they pay, and the e-invoicing requirements of the Zakat, Tax and Customs Authority (ZATCA) are explicit about it. The billing layer therefore connects to the ERPNext accounting system, issuing ZATCA-compliant invoices without the provider building a bespoke accounting bridge — and this integration is available today, not a roadmap promise. The rest of the available integrations are listed on the integrations page.

The resulting arrangement is practical and clean: the wallet governs cash flow, suspension, and release in real time inside the platform; ERPNext carries the formal accounting and tax face; and every party — customer, provider, auditor — holds a complete, compliant document.

Why through ERPNext rather than a home-grown accounting build? Because tax compliance is a discipline of its own, whose requirements move with the authority's decisions rather than a product roadmap — and separating the operating platform from the accounting system keeps each side doing what it does best: the platform measures and controls in real time; the accounting system issues and archives formally. That same separation is what reassures an external auditor reviewing your books.

The dealer layer: wholesale purchasing and periodic settlements

In a multi-tenant platform model, the billing equation repeats at two levels: the platform bills the dealer, and the dealer bills his customers. Run both levels postpaid and debt multiplies in every layer. The upper level is therefore run as wholesale billing: the dealer buys the service at wholesale rates according to his volume, with clear, itemized periodic dealer settlements between him and the platform — while he sells to his own customers at his own pricing and tiers, keeping the difference as his margin.

Under this arrangement the dealer knows his cost up front and his margin on every tier, the platform knows its receivables without chasing anyone, and the end customer stays on the same wallet rule. The commercial model for dealers is detailed on the dealer program page, and package structures on the pricing page.

This clarity pays beyond peace of mind: a dealer who knows his cost and margin on every tier can plan expansion with confidence, quote customers deliberately rather than improvising, and walk into any financial review — internal or in front of a financier — with numbers consistent from wallet to settlement to invoice.

Designing your own model

If you are a provider or dealer rethinking your financial model, start with three written decisions before any technical setup: the suspension rule (exactly when the customer is alerted and when service is suspended), the tier ladder (each tier's boundaries and unit price, set so your margin survives even in the smallest tier), and the invoice path (what the customer receives as a formal document, and how often). Then make the system — not your staff — the executor of those decisions. A good financial model is one that works the same on the day you are away as on the day you are in.

And review the model periodically with specific questions, not general impressions:

• How many customers hit automatic suspension this quarter, and how many returned with a top-up within days? A quick return means the rule is working; a long lapse deserves a sales call, not a collections call.
• Are most of your customers clustered at the edge of a single tier? The threshold may need moving.
• Does the count of issued invoices match wallet movements over the same period? Consistency between the two layers is what keeps your financial review free of surprises.

To see the whole machinery — wallet, tiers, settlements, and ZATCA invoicing — running on data that looks like yours, contact us for a hands-on tour of the billing layer.