Share Admin Setup

Use this sequence when introducing or revising a share product.

1. Review The Seeded Type Taxonomy

Open Administration → Shares → Type Taxonomy.

This page is for review, not ongoing end-user maintenance. It shows the seeded share types and the flag profiles attached to them.

Use it to confirm:

• product group
• product type
• key characteristics
• the number of flags attached to each type

The platform flag definitions and type-level flag assignments are seeded. They are not managed from the normal shares administration flow.

2. Create The Share Product

Open Administration → Shares → Share Products.

Configure the base product information:

• name
• taxonomy
• currency
• par value
• issue limits
• dividend policy
• governance defaults
• membership and contribution fields
• pricing profile
• tax pricing profile

Then use Runtime Flags & Integrations to review the flags loaded from the selected type and apply only the permitted product-level overrides.

3. Review The Runtime Preview

Before saving or approving the product, review the preview for:

• available workflows
• account components
• dividend behavior
• governance rights
• lending restrictions

If the preview is wrong, adjust the selected product overrides or review whether the chosen share type is the right one.

4. Complete GL Setup

Use:

• Administration → Shares → GL Links
• Administration → Shares → Posting Rules

These two layers are both required:

• GL links tell PinkApple which standing accounts the product uses
• posting rules define how operational events become journals

Without complete GL setup, a share transaction may validate operationally but fail when the accounting event is posted.

5. Apply Business Unit Restrictions

Use Administration → Shares → BU Restrictions if the product should only operate in specific business units.

6. Validate Related Domain Dependencies

Check the external domains that the product expects to use:

• Clients for member, employee, KYC, age, and segment restrictions
• Pricing for fee, tax, valuation, and tier logic
• Loans for share-backed lending rules
• Deposits / Cash for funding and dividend payout routing
• Governance for meetings and voting execution

7. Test Transaction Outcomes

Before production use, test at least:

• immediate posting
• approval-routed posting
• rejected posting
• returned posting where applicable
• future-dated posting if allowed

Confirm that ownership state changes only happen after the GL outcome becomes terminal POSTED.

Operational Note

If a share transaction goes through GL approval or scheduled future posting, PinkApple preserves the transaction intent first and applies ownership effects only after the final posting outcome succeeds. This prevents balances from changing before the accounting event is actually accepted.