Hybrid Share + Deposit Distributions

PinkApple supports a hybrid member-distribution model for share products whose dividend computation method is HYBRID_SHARE_DEPOSIT_DAYS.

This mode computes a distribution pool from two evidence streams:

• share value-days for the selected share product
• qualifying deposit balance-days for the same member

The hybrid engine runs under a normal dividend_event, but it stores its policy, runs, segment evidence, and computed allocations in dedicated hybrid distribution tables before a final run is synced into dividend_allocation.

When To Use It

Use hybrid distributions when the institution wants the final member surplus to consider both:

• the member's time-weighted paid-up share position
• the member's time-weighted qualifying deposit balances

Use the standard SHARE_DAYS dividend path when only share ownership should drive the payout.

Preconditions

Before declaring a hybrid event:

• the share product must be dividend-eligible
• the product dividend computation method should resolve to HYBRID_SHARE_DEPOSIT_DAYS
• the dividend event must have a fiscal year
• the member accounts must already exist and be approved
• any qualifying deposit accounts must already exist and be approved

User Flow

1. Declare the Dividend Event

Go to Shares -> Dividends -> Dividend Events.

When the selected product is configured for hybrid distribution, the declaration form will only offer:

• Hybrid Share + Deposit Days as the calculation basis

Save the event first. This creates:

• the dividend_event
• a default hybrid member-distribution policy linked to that event

2. Open Hybrid Distribution Manager

On the event row, choose Manage Hybrid Distribution.

This opens the event-specific manager where users can:

• review and update the hybrid policy
• compute projection runs
• compute final runs
• inspect run allocations and segment evidence
• post a final run into the normal dividend allocation table

3. Save the Policy

Policy fields determine how the pool is allocated.

Important fields:

• Allocation Model
  • SPLIT_POOL: first split the pool into a share component and a deposit component, then allocate each component independently
  • WEIGHTED_POINTS: convert share and deposit weights into one combined weighted-points pool
• Share Pool % and Deposit Pool %
  • only used as pool splits for SPLIT_POOL
  • must total 100%
• Share Weight Factor and Deposit Weight Factor
  • used in WEIGHTED_POINTS
  • higher factors increase that component's influence
• Share Valuation Basis
  • PAID_UP_SHARES_X_PAR_VALUE is the default and recommended basis
• Deposit Balance Basis
  • CLEARED_QUALIFYING_DAILY_BALANCE is the default and recommended basis
• Zero Denominator Policy
  • BLOCK_CALCULATION: stop the run if a required denominator is zero
  • REDISTRIBUTE_TO_OTHER_COMPONENT: move that pool to the other component
  • RETAIN_UNALLOCATED: keep that pool unallocated
• Distribution Start Date and Distribution End Date
  • define the evidence window used for share value-days and deposit balance-days

Run Types

Projection Run

Use a projection run to preview the outcome without syncing anything into dividend_allocation.

Projection runs are useful for:

• finance review
• management sign-off
• validating the policy before final posting

Final Run

Use a final run when the policy and evidence window are settled.

The final run:

• computes the same hybrid allocations
• stays in the hybrid run tables until you explicitly post it

Posting The Final Run

When the selected final run is in COMPUTED state, choose Post Selected Final Run.

This does three things:

1. syncs the final hybrid allocations into dividend_allocation
2. marks the run as synced/posted
3. updates the parent dividend_event to COMPUTED

At that point the event is ready for the normal dividend payment step.

Payment Processing

After the final run is posted:

• non-workflow events can use Process Payments
• workflow-managed events continue through the workflow transition path

The actual payment/reinvestment stage still reuses the standard dividend payment pipeline.

Workflow Behaviour

If the dividend event is workflow-managed:

• the workflow compute transition will compute a final hybrid run and sync it automatically
• the workflow process transition will then use the normal dividend payment process

This keeps the event on the same workflow template while using the new hybrid computation engine underneath.

What Evidence The Run Uses

For each member share account, the run stores segment evidence including:

• opening and closing share units for the distribution window
• share value-days
• deposit balance-days
• derived share and deposit weights
• qualifying deposit account count

For each allocation, the run stores:

• share component ratio and amount
• deposit component ratio and amount
• gross amount
• tax amount
• net amount
• dividend option and payment method

Current Scope

This implementation covers:

• hybrid policy management
• projection and final runs
• segment evidence
• allocation review
• sync into normal dividend allocations
• normal payment processing after sync

It does not yet import historical pre-cutover hybrid evidence segments automatically. If migration cutover happens mid-period, the institution must decide whether the first hybrid run starts from migration snapshot date or whether historical balance segments will be loaded separately.