We've activated the password aging when using the Windows-client (for Baan4) some month ago. I think Baan4 is already able to handle your request, by just using the standard. (It seems you included a Baan4 hardcopy in your wordfile.)
You may need to updates some tool-sessions, to get the latest version of session ttstppwdaging. This session will do the trick, when inserted in the BMS Mask Data.
The thession ttstppwdaging will use the aging-data of the OS-users used by the Baan4-Server (it takes the information of the used user-accounts, so the server involved may not be the Baan4-Server itself).
We're using Baan 4 running on a Suse Linux Server. The aging question didn't come up as expected, so I opened an Infor365-case. We received extensive explanations (with testing and debugging information for Unix), which are available in KB 1116764.
The solution will also name other solution for setup and the latest component-updates.
We had to change the password-aging setup of the users in Suse Linux. Somehow the "countdown" prior to 30 days didn't work. But we activated an option which allowed the users to change their password after the 30 days (i.e. after 30 days the users will see a window on Baan-login telling them, to change their password within 10 days).
If you're using windows you may need to check Infor-support on specific info.