Tax, Zakat & E-Invoicing Coming soon
Egypt (ETA) and Saudi Arabia (ZATCA) — either your books hold up under inspection or they do not.
The gap between your return and your books is what you later pay for in penalties. seg-audit reconciles returns to books, computes the zakat base from your balance sheet, and checks e-invoicing readiness against both the Egyptian Tax Authority (ETA) and the Saudi Zakat, Tax and Customs Authority (ZATCA) — putting you in permanent readiness, not emergency preparation.
Reports in this section
What zakat base do you owe this year, and how was it reached, line by line?
- Balance sheet: current assets and short-term liabilities
- Working capital, investments and inventory
- Retained earnings, provisions and allowable deductions
The zakat base computed under both the net-asset and sources methods, with a detailed schedule of every added or deducted item traced to your books.
Owner and CFO — a number you can defend before ZATCA with ledger evidence, not an estimate.
Are your invoices ready for integration with the Saudi Fatoora platform?
- Invoice XML structure and mandatory fields
- QR code, hash and UUID
- 15-digit VAT number and entity details
Every invoice or setting that will be rejected at integration, with the exact missing field — before it is rejected.
CFO and compliance — a Fatoora rejection stops collection, not just invoicing.
How many invoices never reached the Egyptian portal or were rejected — and what are they worth?
- Submission status of each e-invoice
- Recorded rejection reasons
- Item codes (GS1/EGS) and tax ID
Rejected and unsubmitted invoices, classified by rejection reason and value.
Accountant and CFO — every unsubmitted invoice is a live violation.
Does what you declared actually match what is in your books?
- Sales invoices and output tax
- Purchase bills and deductible input tax
- Returns filed in the period
A line-by-line reconciliation of return to books, with each difference and its cause.
CFO and owner — a difference you find is far cheaper than one the inspector finds.
Is your customer and item data complete enough to issue an accepted invoice?
- Tax IDs and customer details (Egypt 14-digit / Saudi 15-digit)
- Item codes and units
- Line details and applied taxes
The missing data that will cause a rejection — before it causes one.
Accountant — a proactive fix that prevents rejection entirely.
Was tax withheld at the correct rates and on the correct items?
- Payments subject to withholding
- Rates applied per activity type
- Related supplies and filings
Cases where withholding was missed or applied at the wrong rate, with the value difference.
CFO — the obligation falls on you, not the supplier.
Does the tax recorded in the entry match the tax on the invoice?
- Tax at invoice and line level
- Corresponding journal entries
- Tax account balances
Differences between invoice and entry, and the impact on the tax account balance.
Accountant — small differences accumulate into an unexplainable tax balance.
If an inspection came tomorrow — from the ETA or from ZATCA — what would be held against you?
- Completeness of supporting documents
- Consistency of returns across periods
- High-risk items per authority
A readiness assessment against the relevant authority, with the points an inspector is most likely to stop at.
Owner — know your position before someone else does.