العربية

Start free trialBook a demo

Browse the documentation

Documentation

All appsHow the apps connectTeam workflowsCompare

Apps

HR ManagementRecruitment (ATS)Payroll & WPSTime & AttendanceAccounting & E-InvoicingCRM & Sales PipelineSales Orders & FulfilmentInventory, Purchasing & WarehousingProcurement & TendersConstruction & ContractingContracts & E-SignatureProducts & Online StorePoint of SaleRentalsSubscriptions & LicensingHelpdesk & TicketingSocial Media SuiteInfluencer Marketing & Campaign ROIProject ManagementActivities WorkspaceDocument ManagementPDF Tools & E-SignatureCorrespondence RegisterTeam Chat & CallsMeetings & VideoLearning & Certification (LMS)Asset ManagementFleet ManagementRecognition & GamificationContacts & PartnersNotification CentreReports & DashboardsInsights — Business Intelligence & AppsAI CopilotAI Agents & AutomationAI Diagram StudioWebsite BuilderISO Compliance Suite (Imtithal)App MarketplaceCustomer & Partner PortalSecurity, Access & Compliance

A rejected Saudi e-invoice is fixed and re-issued

Who is involved

RoleWhat they do
Accounts receivable clerkIssues the invoice and sees the outcome.
Tax agentFinds the rejection, fixes the cause and re-issues.

Step by step

  1. Accounts receivable clerk

    Issues a business invoice, using Issue and send to ZATCA for clearance.

    What they see:Waiting for ZATCA clearance.

  2. Tax agent

    Is alerted and opens the exceptions queue in the compliance overview.

    What they see:The rejected invoice with Explain this error.

  3. Tax agent

    Opens the error card and uses Fix to correct the customer's details, then Re-issue.

    What they see:A corrected copy with the same invoice number and the rejected copy kept in history.

  4. Accounts receivable clerk

    Refreshes the invoice.

    What they see:Cleared by ZATCA, with the tax agent shown on the timeline.

Who is told what

The issuer and everyone able to submit e-invoices get a severity 3 alert on rejection, and the issuer is told when it clears.

Related