Payout
Mapping between WeGive Payouts and Salesforce custom Payout objects
Payout
The Payout mapping between WeGive and Salesforce is a critical component of the integration, enabling seamless tracking of payment distributions and financial reconciliation between the two platforms. This mapping ensures that payout details, transaction summaries, and financial data are properly tracked and synchronized, providing a comprehensive view of your payment processing and distribution strategy.
Key Concepts
The integration between WeGive Payouts and Salesforce Payout objects is designed to provide a robust financial tracking solution. Understanding these key concepts is essential for effective implementation and usage.
Object Mapping
- WeGive Payouts map to Salesforce custom Payout objects
- Requires WeGive Managed Package installation
- One-directional sync (WeGive to Salesforce)
- Custom object integration
Managed Package Details
- Custom object name:
wegive__Payout__c - Package source: WeGive Managed Package
- Installation required for functionality
- Custom fields included
Sync Behavior
- One-directional synchronization
- Real-time updates
- Payout creation and tracking
- Transaction summary
- Financial reconciliation
Dependencies
- Transaction synchronization
- Payment processing
- Financial tracking
- Reconciliation management
Field Mappings
The field mappings between WeGive and Salesforce payout objects are designed to ensure comprehensive data synchronization. These mappings cover all essential payout information, from basic details to complex financial data.
Standard Field Mappings
| Salesforce Field | WeGive Field | Direction | Create Only | Default Mapping | Notes |
|---|---|---|---|---|---|
name | name | Export | No | Yes | Payout name |
payout_date | payout_date | Export | No | Yes | Distribution date |
status | status | Export | No | Yes | Payout status |
amount | amount | Export | No | Yes | Total amount |
transaction_count | transaction_count | Export | No | Yes | Number of transactions |
currency | currency | Export | No | Yes | Currency type |
reference_number | reference_number | Export | No | Yes | Payout reference |
description | description | Export | No | Yes | Payout description |
created_date | created_date | Export | No | Yes | Creation timestamp |
modified_date | modified_date | Export | No | Yes | Last modified date |
Important Notes
Understanding these important aspects of the Payout integration is crucial for successful implementation and ongoing management.
Package Requirements
- WeGive Managed Package must be installed
- Custom objects must be deployed
- Field-level security must be configured
- User permissions must be set
Sync Behavior
- One-directional synchronization
- Export-only updates
- Transaction summary
- Financial tracking
- Reconciliation support
Field Considerations
- Required fields must be mapped
- Custom fields can be added
- Field types must match
- Validation rules apply
- Default values supported
Best Practices
Following these best practices will help ensure a smooth and successful payout integration:
Data Management
- Regular data validation
- Monitor sync status
- Check for duplicates
- Verify field mappings
- Review error logs
Integration Configuration
- Test in sandbox first
- Verify permissions
- Check field security
- Monitor performance
- Regular maintenance
Troubleshooting
- Check sync logs
- Verify connections
- Review error messages
- Test field mappings
- Contact support if needed
Common Scenarios
Understanding these common scenarios will help you effectively manage payouts across both platforms:
New Payout Creation
- Process payout in WeGive
- Sync to Salesforce
- Verify details
- Track status
- Monitor reconciliation
Payout Updates
- Update status
- Modify details
- Track changes
- Verify amounts
- Monitor sync
Financial Reporting
- Generate reports
- Verify totals
- Check transactions
- Review status
- Track history
The Payout integration provides a robust solution for managing payment distributions across both WeGive and Salesforce, ensuring that all payout-related data is properly synchronized and maintained.