@@ -158,49 +158,51 @@ effort for the first release.
to define a policy, "If an employee did not use a preferred airline, and
did not travel internationally, it does not meet policy."
* Flag non-reimburseable expenses based on policy validations
When the requestor answers questions that are outside the policy
validations, the system should flag the answer and explain how it falls
outside policy. The requestor should still be able to submit the request,
but they should be prompted to explain why the request should be fulfilled
despite policy problems.
* Ask additional questions based on policy validations
For example, "If the expense type is office supplies, and the cost is over
$50, prompt for a receipt."
* 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
* Export to LedgerSMB
* [Certainly many more, feel free to add them here]
* Richer lifecycle management
* Support requests for pre-approval, probably with two states
"Pre-Approval Draft" 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 Draft
state. Their rejection moves the request to the Rejected sate.
* Support more review: a leader (such as a manager or program
director) may need to review and approve a request along with, or
instead of, the bookkeeper
* Support automatically determining the appropriate leader for a
payment request based on information in the request, like a
"What project is this for?" selection
* A new state after Approved, Filled, which means that the
organization has arranged for payment to go out. The requestor