Add tag and additional workflow configurablity.
This commit is contained in:
parent
9e269502cf
commit
a8b1938793
1 changed files with 7 additions and 2 deletions
|
@ -1,13 +1,18 @@
|
||||||
# Non-Profit Workflow
|
# Non-Profit Workflow
|
||||||
|
|
||||||
|
<a id="workflow-dictated"></a>
|
||||||
|
|
||||||
Many accounting systems seem to assume that the workflow fits a certain type
|
Many accounting systems seem to assume that the workflow fits a certain type
|
||||||
of uses. While the ability to impose a specific workflow (e.g., for a
|
of uses. While the ability to impose a specific workflow (e.g., for a
|
||||||
bookkeeper who might make an error easily if the system doesn't require a
|
bookkeeper who might make an error easily if the system doesn't require a
|
||||||
workflow), the workflow should not be dictated.
|
workflow), the workflow should not be dictated.
|
||||||
|
|
||||||
|
<a id="workflow-configurable"></a> Ideally, in fact workflows should be
|
||||||
|
configurable in some way. Many systems try to do this and are a bit
|
||||||
|
constraining on it.
|
||||||
|
|
||||||
## <a id="unaccrued-invoice"></a>The "Unaccrued Invoice" Example
|
## <a id="unaccrued-invoice"></a>The "Unaccrued Invoice" Example
|
||||||
|
|
||||||
|
|
||||||
The easiest example I have of this relates to accruing income upon invoice
|
The easiest example I have of this relates to accruing income upon invoice
|
||||||
generation. Non-profits very typically generate invoices as part of a
|
generation. Non-profits very typically generate invoices as part of a
|
||||||
fundraising discussion *even though* the non-profit doesn't have a good faith
|
fundraising discussion *even though* the non-profit doesn't have a good faith
|
||||||
|
|
Loading…
Reference in a new issue