Periodic Activity of Override Accounts Translated at Average Rate

Summary

Explanation of why the out-of-the-box logic uses the Average Rate to translate periodic activity of override accounts instead of the EOM Rate

Content

Hi,

We are transitioning from an old Essbase consolidate system to Oracle FCCS. In the old system, any periodic activity on an override account was translated using the EOM Rate. FCCS translates the periodic activity of any override accounts using the Average Rate instead of the EOM Rate. Could you please provide an explanation behind the logic for using the Average Rate to translate periodic activity of override accounts instead of the EOM Rate? We would like to rely on the out-of-the-box logic in FCCS, but would prefer to have an Oracle explanation for why the Average Rate was chosen as