Credit note return codes

Credit Note Return Codes are returned during credit note creation, validation, approval, cancellation, and retrieval operations.

These codes typically occur when a credit note references an invalid invoice, violates EFRIS business rules, or conflicts with an existing credit note or debit note.

Kumusoft Validation Layer
The Kumusoft EFRIS API performs extensive validation before submitting credit note requests to EFRIS. As a result, many validation errors documented in this section may never be encountered during normal API usage.
This reference is provided primarily for troubleshooting, diagnostics, support investigations, and understanding responses returned directly by the underlying EFRIS platform.
Whenever possible, validation errors are detected and reported by the Kumusoft platform before the request is submitted to EFRIS.

Credit Note Codes Summary

Code Range	Description
300 - 319	Credit Note and Debit Note processing errors

Code	Description	Explanation
300	The original invoice number does not exist	The invoice referenced by the credit note could not be found.
301	The original invoice number has not been completed	The referenced invoice has not yet completed processing.
303	Update failed	EFRIS was unable to update the credit note record.
304	According to the original invoice number, the result is null	No invoice matching the supplied invoice number was found.
305	Invoice approval failed	EFRIS was unable to approve the credit note request.
306	A credit note has already been issued against this invoice. Please cancel the existing credit note to proceed	A credit note already exists for the referenced invoice.
307	Get process template is empty	Required EFRIS workflow configuration could not be found.
308	Approval failed	The approval process failed.
309	Items cannot be empty	At least one item is required in the credit note.
310	The data cannot be voided	The transaction cannot be voided.
311	BusinessKey does not exist	The referenced business key could not be found.
312	Cannot apply for credit note/debit note, the fiscal document has exceeded the allowable application days	The correction period for the invoice has expired.
313	The application has been voided	The application has already been voided.
314	The application cannot be voided for initiated sub process, please contact URA	Processing has already started and the request cannot be cancelled.
315	Successfully Operated	Operation completed successfully.
316	Seller does not have taxpayer account	The seller is not registered as a taxpayer.
317	A debit note has already been issued against this invoice. Please cancel the existing debit note to proceed	A debit note already exists for the referenced invoice.
318	The debit note has a cancellation request in process, please don't apply repeatedly	Debit note cancellation is already in progress.
319	The credit note has been cancelled, please don't apply repeatedly	The credit note has already been cancelled.

Commonly Encountered Codes

The following codes are the most frequently encountered during credit note processing.

Code 300 - Original Invoice Number Does Not Exist

Cause

The referenced invoice could not be found in EFRIS.

Resolution

Verify the invoice number.

Confirm that the invoice was successfully submitted.

Retrieve the invoice before creating the credit note.

Code 301 - Original Invoice Not Completed

Cause

The invoice is still being processed by EFRIS.

Resolution

Wait for invoice processing to complete.

Retry the credit note request later.

Code 306 - Credit Note Already Exists

Cause

A credit note has already been issued for the invoice.

Resolution

Retrieve existing credit notes before creating a new one.

Cancel the existing credit note if appropriate.

Code 312 - Application Period Expired

Cause

The invoice exceeds the maximum correction period permitted by EFRIS.

Resolution

Verify the invoice issue date.

Confirm that the correction period has not expired.

Code 317 - Debit Note Already Exists

Cause

A debit note already exists against the referenced invoice.

Resolution

Review existing debit notes before creating a credit note.

Resolve any outstanding debit note processes.

Best Practices

Always verify that the original invoice exists before creating a credit note.

Ensure the original invoice has completed processing.

Check for existing credit notes before creating a new one.

Create credit notes as soon as a correction is identified to avoid exceeding the allowable correction period.

Retain the original invoice number for audit and reconciliation purposes.

Credit Notes

Invoice Return Codes

Taxpayer Return Codes

General System Return Codes

Return Codes Overview

Note: Credit note validation rules are enforced by EFRIS. The Kumusoft EFRIS API performs additional validation to reduce common submission errors, but EFRIS remains the final authority for credit note processing and approval.

Credit note return codes

Credit Note Codes Summary#