I take it back. Once you update QB and apply the latest fixes from within 2023, the issue is again resolved. The initial downloaded version has this bug, but installing released updates fixes it. All good.
