A Tally alternative that handles ZATCA Phase 2

Tally is very good at what it was built for. Saudi Phase 2 is not what it was built for, and the gap shows in specific places rather than everywhere.

What actually causes friction

The stamp and the chain. Phase 2 wants each invoice cryptographically stamped with a device certificate and hash-chained to the previous one. That is a signing service sitting next to the ledger, and in a Tally setup it usually arrives as a third-party connector — one more vendor, one more failure point at 4pm on a deadline.

Clearance timing. Standard B2B invoices must be cleared by ZATCA before the buyer gets them. Software designed around print-then-file has to be bent into issuing an invoice that does not exist until an API answers.

Arabic on the document. Not just supported — required, laid out correctly, alongside English.

What a migration moves

Ledger masters, stock items, parties, opening balances and vouchers come across through the migration tools. Customised TDL reports do not, and no vendor can honestly promise otherwise. If your operation depends on three heavily customised Tally reports, budget for rebuilding them.

The recommendation

Run both for a month. Issue from Fatoza, keep Tally as the book of record, reconcile at month end, then decide. If the numbers agree and the counter staff prefer the new screen, cut over. If they do not, you have lost a month and learned something specific instead of arguing about it in the abstract.

We will do the migration and the reconciliation with you on the support plan. Talk to us before you move data — the questions are always about your chart of accounts, and those are faster answered than guessed.