RCPT015 Credit Note Does Not Identify Its Invoice

A credit or debit note does not identify the invoice it reverses, or that invoice was never fiscalised on this device.

This code comes from ZIMRA. FDMS validated the receipt and refused it.

Why It Happens

A credit note is not a negative sale; it is a reversal of a specific receipt, and FDMS will only accept it if it can find that receipt on the same device. The link travels as the original's receipt global number and fiscal day number. Both sides of that check fail the same way: a credit note with no link, and a credit note pointing at an invoice this device never filed.

What FDMS Is Checking

creditDebitNote carries receiptGlobalNo, fiscalDayNo and receiptID, and they resolve to a receipt on this device.

What ThatFiscal Does About It

Raising the credit note from the original invoice — Open the invoice → Issue Credit Note — fills the link for you and it cannot be wrong. The connectors do the same from Odoo's reversed_entry_id and QuickBooks' LinkedTxn.

How to Fix It

1. Make sure the ORIGINAL invoice is fiscalised first. If it is sitting in error, fix and resend that one before the credit note.
2. Raise the credit note from the original rather than as a new standalone document.
3. Over the API, send credited_invoice with the original's receiptGlobalNo and fiscalDayNo.

Often seen with: RCPT034.