It is observed that in the XML for signing time, the HH:MM:SS format is supposed to be provided. Time in either AST or UTC can be used. if sent in UTC, suffix with ‘Z’.
When we send timing as in UTC suffixed with a Z, our XMLs did not get any error.
When we sent timing in AST but without a ‘Z’ our XMLs were rejected. Due to this we are forced to add a ‘Z’ even in this case. Should the signing time in the XML always be in UTC??
As per the latest version 2.0 of ‘Detailed Guidelines for E-Invoicing’ on page 26, it is stated, 'Each stored invoice must follow a naming convention for naming of the file: VAT Registration (tax registration number) + Timestamp (date and time at the point of invoice generation) + Invoice Reference Number.
Should this be read as send time in Zulu timezone and add ‘Z’ in the file name if EInvoice is generated outside KSA timezone?
There is a bug on the time zone. The fix will be deployed shortly. You should be able to provide “time” as local time without suffix Z or if you choose to mention “time” in UTC then with suffix Z. Please retest after the announcement of bug fix.
Regarding the timestamp in File name, it is be based on Invoice Issue Date (BT-2) and Invoice Issue Time (KSA-25). If the time is in local time then there is no need to add suffix Z in the timestamp in file name.
Hi Ankit, as a follow-up, should time be in 24 hour format or in 12 hour format? Because in the latest SDK 24 hour format fails validation when time is after 12 noon. So we are currently sending time in 12 hour format. But we did not understand how to specify the AM/PM.
Time should be in 24 hour format. 12 hour format is not allowed. Please refer paragraph 7.3 (entry # 10 in table) of XML Implementation Standards.
The type time represents a time of day in the format HH:mm:ss where HH represents the hour, mm the minutes, and ss the seconds. An unlimited number of additional digits can be used to increase the precision of fractional seconds if desired. The time is based on a 24-hour time period, so hours should be represented as 00 through 24. Either of the values 00:00:00 or 24:00:00 can be used to represent midnight.
Times shall not include time zone information if the time is local in the KSA.
Alternatively, UTC time zone may be used by appending the suffix Z (Zulu time) at the end of the time stamp value.
On the strength of the reference to the rule provided by you in your reply, we used to send time in 24 hour format but the same is not validated by the latest SDK in the dot net dlls. due to this we are facing issue.
also unless I suffix ‘Z’ in the time format, my XMLs are not accepted by the portal
When can these be resolved?