A hand-written invoice gets lost, reminders are late, and today’s receivables are hard to see. What is needed is a clear invoice, a tracked status and organised reminders.
Every invoice takes its number from a yearly counter inside one transaction, so two invoices issued at the same instant never share a number.
Record payments in instalments; an invoice shows as part-paid or overdue on its own, from its due date.
Tax rate per line, rounded per line, so the total matches what the customer gets by adding up the printed lines.
An issued invoice and a recorded payment post to the ledger without anyone typing an entry.
A credit note is a record of its own with its own numbering, and the notes against an invoice can never add up to more than it. It reverses the revenue and the tax at the rate the invoice itself was posted at, so nothing is left behind in receivables.
A link per customer, shared on WhatsApp and withdrawn whenever you like: they see their invoices, quotations, orders and tickets, and can accept a quotation themselves — which makes it a sales order in your workspace. No account, no password.
A message to the customer when the invoice is issued and when a payment is recorded, sent in the background so no screen waits on it, and recorded with a plain reason when it is not.
The Phase 1 QR on a simplified invoice, and the Phase 2 UBL document with its hash and its chain — all generated on your own server. No submission, no clearance, no reporting, and no cryptographic stamp, because a stamp needs a certificate the authority issues after a unit is onboarded. No approval from ZATCA or anyone else.
A recurring agreement — monthly, quarterly or yearly — has its invoice raised by a background job, never by somebody opening a screen. One period is never billed twice however often the job runs or the button is pressed: the guarantee is a database index on the subscription and the period’s own first day, not a hoped-for order of requests.
A subscription that starts on 31 January is billed on the 31st: 31 January, 28 February, 31 March — each boundary computed from the start date rather than from the one before it, so February does not drag the billing day back for good. Pausing stops the next period and leaves an invoiced one alone: giving part of it back is a credit note a manager raises from the invoice, not a button that quietly moves revenue and VAT.
What the software did is written onto the invoice itself in both languages at once — issued with its number, its amount and its due date; a payment recorded; the balance moved — alongside notes the team writes and a follow-up with a date and an owner: a call, a meeting or a task. A line the system wrote can be neither edited nor deleted, and a deleted note leaves its trace behind with its text never reaching the browser.
Scheduled reminders before and after the due date.
The path is built and tested end to end against a test gateway that refuses live mode. No real gateway is offered today, so no card can be charged.
On one set of data: what happens here reaches these apps without anyone retyping it.
Yes. Each invoice takes its number from a yearly counter inside one transaction, so two invoices issued at the same instant never share a number. A draft gets no number until it is issued.
Yes. Record any number of payments by cash, transfer, card or cheque; the invoice shows as part-paid, paid or overdue by itself, from its due date.
Yes — every invoice shows its total in Arabic or English words, and can be sent to the customer on WhatsApp in a ready message.
From the invoice itself. The note is a record of its own with its own numbering, and the notes against an invoice never add up to more than it. A credit note does not pay money back and does not return goods to the shelf — those are separate acts.
No, and we do not say otherwise. What exists: the Phase 1 QR on a simplified invoice, and the Phase 2 UBL document with its hash and its chain, all generated on your own server. What does not: submission, clearance, reporting and the cryptographic stamp — a stamp needs a certificate the authority issues after a unit is onboarded — and no approval from ZATCA or anyone else.
Yes. A recurring agreement is monthly, quarterly or yearly, each period’s invoice is raised by a background job rather than by anyone opening a screen, and a period is never billed twice. Periods are anchored to the start date: one that starts on 31 January bills on 28 February and then returns to 31 March.
Not today. The customer’s page shows their invoices and the payments already recorded; the path to a payment gateway is built and tested, but no real gateway is offered yet.
Marketing agencies with retained clients, campaigns, creative deliverables, and team hours as the real cost.
Cleaning companies on recurring contracts with scheduled visits, large crews and daily site allocation.