In Nonprofit Success Pack (NPSP), an Opportunity represents a donor’s commitment to give, while a Payment represents the actual receipt of funds. Opportunities and Payments are tightly linked as two parts of the same donation lifecycle.
For standard one-time donations, NPSP automatically creates a single Payment record associated with the Opportunity if "Automatic Payment Creation" setting is checked in NPSP Settings and Do_Not_Automatically_Create_Payment__c on Opportunity record is set to FALSE.
Users may notice the following behaviors using GIFT ENTRY:
These behaviors are standard NPSP functionality intended to maintain data consistency between Opportunities and Payments.
When a user selects Update Payment in Gift Entry, NPSP interprets the action as confirmation that the donation payment has been received. As part of the gift processing workflow:
If users need to modify Payment details of Opportunity that has exactly ONE UNPAID PAYMENT without marking the Payment as Paid, they should:
Avoid using Gift Entry for administrative-only updates to unpaid Payments
When an Opportunity has exactly one unpaid Payment, NPSP disables the Update Opportunity option in Gift Entry because allowing direct Opportunity updates could cause the Opportunity and Payment records to become inconsistent.
This behavior prevents Opportunities and Payments from becoming unsynchronized. For example, updating the Opportunity independently could leave the associated Payment in an unpaid state.
If updates are required for an Opportunity with a single unpaid Payment, users should edit the Opportunity record directly outside of Gift Entry.
https://help.salesforce.com/s/articleView?id=sfdo.npsp_enter_gifts_in_ge.htm&type=5
005321984

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.