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.
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’.