nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Recurring Gift Carry Over Fields

Lee Grisham

Good day all,

Does anyone know specifically what fields carry over when a Recurring Gift creates a Payment? There is some information we must put in each batch when the payment comes through, but there are a few fields that are universal that could minimize field entry if they would automatically be added to the Payment Record.

Thanks!

Update: When in a training, a recurring gift payment would have the same Attribute from the Recurring Gift record. I have not seen that applied in my database. Any ideas as to why? Does it have something to do with creating them in DB view instead of NXT?

Find more posts tagged with

Comments

Cathleen Zinn

@Lee Grisham

It will populate the campaign and fund fields, but not the appeal or package.

Carrie Aranda

@Lee Grisham, are you using automatic recurring gifts set up in RENXT? If so, then the fields set up on the recurring gift will be on the automatic recurring gift payment. For us, the only field we have to change in NXT batch is the Post to GL date (our rules require it to match the BBMS deposit date). Otherwise, gift subtype, campaign, fund, appeal, letter code, etc are all automatically set on the payment.

Lee Grisham

@Carrie Aranda, yes, all NXT gifts. We would really like to use the Reference/Comments field and any Custom Fields/Attributes as they keep our CC information that we use for reporting (not the numbers of course). Processing fees are important for our finance to reconcile the bank side and those are in Attributes.