NPO-Accounting/npo-accounting-ikiwiki Files · UseCases/ReadingAPI.mdwn

Files @ 2204e09bfe39

Branch filter:

Location: NPO-Accounting/npo-accounting-ikiwiki/UseCases/ReadingAPI.mdwn

2204e09bfe39 658 B text/plain Show Annotation Show as Raw Download as Raw

bkuhn

Slightly increase scope: include payment requests

The project should really include outgoing payments along with it.
Submitting an invoice for payment as an external party is really just a
"base case" of a reimbursement request.

The only complication I can imagine this adds is allowing the general
public to create an account on the system, or allow for anonymous
submission, which might lead to spam concerns in deployment.

I believe these issues should be easily mitigated and will not
drastically increase scope of the project.

As part of this actual change to the text, some wordsmithing and changes
throughout to s/reimbursement/outgoing payments/ and other similar
changes are made.

# API

As a developer, it's essential that I have access to a clearly documented API
(at least) to read and (possibly) to write/update the financial data.

Specifically, the need to generate reports and analyze data in new ways is
essential, and while many systems try to give some sort of "report builder",
which are perhaps useful for some needs, are never adequate to foresee every
type of necessary issue.

The API should allow for not only custom reports, but the ability to generate
a programmatic analysis.  For example, this sort of API would be used to
compute the [[public support test for USA 501(c)(3) organizations|UseCases/PublicSupportTest]].