Required Exclusions

Last updated: May 14, 2026

The following three TDTM trigger handlers should have the WeGive Integration user added to the Usernames to Exclude field. This should be configured for every NPSP org running the WeGive integration.

#	Trigger Handler Class	Object	Why Exclude
1	`ALLO_Allocations_TDTM`	`Allocation__c`	Prevents NPSP from auto-managing GAU Allocations on records pushed by WeGive. WeGive handles allocation data directly.
2	`PMT_Payment_TDTM`	`npe01__OppPayment__c`	Prevents NPSP from running payment validation on Payment records inserted by WeGive. WeGive sends fully-formed Payment records, so NPSP validation is redundant and can trigger governor limits under concurrent load.
3	`ALLO_PaymentSync_TDTM`	`Allocation__c`	Prevents NPSP from syncing allocations when WeGive creates or updates Payment records. WeGive manages allocation sync independently.

Important: There is also a PMT_Payment_TDTM handler registered on the Opportunity object. Do not exclude the Integration user from that one. WeGive already sets npe01__Do_Not_Automatically_Create_Payment__c = true on Opportunities it pushes, which handles the Opportunity-side trigger correctly.