@@ -2,13 +2,13 @@
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
bookkeeper who might make an error easily if the system doesn't require a
workflow), the workflow should not be dictated.
## <a class="idOnly" id="unaccrued-invoice">The "Unaccrued Invoice" Example</a>
## <a id="unaccrued-invoice"></a>The "Unaccrued Invoice" Example
The easiest example I have of this relates to accruing income upon invoice
generation. Non-profits very typically generate invoices as part of a
fundraising discussion *even though* the non-profit doesn't have a good faith
belief that the invoice will be paid. Using an invoice to convince a donor