* 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

  * [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

    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

* Show currency amounts in the requestor's reimbursement currency

  For example, the requestor can submit a reimbursement with expenses in

  USD, EUR, and CHR, but wants payment in INR.  Unclear what

  interface for this would look like, but real-time data about past currency

  rates might be available via an API somewhere, and we can use that to have

  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.