CiviCRM Community Forums (archive)

I apologize if this has been answered before - I gave a quick search but could not find anything.

I am testing out whether Civi is an appropriate platform for a small charity I am helping.  While running my test environment, I noticed that the receipt number is, essentially, the transaction_id, and that there is no other real information to be able to regenerate a receipt properly.

Canadian receipting rules require receipts to be serialized, which the transaction ID is.  However, if one makes a change to a receipt, the old receipt must be voided and a new receipt must be generated.  Unless we perform a full refund and re-do the transaction, the transaction ID will stay the same.

Ideally, any change to the receipt would cause a new receipt number to be generated and recorded in the system, and the new receipt would pull the old receipt number into the system.  Any new receipt must say that it is voiding a previous tax receipt.

Further, I see no audit of receipts sent.  I see the one receipt date, but if multiple are sent, I see no log of that.

There are a few other receipt requirements, but these are the main ones right now.  These are a good way to get nailed by CRA and risk losing charitable status in Canada.  Improper receipting is a big no-no, so I want to ensure that there is a feasible solution (obviously we could program something, but I'm hoping a solution exists out there).

Any help would be appreciated.

-Kirk

So what is cancelling doing on the backend?
Is it refunding the donation as well to the contributor?
Is this zeroing out the donation on the database end for accounting purposes?
Is there a way to reference the old transaction when pulling the new receipt (as per the requirements I listed) without manually entering something?

Thanks for your answers Kurund, but given what you have told me, I can potentially see problem with audit trails with CRA.

Anyone else out there have any custom code which satisfies CRA's requirements?

Thanks to some help from a few people, this link was found:

http://groups.drupal.org/node/12979#comment-240173

If it doesn't do the linking to the last receipt, it at least gets us close enough that a little custom code should fix it.