This article explains why Salesforce Billing blocks unallocation of a credit note that was generated by Cancel and Rebill, and how to correct invoice balances when the auto-generated credit note was wrong, duplicated, or needs to be redirected to a different invoice. The exact error returned on the Credit Note Allocation Unallocate action is: "Credit Note Allocation for a credit note which was generated as a result of cancelling and re-billing an invoice cannot be cancelled". A related error appears when you try to clear or change a posted credit note line: "Updating LegalEntityReference on posted credit note line is not allowed". Customers describe this as: "The user is unable to unallocate the credit note because the invoice it is attached to has been cancelled and rebilled" and "The Credit Memo has a Posted Status so there is nothing to recover". Trigger conditions: the source invoice was in Posted status, a user clicked Cancel and Rebill on the invoice [blng__Invoice__c], and Salesforce Billing automatically created a posted Credit Note [blng__CreditNote__c] allocated in full to each invoice line to zero out the invoice balance. Any later attempt to click Unallocate on that Credit Note Allocation [blng__CreditNoteAllocation__c] is blocked. Affected scope: all Salesforce Billing editions, Salesforce Billing managed package 7.0 and later, any user profile with edit access to the Credit Note record. Salesforce Billing follows Generally Accepted Accounting Principles, which is why credit notes, debit notes, payments, and refunds cannot be deleted or unallocated once posted by the Cancel and Rebill process.
Use the steps below based on what you are trying to accomplish. Do not attempt to delete the credit note, edit the posted credit note line, or change LegalEntityReference [blng__LegalEntityReference__c] on a posted credit note line — those actions are blocked by design.
005385187

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.