Skip to content
Basmtak Books
العربية Talk to usTalk to us
Pricing The app For accountants Moving over Contact
Inside the product
Sales & invoicingQuotes, invoices, credit notes, receipts E-invoicingFatoora phase 1 and phase 2 PurchasesPOs, supplier bills, approvals BankingStatements, rules, matching, reconciliation Inventory & manufacturingWarehouses, counts, bills of material ReportsP&L, balance sheet, aging Payroll from HRThe payroll journal arrives posted Fixed assetsRegister, depreciation, disposals Tax & ZakatVAT return, withholding, Zakat AutomationRecurring documents, alerts, close IntegrationsAPI, webhooks, payment gateways All features
Sign in Talk to us
العربية
E-invoicing

Integrated with Fatoora: phase 1 from the first invoice, phase 2 built in

A QR code and hash chain on every invoice, and phase-2 integration from inside the product: device onboarding with an OTP from the Fatoora portal, signed UBL 2.1 XML, clearance for tax invoices and reporting for simplified ones, and every document's status in front of you — with no third-party unit.

Talk to us All features
In every plan Hosted in the Kingdom On iPhone and iPad
The integration screen: current environment, onboarding steps, the certificate and its validity, and counters for cleared, reported and rejected.

The integration screen: current environment, onboarding steps, the certificate and its validity, and counters for cleared, reported and rejected.

What it does

E-invoicing

The invoice QR and the hash chain

The phase-1 QR in TLV format on every invoice, and a hash tying each invoice to the one before it so none can vanish from the middle.

Device onboarding, step by step

The signing key is created on our server and never leaves it, you enter the OTP from the Fatoora portal, the compliance checks pass, then the production certificate is activated — each step with its status on the integration screen.

Signed UBL 2.1 XML

Every invoice has an XML document in the format ZATCA requires, signed with your certificate, ready to download and archive.

Clearance and reporting

A standard tax invoice is sent for clearance before it is handed over; a simplified one is reported within the window after it is.

Sent in the background, with retries

Submission to ZATCA runs in the background every five minutes; what stumbles is retried, and what is rejected shows with its reason.

A rejection never gets lost

A rejected invoice is an alert in the product and on the phone's home screen, with the rejection text as ZATCA returned it.

Three environments, from Settings

ZATCA's three environments, from the developer sandbox to production — the establishment moves between them from its settings, and the product tells you which one you are on.

From inside the product

Real screens from Basmtak Books, with sample data.

The invoice QR and the ZATCA status on the document itself, with the XML to download.
The invoice QR and the ZATCA status on the document itself, with the XML to download.
How it flows

From the key to clearance

Onboarding happens once per establishment; after that every invoice travels on its own.

  1. Create the signing key

    Generated on the server with the certificate request; the key never leaves your books.

  2. Enter the Fatoora OTP

    On the Fatoora portal add a new device and copy the six-digit code.

  3. The compliance checks pass

    The product submits the test invoices ZATCA asks for and shows the result.

  4. Activate the production certificate

    From then on every invoice is signed with your own certificate.

  5. Issue, and rest easy

    Clearance or reporting in the background, the status on the invoice and on the integration screen.

Where it stops today

We write down what we have not built yet, so you do not discover it after subscribing.

  • Onboarding, the compliance checks and clearance run from Books' own unit — no third-party provider; each establishment links its own certificate from its settings with its own OTP, which is what makes the invoice its own.
  • We do not describe the product as "certified" by ZATCA; the accurate description is that it is integrated with Fatoora, and the proof is your own invoices clearing.
  • A standard tax invoice is not handed over before it clears, because it is not a valid invoice until then; a simplified one is handed over at once and reported afterwards.

Related pillars

Sales & invoicing Tax & Zakat Automation All features
Common questions

E-invoicing

Do I need a device or an external unit for phase 2?

No. Signing, submission and archiving all happen inside the product. What you need is an OTP from the Fatoora portal to register the "device", which here is your Basmtak Books account.

What is the difference between clearance and reporting?

A standard tax invoice (business to business) is sent to ZATCA and cleared before it is handed to the customer. A simplified invoice (to a consumer) is handed over at once and reported afterwards. The product knows the type and takes the right path.

What if an invoice is rejected?

It shows as rejected with ZATCA's own text, and you get an alert. Correct the data and resubmit as a new attempt; if the rejection is about the invoice itself, a credit note and a new invoice.

Connect your establishment to Fatoora from your books

The free trial includes the whole integration screen.

Talk to us See pricing

Self-serve signup is closed right now. Leave your details and we will open the account for you.