Finance department, bank position import
The green dot
A bank position import that starts with one button, runs on its own and says it has run.
- Service
- Automations
Context
A finance department imports the file of its bank positions. Its teams then record their entries against those positions.
The problem
Every month, someone forgot the import. Nobody knew who, or when. When it was late, the teams worked on outdated positions. Twice, duplicates.
And one day: “Import complete”, all green, zero rows imported. The process was reading an Excel file as text, then deleting the rows in error.
What we built
An “Import” button. Behind it, the whole chain runs on its own: refresh, load, checks. A Teams notification alerts the team. A time-stamped green dot says the import has run.
After the incident, two additions:
- an explicit message when the import brings back zero rows;
- an alert email with the link to the run.
Result
At 2:55 p.m. on the day of the incident: 117 rows imported, 62 positions created. Nobody asks “was the import done?” anymore.
For your IT team: Power Apps, Power Automate, SharePoint, Dataverse
- Hosting: inside your Microsoft 365. If an outside tool is useful, it is named and you decide.
- Accounts: a service account of your own for the automations.
- Permissions: inherited from your Microsoft 365 groups, nothing separate to maintain.
- Licenses: announced before we start, with the exact cost.
- Handover: documentation, user guide, quick reference; no proprietary code.
A process that costs you too much? An Excel file that has outgrown itself? A team losing time?
Describe it in five lines. Reply within 24 h with a costed estimate.