Note issued with no reason

What does this mean?

The rule applies to notes only — documents whose type (BT-3) is credit 381 or debit 383. Ordinary invoices are not asked for a reason.

The reason is a data field (KSA-10) inside the note file, not a free-text remark on the printed page.

This rule is not the original-invoice reference rule: a note needs both — the number of the invoice it corrects, and the text of the reason for correcting it.

Why does it happen?

Ordered from the most common to the least — your cause is most likely the first or the second.

• A store integration that turns returns into notes without passing the return reason through from the platform.
• An issuing screen that makes the reason field optional, or drops it from the request when it is left empty.
• A note template built by copying the invoice template, where the reason field does not exist in the first place.

How to fix it

2 steps, then send the invoice again.

1. 1
   Write the actual reason in one short sentence

   Clear text is enough: goods returned, price correction, or a discount agreed after issuing. What matters is that it describes what really happened — it is part of a tax document that will be referred back to.

2. 2
   Make the field mandatory in your system

   If notes are issued from an integration or a form, make the reason a field that cannot be skipped, and pass it from the source of the transaction (the return reason in the store, for example) instead of leaving it to memory.

Once corrected, send the invoice again. A rejected invoice was never recorded with the Authority, so it needs no credit note — send the corrected invoice itself.

Frequently asked questions