Changeset - 98b5bc47fa74
[Not reviewed]
0 1 0
Brett Smith (brett) - 8 years ago 2016-08-31 19:23:29
brett@sfconservancy.org
markup cleanup
1 file changed with 4 insertions and 0 deletions:
0 comments (0 inline, 0 general)
Reimbursements/Requirements.mdwn
Show inline comments
...
 
@@ -174,16 +174,19 @@ effort for the first release.
 
* Allow optional questions
 

	
 
  Along with this, policy validations probably need to
 
  be extended to address the case of "other question isn't answered"
 

	
 
* Additional exporters
 

	
 
  * Export to SQLedger
 

	
 
  * [Certainly many more, feel free to add them here]
 

	
 
* 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
...
 
@@ -203,12 +206,13 @@ effort for the first release.
 
  the requestor give us "preferred currency for payment" so all changes
 
  happen in real time in the interface (even allowing the requestor to be
 
  able to decide *while filling out the report*: "ugh, these exchange rates
 
  to INR are horrible; I'll have them pay my USD account instead").
 
  
 
* Data import
 

	
 
  * Apps like [Tricky Tripper](http://trickytripper.blogspot.de/) let users
 
    track expenses for a trip as they go.  The system could import this data
 
    to prepopulate answers to questions about the request and expenses in
 
    it.  Probably there would be an import API that can map different import
 
    formats to a common format, and then administrators can define how
 
    questions in their system can be answered based on imported data.
0 comments (0 inline, 0 general)