# Generating Draft Transactions

As a manager at a nonprofit, I need the ability to have staff propose draft

transactions that are not added to the books official until approved.

As a bookkeeper, I'd like the ability to set up and review draft transactions

before officially adding them to the books, so I can see if they were entered

correctly.

provide all functions, reports, editing, interaction and viewing to allow a

user to view a "subset" of the books that are specific to any given fund.  In

essence, the books of a fiscal sponsoring org are proper superset of all the

books of its projects.

Thus, an individual project contributor wants to:

- View the books for that project as an independent set, unencumbered by

  transactions for other projects.

- [[Generate reports|GeneratingReports]] for that project's financial

  data, and have those reports only include data specific to that project.

The non-profit administrators want to:

- View the entire set of books for the organization, treating all income,

  expenses, and assets as belonging to the entire org, and only seeing the

  differences treating the project funds merely as "temporarily restricted

  assets".

- Be able to perform operations that span the entire books, such as

  reconciling bank accounts that are contain funds temporarily restricted for

  different projects.

## Other Resources

useless to some organizations.

There are roughly two operating modes that I've observed in use by non-profit

organizations.

## A "One Native Currency" Organization

In the USA at least, and perhaps elsewhere, the native currency to the

location of the entity is treated as the "one true currency" (which the USA

IRS calls your "functional currency") of the organization.  Specifically in

the USA, the IRS makes

[the following recommendation regarding currency conversion](http://www.irs.gov/Businesses/Small-Businesses-&-Self-Employed/Foreign-Currency-and-Currency-Exchange-Rates):

While [[double entry accounting|UseCases/DoubleEntryAccounting]] transactions

are the heart of any accounting system, auditors and managers need the

ability to dig down and determine what contracts, invoices, receipts or other

backup documentation relate to a given accounting document.

An adequate accounting system should provide easy link-up between

double-entry accounting transactions and the documentation that relates to

the transactions.  For example,

[[expense reports and reimbursement requests|UseCases/ReimbursementRequest]]

often have a myriad of receipts and invoices associated with them.

[[Handling contractors|UseCases/ContractorsAndContracts]] has similar types

of backup documentation.

Ideally, the system should allow the exploration of and linkage to

documentation in both directions.  It should be trivial to answer questions

   * I have this receipt/invoice from our document repository.  Which

     accounting transactions relate to this receipt?  Has the transaction

     been [[reimbursed|UseCases/ReimbursementRequest]]?

   * Looking at this invoice, can I see the transaction where it was accrued