Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-7188

Deleting membership or pledge deletes associated contribution records.

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.3.0
    • Fix Version/s: 4.3.0
    • Labels:
      None

      Description

      I'm logging this as a bug since it affects the financial integrity of the system.

      In at least 3.2.x and forward when a membership is deleted the associated contribution is deleted as well.

      This completely compromises the financial integrity of the system.

      Here is a scenario.

      Say 10 memberships of $100 each are paid for by credit card.
      The organization transfers the combined amount ($1000) to their general ledger system.
      The organization decides to migrate the old memberships to a new type.
      Deleting the old and creating new seems logical. (except that the contributions are deleted eventhough no money was refunded.)

      Sometime in the future the organization tries to obtain the detail behind the $1000 general ledger entry.

      Except - the transactions are now gone

      I can't think of a reason why deleting the membership and the payment should be so tightly coupled.
      If it is considered necessary in some contexts then there should be a option on the delete confirmation page to choose to delete the contributions as well.

      – Dave

        Attachments

        1. Picture 63.PNG
          46 kB
          David Greenberg
        2. Screen shot 2011-03-28 at 5.28.17 PM.PNG
          48 kB
          David Greenberg

          Activity

            People

            • Assignee:
              dgg David Greenberg
              Reporter:
              dschafer Dave Schafer
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: