When processing checks for recurring gifts in the Nonprofit Cloud, the system attempts to find an "expected" payment record to match against the physical check. In the NPC data model, recurring gifts are managed via Gift Commitments and Gift Commitment Schedules.
The system creates "expected" transactions (installments) based on the schedule. However, donors often send checks that arrive slightly before or after the exact scheduled date. If a check arrives outside of the system's "window of expectation," the Gift Entry interface will not automatically suggest the matching commitment, leading to the "no matching records appear" issue.
The Solution: Installment Extension Day Count
Function: This setting defines the number of days beyond the scheduled date that the system will look to find a matching installment. For example, if a gift is scheduled for the 1st of the month but the check arrives on the 10th, and the extension is set to 5 days, the system won't see it.
Configuration: The consultant must go to Fundraising Settings in the Setup menu.
Adjusting the Value: By increasing the Installment Extension Day Count (e.g., to 14 or 30 days), the consultant widens the "search window."
Result: The next time the manager enters a check for that donor, the Gift Entry tool will successfully find and display the active Gift Commitment as a suggested match because the check's date now falls within the extended installment window.
Option C is incorrect because "Donor Matching" helps find the person, but the question specifies that the issue is matching the check to a specific Gift Commitment (the recurring gift record). Option B (RFM scoring) is for analytics and has no impact on the technical matching logic of the gift entry engine.
