# Reported\_successfully\_earlier

**URL:** <https://zatca1.discourse.group/t/reported-successfully-earlier/9514>\
**Category:** Clearance and Reporting\
**Created:** [January 6, 2026, 2:11pm UTC](https://zatca1.discourse.group/t/reported-successfully-earlier/9514 "2026-01-06T14:11:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SP\_DolphinSolution](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@SP\_DolphinSolution](https://zatca1.discourse.group/u/SP_DolphinSolution)\
**Post date:** [January 6, 2026, 2:11pm UTC](https://zatca1.discourse.group/t/reported-successfully-earlier/9514/1 "2026-01-06T14:11:13Z")

</div>

REPORTED\_SUCCESSFULLY\_EARLIER

to all our clients with no changes, we didn’t change anything even each customer has there own server

we receiving this error as follows

REPORTING {‘validationResults’: {‘infoMessages’: , ‘warningMessages’: , ‘err  
orMessages’: [{‘type’: ‘ERROR’, ‘code’: ‘Invoice-Errors’, ‘category’: ‘Duplicate  
-Invoice’, ‘message’: ‘Invoice Hash Previously Submitted’, ‘status’: ‘ERROR’}],  
‘status’: ‘ERROR’}, ‘reportingStatus’: ‘REPORTED\_SUCCESSFULLY\_EARLIER’}

Even we checked the hash and its not dublicated

---

<div class="post-metadata">

**Author:** ![mhaba](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@mhaba](https://zatca1.discourse.group/u/mhaba)\
**Post date:** [January 7, 2026, 10:21am UTC](https://zatca1.discourse.group/t/reported-successfully-earlier/9514/2 "2026-01-07T10:21:47Z")

</div>

Hey it might be due to first time getting error in 500 series and later resubmitted this occured.

---

<div class="post-metadata">

**Author:** ![WlGovinda](https://avatars.discourse-cdn.com/v4/letter/w/258eb7/32.png) [@WlGovinda](https://zatca1.discourse.group/u/WlGovinda)\
**Post date:** [February 4, 2026, 1:15pm UTC](https://zatca1.discourse.group/t/reported-successfully-earlier/9514/3 "2026-02-04T13:15:28Z")

</div>

did any one re-tried such failed invoices? it is getting sucess after re-trying couple of times.

---

<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:** [February 4, 2026, 8:37pm UTC](https://zatca1.discourse.group/t/reported-successfully-earlier/9514/4 "2026-02-04T20:37:43Z")

</div>

In the case of rejection, you will never receive a 409 or 208 response.

These codes are exclusively issued for successful submissions that have been officially reported by Zatca, differing from their status within your system.

This discrepancy commonly arises when the system fails to obtain a complete response during the initial attempt and subsequently retries the transmission.

---

<div class="post-metadata">

**Author:** ![Akbersha\_20](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@Akbersha\_20](https://zatca1.discourse.group/u/Akbersha_20)\
**Post date:** [April 28, 2026, 9:33am UTC](https://zatca1.discourse.group/t/reported-successfully-earlier/9514/5 "2026-04-28T09:33:59Z")

</div>

Yes, we’ve encountered this behavior as well.

When invoices are retried, they do get submitted successfully, but the status still appears as \*\*“REPORTED\_SUCCESSFULLY\_EARLIER.”\*\*this status message can understandably confuse end users, especially clients who may assume that the invoice is being submitted multiple times and could cause discrepancies in VAT filings .Anyone have implemented a cleaner way to handle this case?