Enterprise Cooperative CRM
In a cooperative the counterpart is not a customer but a member; the share, the payment and the voting right come together in the same person. When these three pieces of information are kept in separate ledgers, the attendance list is drawn up from scratch before every general assembly.
A member is a person record; the share count, dues lines and transfer history sit on the same card. Who the general assembly notice reached and who attended by proxy is read from the event record.
- Keep member records on a single card together with the share information, the payment history and the communication consent
- Process dues and instalment movements per member and see overdue payments in a single list
- Send the general assembly notice to members by SMS and WhatsApp and follow attendance and proxy status on the same record
- Record membership transfers together with their date and read from the history who held the share in which period
| Member Record | A member is a person record; the number of shares, the membership status and the date of joining are its fields, and the payment lines accumulate under the card. |
|---|---|
| Share and Dues Movement | Accrual and payment are lines tied to the member record; the balance is calculated from those lines and overdue ones fall into a list. |
| General Assembly | The general assembly is an event record; the sending of the notice, attendance and proxy status are held in fields tied to it. |
| Membership Transfer | A transfer is a record with a date field; it is tied to the cards of the transferring and the receiving member, and the history of the share is read from these records. |
The board of a cooperative changes; the member list stays. When a share transfer is made by contract and only filed away in a folder, a few terms later who holds a share can only be found out by asking the former manager. Something similar happens on the payment side: which member's instalment an amount that came into the account should count towards is matched by hand at the end of the month, and the objection arrives at the general assembly.
In Rapitek CRM the member is a record; the share information, the payment lines, the transfer history and the communication consent sit on the same card. Payment movements are entered by hand or by import; if a connection to the bank side is wanted, it is set up specifically for the project over the API — there is no out-of-the-box module. When the general assembly is opened as an event record, who the notice went to, who attended and who holds the proxy are read from the same record; when the meeting ends, the attendance list is not compiled all over again.
The scope of the plans and the separately priced items are written on the pricing page.
