We at Grynn have developed a Swiss E-Invoicing App.
The Swiss E-Invoicing standard is based on the French / German ZugFerd Standard, which proposes a HYBRID invoicing which is both human readable and machine readable. What that means an invoice generated in this manner is a PDF file, with an attached XML file.
So this means, no OCR / no guess work / No "machine learning etc is required to take an PDF invoice and feed it to a computer which can unpack this PDF and read the XML file and take the necessary steps to create a purchase invoice on the supplier’s side.
A Factur-x e-invoice will be generated when you submit a Sales Invoice & attached to your Sales Invoice. Everything is automated. Would be great to get a feedback.
No data transfer to another server, no microservices
Our app seems to have a valid A/3 and validates using XSD. But the platform is showing some issues. We know the 3-4 issues we have found to make this platform validator happy but haven’t had the time to fix it. Maybe we will look at it in 2-3 weeks. Best
We have released v1.0.1. We have validated the PDF A-3 validity + the ZUGFeRD Community portal for XML validation. So now it should be compliant with French / German / Swiss / EN16931 standards of e-invoicing.
There are a few limitations are there :
Don’t add charges to the “sales taxes and charges” template. If you add it, ERPNext will still function, however XML will not be valid as the e-invoicing XML does not provide adding charges mixed into the taxes table.
Don’t add header level discounts. We have not covered it in our APP. If needed, kindly contact us. Again it wont break ERPNext. However the XML will not be valid.
If you find any issues, kindly open a GitHub issue.