Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sequester unpaid projects 100 days after invoicing #82

Closed
4 tasks
pbchase opened this issue Sep 12, 2022 · 1 comment
Closed
4 tasks

Sequester unpaid projects 100 days after invoicing #82

pbchase opened this issue Sep 12, 2022 · 1 comment

Comments

@pbchase
Copy link
Contributor

pbchase commented Sep 12, 2022

Unpaid projects will need to be sequestered if no one pays for them after 100 days. Identify the unpaid projects by reading invoice_line_item in the rcc.billing DB.

Sequester unpaid projects 100 days after line item creation

If an invoice line item for a project has status == "invoiced" & get_script_run_time() - date_sent > days(100) and the project is not sequestered, then sequester the project by calling sequester_projects()

Email each project team using a templated email (steal the first draft of the template from Issue #77) telling them:

  • the project was sequestered
  • what sequestered means
  • that the Owner named in the email will need to contact the CSBT at the provided email address to pay the invoice.
  • that they can requester temporary un-sequestration by opening a ticket via the provided link.

The sequestrations need to be logged in the job log.

@pbchase pbchase added this to the Sequester unpaid projects milestone Sep 12, 2022
@pbchase pbchase changed the title Sequester or delete unpaid projects Sequester unpaid projects 100 days after invoicing Nov 1, 2022
@pbchase
Copy link
Contributor Author

pbchase commented Mar 17, 2023

@pbchase, produce an email template for @ChemiKyle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants