Pre-approval can wait until after the first release.
This is a very valuable feature, and we want it soon, but it doesn't have to be in literally the first release.
This commit is contained in:
parent
d921c03d6f
commit
49efe41741
1 changed files with 15 additions and 12 deletions
|
@ -28,7 +28,7 @@ doable by a bookkeeper with appropriate privileges.
|
|||
|
||||
### Defining the request form
|
||||
|
||||
Requests for payment have five states: Pre-Approval, In Progress, Submitted,
|
||||
Requests for payment have four states: In Progress, Submitted,
|
||||
Accepted, and Rejected.
|
||||
|
||||
Administrators can define questions to ask the requestor about the entire
|
||||
|
@ -66,21 +66,13 @@ accommodations expenses, etc.).
|
|||
### Requestor workflow
|
||||
|
||||
Requestors can log in and see the status of all their requests. They can also
|
||||
create a new request, which starts either the Pre-Approval or the In Progress
|
||||
create a new request, which starts in the In Progress
|
||||
state.
|
||||
|
||||
When they view a report, it shows the questions and answers about the entire
|
||||
report, and a list of associated expenses. Viewing a specific expense
|
||||
similarly shows all the questions and answers about it.
|
||||
|
||||
When a report is in the Pre-Approval state, the requestor is submitting not
|
||||
receipts or invoices, but documents regarding potential expenses that have
|
||||
not yet been incurred, but for which organization policies require
|
||||
preapproval by organizational management ahead of time. The appropriate
|
||||
management representatives are duly notified by the system of pending
|
||||
Pre-Approval requests, and their approval moves the request into the In
|
||||
Progress state. Their rejection moves the request to the Rejected sate.
|
||||
|
||||
When a report is In Progress state, the requestor can edit any answer in the
|
||||
report or an associated expense. They can also add an expense, which begins
|
||||
by asking them unconditional questions associated with expenses, and then
|
||||
|
@ -157,7 +149,18 @@ be extended to address the case of "other question isn't answered"
|
|||
* Export to SQLedger
|
||||
* [Certainly many more, feel free to add them here]
|
||||
|
||||
* Richer lifecycle management: A leader may need to approve a request before
|
||||
* Richer lifecycle management
|
||||
* Support requests for pre-approval, probably with two states
|
||||
"Pre-Approval In Progress" and "Pre-Approval Submitted." In the
|
||||
Pre-Approval state, the requestor is submitting not receipts or
|
||||
invoices, but documents regarding potential expenses that have not yet
|
||||
been incurred, but for which organization policies require preapproval
|
||||
by organizational management ahead of time. The appropriate management
|
||||
representatives are duly notified by the system of pending Pre-Approval
|
||||
requests, and their approval moves the request into the In Progress
|
||||
state. Their rejection moves the request to the Rejected sate.
|
||||
|
||||
* A leader may need to approve a request before
|
||||
it's added to the books, like an employee's manager or a program director
|
||||
|
||||
* Various currency improvements:
|
||||
|
|
Loading…
Reference in a new issue