The world is complex. There is rarely such a thing as a single person writing a few lines of code, and that code directly leading to $ savings. There are complex interactions and dependencies. Also, not all engineers are working on code that has measureable bottom-line impact, so these statements are only possible for a few. For example, an engineer refactoring old code can save a company millions over the lifespan of that code, and it would never show up as dollar values anywhere.
On the other hand, someone can change a cell in an Excel spreadsheet that had a typo in it and save the company $100,000. Should I hire the person because they found a typo? These kind of statements with dollar values are meaningless because the reader is missing context. More often than not, they are vanity statements and come across as disingenuous. I'd rather have you describe what you actually did.
A better example would be "Architected and implemented new real-time event messaging infrastructure using technologies X and Y that allowed us to move of expensive SaaS service Z and save $$.", or something like that. At least that tells me what you did, but even here the $ value is meaningless.