- Changed the way we process some data about account changes received from our banking partner
- Enabled & tested SS4 upload during employer signup and in the employer settings screen (previously we only accepted EIN letter for proof of employer’s tax ID; now, the employer can choose which type of document they wish to submit for this)
- Improved performance in our internal admin tools
- Added caching to improve performance fetching user data from our banking partner
- Changed some internal business logic to not rely on population of timestamps – the result is that certain employee balance mismatches that we had been detecting and fixing manually should no longer occur
- Added idempotency keys to some calls to our banking partner to make it less likely that duplicate transactions will be created
- Fixed an issue with transferring funds in our internal admin tools
- Updated the color scheme of email notifications for improved readability
- Removed the annual estimate on the change contribution screen for employees, as this didn’t take employer’s pay schedule into account so was usually inaccurate
- Performed cleanup of some older user & transaction data from our banking partner; the result should be improved performance
- Added to our internal admin tools the ability to require employees to have completed a contribution in order to receive a sign-on bonus – this ability was previously implemented in the employer version of this screen, but now can also be done by our CS team for customers on the managed services tier
- Fixed a bug that would sometimes cause duplicate contribution processes to be started – this was only seen in one of our test environments and did not affect any live customer accounts
- Fixed a setting in our firewall to be more secure & SOC 2–compliant
- Made adjustments to a script that automatically fixes mismatched ending balances in our ledger
- Fixed a bug that would cause the ask for a reward process to incorrectly be zero under certain circumstances – this was only seen our test environments, and did not affect live customer accounts