Real-World Example
ABC Collections schedules a weekly report for its finance team. On Monday morning, the selected recipients receive an email with a secure Download Report button. They can download the report directly from that email for 90 days without signing in to the portal.
If ABC Collections selected SFTP instead, the report is delivered to its configured SFTP destination and is not retained as an email download.
Visual Flow
How It Should Work
- It should run scheduled exports at the configured daily, weekly, or monthly cadence.
- Email delivery should send a secure download button instead of attaching the report.
- An email recipient should be able to download the report directly from the email for 90 days.
- Each download should return the exact report generated for that scheduled run.
- Reports should remain private and should only be available through their secure email link.
- After 90 days, the link should expire and the stored report should be removed automatically.
- SFTP delivery should continue sending the report to the configured destination and should clean up its temporary delivery file afterward.
How It Should Not Work
- It should not send a report to the wrong creditor recipient or SFTP destination.
- It should not generate duplicate reports for the same schedule window.
- It should not attach large report files to email.
- It should not expose a report through a public storage address.
- It should not allow an expired or modified download link to retrieve a report.
- It should not retain an emailed report beyond its 90-day availability period.
Last modified on August 1, 2026
