Effective date: 7 April 2026 Notice issued: 9 March 2026
This changelog details all changes between the Transactions Export v2.0 and v3.0 specifications. It is intended to help customers update downstream data processes such as CRM upload mappings, data warehouse ETL jobs, and reporting integrations.
Transition period: v2.0 exports will remain available alongside v3.0 after the 7 April go-live date. You do not need to update your downstream processes immediately. We will provide advance notice before v2.0 exports are retired.
Note: Column positions have changed significantly in v3.0. Do not rely on column letter/index - use column headers for mapping.
Summary of changes
17+ new columns added (product/ticket tracking, payout detail, recurring donation detail, linked record model, and more)
16 columns removed (fundraiser-specific columns replaced by a generic "Linked Record" model; Meta and audit fields removed)
10 columns renamed (shorter, more consistent naming)
Several value sets updated (Transaction Type, Status, Gift Aid Status, Processor, Platform, Event Type, Campaign Type)
Column ordering restructured - all column positions have shifted. Map by header name, not position.
Key concept: Linked Records
v3.0 introduces a Linked Record model which replaces the dedicated fundraiser columns from v2.0.
In v2.0, every transaction was assumed to relate to a fundraiser - so columns like Fundraiser ID, Fundraiser Title, Fundraiser First Name, etc. were hardcoded into the export. This worked when the export only covered donations to fundraiser pages, but it doesn't scale to other transaction types.
In v3.0, the export now covers a wider range of transactions including ticket and item purchases, team donations, and donations to fundraiser pages. Each of these links to a different type of record:
Transaction | Linked Record Type | What the Linked Record represents |
Donation to a fundraiser page | Fundraiser | The fundraiser page receiving the donation |
Donation to a team page | Team | The team page receiving the donation |
Ticket or item purchase | Registration | The registration of the person who bought the ticket/item |
The Linked Record columns (BN–BV) provide a consistent set of fields - ID, Type, Title, URL, and the supporter details of the record owner - regardless of which record type is linked. This means customers with downstream processes that previously mapped fundraiser columns should now filter on Linked Record Type = "Fundraiser" to replicate their existing behaviour.
New columns
v3.0 Ref | v3.0 Column | Type | Description |
J | Category | Single select | Billing category: Managed, Assisted, Organic |
M | Platform Fee | Number | Fee applied by the platform (e.g. registration fees on ticket sales) |
O | Product ID | Number | Purchasable product ID (where Type = "Product") |
P | Product Type | Single select | Item, Ticket, or Ticket Group |
Q | Product Name | Short text | Name of the product sold |
R | Discount Code | Short text | Discount code applied (Product transactions only) |
S | Discount Amount | Number | Discount value applied (shown as positive) |
W | Payment Method | Single select | Card, Pending, Link, Pay by bank, Google Pay, Apple Pay, PayPal |
AC | Payout ID | Number | Unique ID of the weekly payout containing this transaction (Social Sync transactions only) |
AE | Payout Status | Single select | Processed, Pending, Held |
AF | Recurring ID | Number | ID for identifying recurring transactions (replaces Frequency) |
AG | Recurring Type | Single select | Subscription, Direct Debit |
AH | Recurring Created On | Datetime | Date + time the recurring donation was first created |
AJ | Display Name | Short text | The name left by the donor |
BN | Linked Record Type | Single select | Whether the transaction links to a Fundraiser, Team, or Registration (see Linked Records above) |
BO | Linked Record ID | Number | The ID of the linked Fundraiser, Team, or Registration |
BP | Linked Record Title | Long text | Title of the linked fundraiser or team page (blank for ticket/item purchases) |
BQ | Linked Record URL | URL | URL of the linked fundraiser or team page (blank for ticket/item purchases) |
BR | Linked Supporter ID | Number | Supporter ID of the linked record owner |
BS | Linked External ID | Number | External ID of the linked supporter record |
BT | Linked First Name | Short text | First name of the linked supporter |
BU | Linked Last Name | Short text | Last name of the linked supporter |
BV | Linked Email | Email of the linked supporter | |
BY | Event Activity | Single select | Event activity type (Walk, Run, Marathon, Swim, etc.) |
Removed columns
v2.0 Ref | v2.0 Column | Notes |
U | Processor Fee | Removed as a standalone column. Processor fees are now factored into the Net Amount (X) calculation |
AB | Grand Total | Removed. Use Gross Amount (H) + Gift Aid Amount (AA) if needed |
AC | Fundraiser Supporter ID | Replaced by Linked Supporter ID (BR) |
AD | Fundraiser External ID | Replaced by Linked External ID (BS) |
AE | Fundraiser First Name | Replaced by Linked First Name (BT) |
AF | Fundraiser Last Name | Replaced by Linked Last Name (BU) |
AG | Fundraiser ID | Replaced by Linked Record ID (BO) where Linked Record Type = "Fundraiser" |
AH | Platform Fundraiser ID | Removed. Use Platform ID (K) or Linked Record ID (BO) |
AI | Fundraiser Title | Replaced by Linked Record Title (BP) |
AJ | Fundraiser Link | Replaced by Linked Record URL (BQ) |
AK | Fundraiser Registration ID | Removed. Registrations are now a Linked Record Type |
AP | Event External ID | Removed |
BC | Meta Full Name | Removed |
BD | Meta Email | Removed |
BZ | Last Modified | Removed |
CA | Last Modified By | Removed |
Renamed columns
v2.0 Name (Ref) | v3.0 Name (Ref) | Notes |
Transaction Date Time (M) | Created On (B) | No change to data; renamed for consistency |
Transaction Type (H) | Type (C) | Values also changed - see below |
Transaction Status (P) | Status (D) | Values also changed - see below |
Sender Currency Transaction Amount (R) | Sender Currency Amount (F) | Shortened name; no change to data |
Transaction Amount (T) | Gross Amount (H) | Clarifies this is the pre-adjustment amount |
Platform Transaction ID (C) | Platform ID (K) | Shortened name |
Processor Transaction ID (F) | Processor ID (U) | Shortened name |
Payout Amount (V) | Net Amount (X) | Renamed and calculation updated - see Structural Changes |
Transaction Message (W) | Message (AK) | Shortened name; no change to data |
Anonymous Transaction (AU) | Anonymous (AI) | Shortened name; no change to data |
Frequency (I) | Removed | Replaced by Recurring ID (AF), Recurring Type (AG), and Recurring Created On (AH) |
Changed values and definitions
Transaction Type (H) → Type (C)
v2.0 values | v3.0 values |
Sponsorship, Donation, Ticket, Purchase | Donation, Product, Offline, Matched, Refund, Chargeback, Chargeback Reversal |
Key changes: "Sponsorship" removed as a distinct type. "Ticket" and "Purchase" consolidated under "Product" (use Product Type column P to distinguish). "Offline" and "Matched" are new types. Refund, Chargeback, and Chargeback Reversal moved here from Status.
Transaction Status (P) → Status (D)
v2.0 values | v3.0 values |
Pending, Confirmed, Successful, Paid Out, Refund, Chargeback, Chargeback Reversal | Pending, Successful, Refunded, Pledged, Pledge Received |
Key changes: "Confirmed" and "Paid Out" removed. Refund/Chargeback/Chargeback Reversal moved to the Type column (C). "Pledged" and "Pledge Received" are new statuses. "Refunded" replaces "Refund" as a status.
Gift Aid Status (AA → AB)
v2.0 values | v3.0 values |
Pending, Submitted, Rejected, Approved, Paid | None, Pending, Approved, Rejected |
Key changes: "Submitted" and "Paid" removed. "None" added as a default value.
Platform (B → I)
v2.0 values | v3.0 values |
Social Sync, Facebook, Instagram, JustGiving | Social Sync, Facebook, Instagram, JustGiving, GoFundMe |
Processor (E → T)
v2.0 values | v3.0 values |
Stripe, PayPal | Social Sync, JustGiving, PayPal Giving Fund, Offline |
Key change: "Stripe" is no longer listed. Social Sync is now the processor for direct transactions. "Offline" used for Matched and Offline donation types.
Event Type (AM → BX)
v2.0 was a generic "Social Sync event type". v3.0 provides specific values: Standard, Own Place, Charity Place, Supporter Created.
Campaign Type (AR → CC)
v2.0 values | v3.0 values |
Fundraising | Fundraising, Programme, DIY |
Other structural changes
Frequency → Recurring fields
The single "Frequency" column (I) with values Single, Monthly, Quarterly, Annual is replaced by three columns: Recurring ID (AF), Recurring Type (AG: Subscription or Direct Debit), and Recurring Created On (AH). One-off transactions will have no Recurring ID.
Net Amount calculation
v2.0's "Payout Amount" (V) was Transaction Amount minus Processor Fee. v3.0's "Net Amount" (X) is Gross Amount minus Discounts, Platform Fees, and Processor Fees - a broader deduction.
Charge Date clarification
The Charge Date (N) description is updated to reference "Meta" instead of "Facebook" and clarifies that non-Meta transactions show the local-time transaction date (aligning with Created On).
Source columns
Source ID and Source Type remain but their values have been updated. Source Type (CG) now specifies "Donation Form" for managed donations, and "Flow" or "Form" for products. Source ID (CF) is now described as a donation form version ID or Flow ID.