See which codes a portfolio actually posts to

Nominal codes can be set for a single portfolio, so different parts of your business can post to different accounts. Until now those codes were only visible in Settings, behind a scope selector, and the portfolio page itself said nothing about them.

Every portfolio page now carries a GL Mappings panel. It lists each account type with the code that will actually be used for that portfolio, and says where the code came from: a portfolio override, or the organisation default it inherits. Where an override replaces a default, the panel names the code it replaced. Anything with no code is marked Not mapped, so a gap is stated rather than left blank.

The figures are worked out exactly as a posted journal works them out, including a rule that is easy to miss: a portfolio's own default takes precedence over an organisation-wide asset-class override.