Automate the issuance of electronic service invoices directly in your WHMCS through the Invoice Module for WHMCS via NFE.io. With this module, you can automate the routine of generating and sending NFSe to your customers when they pay an invoice for a recurring order or service, issue invoices from individual invoices or every time a payment is received in WHMCS, for example.
Be the first to review NFE.
The best place to start if you need help with a specific product is to contact the developer. All WHMCS Marketplace developers have both a website and support URL listed.
A new Validations
helper class has been included in the NFEioServiceInvoices
module. This class contains methods to validate CPFs and CNPJs based on the validation algorithm, according to verification rules, instead of defining document validity by character size, ensuring the integrity of the processed data.
Now when the document number is not valid, whether it is a CPF or CNPJ, the invoice issuance process will be terminated and a message with the reason will be shown to the user, in addition to a detailed record in the module log when in debug mode.
A new webhook validation method has been added to the validation class and a new webhook handling in the callback file. It is now possible to verify the webhook signature (HMAC) and make sure it is from a trusted source before processing it.
The return of errors and response codes for API calls to the callback has also been improved. This allows the API to make new attempts to send in cases where processing is not possible on the first call, preventing updates to information in the module from being affected by any momentary inability of the module to listen to the returns.
A new option has been added to the administrator interface that allows the update of the note status manually. With this, it is possible to search for the information directly in the API to reflect this information in WHMCS.
This feature is useful in cases where the note status information has not been synchronized with the module.
Refactored the handling of the note status when cancellation is performed to comply with the current return structure of the cancellation API. Previously, when canceling a note via API, the return object had a "message" attribute that the process of updating canceled notes was based on. Now, the cancellation API is returning the nf in the object and status code 202. Due to this, canceled notes were not being recorded properly.
The flowStatus value of webhook returns has been recorded, ensuring that in failure or problem scenarios, the information in this attribute is recorded correctly for troubleshooting. This will make it possible to analyze return messages more efficiently and also use their values for processing in the return message routines implemented in these updates.
Identifiers have also been standardized and new log records have been added to allow better debugging, both of the webhook return and of internal module routines.
NOTE: The ApiNoResponse message is an internal message used to identify when a cancellation action did not return the appropriate status because the invoice was already canceled in the API or its issuance was not completed and the user tries to cancel it in the same way.
Confirmation modals have been added for the cancellation and reissue of invoices.
Now, when performing one of these actions, the user will be asked if they want to continue with the action.
A problem was fixed in the definition of the default value type for the created_at and updated_at fields in the module tables. The information was not being recorded properly due to some manual date definitions of legacy routines and also due to the lack of a definition of default values for these timestamp type columns that could generate an incorrect assignment of values in these fields.
Details of the analysis and correction can be found in issue 156
A condition that could lead to duplicate issuance of invoices when the administrator tries to generate new invoices from the preview of an invoice has been fixed. #160
Integrate your financial data stored in WHMCS into QuickBooks Online.