PSFS Offering - Import: How to format a contribution import file

How to format a contribution import file

You can import contribution data into ParishSOFT by creating a CSV file in a format that ParishSOFT will read. 

 

Creating an Import File

The import file can have any name, but it must be saved in CSV (Comma-Separated Values) format. In Windows, it must have a .csv (comma separated value) extension. The file must contain contribution records only—no pledge records are accepted. To view an example of an import file, see Import File Example.

After you create the file save it to your hard drive. Make note of where you save the file because you will need to locate it when you do the import.

 

Header Information

The first row of the import file contains the header. The header is required and must contain the following information: 

Column

Expected Data

Description

A

H

Identifies the header row.

B

Organization ID

Organization ID.

C

2

Identifies the type of data in the file.

2: indicates that the file contains contributions only.

 

Contribution Data

Contribution data immediately follows the header row. Each contribution record occupies a single row. The following tables detail the required and optional data in a contribution record.

 

Required Contribution Data

The data required in each contribution record is identified in the following table. If a given record is missing any this data, the system cannot import it.

Column

Expected Data

Description

A

C

C: Identifies a contribution record.

B

Envelope #

Family envelope number.

Data in this column is required if your system is configured to use the family envelope number as the preferred identifier for family and member contributions. The option that sets the envelope number as the identifier is located in the Administration module on the Module Settings page. Only a user with organization administrator privileges can configure the option.

If desired, your organization can choose to use the Diocesan ID as the preferred identifier. See description for Column K in the Optional Contribution Data table.   

C

Amount

Contribution amount in xx.xx format.

D

Date

Contribution date in mm/dd/yyyy format.

E

Fund ID

Fund ID from ParishSOFT Offering.  See where to find the Fund ID in the example below.

 

 

Optional Contribution Data

A contribution record can contain the data defined in the following table, but this data is not required. 

Column

Expected Data

Description

F

Check number

Check number. Any combination of alphanumeric characters. Up to 50 characters allowed.

G

Cash, Credit, Check

Payment Type.

H

Memo

Memo text. Any combination of alphanumeric characters. Up to 980 characters allowed.

I

Pledge DUID

Pledge ID. Must be an integer. Letters, symbols, and spaces are not allowed.

J

External Contribution ID

External Contribution ID.

K

Diocesan ID

Diocesan ID. Any combination of alphanumeric characters. Up to 20 characters allowed.

Data in this column is required if your system is configured to use the Diocesan ID as the preferred identifier for family and member contributions. The option that sets the Diocesan ID as the identifier is located in the Administration module on the Module Settings page. Only a user with organization administrator privileges can configure the option.

If desired, your organization can choose to use the envelope number as the preferred identifier. See description for Column B in the Required Contribution Data table.   

L

0 or 1

0: indicates that the contribution is not anonymous.

1: indicates that the contribution is anonymous.

 

Import File Example

The following illustration shows you an example of an import file containing contribution data from non-ParishSOFT systems. Note that the first row contains header information. The remaining rows in the file contain contribution data in the imported records:

 Tim4.jpg

Related Articles

Setting up contribution import in ParishSOFT

Common errors for contribution imports

How to view the details of a batch

How to format contribution export files to fit the "simple import" format

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.