The development of this version has cost 3,800 euros. The accumulated cost for this year is 6,300 euros. The accumulated cost since the first version is approximately 18,300 euros, but the cost for you is only the license.
New branch 6.1.x of the plugin Autónomos Premium for WooCommerce. It is the largest version in recent years: corrective invoices in FacturaScripts for each return, IRPF in the express payment of Redsys (Apple Pay and Google Pay), automatic retries of synchronization, and a complete security review.
Branch versions
6.1.0
Before updating:
- Check that the IRPF percentage is saved in WooCommerce → Settings → Taxes → Autónomos. If you have never saved it, from this version the IRPF is 0% until you do.
- For corrective invoices, the series
R(or the one you configure) must exist in FacturaScripts. - If your server uses Nginx, add the rule that blocks the invoice folder described in the documentation. In Apache, it is automatically protected.
- If you use the block checkout, check the setting "Activate NIF field": now the NIF field only appears if it is activated.
New:
- Corrective invoices in FacturaScripts for each return of WooCommerce: total, by lines or only by amount. Each line retains the IRPF it had in the invoice, so a mixed order remains mixed.
- My account shows the invoice and all corrective invoices for each order, and the refund emails include their corrective invoice.
- IRPF per product in the express payment of Redsys (Apple Pay and Google Pay on the product page, classic checkout, and block checkout): the Redsys modal asks for the type of customer when the cart has products with IRPF, and a wallet that cannot ask it is not offered for those carts.
- Each line of the order retains its IRPF percentage when placing the order. The order, invoices, and corrective invoices use that value even if you later change the product mode or the IRPF of a product. Orders from previous versions are still calculated as before.
- Automatic retries of failed synchronizations with FacturaScripts (at 5 minutes, 30 minutes, 2 hours, and 12 hours), with a note in the order on each attempt. An invoice or corrective invoice is never created twice.
Changed:
- The IRPF percentage is 0% until you save it in the settings. Previously, different parts of the plugin assumed 1% or 15%.
- The NIF field of the block checkout follows the setting "Activate NIF field", just like the classic checkout: it only appears if it is activated and is only mandatory if the synchronization with FacturaScripts is active.
- The saved customer type of a registered customer applies when the order does not have one, and the block checkout shows it pre-selected.
- A line refund in an order with IRPF returns what the customer paid for those lines (base + VAT – IRPF). Integrations that refund by lines via the REST API must send that amount.
- A FacturaScripts customer is only reused if the NIF and email match, and is never overwritten with the order data. A WordPress account is only linked to that customer if the billing email is that of the account itself. If a customer changes their name, company, or phone number, it must be updated manually in FacturaScripts.
- Guests receive their invoice by email; the download of invoices is reserved for the customer with an active session or a store manager. The download links that were shown before updating need to reload My account.
- Activating the license requires the capability
manage_optionsand a valid TLS certificate chain on the store server.
Fixed:
- The IRPF in renewal orders after a free trial period.
- The invoice PDF is attached to renewal and subscription change emails. Renewals are invoiced upon completion, just like a first order, both with WooCommerce Subscriptions and Advanced Subscriptions.
- Invoices from FacturaScripts carry the IRPF per line in a single step, pairing lines by position and not by SKU. The plugin detects if your FacturaScripts installation supports IRPF per line instead of assuming it, and never issues an invoice whose IRPF per line could not be confirmed.
- Company orders from the block checkout were invoiced in FacturaScripts without IRPF; the shipping line carried IRPF even if no product did; and company orders from outside Spain were invoiced with an IRPF that had never been withheld.
- Changing the customer type of a pending order recalculates its total and its IRPF. Orders from outside Spain no longer show or discount IRPF on the order screen, the invoice PDF, the renewal email, or refunds.
- The block checkout no longer shows an estimated IRPF (a fixed percentage of the cart) when the server does not respond.
- The NIF of the block checkout is saved in the order just like that of the classic checkout, so it reaches the invoices and customers of FacturaScripts.
- The security check for refunds with IRPF no longer counts the refund being created itself, which could reject a valid refund.
- Customer requests to FacturaScripts have a limit of 30 seconds instead of blocking the order, and guest orders never write data to a user account.
Security:
- The PDF invoices are stored privately with impossible-to-guess names (existing ones are migrated automatically) and the download checks that the requester is the owner of the order.
- The REST route of the customer type of the order only accepts the draft or pending order from the checkout itself, never an order created by the store, such as those created from the admin or renewals.
- FacturaScripts logs no longer contain personal data.
- The license and update channel verifies TLS and only offers packages of this plugin.



