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

follow-up questions as necessary based on those answers.

When an In Progress report has at least one expense associated with it, and

all questions have been answered, the requestor may submit the request for

approval.  If any of the answers do not meet the administrator's conditions

for payment, the requestor may still submit the request, and provide an

explanation for why the request should be paid (e.g., because it was

approved in advance).  Once the request is submitted, it moves to the

Submitted state.

### Bookkeeper workflow

Bookkeepers can log into the system and see all requests.

When bookkeepers review a Submitted report, they can change the report's

state, and include a note explaining why the report was moved to that state

(e.g., moved back to In Progress because a specific receipt was insufficient

letting them know about the change, including the rationale provided by the

bookkeeper.

The bookkeeper can export any request to the books.  The first release of the

software will simply provide an archive that includes all of the request's

supporting documentation, plus a `.ledger` file with entries for each

expense.  However, note that when building this feature in the code and UI,

it should be relatively generic.  Exporting should remain abstract enough

that integration with other accounting systems remains simple and

straightforward.  Note that even the mechanics could be different; for

example, an SQLedger exporter may add entries to the system directly, rather

than providing the bookkeeper with a file download.

## Requirements potentially for first release

These are features that we would like the system to have, and it may make

sense to make them requirements of the first release depending on how it's

built.

* CiviCRM integration: Many NPOs are already using CiviCRM.  CiviCRM

  integration would provide a familiar interface to users, and simplify

  system administration for the organization.  It may be possible to build

  the system as a CiviCRM extension.  If so, we would get this feature for

  "free."