ZATCA error after 12 AM

Question

In Saudia Arabia ZATCA  rejected invoices after 12 am. Because ZATCA to receiving Issue Date +1.
I hope can help me. Image [1]
Image [2] Image [3]

[1] data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABxkAAAKICAYAAACsd0QvAAAABHNCSVQICAgIfAhkiAAAABl0RVh0U29mdHdhcmUAZ25vbWUtc2NyZWVuc2hvdO8Dvz4AAAAtdEVYdENyZWF0aW9uIFRpbWUAVHVlIDI0IEZlYiAyMDI2IDAyOjA0OjQ2IFBNICswM88K3EAAACAASURBVHic7N13fFPV/8fxV9Kke0JLW1YLhRZk740sGTJkgyKCinvinrjnFxXc/hRFUZYMkWFBNrJnKVBmoWVTunfT5P7+KEpBVqWljPfzL7g5OfeTkxse5L5zzjEZhmEgI

Shameena Moin Qaisar · Accepted Answer

This is a classic Timezone Synchronization issue between Odoo and the ZATCA API. ZATCA expects the 'Issue Date' and 'Confirmation Datetime' to be in KSA local time (UTC+3). If your Odoo server is set to UTC, after midnight, it sends the previous day's date, which ZATCA rejects. ​I have fixed similar Phase 2 integration errors for several Saudi clients using Odoo 16/17. You need to adjust the Python fields.Datetime.now() logic in the ZATCA module to ensure it respects the KSA timezone before gene

Kunjan Patel · Answer

Hello,
I hope you are doing well
*
Quick fix for the user:*
1. Go to* Settings → General Settings → Timezone* → set to *Asia/Riyadh*
2. Ensure all SA users have timezone set to* Asia/Riyadh* in their user profile
I hope this information helps you
Thanks & Regards,
*Kunjan Patel*

Verknüpfte Beiträge	Antworten	Ansichten
Send Credit Note to ZATCA issue " invoiceHash_QRCODE_INVALID " accounting edi einvoice saudi ZATCA	0 Apr. 25	2521
Error while reversing the journal accounting ZATCA Odoo16	1 Sept. 25	3255
AVCO Vendor Return Creates Inventory Valuation Difference – Correct Accounting Treatment? accounting	1 Juni 26	803
in odoo 19 the amount does not appear distributed Profits/Losses after closing the balance accounting	2 Juni 26	2259
Receipt accounting	2 Juni 26	1728

Diese Frage wurde gekennzeichnet

Diskutieren Sie gerne? Treten Sie bei, statt nur zu lesen!