Monthly regulatory return, assembled and signed off
The month-end return as a scheduled pipeline instead of three days of assembly. Exposures are read, grouped and totalled by category, each total is checked against the rule set, and the finished return is emailed to compliance as a CSV for sign-off before anything is filed. A set-state node records the period it covered, so the next run knows where the last one stopped — and because state commits only when the run succeeds, a failed month is re-run rather than skipped. Seeded switched OFF, like the cron demo: a return that files itself the moment you press the button is not a demo anybody wants.
The pipeline
This is the actual graph the template creates — 10 steps; dashed lines are the failure/invalid paths.
Connects to
- PostgreSQL
How you know it worked
Run it by hand rather than waiting for the first of the month. Six exposure lines become three category totals, and the review copy lands in MailHog as a CSV.
Try this templateUsed in: Banking & finance
Related templates
Database → CSV on SFTP
Writes a CSV onto the SFTP server — including one deliberately broken row. It exists to give the validate-and-route demo something to find, which…
File in, validation, two destinationsSFTP CSV → validate → database, rejects emailed
Reads the CSV back off SFTP and takes it a row at a time: good rows are loaded into a table, a bad one is emailed to somebody instead of being…
Excel exportDatabase → Excel workbook in object storage
The same rows again, this time as a real .xlsx workbook dropped into MinIO. Nothing about the pipeline changes except the format — that is the…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.