Automatic effects and module connections
Use this reference to distinguish what a completed action does from the separate work the team still needs to perform. The current implementation supports deliberate workflows rather than scheduled collection or communication.
Effect matrix
| Action | Application effect | Separate work |
|---|---|---|
| Activate donor | Adds DONOR to existing Party | Identity verification and accurate Party maintenance |
| Save fund | Saves tenant definition and version | Approve restriction and income mapping |
| Save donation draft | Saves details, allocations and lifecycle evidence | Verify money/evidence and arrange posting |
| Post donation | One internal receipt, initial journal, revision and history atomically | Bank/cash reconciliation and external acknowledgement process |
| Correct classification | Inverse plus replacement and new effective revision; same payment | Approve reason and verify resulting classification |
| Reverse duplicate | Inverse duplicate journal, REVERSED receipt/donation and canonical linkage | Independently verify duplicate evidence |
| Reach midnight | No automatic Charity business-date advance | Authorised finance calendar advance |
| Start sponsorship | Creates commitment relationship/history | Any external payment arrangement |
| Lose beneficiary sponsor eligibility | Computed Needs transfer flag/worklist | Officer chooses transfer or end |
| Transfer sponsorship | Ends old and creates linked new relationship | Review outstanding communications |
| Approve update | Freezes approved message | Officer's publication decision and any approved external delivery |
| Mark published | Saves status/actor/time | No email, portal delivery or print run is performed |
Ownership map
The connections do not make every record editable in every workspace. Generic customer payment actions cannot mutate Charity receipts. Accounting owns GL posting; shared reports expose minimised financial context. Sponsorship never opens the confidential Care record merely because an officer can see an alias.
Current boundaries
The Charity navigation reviewed here has no separate fundraising campaign, pledge-collection scheduler, Gift Aid claim workflow, volunteer management workspace, donor portal or mass mailing screen. Capability names declared elsewhere are not evidence that those user workflows are implemented.
There is no automatic donation-to-sponsorship matching, instalment reminder, bank collection, refund/disbursement, foreign-currency posting conversion or statutory receipt issuance. Photos are storage references only. Approved/published update text cannot be rewritten in place.
Example: Recording GBP 30 monthly sponsorship and a GBP 30 donation to the same fund does not link them. Staff can use their approved external reconciliation process, but should not claim the application has marked that month's commitment paid.
Any future automation should be documented only after its implemented screen, policy and side effects are verified. For today's workflow, use the detailed task chapters and check the saved state after each explicit action.