Identifiers use the prefix gc:

The GoodCompany integration processes workplace giving remittance reports from Australian employers. The platform code is gc.

Slugs are lowercased with spaces replaced by hyphens and apostrophes removed.

Campaign hierarchy#

Campaigns support up to three tiers depending on configuration. All donations are grouped under a generic GoodCompany campaign (gc:goodcompany).

When Build account-level campaigns from Site (employer) is on, each employer (Site) becomes a team campaign underneath, keyed by the slugified Site name (for example, gc:acme-corp). Rows where the Site is GoodCompany are direct donations and get no Site campaign.

When Build charity-level campaigns from Gift Name is also on, a third tier uses the combined Site and Gift Name (for example, gc:acme-corp-community-support-programme). When there is no Site campaign — because the row is a direct donation or account-level campaigns are off — the Gift Name campaign is keyed on the Gift Name alone (for example, gc:community-support-programme) and sits directly under the top-level campaign.

Donations and matched gifts#

Each donation is keyed by its Transaction Reference with a suffix that distinguishes the row type:

• -D — the employee donation (a PayrollGiving or CreditCard row).
• -M — the employer match (a MatchedGiving row).

A PayrollGiving row and its paired MatchedGiving row share the same Transaction Reference, so the -D / -M suffix is what keeps their platform keys distinct. Both donations also carry the same receipt number (the bare Transaction Reference). In NPSP, the employer match's Matching Gift lookup points to the employee's Opportunity when both rows are in the same file. See How employer matching works.

Recurring donations#

When Create Recurring Donations is on, a PayrollGiving row with Recurrence = EveryPayCycle from a named donor creates a Recurring Donation keyed on the donor's email (for example, gc:sarah.williams@example.com). Because the key is the email alone, each donor has at most one recurring record for this integration. See Recurring donations and pledges.

Anonymous donations#

Anonymous rows (First Name = Anonymous) have no donor key. The Fundraising and Donations extension assigns the donation to the Anonymous Contact configured in MoveData Settings. The donation still sits under the employer's Site campaign, which is linked to the employer Account.

Related articles#

• Setting up GoodCompany
• Platform Key Syntax overview