Looking for feedback on an invoice reminder workflow architecture
Hey everyone,
I’ve been building a payment follow-up workflow and wanted some honest feedback on the architecture and logic from people with more automation experience.
The workflow currently:
- reads invoice data from a spreadsheet
- validates unpaid invoices
- calculates reminder stages based on due dates
- sends progressively firmer reminder emails
- prevents duplicate reminders
- escalates long-overdue invoices
- sends team alerts for failures/escalations
- tracks reminder history back into the data source
I intentionally tried to keep it relatively lean instead of turning it into a giant multi-agent system.
A few things I’m unsure about:
- Is a spreadsheet-based setup a reasonable source of truth at small scale, or does this become painful quickly?
- Would you handle escalation logic differently?
- Is there a cleaner way to manage staged email templates without creating visual chaos?
- At what point would you move something like this into a proper database?
- Any common failure points or edge cases I should anticipate in reminder/escalation workflows?
- How would you approach dispute detection/reply handling in a cleaner way?
Would appreciate any technical or operational feedback from people who’ve built similar workflows.
u/Lower-Kale-6677 — 5 days ago