# Breaking Change: Checking the duplicate (response codes 208 & 409) **URL:** \ **Category:** Announcements\ **Created:** [May 5, 2025, 7:30am UTC](https://zatca1.discourse.group/t/breaking-change-checking-the-duplicate-response-codes-208-409/6859 "2025-05-05T07:30:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\ **Post date:** [May 5, 2025, 7:30am UTC](https://zatca1.discourse.group/t/breaking-change-checking-the-duplicate-response-codes-208-409/6859/1 "2025-05-05T07:30:07Z")
**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: 1. **Objective:** To improve overall system performance and efficiency by identifying duplicate invoices submitted on Clearance APIs and Reporting APIs by comparing the hash values of invoices submitted within **24-hours**. 2. **Functionality Overview:** 3. **Impacted Components:** 4. **Deployment Plan:** For questions or clarifications, contact [[sp\_support@zatca.gov.sa](mailto:sp_support@zatca.gov.sa)]. ---
**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\ **Post date:** [May 5, 2025, 7:31am UTC](https://zatca1.discourse.group/t/breaking-change-checking-the-duplicate-response-codes-208-409/6859/2 "2025-05-05T07:31:26Z")
---
**Author:** ![Ankit.K.Tiwari](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@Ankit.K.Tiwari](https://zatca1.discourse.group/u/Ankit.K.Tiwari)\ **Post date:** [May 25, 2025, 1:15pm UTC](https://zatca1.discourse.group/t/breaking-change-checking-the-duplicate-response-codes-208-409/6859/3 "2025-05-25T13:15:12Z")
Dear Community Members, Hope you have tested the new validation rules for front end duplication check (208 and 409 response codes). If you have any concerns please post the feedback on forum asap. tagging the participants who shared feedback on 409 response code earlier on a separate thread: @eCloud @Adithya_Raviraja @mkw @Malik @sameer @Maala @pmohdameen @mohdzeeshan5c0 @Hadi @rudyzidan @Arratech @BEX @plasker @y.khraishi @abin @m.alnoursi @sameer @mohammad.mt ---
**Author:** ![Ankit.K.Tiwari](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@Ankit.K.Tiwari](https://zatca1.discourse.group/u/Ankit.K.Tiwari)\ **Post date:** [July 7, 2025, 9:45am UTC](https://zatca1.discourse.group/t/breaking-change-checking-the-duplicate-response-codes-208-409/6859/4 "2025-07-07T09:45:37Z")
Dear Community Members, Please note that the new validation rules for front end duplication check (208 and 409 response codes) will be deployed by July 20. If you have any concerns please post the feedback on forum asap. tagging the participants who shared feedback on 409 response code earlier on a separate thread: @eCloud @Adithya_Raviraja @mkw @Malik @sameer @Maala @pmohdameen @mohdzeeshan5c0 @Hadi @rudyzidan @Arratech @BEX @plasker @y.khraishi @abin @m.alnoursi @sameer @mohammad.mt ---
**Author:** ![Ankit.K.Tiwari](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@Ankit.K.Tiwari](https://zatca1.discourse.group/u/Ankit.K.Tiwari)\ **Post date:** [August 7, 2025, 8:38am UTC](https://zatca1.discourse.group/t/breaking-change-checking-the-duplicate-response-codes-208-409/6859/5 "2025-08-07T08:38:27Z")
Dear members, please note that 409 and 208 front-end duplication check validations are deployed to Production, below announcement contains further details. [@eCloud](https://zatca1.discourse.group/u/ecloud) [@Adithya\_Raviraja](https://zatca1.discourse.group/u/adithya_raviraja) [@mkw](https://zatca1.discourse.group/u/mkw) [@Malik](https://zatca1.discourse.group/u/malik) [@sameer](https://zatca1.discourse.group/u/sameer) [@Maala](https://zatca1.discourse.group/u/maala) [@pmohdameen](https://zatca1.discourse.group/u/pmohdameen) [@mohdzeeshan5c0](https://zatca1.discourse.group/u/mohdzeeshan5c0) [@Hadi](https://zatca1.discourse.group/u/hadi) [@rudyzidan](https://zatca1.discourse.group/u/rudyzidan) [@Arratech](https://zatca1.discourse.group/u/arratech) [@BEX](https://zatca1.discourse.group/u/bex) [@plasker](https://zatca1.discourse.group/u/plasker) [@y.khraishi](https://zatca1.discourse.group/u/y.khraishi) [@abin](https://zatca1.discourse.group/u/abin) [@m.alnoursi](https://zatca1.discourse.group/u/m.alnoursi) [@sameer](https://zatca1.discourse.group/u/sameer) @mohammad.mt@anusv > [@Deployment Notification | Duplication check - response codes 208 and 409](https://zatca1.discourse.group/t/deployment-notification-duplication-check-response-codes-208-and-409/7954): > > Dear Community Members, Further to the previous announcements, please note that the front-end duplication check has been deployed to the Production Environment with response code 208 for duplicates on Clearance API for B2B invoices and response code 409 for duplicates on Reporting API for B2C invoices. Taxpayers should expect API responses indicating duplicated hash submissions. Below are the key details: 1.Objective : To enhance overall system performance and efficiency by identifying dupli…