Fix a donation that isn't counting toward compliance

If a gift you expected to be disclosable shows no cap usage or disclosure obligation, its revenue code is almost always the reason - here is how to find the cause and fix it.

A donation counts toward a jurisdiction only when both are true:

• It has a revenue code.
• That code is assigned to the jurisdiction you expect (Federal or a state regime), not left Unregulated.

That assignment, not the amount, is what creates a cap or disclosure record. For the full setup, see Set up revenue codes.

You assign a jurisdiction to each code at Settings -> Compliance -> Revenue codes.

Click to expand

×

Find the cause

Open the donation and check its revenue code. One of these is almost always the reason it isn't counting:

• No revenue code. A donation with no code is Unregulated and counts toward nothing.
• The code is set to Unregulated. The code is in your library but has no jurisdiction yet.
• The code came from your CRM but isn't registered. A code arriving from your CRM for the first time lands Unregulated until you assign its jurisdiction.
• A duplicate was removed and the untagged copy was kept. See Keep the tag when you remove a duplicate below.

Fix the code's jurisdiction

If the donation already carries a code that is Unregulated or set to the wrong jurisdiction, fix the code, not the donation. Go to Settings -> Compliance -> Revenue codes, find the code, and assign its jurisdiction. Every donation on that code recomputes, whatever its source. This is the most common fix.

Add a code to a donation that has none

What you can change depends on where the donation came from:

• A manually recorded gift: open the donation, edit it, set a code assigned to the right jurisdiction, and save. Only manually recorded gifts can be edited this way.
• A donation-form or checkout-link gift: you can't re-tag an individual gift after the fact. Set the revenue code on the form or checkout link so future gifts carry it, then assign that code its jurisdiction.
• A gift synced from your CRM: set the code in your CRM, then pull it in - see Fix a donation synced from your CRM.

Fix a donation synced from your CRM

Set the tracking code on the donation in your CRM, not in Together. That keeps both systems in agreement and the change survives future syncs.

1. In your CRM, open the donation and set its tracking code (NationBuilder) or campaign (Raisely). Use a code you have already assigned to the right jurisdiction in Together. Spelling and punctuation must match; capitalisation does not.
2. Pull the change into Together. The next scheduled sync applies it. To apply it immediately for a NationBuilder donation, open the donor's record and click Sync from NationBuilder - that re-reads the donor's NationBuilder donations, applies the updated tag, and refreshes their compliance totals (requires ADMIN). For other CRMs, wait for the next scheduled sync.
3. If you used a code Together has not seen from that CRM before, it arrives Unregulated. Go to Settings -> Compliance -> Revenue codes, find the new code (it carries a badge showing which CRM it came from), and assign its jurisdiction. Totals recompute as soon as you save.

Together keeps a separate library entry for the same code text depending on where it came from. A code you created for manual gifts is a different entry from that same word arriving from your CRM, and each entry has its own jurisdiction. A CRM donation must carry a code that is registered against that CRM - a manual-only code with the same spelling will not give it a jurisdiction.

Keep the tag when you remove a duplicate

Sometimes the same gift is recorded twice: once entered by hand and once synced from your CRM. When you remove one of the two, keep the copy that carries the jurisdiction revenue code, or re-tag the copy you keep.

If you void the tagged copy and keep an untagged copy, the money is still recorded but the gift no longer counts toward any jurisdiction. A donation that looked compliant before the cleanup quietly drops off the compliance totals. Before voiding a duplicate, check which copy carries the code, and make sure the surviving donation is tagged.

Confirm it worked

Compliance totals recalculate on their own after any of these changes. You do not run anything.

• Open the donor and check their compliance view. The donation now counts toward the jurisdiction you set.
• If the donor has crossed the disclosure threshold for that jurisdiction, a disclosure obligation appears for them.
• The Compliance dashboard reflects the updated cap usage, and the donor surfaces in the attention list if they are approaching a cap.

What to read next

• Set up revenue codes - assign every code in your library to a jurisdiction.
• Connect NationBuilder or Connect Raisely - how donations and codes flow in from your CRM.
• Resolve a compliance alert - clear the alerts a new obligation can raise.