Start with a week of real work
List who issues invoices, records supplier bills, approves payments and closes the month. A service firm might need recurring billing and project margins; a retailer might need POS totals, returns and stock costing. Ask the vendor to run those transactions with anonymized data. If a demo shows only a dashboard, you still do not know whether staff can correct a payment or trace a balance.
Test the Saudi invoicing workflow
Where applicable, ask how the system handles the invoice types and FATOORA integration your business needs. Bring a standard invoice, a simplified invoice and a credit note. Ask what the software shows when a submission is rejected, and who owns the fix. Confirm requirements against ZATCA guidance and your own notification. An Arabic invoice layout alone does not demonstrate integration.
Verify the reports you will actually use
Ask for an aged receivables report, a bank reconciliation and a trial balance for the same cut-off date. Pick one overdue invoice and follow it to the original document and any payment. Check who can change a posted entry, whether changes are logged, and whether your team can export records in a usable format.
Compare implementation cost and exit options
Put license, migration, training, integrations and support in one comparison. Define which opening balances, unpaid invoices and historical transactions will be migrated. Make the final sign-off measurable: compare the opening trial balance, agree outstanding differences and confirm that your team can run the next close without vendor intervention.
What should I take to a demo?
Take an anonymized sales invoice, supplier bill, bank statement and month-end report. Ask the vendor to show the full path from entry through reconciliation and reporting.
