I’ve seen that a lot of test invoices are (incorrectly) using the corrective KSeF number in the XML for the corrected invoice KSeF number. This is likely an artifact of test data but since this pattern shows up more frequently than the proper one (where the KSeF number of the corrected invoice is put into the XML instead), I worry it is a common problem in production usage.
Therefore the module now checks and notifies for such XML errors when importing.
It also will request you to import the original invoice before importing the corrective invoice, so that the invoice linking in Dolibarr works properly.
v1.3.2 Released fixing cron job classnames, some calculation errors for missing fields, adding ability to have custom field mappings, and automatic translation application for these custom fields as well as more.
And a thank you to everyone who had found and reported issues so far, it helps quite a lot.
v1.3.3 released, addressing some last-minute issues - barring a critical issue this is last release before the KSeF system becomes mandatory for small/medium businesses.
I missed announcing v1.3.4 as it was a quick fix for some PDF issues, but v1.3.5 is released. Now queries the KSeF lighthouse for status/maintenance issues, including a new cron job, reworked the KSeF dashboard a bit, and a resolve a few issues that have come up.
Additionally, although there is complete in-module documentation in the “How To Use” tab, we also have finally finished a more detailed documentation with a bunch of screenshots which is available on our website as well in English and Polish. If you run into issues or think something is missing, please let us know and we’ll add it! I have added information about how to ensure the Bank Account information is added to invoices in the How to Use in the module, but this is yet missing from the website and will add it later today.
left u a 5 star review on google, least i could do
