Odootec Supports the Second Phase of the Electronic Invoice
OdooTec currently supports the linkage and integration phase, which is the second phase of the electronic invoice. This phase will enter into force starting from January 1, 2023, when the Saudi Zakat, Tax and Customs Authority will define the stages to connect electronic invoicing systems and notify the targets in each step. At this phase, the customer's invoicing system will be linked to the (Fateora) platform so that the customer's invoices are sent periodically to the platform for the Authority to verify the validity of the data and its compliance with the specifications and conditions.
Odootec, which is classified as one of Odoo's best partners in the Middle East and North Africa, is one of the first companies that hastened the development of the electronic invoice system to comply with the requirements of the second phase of the authority. The system supports linking supplier invoices to the platform with its two types, according to the nature of the billing as follows:
- The invoice of type B2B, which is the invoice issued to a commercial entity with tax registration. In that case, the supplier issues an electronic cryptographic stamp on the invoice, which is its stamp received from the authority. Then the invoice (or notice of discount or addition) is sent to the authority in XML format for the authority to verify that the invoice conforms to the authority’s requirements and then issues an electronic stamp on the invoice (Digital Stamp), which is known as the instantaneous clearance process. The invoice is returned to the supplier, who can then send it to the customer. In this invoicing type, The seller must send the invoice to the authority upon issuing, as it cannot be sent to the customer before that.
The B2C type. This type is usually used in point of sale. The supplier also issues an electronic cryptographic stamp on the invoice. This stamp appears on the invoice like a QR code to deliver the invoice to the customer. Then the invoice is sent to the authority in XML format to verify the invoice's validity, which is known as the reporting process. In this case, the invoice is not required to be sent immediately to the authority, but any number of invoices can be sent all at once, provided that 24 hours have not passed since its issuance. After that, the authority verifies the invoice's validity and notifies the seller of the acceptance or rejection of any of the sent invoices with an indication of the reason for the rejection.
The System Considers the Following Points:
- Ease and simplicity of the procedures related to sending the invoice electronically, whether it is of B2B or B2C type.
- Before sending the invoice, the system verifies that it conforms to the specifications set by the authority. The invoice will not be sent unless it includes all the information required for the electronic invoice, such as the universally unified identification number for the invoice in the form (UUID), the name of the facility and the customer and the number of the invoice, tax registration, cryptographic stamp, and more.
- Once the invoice is issued, the system checks the supplier's Digital Certification key to verify the seller's identity registered with the authority and then ensures that the invoice values or content are not tampered with.
- The invoice can be issued to the authority in (XML) or (PDF / A3) format.
- The system encrypts the invoice upon issuing to maintain the highest levels of security of the invoice data and ensure that its content is not tampered with by any party.
- The system also supports sending debit and credit notes related to any bill modification, whether B2B or B2C billing.
- The system supports showing instant notifications about the status of the invoice, whether it has not yet been sent, sent to the platform or rejected, and a statement of the dismissing reasons. In the event that the invoice is rejected, the user will modify it based on the reasons for the rejection to be accepted by the platform when it is sent again.
- The system supports the three highest levels of security related to billing and dispatching as follows:
- Application Security supports giving special permissions to each user of the system so that the user cannot edit the invoice, modify or delete it except according to the authorities granted to him on the system.
- Database Security: Odoo systems never allow modification of the issued invoices by dealing directly with the database, as in local programs.
- Compliance with the cyber security investigation recommended by the Saudi Authority for Cyber Security. Odoo systems work with the cloud computing methodology, where the database is hosted on one of the servers, as it is known in Odoo systems. This methodology is characterized by the databases' highest degree of cyber security. Odoo also provides local hosting in the customer's data center if desired.
The POS System by Odootec Complies With the Terms of the Saudi Authority
OdooTec supports a cloud POS system that allows the issuance of an unlimited number of electronic invoices under the authority's requirements in its first and second phases. The POS (Cashier) system supports the mechanism of linking with any of the external systems via an application programming interface (API). The invoice platform is linked to sending the authority's electronic invoices through this interface. Through this interface, you can also link your OdooTec POS to the accounting system to synchronize the invoices issued by the POS (Cashier) system to your billing system.