Boise Cascade
Boise Cascade implemented Page and Field Configurator change tracking functionality
Summary
Boise Cascade implemented Page and Field Configurator change tracking functionality. The feature allows them to log changes made to journal entries before posting, and track assets in new physical locations when asset locations are changed.
This has saved hours of manual effort, improved accuracy, and resulted in cost savings.
Boise Cascade plans to expand the use of the feature in the coming year to track changes in vouchers after initial entry.
Customer comments
Boise Cascade is currently using the Page and Field Configurator change tracker for logging changes made to saved, but not posted, journal entries. We want to see if someone changes account strings or amounts on the journal entry, specifically an automated/subsystem entry, before the journal has posted. We receive regular requests from internal and external auditors to review journal entries that meet this criterion, but we’ve never had an easy way of providing the information. We can easily do this now by querying the EOCC records. By being able to query the table by date and providing the detailed results of exactly what was changed, we save hours by not having to manually look for journal entries that might have this issue.
We are using Page and Field Configurator change tracker to look for changes made to asset locations that were changed without adding an effective dated row. Our property tax group has struggled for years to look for assets in new physical locations under the same business unit. They would run a prior year end net book value query and then manually compare that against a current month net book value query. This would take several hours to accomplish and was easy to miss a change. Now we provide the property tax group with the results from a query based on the EOCC_CHGTRK_LOG and EOCC_CONFIG_HDR records. This has saved both time and money.
We also plan to expand use of Page and Field Configurator change tracker to Accounts Payable by mid-2025. For Accounts Payable we need it to track the changes that have been made to a voucher after the initial entry for audit purposes. We also need it to track if any questions regarding the voucher come up, which typically happens when a voucher is unposted or cancelled. This gives us more visibility to what happened than we have with the last updated date/time stamp and modified by fields on the Summary tab of the voucher header.
This is what we’ve currently implemented in our production environment. Audit has done an initial review and is happy with the functionality so far.