Before your zakat review: organise a file people can use

A useful review file is more than a collection of attachments. The person receiving it should understand which business and period it covers, which version to use and what still needs an answer.

This guide offers an internal organisation method for business owners and finance teams. It does not calculate zakat or prescribe a universal list of mandatory attachments.

Start with the requirements that apply

ZATCA’s zakat journey identifies registration information, the correct return and financial period, and business financial information as preparation points. It notes that requirements may vary by return type. A different business’s checklist is not a substitute for checking your own requirements. ZATCA: zakat journey (Arabic)

Give the file four clear sections

The structure below is our suggested working method. It is not an official submission template.

1. File overview. Add a short cover note identifying the business, the period covered and the person coordinating the file. Make responsibility for collecting and reviewing information clear.

2. Financial information. Bring together the versions intended for review. Use descriptive filenames and distinguish work in progress from material approved internally. Labels such as “final-new” and “final-latest” do little to explain the difference between two files.

3. Explanations and supporting material. Connect each explanation to the information it addresses. Add a short description of why an attachment is included and who can answer questions about it. Let the responsible specialist determine what is relevant to the case.

4. Open questions. Keep unresolved points in one list. Give each question an owner, a description of the missing information and a current status. A visible question is easier to discuss than an assumption buried in a message chain.

A simple example

Imagine a team with two versions of a financial file. Instead of sending both without explanation, the team marks one “under internal review”, explains the outstanding issue and identifies the person responsible for resolving it. A separate question list becomes the agenda for the review discussion.

This is a hypothetical workflow example, not a client case or a tax treatment.

Before sharing, check five things

• Can the reviewer identify the business and period for each group of files?
• Is each version's status clear without reading a long message history?
• Do unfamiliar attachments have a short explanation?
• Are unanswered questions collected in one place?
• Has an appropriate sharing route been agreed with the intended recipients?

When a question needs professional input

If you are unsure which requirements apply, how an item should be treated or why information is needed, turn that uncertainty into a specific question for the responsible specialist. A well-organised file supports the discussion; it does not establish that obligations are complete or determine the zakat base or amount due.

An optional next step: explore the scope of Mada's zakat advisory support and identify what you would like to clarify. The guide itself is available without providing contact details.

General educational information. Actual requirements and treatment depend on the business's circumstances and should be checked against official sources and appropriate professional advice.