What it means
A credit note reduces or reverses amounts from a preceding invoice and usually requires explicit references, reason codes and corrected tax treatment.
Some systems use separate document types while others use specific invoice codes or correction structures.
Implementation method
- 1Link the original invoice using the required reference.
- 2Describe the correction reason and affected lines or totals.
- 3Apply the target credit-note schema/profile and tax rules.
- 4Preserve both original and correction authority outcomes.
Common mistakes
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Questions and answers
Can I change an accepted invoice directly?
Usually no. Use the correction, cancellation or credit-note mechanism prescribed by the system.
Should credit-note numbers use the invoice sequence?
Country rules differ; keep document-type sequences configurable and auditable.
Can EInvoiceLab officially certify electronic credit notes?
No. EInvoiceLab can inspect, prepare and explain technical data, but official conformance, delivery or acceptance depends on the active authority, network, accredited provider and validation artefacts.
Should I keep the original structured file?
Yes. Preserve the original XML or JSON, its hash, every validation report and the final authority or network response. A readable PDF should not replace the source document.