IT and software
You do not just need an invoicing system — your product needs to invoice
A Saudi technology company lives two lives: its own books, and its product issuing invoices to its own customers. The second one means your product is issuing tax invoices, and under Phase 2 those have to be built, stamped, cleared or reported like anyone else’s. The Mezan API exists for exactly that.
- Subscriptions that renew, with revenue spread across the subscription term
- Implementation projects in stages, at actual cost rather than estimated
- A public REST API and webhooks for issuing invoices from your product
- Developer payroll charged to the right project or product
The actual work
Three revenue streams that are not managed the same way
Subscriptions are recurring, implementations are staged, support is contractual and renews. Merging all three into one P&L hides which of them is actually funding the company.
Subscriptions and renewals
The annual or monthly contract invoices itself on its date, and the renewal surfaces well before it lapses. Subscription revenue collected up front is spread across its term instead of landing in one month and distorting it.
Staged implementation projects
Analysis, build, test and launch are stages, each with its instalment. The project is a dimension collecting team hours and licence costs, so you know its actual cost rather than the one you estimated at quoting.
Support contracts and SLAs
Recurring revenue that depends entirely on renewal. A report of contracts expiring in the next ninety days is the cheapest growth tool a technology company has, and the most neglected.
Resold licences and infrastructure
Licences, cloud and hardware bought and sold alongside the service. Booked as direct cost against the client or project rather than blended into general overhead.
Developer payroll is the cost base
In a software company, payroll is very nearly the whole cost. Charging it to the right project or product is the difference between knowing your margin and only knowing your revenue.
Your product invoices your customers
If your product sells subscriptions or transactions, it is issuing tax invoices. Over the Mezan API your product issues them from inside Mezan — format, stamp and integration included — instead of building an invoicing layer from scratch.
The documents
What actually leaves the company
Most technology customers are companies, so most of these are standard tax invoices going through clearance.
- Proposal and technical scope
- Deliverables, stages, timeline and assumptions. It becomes a contract and a project without re-entry.
- Subscription or licence agreement
- Term, value, user count and renewal terms. The recurring invoice and the renewal alert are generated from it.
- Recurring renewal invoice
- Issued on its date for the life of the contract. A standard tax invoice in the client company’s name, cleared before delivery. Standard tax invoice (B2B) — cleared before delivery
- Project stage invoice
- An instalment tied to a completed and accepted stage, linked to the project so it appears in its cost and margin.
- Licence or cloud purchase order
- A supplier commitment charged to the client or product, matched against their invoice before payment.
- Credit note on cancellation
- A cancelled subscription or a reduced user count after billing. Issued electronically and linked to the original invoice. In scope for e-invoicing
Mezan products
The parts of the platform you actually need
This is the one sector where the API is a headline product rather than a developer convenience.
Mezan API
A public REST API, OpenAPI documentation, an SDK and webhooks. Your product creates invoices in Mezan over the API, and they come out with the right format, the stamp and the Fatoora integration — without you building a compliance layer.
Learn moreMezan Core
Recurring invoicing for subscriptions, dimensions for projects, products and clients, multi-currency purchasing for licences and cloud, and subscription revenue spread across its term.
Learn moreMezan HR
Payroll for developers, engineers and support, with leave, attendance and end-of-service charged to the right project or product rather than to one line called "salaries".
Learn moreMezan Pay
Collect subscriptions online — Apple Pay, Google Pay, mada and cards — with the receipt posting straight to the customer’s invoice.
Learn moreE-invoicing
If your product invoices, your product is in scope
Technology companies arrive at this page for two different reasons: the company’s own invoices, and its product’s. The first are standard tax invoices to companies, cleared before delivery. The second is the harder one — building a compliant invoicing layer inside your product means XML, the invoice hash chain, a cryptographic stamp certificate per invoice-generating unit, clearance, reporting and error handling. Over the Mezan API your product issues its invoices from inside Mezan instead of you building all of that.
Read the e-invoicing page- Your own invoices to company clients are submitted for clearance and returned stamped before delivery
- Your product can issue its invoices over the API, produced with the required format, stamp and integration
- Webhooks tell your product the status of every invoice: cleared, cleared with warnings, or rejected with the reason
- A cancelled subscription or reduced user count is handled with an electronic credit note linked to the original invoice
Frequently asked
Can we issue our customers’ invoices from our product through Mezan?
Yes — it is one of the reasons the Mezan API exists. Your product creates the invoice over the API, Mezan handles the format, the stamp and the connection to Fatoora, and webhooks return the status of each invoice to your product. Show us your billing model in the demo and we will tell you honestly where the coverage ends before you commit.
How is an annual subscription paid up front treated?
The cash is collected up front but the revenue belongs to the whole term. It is recorded as a liability and spread across the months of the subscription, so the income statement stays steady rather than spiking in the month of collection and emptying afterwards. The exact method is your accountant’s decision and the system applies it as specified.
We sell inside and outside the Kingdom. Is that supported?
Yes, for invoicing, currencies, collection and reporting consolidated in Riyals. How exported services are classified for tax remains your accountant’s decision, and Mezan applies it to every invoice raised for that customer.
Book a demo
Leave your details and we’ll call you back within one business day to arrange your session.