Hi John A. I get where you're coming from in seeking to understand the technical possibilities and what others have done.
But rather than answer your (great question) I wanted to go off on what I see as an important tangent picking up on the saying... "For a man with a hammer everything is a nail". Or rather, to an engineer with Workato everything is an integration challenge 😀
Putting it another way... just because something COULD be done, doesn't mean it SHOULD be done. Everything is possible, but usually resources are limited and prioritisation is key and in this business requirements are key.
So I'd suggest sitting down with your finance team (especially the button pressers that actually do the tasks each day) and asking them what takes them the most time, is most boring and repetitive and that they think someone should "magic away". Users may or may not have an understanding of the art of the technically possible, but they can certainly tell you what takes time and feel like little value add.
These are (at least some of) the requirements of the Business. You can then quantify each scenario they flag (by asking how many people do this task x how often x how much time does it take on each occurence). That gives you the impact and how long it will take for "payback" (i.e. how many days/weeks/months of your solution being in place before the cost of your dev time is recouped). Prioritisation is not necessarily purely done on payback, but it certainly helps.
And speaking to those in Finance management may also surface other higher level process inefficiencies and possibly other frustrations (perhaps more to do with data they can't see).
Apologies if you know all that already, and for not answering your question directly. I'm sure someone else will be along shortly with a more direct response, but after many years as a Business Analyst and Product Owner (as well as developer) I can't let the opportunity pass to bang the "requirements not technology first" message 😆
