> ## Documentation Index
> Fetch the complete documentation index at: https://docs.port.church/llms.txt
> Use this file to discover all available pages before exploring further.

# FellowshipOne GO

> Required and optional columns for FellowshipOne GO giving imports

Use this guide when your giving export source is FellowshipOne GO.

## Required Columns

| Column         | Description                                                   |
| -------------- | ------------------------------------------------------------- |
| Tax Deductible | Whether the donation is tax deductible                        |
| User Id        | The donor's unique identifier in FellowshipOne GO             |
| First Name     | Donor's first name                                            |
| Last Name      | Donor's last name                                             |
| Category       | The fund or category the donation was given to                |
| Amount         | The donation amount                                           |
| Note           | Used as the **payment method** in Planning Center (see below) |
| Date           | The date the donation was received                            |
| Check Number   | The check number, if applicable                               |

## Optional Columns

| Column         | Description                                                 |
| -------------- | ----------------------------------------------------------- |
| campus         | The campus associated with the donation                     |
| labels         | Labels to apply to the donation                             |
| payment method | Overrides the Note column as the payment method (see below) |
| payment source | The payment source for the donation                         |
| person id      | A Planning Center person ID for direct matching             |

## Setting Up the Payment Method

Planning Center requires a payment method for every donation. You have two options for how Port determines the payment method:

### Option 1: Add a `payment method` column (Recommended)

Add a column called `payment method` to your CSV. When this column is present and has a value for a row, Port uses it directly as the payment method — the Note column is ignored for that row. This gives you full, explicit control without needing to repurpose the Note column.

If the `payment method` column is empty for a given row, Port falls back to the Note column for that row.

### Option 2: Use the Note column (Default)

If no `payment method` column is present, Port uses the **Note** column from your FellowshipOne GO export as the payment method value. Since FellowshipOne GO does not export a dedicated payment method field, you will need to review and populate this column before uploading your file.

**You are in full control of this value.** The Note column is where you define the payment method for each donation. Whatever value you enter in this column is exactly what will be sent to Planning Center. You are not locked into any defaults — review your data, verify it is correct, and set each value to whatever best represents how the donation was received.

### Understanding Your Data

Your FellowshipOne GO export contains two columns that are useful for determining the correct payment method: **Check Number** and **Note**.

* The **Note** column often already contains transaction details from your payment processor — values like "Stripe", "ACH", a credit card type, "Cash", or other descriptors. Review these values carefully. If they accurately describe the payment method, you may be able to use them as-is.
* The **Check Number** column indicates whether a donation was made by check. If a check number is present, the payment method is typically "Check".

### How to Fill In the Note Column

The table below provides suggestions to help you get started, but **you should verify each value matches your records**:

| Check Number             | Note (existing value)                       | Suggested Payment Method       |
| ------------------------ | ------------------------------------------- | ------------------------------ |
| Has a value (e.g., 1001) | Any                                         | `Check`                        |
| 0 or empty               | Contains "ACH", "bank", etc.                | `ACH`                          |
| 0 or empty               | Contains "Stripe", "card", credit card type | `Card`                         |
| 0 or empty               | Contains another descriptor (e.g., "Cash")  | Use that value directly        |
| 0 or empty               | Empty or unclear                            | `Cash` or `Card` (your choice) |

These are suggestions only. You may choose to set all remaining rows to a single value like `Cash` or `Card` if that reflects how most of your non-check donations were received, or you can set each row individually based on your knowledge of the transaction.

### Steps

1. Export your giving data from FellowshipOne GO.
2. Open the CSV file in a spreadsheet application (Excel, Google Sheets, etc.).
3. Review the **Check Number** and **Note** columns together:
   * **If Check Number has a value**, set the Note to `Check`.
   * **If Check Number is 0 or empty**, look at the existing Note value. If it already describes the payment method (e.g., "Stripe", "ACH", "Cash"), you can keep it as-is or standardize it to a consistent value.
   * **If both are empty or unclear**, decide on the appropriate value based on how your church typically receives donations. The two most common non-check transaction types are `Cash` and `Card`.
4. **Verify your data is correct.** Double-check that the Note column accurately represents the payment method for each donation before uploading.
5. Save the file and upload it to Port.

### Common Payment Method Values

Planning Center accepts any text as a payment method. The most common values are:

* `Cash`
* `Check`
* `Card`
* `ACH`

You can use any value that makes sense for your church. Keeping values consistent will make reporting easier in Planning Center.

## Import Behavior

* Header matching is case-insensitive.
* Unrecognized columns are ignored by the parser.
* Setup includes a Remote ID toggle for this provider using the column "User Id".
* This provider does not use the Setup template-download option.
* Matching-relevant columns present in this parser: First Name Last Name person id.
* FellowshipOne GO currently uses the same parser implementation as Church Office Online.

## Related

* [Choosing a Provider](../choosing-a-provider)
* [Uploading Your File](../uploading-your-file)
* [Handling Refunds](../handling-refunds)
