App V2 | Send visit confirmation e-mail as a task FEATURE: In addition to automated dispatch, it is now also possible to send visit confirmations and certificates via scheduled tasks. With scheduled dispatch, the system behaves in the same way as with automatic dispatch - however, the time of delivery can be set individually for each offer.
E-mail task: The visit confirmation can now also be sent automatically at a later date
App V1 & V2 | ZUGFeRDsettings FEATURE: ZUGFeRD has been added as a setting to the payment system "Invoice for offline payment". By activating this option, an XML file is also created for each invoice and cancellation invoice and saved in the corresponding invoice.pdf or cancellation invoice.pdf. This file can be read by accounting programs such as DATEV. Automate this process with Zapier to automatically import the invoices into your accounting system.(e.g. DATEV Zap Template)
In order to be able to use the ZUGFeRD e-invoice, the following requirements must be met:
The correct recording of the VAT number and VAT rate
The correct allocation of the VAT rate to the respective offer
The correct recording of participant data: Name, street, zip code and town must be
The invoice must not contain any positive manual transactions
After setting up ZUGFeRD, please check one or more invoices via the official service of portal3.gefeg.com
Technical details:
The Basic v2.1.1 standard is used to create the XML file (exact designation: EN 16931 - FacturX 1.0.05 - ZUGFeRD 2.1.1 - BASIC). The invoice type must be specified in accordance with UNTDID 1001, edoobox uses these two codes:
380 for the invoice (Commercial invoice)
384 for Corrected invoice
edoobox PDF invoice
The XML file is attached to the PDF file using the PDF/A-3 method and supplemented with the ZUGFeRD version XMP RDF in the metadata. Compliance Level: PDF/A-1b
ZUGFeRD: Activate e-invoice in V1
ZUGFeRD: Activate e-invoice in V2
APP V1 & V2 | QR codesettings FEATURE: The QR code has been added as a setting to the payment system "Invoice for offline payment".
Zapier UPDATE: A single webhook is executed for each individual appointment that is created. This mainly affects the creation of duplicates, as previously only one webhook was ever executed.
