# 409 status code - Duplicate-Invoice error **URL:** \ **Category:** Clearance and Reporting\ **Created:** [October 30, 2024, 11:11pm UTC](https://zatca1.discourse.group/t/409-status-code-duplicate-invoice-error/3932 "2024-10-30T23:11:55Z")\ **Posts on this page:** 1\ **Showing post:** 42
**Author:** ![pmohdameen](https://avatars.discourse-cdn.com/v4/letter/p/c89c15/32.png) [@pmohdameen](https://zatca1.discourse.group/u/pmohdameen)\ **Post date:** [November 1, 2024, 11:12am UTC](https://zatca1.discourse.group/t/409-status-code-duplicate-invoice-error/3932/42 "2024-11-01T11:12:16Z")
> [@Adithya\_Raviraja](#): > > And in our case, we received this response in the first attempt of sending the invoice. Same here bro. and during retries, it will go to failure loop as they might now already have those invoices as reported on their side. Anyways, treat those invoices as reported (for now) since they’re giving 409 status code [used for conflict] and they do agree in error message that they have received the hash before. _The only problem at this point is:_ We don’t have an official API response saying that its reported. Since they have mentioned it before that it’s our only source of truth to prove to client/zatca, that this particular invoice is reported or not. > [@We have issue in statistics in zatca portal](https://zatca1.discourse.group/t/we-have-issue-in-statistics-in-zatca-portal/1213/4): > > Dear @Ammar each API call gets a response whether it is accepted, rejected or accepted with warnings. You can build your report based on API call responses and rely on it as the single source of truth. Don’t think they are going to comment on this issue today as its Friday. Lets see in coming days if they can give a closure on this or change how the API behaves [either reverting the behaviour entirely or making a change in current response acknowledging its current reportingStatus tag as ‘REPORTED’. --- _[View the full topic](https://zatca1.discourse.group/t/409-status-code-duplicate-invoice-error/3932)._