Does Your Accounting System Support XBRL? Odoo vs QuickBooks vs Tally vs Excel for Qayd

Having accounting software and being ready to file Qayd are not the same thing. A business can run a perfectly functional accounting system for years — invoicing, payroll, bank reconciliation, all working fine — and still have no path to producing what Kuwait's Qayd portal actually requires: a validated XBRL instance document built on the IFRS taxonomy.

This is a practical, system-by-system look at where the common platforms in Kuwait actually stand.

What "XBRL support" actually requires

Three layers have to be in place together, not just one:

1. IFRS-structured books. Your trial balance, balance sheet, and income statement need to already follow IFRS presentation — correct classification, consistent totals, proper note structure. A system that just produces "a balance sheet" isn't enough if it isn't an IFRS balance sheet.
2. Taxonomy mapping. Every line item needs to map to the correct tag in the Qayd XBRL taxonomy — the same way every product needs the right barcode, not just any barcode.
3. A validated export. The system needs to actually generate the XBRL instance document and, ideally, catch inconsistencies (totals not matching sub-totals, opening balances not matching prior closing) before you submit — because the Qayd portal will catch them anyway, just later and more painfully.

A system can have layer 1 and still fail on 2 and 3. That's the trap.

System by system

Odoo, configured for Kuwait IFRS — The accounting engine is IFRS-aligned by design, which covers layer 1 when implemented properly. XBRL export itself needs a purpose-built module mapping Odoo's IFRS reports to the Qayd taxonomy — this is not a default feature of a generic Odoo install, it needs to be configured by a partner who understands both Odoo and the Qayd taxonomy specifically. CentrixPlus builds this as part of Odoo accounting implementations for Kuwait clients.

QuickBooks — Does not produce IFRS-tagged XBRL output for Kuwait's taxonomy. Businesses on QuickBooks are looking at either a third-party conversion tool re-run every filing period, or a migration.

Tally — No native XBRL export. The re-keying workaround is slow, error-prone, and doesn't scale — every filing period repeats the manual work and the risk. See our Tally-to-Odoo migration guide if this is your starting point.

Excel-based bookkeeping — Effectively a non-starter. No structured chart of accounts, no IFRS reporting engine, no realistic path to a validated XBRL export without a full accounting system underneath it first.

Older SAP Business One installs — Technically reachable via third-party add-ons, but the GCC XBRL add-on ecosystem for SAP B1 is thin and the configuration cost is high relative to the size of business that typically runs it in Kuwait.

How to check where you actually stand

Don't guess — run a short gap assessment:

1. Export a full set of financial statements from your current system.
2. Check them against IAS 1 presentation requirements — correct current/non-current classification, comparative periods, note disclosures.
3. If they don't already look like a proper IFRS statement, tagging is premature — fix the structure first, because XBRL tagging can't repair statements that were never built to IFRS in the first place.
4. If they do, the remaining question is purely technical: does your system (or an add-on to it) produce a validated Qayd-taxonomy export?

If you're not ready

A realistic path for a business starting from Tally, QuickBooks, or Excel:

All-in, a realistic timeline is 60 to 90 days. Starting that process now, during the voluntary window, means fixing problems on your own schedule. Starting it in Q4 2026 means fixing them under deadline pressure, during your busiest accounting period.

If you're also unsure whether Qayd is even the deadline that applies to you — as opposed to the CMA's separate Ifsah 2 system — see our Ifsah 2 vs Qayd breakdown first.