cancellation-demand-reversal-gap-on-original-unit
Transfer flow in fullcopy moves payment demands to the new booking but does not reverse or cancel the original demands on the old unit. This creates an accounting discrepancy risk where both old and new units may show outstanding demands post-transfer. Demand reversal logic must be added to the transfer completion handler before go-live.
Related
- cancellation-status-picklist-vs-code-value-mismatch
- salesforce-trigger-architecture-booking-c-has
- cancellation-dual-retention-gate-not-enforced-in-code
- salesforce
- duplicate-crontab-root-vs-claude-user
- booking-cancellation-module-audit-baseline-apr-2026
- quotetriggerhandler-broker-av-recalc-commented-out
- quotation-credit-note-sap-integration-chain
- quotationextn-legacy-apex-api-v41-massive-class