In Malaysia the e-Invoice is going to be implemented in phases from next year (2024) The guidelines are published here: https://www.hasil.gov.my/en/e-invoice/ I’ve gone through the almost similar topics here: [image] E-Invoice System for India Indian govt has approved and are introducing E-Invoice for businesses implement 100% by end of this financial year. Now its compulsory for companies TO above 10Cr.same which would help with smoother implementation within Manager. the official link Goods & Services Tax (GST) | News and Updates provides all the basic details necessary to understand the E-Invoice concept, the schema and the template. [image] Saudi Arabia new law e-Invoice require API integration Please confirm If the Manager have API for integration and it comply with any cybersecurity requirement compliance. It will be minditory from 4th december 2021 in saudi arabia to generate digital invoices and the software must comply with the following requirements. Ability to connect to the Internet. 2)A tamperproof solution, which allows the detection of any tampering performed (anti-tampering). Ability to integrate with external solutions using Application Programming Interface (API)… [image] E-Invoice for Taxes in Egypt Hello Due to some new laws in Egypt, the tax authorities here made ERP system or any alternative is a must to connect with the tax website to release any sale invoice…is it available on Manager ? [image] Saudi Arabia After reading the guidelines you provided, I do not think Manager is required to generate QR codes. The rules seem similar to our country. The invoice details are sent to your govt portal where an e-invoice is generated with a unique hash. This hash is included in the QR code generated by the portal and this is what you need to print on the invoice. So Manager needs to facilitate sending the required invoice details to such portal and download the generated QR code which should then be display… [image] Saudi Arabia GAZT E-Invoicing requirement @lubos, have you seen this before? ZATCA Saudi Arabia E-Invoice Guidelines for system developers. I hope you success and make Manager match all these requirements ASAP. [image] Electronic Invoicing the same is applicable to India. still awaiting a response from @lubos @Dimitris_Kontodimos it would help with the development if you provide any official links where the requirements are explained clearly. [image] New Greek IRS digital "e-books" and myDATA from 01/01/2021 Dear @lubos, first of all thanks for your availability. I try first of all to make a small introduction to “Fattura Elettronica” which is the Italian implementation of the European e-invoice. As always in Europe what we have is a Directive, ie a guideline, which sets the minimum requirements and every country is free to implement the directive in its own way respecting those requirements. As said it was introduced in Italy as the first country of Europe on 1/1/2019, ie we have been the tester … But could not find any solid conclusion/implementation about it (I might have missed if any). Cloud anyone please let me know, how business in Malaysia who are using Manager.io can adopt this e-invoicing matter.

See [image] SAF-T future Request ideas There are multiple countries coming up with similar requirements. Over the past few months I was experimenting with various approaches. At this point I’m set on the solution but it will take a few months to get there. Mostly because this will require outside programming help in those countries and first I need to get things prepared at my end. So this is absolutely on my mind because it’s deal-breaker feature. [image] Invoice Label Changes @Stewart this is similar to what other countries around the world are doing. I don’t have a solution yet but new API that I will soon make available will get us closer to the solution. and [image] Added new API endpoint and "Access Tokens" screen The latest version (23.12.2) is adding Access Tokens under Settings tab. [image] Access Tokens are per-business tokens which can be used to access any data in Manager using new API. New API is based on Open API spec so should be easier to use it. Open API spec is at ~/api2 endpoint and for testing/exploring purposes the JSON can be pasted into a tool such as https://editor-next.swagger.io/ Besides adopting Open API standard, new API works across all editions (including free desktop edition). …

Creating a custom program from an API cannot be considered a solution.

A country specific localisation is custom programming already. Encapsulating specific interface code in a separate program with a clear interface to Manager is a method of separating the code bases. @Davide why do you believe a separate program interfacing between Manager and a country’s tax authority is not a solution to EDI requirements.

This is all a bit deep. All that is needed is the ability to easily customise invoices and credit notes to suit fiscal signature devices. The signature devices handle the communication with the tax authorities I have had to introduce post processing in a graphics application to swap out the column heads and other labels. There is no problem with the actual data. For me this a is a form design problem only A fiscal device looks for information either in a specific position (needs fixed form length) or the first number after x. X being “total including VAT” or “Excluding VAT” and so on. Following from this a document with the word “invoice” or total" appearing in 2 different places is an issue.

[image] Stewart: All that is needed is the ability to easily customise invoices and credit notes to suit fiscal signature devices. This is incorrect and not simple at all. Many authorities require electronic submission to their server system which then adds their authorization to the e-invoice that then can be issued to the customer or supplier. The challenge is that this internet-based connection between the business Manager application and the Authorities e-invoice approval application needs internet interfaces as required by the authorities in their formats. The actual format of such invoices is the easy part, the inter-facing between systems is the messy and difficult part as discussed here.

@eko It may be different in different jurisdictions. I have looked into online fiscal signature devices which add some kind of authentication. In our case it will place a QR code upon the invoice. It all works off a virtual printer which makes a pdf that is then put through the authentication device which reads off the relevant information of interest to the tax authorities. The thing is live and the tax authority gets realtime information. If your invoice passes muster a code of some sort is applied. In our case a qr code. This is the way it is done in many places. There does not need to be a direct data link t from your accounts application to the Tax authority server. The fiscal signature device does this. This way the system is accounts application independent.

The guide in Malaysia says: [EI1] [EI2] [EI3] Further and clear explanation of Malaysian e-Invoicing can be found here: https://www.hasil.gov.my/en/e-invoice/

[image] Stewart: This way the system is accounts application independent. I did not disagree with that. However, for those that want to interface with the Invoicing of Manager some interface must exist, even if through intermediaries and thus seems suitable for programming interfaces such as API. I only mentioned that it is not simply changing the invoices format but changing how interactions between different applications including Manager and those of authorities (also through intermediaries) in different countries can be facilitated, and that is pretty complex.

I am literally doing as I have stated above and it works. The core problem for me is the lack of flexibility on the layout

[image] Stewart: This is all a bit deep. All that is needed is the ability to easily customise invoices and credit notes to suit fiscal signature devices. The signature devices handle the communication with the tax authorities Manager has features added to support a broad market requirement. The solution to e-invoices must address most countries requirements. Doing so requires a general interface to Manager. Further features are added in a cumulative manner. By which I mean base features are added first then features which use the prior feature additions. An API has many uses so is more capable again than strictly required for e-invoices. In summary, yes software feature addition is more complicated than initially appears and a lot more complicated than addressing one user’s request.

E-invoicing in Malaysia

Uncategorized

Patch December 9, 2023, 3:25am 2

See

and

Topic		Replies	Views
Electronic Invoicing Uncategorized	31	4012	November 18, 2020
Electronic invoicing system in Egypt Uncategorized	68	2261	May 14, 2026
Saudi Arabia GAZT E-Invoicing requirement Uncategorized	18	2546	January 2, 2023
UAE - E-invoicing Uncategorized	19	1194	October 13, 2026
Real-time invoice verification by tax authority Uncategorized	41	2939	August 2, 2022

E-invoicing in Malaysia

Related topics