Gift Aid T-Casts Questions and Discussion

Suzanne,

Separation of Gift Aid by business unit can be accomplished using separate Gift Aid Types for the arts trust and productions ltd.  Declarations can be made separately for each Gift Aid Type, and optionally secured by control group at this level.  Gift Aid eligible payments are assigned to a specified Gift Aid Type according to the Fund of the contribution.

Regarding declarations made to separate names on a constituent record, as v9.0 stands only ONE declaration is permitted on an account for a particular time period, regardless of the Name indicator on the record.  This restriction has been lifted for v10.0, of which the relevant release note (#1463) is copied here:

Gift Aid Declarations are now able to have overlapping time periods within the same gift aid type.  Previously, adding a declaration with an overlapping time period was not allowed.  The Error message returned has been changed to a Warning message, allowing the user to select OK to continue saving or Cancel to make further changes.  The gift aid update process has been changed to accommodate multiple declarations for the same period.  In all cases, a declaration of ineligibility (eligible checkbox is unchecked) will override a declaration of eligibility.  Overlapping declaration periods in general are not recommended, but these situations can occur, for example, when two constituents are merged.  Changes to w_donor_maint and AP_UPDATE_GIFTAID.

In v9.0 and v10.0 (in beta right now if you are interested in testing!), the Name indicators (N1, N2 or both) on the contribution and the declaration are not considered in the Gift Aid payment eligibility update.  A declaration of eligibility to the appropriate gift aid type will be considered regardless of name indicator for any eligible payment made within the declaration period.   The recommendation when this question arose (regarding specifically the separation of Name on constituent), even when using custom functionality developed by the Network, has always been to separate individuals into separate constituent accounts.  The consideration of N1/N2 on eligibility is something that we have explored, but it is currently not possible.  It is something that definitely fits into the philosophy of the Next Generation project.  As the application currently is structured, it’s not as simple as just looking for Name 1 or Name 2 on the declaration and contribution.  It affects the contact information used (which is largely not separated by N1/N2) and general constituent logic.

-Ryan Creps

Hi, question from our Membership and Development dept. 

Will there be fixes to the standard Gift Aid for identified issues when v10 is released? Specifically, will we be able to save a declaration per named party?

We are not a consortium but we do have two business units, arts trust and productions ltd. On a joint account we could need four declarations; N1 GAT, N1 GPL, N2 GAT and N2 GPL which is not possible in the current version.  Is there a plan to address this or are we going to have to wait for V11?

Thanks, Suzanne 

Suzanne,

Separation of Gift Aid by business unit can be accomplished using separate Gift Aid Types for the arts trust and productions ltd.  Declarations can be made separately for each Gift Aid Type, and optionally secured by control group at this level.  Gift Aid eligible payments are assigned to a specified Gift Aid Type according to the Fund of the contribution.

Regarding declarations made to separate names on a constituent record, as v9.0 stands only ONE declaration is permitted on an account for a particular time period, regardless of the Name indicator on the record.  This restriction has been lifted for v10.0, of which the relevant release note (#1463) is copied here:

Gift Aid Declarations are now able to have overlapping time periods within the same gift aid type.  Previously, adding a declaration with an overlapping time period was not allowed.  The Error message returned has been changed to a Warning message, allowing the user to select OK to continue saving or Cancel to make further changes.  The gift aid update process has been changed to accommodate multiple declarations for the same period.  In all cases, a declaration of ineligibility (eligible checkbox is unchecked) will override a declaration of eligibility.  Overlapping declaration periods in general are not recommended, but these situations can occur, for example, when two constituents are merged.  Changes to w_donor_maint and AP_UPDATE_GIFTAID.

In v9.0 and v10.0 (in beta right now if you are interested in testing!), the Name indicators (N1, N2 or both) on the contribution and the declaration are not considered in the Gift Aid payment eligibility update.  A declaration of eligibility to the appropriate gift aid type will be considered regardless of name indicator for any eligible payment made within the declaration period.   The recommendation when this question arose (regarding specifically the separation of Name on constituent), even when using custom functionality developed by the Network, has always been to separate individuals into separate constituent accounts.  The consideration of N1/N2 on eligibility is something that we have explored, but it is currently not possible.  It is something that definitely fits into the philosophy of the Next Generation project.  As the application currently is structured, it’s not as simple as just looking for Name 1 or Name 2 on the declaration and contribution.  It affects the contact information used (which is largely not separated by N1/N2) and general constituent logic.

-Ryan Creps

Hi, question from our Membership and Development dept. 

Will there be fixes to the standard Gift Aid for identified issues when v10 is released? Specifically, will we be able to save a declaration per named party?

We are not a consortium but we do have two business units, arts trust and productions ltd. On a joint account we could need four declarations; N1 GAT, N1 GPL, N2 GAT and N2 GPL which is not possible in the current version.  Is there a plan to address this or are we going to have to wait for V11?

Thanks, Suzanne