-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Implement e-invoicing for UBL formats (EN 16931, Factur-X, PEPPOL, etc...) other than Zugferd. #939
Comments
Hi, I find it a cool feature. It might be a bit of a big change for v1 which should not be getting any new big feature since v2 is coming to life. In my opinion this is for sure a good feature for v2. |
Will put it on the list for v2 |
@nielsdrost7, @naui95 thanks for adding this feature to the IP V2 list. I have been using this feature for several years now and would like to make it publicly available. |
The alternative is:
Conclusion: all solutions that you have would need a pull-request to "pull" it into the development branch |
I am using the invoiceplane database schema at https://www.github.com/rossaddison/yii3-i as a basis. This opensource software can generate openPeppol Ubl Invoices. It uses sabre.io to write the xml. I have developed a PeppolHelper which you might find useful and get a few ideas from. |
- Added fields in tables ip_users and ip_clients. - Removed zugferd selection in invoices - setting. - Added e-Invoice format selection choice for client - bank info input fields for user added and grouped - placed xml configuration files in the folder helpers/XMLconfig - placed xml-template files (Zugferd + UBL example) in the folder libraries/XMLtemplates - created the readme file "About e-Invoicing templates" = How to add/setup XML-template files
…different-(UBL-CII-++)-formats-InvoicePlane#939
…different-(UBL-CII-++)-formats-InvoicePlane#939
In France, businesses will be forced to use a platform that is a certified partner of the tax authorities. |
Maybe we can apply to become such a partner? |
I don't know, seems an administrative puzzle with guarantees of confidentiality and solid exchanges with the tax authorities. |
@ogmkp & @nielsdrost7, Companies will have to fulfill their VAT obligations by sending their (electronic) invoices to the VAT authorities, possibly with the help of "a certified partner". |
…different-(UBL-CII-++)-formats-InvoicePlane#939
…different-(UBL-CII-++)-formats-InvoicePlane#939
Expected Behavior
Send e-invoices to customers in an electronic (UBL or CII) format that they can use to process their workflows more efficiently and automatically. Clients will be able to pay invoices faster and avoid errors during those payments and booking.
Current Behavior
Only for sending e-invoices to clients in Germany this is useful.
For clients in all other countries who want to use e-invoices (UBL/XML format) do not have this option.
Possible Solution
Implement e-invoicing so that users can send e-invoices to clients in countries other than Germany (Zugferd = PDF with embedded XML).
Also implement e-invoicing for other UBL/XML formats (Factur-X, PEPPOL, EN 16931 or derivatives = XML with optionally embedded PDF) than Zugferd.
Context (Environment)
Governments in several European (and other) countries are currently requiring their suppliers to only send electronic invoices (B2G).
Some countries (including Italy) are currently also imposing e-invoices on companies themselves (B2B).
In 2024, this obligation to send (B2B) e-invoices will be imposed in many more (EU and beyond) countries.
Detailed Description
See these webpages about Electronic Invoicing:
Possible Implementation
Via a setting you can choose which UBL/XML or CII (Zugferd/XRechnung/Factur-X) "client country depending template format" the client wants to receive.
Additionally, that client then receives its PDF invoice together with the e-invoice via email.
For Germany this can be the Zugferd format (PDF with embedded XML) and for other clients the UBL/XML format (XML with external and/or embedded PDF) can be delivered depending of the chosen template.
The text was updated successfully, but these errors were encountered: