​

Fund Data Mapping

​

Object Overview

​

WeGive Fund Object

• Purpose: Represents giving categories and designations in the WeGive platform
• API Endpoint: /funds/{fund}
• Unique Identifier: WeGive fund ID
• Management: Controls donation categorization and reporting

​

Blackbaud Fund Object

• Purpose: Represents funds, designations, and giving categories in Raiser’s Edge NXT
• API Endpoint: fundraising/v1/funds/{fund_id}
• Unique Identifier: Blackbaud fund ID
• Financial Management: Controls gift designations and financial reporting

​

Core Fund Mapping

​

Basic Fund Information

​

Fund Classification

​

Financial Information

​

Fund Status and Lifecycle

​

Fund Type Mapping

​

Standard Fund Types

​

Fund Status Values

​

Campaign and Appeal Integration

​

Campaign Linkage

​

Marketing and Attribution

​

Financial Reporting Configuration

​

Accounting Integration

​

Tax and Compliance

​

Custom Fields and Attributes

​

Extended Fund Information

​

Stewardship and Recognition

​

Data Transformation Rules

​

Name and Description Handling

• Preserve original formatting and capitalization
• Maximum length: 255 characters
• Special characters allowed and preserved
• Duplicate name detection across systems

• HTML markup removed for compatibility
• Maximum length: 4000 characters
• Line breaks preserved where possible
• Rich text formatting converted to plain text

​

Amount and Financial Data

• All amounts stored in organization’s base currency
• Multi-currency support for international organizations
• Exchange rates captured at time of creation
• Historical rate preservation for reporting

• Goals rounded to nearest dollar
• Percentage completion calculated automatically
• Progress tracking updated with each gift
• Historical goal changes maintained

​

Date and Time Processing

• Start dates cannot be in the past when creating new funds
• End dates must be after start dates
• Timezone conversion for international organizations
• Date validation ensures logical sequence

• Status change history maintained
• Automatic timestamp recording
• User attribution for manual changes
• Audit trail for compliance

​

Sync Behavior

​

Create Operations

1. Validate fund data and requirements
2. Check for duplicate fund names or codes
3. Create fund record in Blackbaud
4. Set initial status and configuration
5. Store correlation ID for future updates
6. Configure default campaign/appeal linkage

1. Extract fund information and attributes
2. Map to WeGive fund format
3. Preserve fund classification and status
4. Create WeGive fund record
5. Store correlation ID and external references

​

Update Operations

• Fund name and description changes
• Status updates (active/inactive)
• Goal and target modifications
• Campaign and appeal associations
• Custom field and attribute updates

• Fund codes typically immutable after creation
• Status changes may require administrative approval
• Goal reductions may require audit justification
• Major description changes logged for review

​

Archive and Closure Operations

• Status change to “Closed” or “Archived”
• Final gift acceptance date recording
• Balance transfer to successor fund (if applicable)
• Historical data preservation
• Donor notification of fund closure

​

API Examples

​

Create Fund Record

POST /fundraising/v1/funds
{
  "description": "Annual Operating Fund",
  "fund_code": "AOP2024",
  "type": "Unrestricted",
  "status": "Active",
  "goal": {
    "value": 100000.00,
    "currency": "USD"
  },
  "long_description": "Support for general operating expenses and program delivery",
  "category": "Operating",
  "is_restricted": false,
  "is_tax_deductible": true,
  "start_date": "2024-01-01",
  "end_date": "2024-12-31",
  "gl_account_number": "4010-001",
  "default_campaign_id": "annual-campaign-2024"
}

​

Update Fund Status

PUT /funds/{fund_id}
{
  "name": "Annual Operating Fund",
  "status": "active",
  "goal": 100000.00,
  "raised_amount": 25000.00,
  "progress_percentage": 25.0,
  "updated_at": "2024-03-15T10:30:00Z",
  "blackbaud_fund_id": "12345678-1234-1234-1234-123456789abc"
}

​

Fund with Campaign Integration

{
  "description": "Building Campaign - Phase 1",
  "fund_code": "BUILD01",
  "type": "Capital",
  "status": "Active",
  "goal": {"value": 500000.00, "currency": "USD"},
  "category": "Capital",
  "is_restricted": true,
  "default_campaign_id": "building-campaign-2024",
  "default_appeal_id": "phase-1-appeal",
  "attributes": [
    {
      "attribute_category": "Building Project",
      "string_value": "New Community Center"
    },
    {
      "attribute_category": "Architect",
      "string_value": "Smith & Associates"
    }
  ],
  "gl_account_number": "1510-001",
  "project_id": "PROJ-2024-001"
}

​

Error Handling and Validation

​

Required Field Validation

• Fund name/description must not be empty
• Fund code must be unique within organization
• Status must be valid enumerated value
• Goal amount must be positive if specified
• Date ranges must be logical (start before end)

• Name length validation (max 255 characters)
• Code format validation (alphanumeric plus hyphens)
• Amount precision validation (2 decimal places)
• Date format validation (ISO 8601)
• Status transition validation

​

Common Error Scenarios

• Error: Fund name already exists
• Resolution: Append identifier or modify name
• Action: Queue for administrative review

• Error: Fund code format invalid or duplicate
• Resolution: Generate alternative code or modify
• Action: Log warning and use system-generated code

• Error: End date before start date
• Resolution: Adjust dates or use open-ended range
• Action: Log error and notify administrators

​

Retry and Recovery Logic

• Network timeouts: Retry with exponential backoff
• Rate limiting: Respect retry-after headers
• Server errors: Retry up to 3 times with delays

• Validation errors: Log and skip record
• Authorization errors: Alert system administrators
• Data conflicts: Queue for manual resolution

​

Performance Optimization

​

Batch Processing

• Process up to 50 funds per API call
• Validate all fund data before batch submission
• Handle partial batch failures gracefully
• Progress tracking and status reporting

• Delta sync for changed records only
• Timestamp-based change detection
• Bulk update operations where supported
• Minimized API calls through intelligent batching

​

Caching Strategies

• Fund information cached for 30 minutes
• Campaign and appeal data cached for 15 minutes
• Status and type lookups cached for 2 hours
• GL account mappings cached for 1 hour

• Average fund sync time tracking
• API response time monitoring
• Error rate alerting by fund type
• Cache hit ratio optimization

​

Reporting and Analytics

​

Fund Performance Metrics

• Total funds synchronized per period
• Success/failure rates by fund type
• Average sync time per fund
• Peak processing periods

• Validation error rates by field
• Missing required field frequency
• Duplicate detection accuracy
• Status transition compliance

​

Financial Analytics

• Goal achievement rates by fund type
• Average time to reach funding goals
• Donation frequency by fund
• Donor retention by fund category

• Fund performance across systems
• Discrepancy identification and resolution
• ROI analysis by fund type
• Cost-per-dollar-raised calculations

​

Fund Hierarchy and Relationships

​

Parent-Child Fund Relationships

​

Fund Groupings and Categories

​

Best Practices

​

Fund Management

1. Consistent Naming: Use standardized fund naming conventions
2. Clear Descriptions: Provide detailed fund purposes and restrictions
3. Regular Review: Periodically review fund performance and status
4. Proper Classification: Use appropriate fund types and categories

​

Data Quality

1. Validation Rules: Implement comprehensive validation before sync
2. Duplicate Prevention: Check for existing funds before creation
3. Regular Audits: Compare fund data between systems regularly
4. Cleanup Procedures: Maintain procedures for fund merging and closure

​

Performance Optimization

1. Batch Operations: Use batch processing for bulk fund operations
2. Selective Sync: Only sync changed fund records
3. Caching Strategy: Cache frequently accessed fund data
4. Monitoring: Track fund sync performance and errors

​

Compliance and Security

1. Access Control: Limit fund modification permissions
2. Audit Trail: Maintain complete change history
3. Approval Workflows: Require approval for significant changes
4. Backup Strategy: Regular backups of fund configuration

​

Troubleshooting Guide

​

Common Sync Issues

• Verify fund name uniqueness
• Check fund code format and availability
• Validate goal amounts and date ranges
• Confirm user permissions for fund creation

• Review status transition rules
• Check for active donations preventing closure
• Verify user authorization for status changes
• Validate date constraints for status changes

• Compare calculation methods between systems
• Check for currency conversion issues
• Verify gift allocation and rollup logic
• Review date range filters for calculations

​

Data Quality Issues

• Check field mapping completeness
• Verify data availability in source system
• Review sync scope and filtering rules
• Validate required field population

• Review fund type and category mappings
• Check for custom field configuration differences
• Validate enumerated value consistency
• Confirm hierarchy relationship accuracy

​

Performance Problems

• Optimize batch sizes for fund volume
• Review API response times and bottlenecks
• Check network connectivity and latency
• Monitor system resource utilization

• Analyze error patterns and common causes
• Review data validation rule effectiveness
• Check system capacity and rate limits
• Validate integration configuration settings

​

Support Resources

​

Documentation References

• Blackbaud Fund API Documentation
• WeGive Fund API Documentation
• Campaign Mapping Documentation
• Gift Mapping Documentation

​

Support Contacts

• WeGive Support: [email protected]
• Blackbaud Developer Support: Developer Community
• Financial Systems Integration: Available for complex fund management scenarios