Is your feature request related to a problem? Please describe.
Invoicing is made more convoluted by having to go through CSSAT.
Describe the solution you'd like
User story: As a provider, I would like to be able to invoice directly from Sprout (instead of routing invoices through CSSAT, which has to print them up in .pdf format and submit them to DCYF).
Only org admin accounts have the option to send invoices.
May be submitted once per month and clearly be activated deliberately.
First, the org admin attests: “This email certifies under penalty of perjury...”
Warn providers on the submission that they get 1 submission per billing period, and resubmissions will require a special process and may delay payment up to XX days.
If provider already submitted, include instructions for who to contact for an exception.
Updated requirements from Caitlin at DCYF on 11/30/23: "After much discussion and different roads travel down, we are wanting the automatic invoicing to only allow one finalized invoice to be submitted. Any changes needed outside of this will follow our internal over/under payment system which we will communicate with providers."
Effort Size:
Uncertain
Prioritization Process
[x] Confirm the issue is a feature to which we want to devote resources.
[x] Write user story in as a (role) I want (something) so that (benefit) format.
[x] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.
Is your feature request related to a problem? Please describe. Invoicing is made more convoluted by having to go through CSSAT.
Describe the solution you'd like User story: As a provider, I would like to be able to invoice directly from Sprout (instead of routing invoices through CSSAT, which has to print them up in .pdf format and submit them to DCYF).
For more detail see the project plan (in Teams):
Additional context Requirements:
Effort Size: Uncertain
Prioritization Process
[x] Confirm the issue is a feature to which we want to devote resources.
[x] Write user story in
as a (role) I want (something) so that (benefit)format.[x] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.
[ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ ] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.