Fund Data Mapping
Detailed field mapping for funds and GL codes between WeGive and DonorPerfect systems.
Fund Data Mapping
This document details how WeGive funds are mapped to DonorPerfect GL codes, enabling proper fund designation and financial reporting across both systems.
DonorPerfect Table Reference
Primary Table: dpcode (Code Tables)
WeGive Model: Fund
Sync Direction: WeGive → DonorPerfect (Push Only)
Fund Integration Overview
GL Code Management
Core Fund Fields
Primary Identifiers
Fund Information
GL Code Creation Process
Automatic GL Code Generation
Fund Created in WeGive
New fund established in WeGive system
GL Code Check
Integration checks if GL code exists in DonorPerfect
Code Creation
Creates new GL code if it doesn’t exist
Description Sync
Updates GL code description with fund name
Validation
Confirms GL code is available for transaction use
GL Code Update Process
Data Flow Patterns
Fund Synchronization
Transaction Integration
API Operations
DonorPerfect GL Code Management
Error Handling
GL Code Errors: Invalid or duplicate GL codes can prevent transaction processing.
| Error Type | Cause | Resolution |
|---|---|---|
| Duplicate Code | GL code already exists | Use existing code or create variant |
| Invalid Characters | GL code contains invalid characters | Clean code format and retry |
| Code Too Long | GL code exceeds DonorPerfect limits | Truncate or use alternative code |
| Permission Error | Insufficient rights to create codes | Verify API permissions |
| API Timeout | DonorPerfect API unavailable | Retry with backoff delay |
Fund Configuration
WeGive Fund Setup
DonorPerfect GL Code Requirements
Sync Configuration
Fund Sync Settings
Performance Considerations
Efficient Processing
- Batch GL code creation for multiple funds
- Cached GL code validation for transactions
- Minimal API calls for existing codes
- Optimized query performance
Error Recovery
- Automatic retry for failed GL code creation
- Alternative code generation for conflicts
- Manual override options for complex cases
- Comprehensive error logging and alerts
Data Quality and Validation
Pre-Sync Validation
Monitoring and Reporting
Best Practices
Fund Management
Plan GL Code Structure
Design consistent numbering scheme before creating funds
Use Descriptive Names
Create clear, concise fund names within character limits
Maintain Active Status
Regularly review and update fund statuses as needed
Monitor Sync Status
Check integration dashboard for GL code sync issues
Integration Optimization
Proactive Management
- Create funds before launching campaigns
- Test GL code creation in development
- Plan for fund lifecycle management
- Document fund purposes and usage
Error Prevention
- Validate fund names before creation
- Check for duplicate GL codes
- Maintain consistent naming conventions
- Review DonorPerfect GL code standards
Troubleshooting
Common Fund Sync Issues
Limitations and Considerations
Known Limitations
Important Fund Limitations:
Future Considerations
Related Documentation
Transaction Mapping
How GL codes are used in transaction processing
Configuration Guide
Configure fund sync settings
Integration Nuances
Platform-specific fund handling behaviors
Data Overview
Complete data mapping documentation
For additional help with fund data mapping, contact our support team at [email protected].