Decompose the ChartField set into a main account plus a governed financial dimension model, translate trees and combo-edit rules into account structures, and classify ledger and ledger-group usage before choosing a target mechanism.
If organisational modelling decides who owns a transaction, finance modelling decides what the transaction says. In PeopleSoft that meaning is carried by ChartFields, validated by combo-edit rules, rolled up by trees, and recorded against a ledger inside a ledger group.
The instinct is to open the ChartField configuration and start mapping. The better first artefact is the one the playbook names: a ChartField usage heatmap.
The playbook's ChartField rationalisation step asks four questions per ChartField, and the answer must be exactly one of them.
PeopleSoft validates ChartField combinations through combo-edit rules: definitions of which values of one ChartField may appear alongside which values of another. Mature estates accumulate hundreds of them, encoding real financial control — a capital account that may only be used with certain funds, a revenue account restricted to…
Trees are pervasive in PeopleSoft and they do more work than a hierarchy usually does. In a typical estate, trees serve:
A SpeedType lets a user type one code and populate a whole ChartField combination. It is a productivity device rather than a control, and the concept mapping is honest about the target: there is no exact SpeedType object in D365, and you should replicate user productivity only where it is still needed.
This is the area where accurate description of the source matters most, because the source and target genuinely differ in shape and it is easy to describe one using the other's vocabulary.
Where Commitment Control is active, it is a stream of its own. The source material says so three times in three different documents, which is unusual emphasis.
Three supporting areas complete the finance design, and all three are comparatively mechanical after the structural decisions above.
A chart-of-accounts and dimension design is proven by reproduction, not by review.
Finance modelling on a PeopleSoft programme is a reduction exercise disguised as a mapping exercise, and the reduction is the value.