# Clarification on Duplicate Invoice Submission Behavior

**URL:** <https://zatca1.discourse.group/t/clarification-on-duplicate-invoice-submission-behavior/8228>\
**Category:** Clearance and Reporting\
**Created:** [August 28, 2025, 8:04pm UTC](https://zatca1.discourse.group/t/clarification-on-duplicate-invoice-submission-behavior/8228 "2025-08-28T20:04:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sameh.kartngo](https://avatars.discourse-cdn.com/v4/letter/s/dc4da7/32.png) [@sameh.kartngo](https://zatca1.discourse.group/u/sameh.kartngo)\
**Post date:** [August 28, 2025, 8:04pm UTC](https://zatca1.discourse.group/t/clarification-on-duplicate-invoice-submission-behavior/8228/1 "2025-08-28T20:04:07Z")

</div>

Hello,

We are integrating with the ZATCA e-Invoicing system and need clarification about a specific scenario.

Suppose we successfully submit an invoice, but due to an internal issue on our side, we fail to store the submission result in our database. Later, we are unsure whether that invoice was already submitted or not.

If in such a case we resubmit the same invoice again:

- Will ZATCA accept it and consider it a new invoice (thus causing the tax to be duplicated)?

- Or will ZATCA detect that this invoice was already submitted and reject it as a duplicate?

We also noticed that the API does not currently provide any endpoint to check the submission status of a specific invoice (by UUID or invoice number). Is there any recommended approach to handle such cases safely in production?

Thank you for your support.

---

<div class="post-metadata">

**Author:** ![mnuaimi](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@mnuaimi](https://zatca1.discourse.group/u/mnuaimi)\
**Post date:** [August 28, 2025, 11:22pm UTC](https://zatca1.discourse.group/t/clarification-on-duplicate-invoice-submission-behavior/8228/2 "2025-08-28T23:22:38Z")

</div>

Check this out

> [@Breaking Change: Checking the duplicate (response codes 208 & 409)](https://zatca1.discourse.group/t/breaking-change-checking-the-duplicate-response-codes-208-409/6859):
>
> New validation rules to check for duplicate invoices (response codes 208 and 409). Dear Community Members, Numerous taxpayers are pushing increasingly large number of duplicate invoices which is resource intensive for no additional value. Therefore, in order to increase efficiency and performance of overall system, ZATCA will introduce new run time validation to check for duplicate invoices in both Clearance and Reporting APIs. Below are the key details: Objective: To improve overall syste…