Can't show spouse on donor report

[jodelasur]

Some couples in our branch donate jointly under one donor name. Clerksupport.lds.org tells me that I can show the spouse on the donor report by checking a corresponding box when adding/updating donors, but I can't see the checkbox for this. We have MLS 3.5.2.

[Gary_Miller]

You will find the place to do this under the donors information when you edit it.

[jodelasur]

I still don't see it. Maybe I'm in the wrong window? The image attached is the window I see when I edit the donor.

untitled.JPG (37 KiB) Viewed 1310 times

[Gary_Miller]

Maybe I sent you to the wrong area, I was sure it was in the edit screen. Since I'm at home I don't have MLS in front of me so I can't help at this time.

[Gary_Miller]

This is the best I can do for you without being at the computer.

These are the instructions from the Record-Keeping and Technology Support site.

https://www.lds.org/callings/melchizede ... s?lang=eng

Updating Donor Records

To update a donor record:

1. On the MLS menu bar, click Finance.
2. Click Add/Update Donors.
3. Find the donor, and click on the name. You will see a screen where you can change the donor name, type, and address. For member donors, you can also link donor records to member records by using the Select button. You can also check the box labeled Show spouse on donor report to include the spouse’s name on this person’s donor statements. (This is typically used when a husband and wife make all their donations under the husband’s name).
4. Make your changes, and click Save.

[johnshaw]

It's in the Tithing Settlement area...

[jdlessley]

It's in the Tithing Settlement area...

To what are you referring? There is nothing in Finance > Tithing Settlement to add a spouse to a donor report. This is done in Finance > Add/Update Donors.

I still don't see it. Maybe I'm in the wrong window?

You are at the right place. What is missing is the "Show spouse on donor report" checkbox just below the donor name textbox. I am not sure why it is missing. It may be a bug in 3.5.2 since it was there in 3.5.1.

[jodelasur]

Alright. Hopefully this is fixed in 3.5.3.