Summary

As you probably already know, Invoices page of Billing Extension uses our SorTables technology that allows you to add, remove, move, collapse and filter up to 37 columns. This page clearly is way more powerful than the standard one of WHMCS. The problem is that it didn't support massive actions but there's a good news.

With this release Invoices page can be used not only to perform actions like Mark Paid, Mark Cancelled, Mark Unpaid, Send Reminder, Delete but also Snapshot as Invoice, Create Snapshot, Convert to Invoice and Convert to Credit Note. In other words converting multiple proformas into invoices now requires one click!

The second feature we add is very useful if you happen to have a lot of customers from regions and states with special tax regimes like Canary Islands, Liviglio and so on. For them you can finally lock their Tax Exempt status so that it never changes.

Summary

You can now choose your Intermediary platform in one click:

• Fattura Elettronica Sicura 100% automated and fully integrated with WHMCS & BX
• Sistema di Interscambio via FTP Node with digital signature and encryption support
• Manual to import XML files manually on unsupported platforms

We changed color schemes for buttons and icons of electronic invoices. Colors reflects the effective status of XML files like follows:

• Orange to generate XML
• Blue for XML not yet transmitted
• Green for successfull transmissions
• Red for errors and rejections
• White for missing files in FTP node

Moreover the status can be reviewed, filtered and even exported on spreadsheet from Invoice View, Invoices page and also from a new Widget. You can find previews of all these additions in the gallery of this changelog.

Client Custom Fields can now be added as column in Invoices page. Of course this column can be filtered and exported on spreadsheet.

Last but not least we managed to solve long standing issue that was causing troubles to some of our new customers. BX was incorrectly detecting invoices as proformas. For more details about this feature read documentation.

Developer notes

We updated our documentation for Electronic Invoicing. Please, read it in full before opening tickets.

We understand that it's a long article but it provides a lot of useful information and we would like to spend time developing new features instead of answering to the same questions about Electronic Invoicing :)

Thanks for your understanding.

Summary

We continue to improve and add new features based on your feedback in the daily use of Electronic Invoicing.

Developer notes

In the upcoming releases we'll focus on implementing Digital Signature of XML files for transmission to SdI.

Summary

In addition to PHP 7.2+, 7.1+ and 5.6+, it is now possible to download the module as Bundle. For more information read Choosing package for download. As for the rest this release includes some small improvements and changes.

Developer notes

In this release we continue to add new unnecessary nodes to XML files due to Intermediaries. Yes, we're a bit saracstic :)

Our initial goal was to generate XML files as "small" as possible to ease transmissions and save disk space for Conservazione Sostitutiva that usually costs depending on space used. We were focusing on adding only the mandatory nodes and values but Intermediaries seem to love to scare people with unnecessary validations and put emphasis on nodes that are not needed.

We kind of give up. We'll keep adding all nodes they want even though they're completely useless.

Summary

As we anticipated in our Lab, this release focuses on adding support to CUP/CIG codes for electronic invoices towards Public Administration.

The module will automatically add a new column on Invoice View that lets you set those codes when needed. Click on the provided icon (the small toggle inside CUP/CIG column) to open a modal from which it is possible to define both codes and eventually turn on the option to make them recurring on subsequent invoices.

Summary

Some of you found quite strange that the XML files generated by BX always have a Due Amount equal to zero. This is perfectly fine.

First off the node that contains Due Amount is not mandatory. It is used when you still need to collect payments from customers. As you probably already know, in WHMCS XML files are issued only when invoices get paid therefore there's no need to specify a Due Amount.

Some customers in fact could find confusing that you are asking to pay an invoice that has already been paid in WHMCS. Not to mention that when Due Amount is specified some other fields become mandatory.

That said, it is also true the opposite namely that customers see AliquotaIVA, ImponibileImporto, Imposta but not Due Amount and they think that it's an error.

What to do now? Who is right? What is the correct approach? As usual no one knows therefore it's up to us. Considering the feedbacks we received, we go for the second option. From now on Electronic Invoices will have Due Amount even though it wouldn't be necessary.

Summary

The documentation has been updated to provide information about the use of Electronic Invoice among multiple installations of WHMCS and/or stores (e.g. Magento, Prestashop, physical stores...).

Generally speaking in this release we added many new checks, validations and messages that will help you configuring Electronic Invoicing. Moreover sole proprietorship customers can now find new options to properly issue electronic invoices.

Summary

In this release we changed the way Natura and RiferimentoNormativo nodes on XML files are added. Both fields are required when AliquotaIVA is equal to zero.

Before this release, we were forcing Natura and RiferimentoNormativo based on intra/extra EU status and on the fact that WHMCS is used to provide services.

In the end we realised that this was an hypercorrection also because we found out that some of our customers are using WHMCS not to sell services but for things like rentals that follow a different legislation. That said, from now on BX will be more flexible to use.

Summary

We fixed some issues described here in our Lab. If you had problems importing some XML files due to the following reasons:

• Lowercase Provincia and CodiceFiscale
• Credit Balance applied on invoices
• Coupon Codes applied on invoices or items with negative amounts

Simply delete the XML in question from Invoice View and reissue it.

Summary

Invoices with discounts, promotions and coupon codes applied need to be handled in a particular way according to the specifications of Electronic Invoicing.

We noticed that in some occasions such lines could not be detected as discounts therefore we changed a bit the script involved. It's a bit complicated to explain but the short version is that from now on BX will double-check data and will not blindly trust WHMCS to detect discounts.

Summary

Till now we considered Codice Destinatario a mandatory filed for companies because many of you requested us to do so. In reality this field is not strictly necessary.

Yes, an italian company that doesn't even have a PEC address to use as Codice Destinatario sounds pretty strange but let's face it. Even though customers could provide details from an handy page, there's no guarantee that they will care.

People are lazy. Many will simply ignore the newsletter that you are probably already sending about Electronic Invoicing until they realize that they can't get the invoice that they wanted leaving you with tens of tickets to handle.

For this reason and to save you from headache, we are making the following change. From now on Codice Destinatario is an optional field also for companies. For PA it's still required.

That said, don't panic. It will change nothing for you. Revenue Agency in fact allows the sending of XML files with '0000000' in place of Codice Destinatario for companies. It's just that the Agency will not deliver the invoice to the end user on his PEC address or Intermediario. Such clients will need to manually retreive invoices directly from the website of Revenue Agency.

People that still want to use Codice Destinatario as a mandatory field need to contact us. We will provide you a workaround even though you should probably reconsider your decision. There's no need to be so rigorous. The only thing you'll get from this are lot of tickets from customers complaining.

Developer notes

We know that for some of you it could be frustrating to see so many updates in such a short time. Right now we're focusing on delivering you the best possible solution so that you can start the new year without fighting so much against Electronic Invoicing. We promise you that we will slow down as soon as we can.

Summary

This release was scheduled for yesterday late in the afternoon but we've gone a little bit further to fix and improve as much as possible till late night.