Documents
Map corrections in an audit-ready way.
Credit notes linked to invoices; optionally with e-invoicing and category codes for the XML.
These are the points this feature covers day to day.
The workflow in Jupiter ERP, on this page.
Background, typical workflows, and concrete panel capabilities, more detail than the summary above.
Credit notes reference the source invoice: amounts, line items, and taxes are reversed correctly. Optionally you also generate credit notes as e-invoices with embedded ZUGFeRD XML.
Instead of deleting or manually patching invoices, you document corrections as their own document type: important for GoBD-compliant archiving and later audits.
Directly from the invoice you create a credit note via Process document: line items and customer data are already in place. That reduces effort for cancellations and partial credits.
Corrections are their own document, linked to the original invoice. You do not delete the invoice, and tax is included in the XML when you turn e-invoicing on.
A sent or locked invoice should stay as it was. The credit note shows what was reversed, with amount, tax, and date.
That is the trail internal review and the tax adviser follow later, without touching the original file.
The main building blocks at a glance, complemented by the longer description above.
Credit notes with embedded ZUGFeRD XML like invoices.
Start for free: write invoices on the Free plan. Choose plan, term, and add-ons in the app afterwards. Custom adaptations or API integration? Get in touch.
