Account hierarchy processing and trigger framework

I implemented Account processing that keeps hierarchy-derived data aligned with parent relationships. The framework populates the parent chain before changes are saved, recalculates affected hierarchy records after changes, and includes a two-phase batch path for corrective processing across accounts.

It also handles removal of a parent relationship, and sits alongside related account-data rules such as country/region mapping and segment population. It illustrates a class of Salesforce problem that goes beyond updating one record: a change to one account can affect values used across its whole hierarchy.

• Implemented parent-chain population before save and recalculation of affected hierarchy records after change.
• Built a two-phase batch path for corrective processing across accounts.
• Handled removal of a parent relationship.

• Apex
• Batch Apex
• Trigger framework

Client and internal names, payloads and configuration values are deliberately left out of this write-up.