Jump to a section
At a glance
Key takeaways
- Confirm the licensed entity, reporting period and DDA filing route before building the timetable.
- Reconcile subscription, project or platform systems to the ledger rather than relying on an unreconciled export.
- Document software-development decisions at project level and preserve the evidence available at the reporting date.
- Map cross-border services, intellectual property, cloud costs and funding to the entities that perform, own and bear the relevant risks.
Start with the legal entity and reporting boundary
A Dubai Internet City business may operate as an FZLLC, a branch of an overseas company or part of a wider technology group. Before collecting documents, confirm the licensed entity, financial year, reporting framework and intended recipients of the financial statements.
Map which entity signs customer contracts, raises invoices, employs delivery teams, owns intellectual property and pays cloud or platform suppliers. This boundary matters when operational systems serve several group companies or when transactions are recorded centrally.
Review Dubai Internet City audit services and DDA reporting requirements
Build the timetable from the DDA deadline
DDA Circular 421 requires FZLLCs and branches within its scope to prepare and submit annual audited financial statements and an annual return. The ongoing deadline is six months from financial year-end, while a newly registered entity submits after its first completed financial year. Confirm the current authority workflow for the specific entity.
Work backwards from the filing date. Allow time to close the ledger, reconcile systems, prepare schedules, answer audit questions, assess adjustments, approve the statements and complete the agreed filing steps. The statutory or authority deadline is not a suitable date to begin the close.
- Name a finance owner and a deputy for each material schedule.
- Agree dates for parent-company information and external confirmations.
- Identify who approves the accounts, signs appointment or filing documents and retains the submission receipt.
Reconcile contracts, billing and revenue
Create a revenue map for subscriptions, implementation, support, professional services, licences, usage charges, advertising, commissions or equipment sales. For each material stream, connect the contract terms to the billing system, invoices, collections and general ledger.
For subscription services, retain the service period, renewal and termination terms, usage data, credits and contract changes. Reconcile active customers and annual recurring revenue reports to accounting records, but do not assume that a management metric is the same as recognised revenue.
For implementation or consulting projects, retain statements of work, time records, deliverables, customer acceptance, change orders and project-cost schedules. Explain unbilled amounts, advance billing and loss-making or delayed projects.
Platforms and marketplaces should reconcile order or user activity to payment-gateway settlements, refunds, chargebacks, wallets or customer credits. Document the contractual relationships and management’s assessment of gross-versus-net presentation.
Prepare software-development evidence by project
Maintain a project register that identifies objectives, stages, approvals, people and external suppliers. Reconcile employee time and supplier costs to payroll, invoices and the ledger. Separate research, routine maintenance, customer configuration and product development where those distinctions affect the accounting assessment.
Capitalisation is not automatic because a project may generate future value. Apply the applicable reporting requirements to the evidence available at each reporting date. Where relevant, support technical feasibility, intention and ability to complete, availability of resources, expected benefits and reliable measurement.
For completed or existing software assets, keep release, useful-life, amortisation and impairment information. Explain abandoned modules, major changes in strategy and products that are no longer supported. Management’s current optimism should not replace evidence about conditions at year-end.
Reconcile cloud, licences and technology assets
Collect material cloud, hosting, data-centre, network, software-licence and equipment contracts. Explain committed spend, prepayments, customer deposits and usage-based charges. For equipment, reconcile the asset register to invoices, commissioning, location, depreciation, disposals and impairment indicators.
Review whether arrangements contain service, asset or lease components under the applicable reporting framework. The commercial label is not conclusive. Identify assets funded, controlled or used by another group entity and reconcile the related charges.
Coordinate branches and international groups
DDA Circular 421 permits a branch reporting route using consolidated audited parent financial statements or a standalone extract of branch operations. Discuss the route early because the parent period, framework and completion date may not align with the local filing deadline.
Keep local records reconciled even where parent statements will be submitted. Explain head-office funding, shared staff, regional management, cloud infrastructure, intellectual-property charges and balances recorded centrally. Agree how local adjustments flow into the parent reporting pack.
For related-party transactions, retain the agreement, functional analysis, calculation and evidence that the service or arrangement occurred. A transfer pricing benchmark may support a method or range, but it does not replace the actual facts or prove that a charge was received.
Review transfer pricing and benchmarking support
Protect data while giving usable evidence
Technology businesses may hold confidential customer, user, employee and source-system information. Agree secure evidence-sharing arrangements and provide only the fields required for the engagement. Do not place production credentials, unrestricted database access or unnecessary personal data in a general audit folder.
When a system-generated report supports a material balance, record the system, report name, parameters, period and extraction date. Reconcile its total to the ledger and retain an explanation of manual adjustments. A screenshot or spreadsheet without a controlled source and reconciliation may be difficult to rely upon.
A financial statement audit does not provide a cybersecurity certification, penetration test, SOC report, ISO certification or data-protection compliance conclusion. Those objectives require a separate engagement, criteria and specialists.
Keep final accounts, tax and filings consistent
Before approval, reconcile the financial statements to the final trial balance and adjustment list. Check the legal name, reporting period, comparative figures and signatories. Ensure that tax and group-reporting teams receive the approved figures and explanations for relevant changes.
A Dubai Internet City licence does not by itself determine Corporate tax treatment. Assess the legal entity, actual activities, income and statutory conditions separately. Keep the tax reconciliation, related-party schedules and financial statement disclosures consistent.
Request a properly scoped audit proposal
SAIF Chartered Accountants supports Dubai Internet City businesses with annual audit, accounting readiness, DDA reporting coordination and related tax and transfer pricing services. Share the licence, financial year, trial balance, prior report and required date. Explain subscriptions, projects, platforms, software development, branches and group transactions so the work can be scoped accurately.
Accounting preparation and independent audit are distinct services. Any assistance is separately agreed and considered against applicable independence requirements. Management remains responsible for the records, accounting decisions and financial statements.
Authority and verification
Official sources
- Dubai Development AuthorityCircular 421 — audited financial statements and annual reportingChecked 17 September 2026
- Dubai Development AuthorityAppoint or change the company auditorChecked 17 September 2026
- Dubai Internet CityDubai Internet City community directory and business activitiesChecked 17 September 2026
Clear answers
Frequently asked questions
What should a Dubai Internet City finance team prepare first?
Confirm the entity, reporting period and DDA route, then prepare the closing trial balance and reconciliations for the material balances and operating systems.
Is a subscription or CRM export sufficient audit evidence?
Not by itself. Reconcile it to invoices, collections and the ledger, and retain the contract and service-period information supporting material balances.
Can all software-development expenditure be capitalised?
No. The treatment depends on the applicable reporting requirements and project facts. Maintain project-level cost and stage evidence and document management’s assessment.
Does the financial audit cover cybersecurity compliance?
No. Cybersecurity, data-protection, penetration testing and security certifications are separate objectives requiring a specific scope and suitable specialists.
Can a branch rely on its parent company audit?
Do not assume so. Confirm the accepted DDA reporting route, period and local supporting information, and keep the branch records and head-office balances reconciled.
