Verified BursaPay finance workflow: Explains how payment objects are marked as recognized for finance reporting.
1. Overview & Purpose
RevenueRecognitionRecord links a payment object generically, records whether revenue is recognized, and stores the source type as V1 or V2.
2. Requirements & Setup
The underlying payment object must be identifiable through its content type and object ID.
3. Step-by-Step Workflow
- Open the relevant BursaPay finance dashboard workflow.
- Review the required state, filters, dates or records.
- Complete the permitted finance action or inspection.
- Verify the resulting state and audit trail.
4. Rules & Troubleshooting
Each payment object has one recognition record, preventing duplicate recognition rows.
5. Verification & Next Steps
Use the recognition state when tracing revenue through V1/V2 migration paths.