Import Files - FAQ

1. When selecting a file we get BLOB is not a valid UTF-8 string

The most common cause for this is importing a file that is not a CSV (for example, importing an Excel format file).  Check you're importing a CSV.  If that doesn't solve it, try the steps below.

When selecting a file we get BLOB is not a valid UTF-8 string

1.1. Open with Notepad and Save as UTF-8 format

Open with Notepad and Save as UTF-8 format

The simplest way to fix this is to open with windows notepad, then select File > Save As - Next ot the SAVE button, select "UTF-8" from the encoding picklist and then SAVE.

2. How do we create recurring payments from Import Files?

For the import process to create a recurring payment, you need to map:

  1. Frequency AND
  2. Billing Token (credit card token) OR
    Card, Expiry date and optionally CCV

Ensure the values of the frequency match exactly with one of the valid picklist values.  Failure to do so might result in the frequency being treated as daily.  Valid values include: Daily, Weekly, Fortnightly, Monthly, Bi-Monthly, Quarterly, Six Monthly, Annually, Two Yearly

Ensure the values of the frequency match exactly with one of the valid picklist values.  Failure to do so might result in the frequency being treated as daily.  Valid values include: Daily, Weekly, Fortnightly, Monthly, Bi-Monthly, Quarterly, Six Monthly, Annually, Two Yearly

3. What fields are required to import tokenised cards?

When importing and uploading you should try and include as much contact information information as possible.  This will help for the matching de-duplication.

As a minimum the following are required:

  • Last Name
  • Billing Token
  • Frequency
  • Amount or Donation Amount

Recommended additional fields

  • First Name
  • Email
  • Phone and/or MobilePhone
  • Address (in particular city/suburb)

If you are looking at importing cards that have already been charged and you'd like the next payment to be scheduled, then you will need to have the next payment due date as well.  The setup of this is currently outside of the product and our support, please contact to purchase premium support or consulting services.

4. How can I Import Direct Debits?

For Direct Debits, your Import File type selected on the first step must be "Direct Debit".  From version 6.14, the name can have a " - suffix" appended to the name, e.g. "Direct Debit - Initial Load".

The Direct Debit mapping is not delivered with the product by default.  You will need to set this up on the first import by saving the Import File Template on Step 2 as Direct Debit.

Make sure you map the Account No. and BSB fields as part of the import

Note: If your import file is for initial loads only and you do not wish to create Opportunities, then select "Contact Load Only" checkbox on the first step of the import wizard.

5. Do I need to do anything about the warning that is displayed in step 2 of the import file process?

The warning "This Import Line Item field has no equivalent in the Payment Txn Object" message indicates that the Import is being uploaded, but will not stored on the Payment Txn object as part of the down stream processing.  Many of these fields have special meaning and are only temporarily used as part of the upload process.

However, should you add a custom field to the Import File Line Item record and this message appears, then it may indicate that you have an issue or a typo.  The normal reason for adding a custom field is so that the imported (Import File Line Item) is so data is uploaded to the Import File Line Item and once the Import File is processed, this value will be copied to a field with the same API name on the Payment Txn.  The ultimate aim is to then have the field on the Payment Txn copied to the field of the same API name on the Account, Contact, Opportunity or Campaign Member objects when the batch processor runs.

6. How many rows of data can I Import?

The imports are not restricted by the number of rows, but by the overall size of the CSV file. If you have a smaller number of columns, then you can Import more rows of data.  As a general guide, you should be able to import 30,000 and possibly upto 55,000 rows of data.

Should you require more rows of data than allowed, then simply split your files into multiple CSV files and import seperately.

7. Should I import Credit Card and Direct Debits in the one Import Batch?

Our recommendation is to split the two imports out.  One particular thing to keep in mind is that Direct Debits need to have the Import File Type set to Direct Debit (See FAQ above on How to Import Direct Debits.

8. Should we import fundraisers first?

Absolutely.  In particular if you are looking to Soft Credit a fundraiser, then we recommend importing the fundraisers and selecting the "Contact Only Load" on the first step.

The Contact Only Load checkbox will import the contact and de-duplicate the contact with existing contact or create a new contact if they do not already exist.  This will NOT create any related opportunities though.

Loading the contact first will ensure the contact can be found and when using the Nonprofit Success Pack, can be soft credited for with the subsequent uploads.

9. Fundraisers are not being correctly matched, or are Created and linked to the wrong Account/Household

Import the Fundraisers First


Most of the 3rd party providers only provide a few details about the fundraisers in their import files.  These details are often just First Name, Last Name and Fundraiser Id's.

The Matching Process relies a lot on the Fundraiser Id on the Contact record already existing.  The best practice is to Import the Fundraiser details first, then import the donation details as a second import.

When importing the Fundraiser Details, you can use the "Contact Load Only" option so that the process does not expect to be processing donations.  If this option is checked, the creation of opportunities will be turned off.

Note: Make sure when the fundraisers are imported to be created as contacts first, map them to the First Name, Last name fields. Then in the donor import after the fundraiser import, the fundraisers' first and last names are to be mapped to Fundraiser First name, Fundraiser Last name fields.

10. When I process the batch, the "Import File Line Item Payment Txn's" are not being created

To try and locate the cause of this, please check the following.

  1. Check error logs.  First check against the import file line item to see if there is an error reported.  If not, go to the Error Log tab and look at Errors created for today.
    This is the most likely area to have the reason for the error.  It could be that a validation rule or a process builder that has been added to your instance is causing the issue and the error log will contain a description of the issue.
  2. Check on Import File Line Item and Payment Txn. Are there any fields with the same API name. E.g. AAkpay__receipt_number__c is the same as receipt_number__c.  Please check all custom fields that have been added.  It might be that we've added a field with the same name to a future release and that is why it is now causing an issue. Rename the custom field with a duplicate name.
  3. Navigate to Setup.  Search "Apex Jobs".  Locate the importprocessor jobs. Does an error show here?
  4. Make sure you are on the latest release of Payments2Us


11. In Peer-to-Peer imports, the fundraiser's contact role is being listed as Soft Credit, but I want it to be listed as Fund Raiser. How do I update it?

The NPSP application allows for soft crediting to contacts. It is based on the the contact role field is part of the Payment Item object.

1. Go to Setup>Object>Payment Item and select Record Types in the left hand menu

2. Select the Soft Credit record type.

3. Select Edit next to the Contact Field.

4. Select Fundraiser as default.

You can repeat this procedure if you want to add the same or different default to other Record Types.

Once the fundraiser and donor details have been imported, the fundraiser contact will be added to the payment item as the Fund Raiser in their contact role and will be soft credited for that donated amount. For more information on how the NPSP soft crediting works, visit

12. Why can users not save the Import File Templates or they are getting an access error to Import File Settings Object

The template mappings are saved into a Custom Setting File called AAkonsult Import File Settings.  The users will need to have the profile setting "Customize Application" enabled.

For more information on custom settings, please see

13. Which Campaign is allocated if there are multiple campaigns with the same name - e.g. John’s Birthday

Campaigns that are visible to the user and are active are considered.  If multiple Campaigns with the same name exist, then the one with the highest Start Date is used.

14. I keep getting errors with "Bad value for restricted picklist", but I checked and the value is exactly as it appears in the picklist. What's wrong with it?

Check to see if the picklist that is being used is a Global Picklist. If so, you need to use the API Name value instead of the  "Values" value.  Regular local restricted picklists use the Value field.

If possible, set the Values and API names in your Global Picklist to the same values to make this step easier.

15. How do I remove old custom import templates that I don't use any more?

The templates are stored in a Custom Object called "Import File Mappings".  

Payments2Us does not include a tab for this by default for the package.  You can add a Custom Tab under setup.  

After adding the Custom Tab, you will be able to then see the entries and remove those that you do not currently need.

16. How to Import Tokenised Credit Cards?

To import tokenised Credit Cards and to make sure the recurring payments are created with Record Type "Credit Card", follow the steps below.

The key thing is to set  Payment Source to “Credit Card”. To do this, save the Import Type Template as "Credit Card". Alternatively add a workflow update that change the import file line item “Payment Source” from say “Credit Card – Token Load” to “Credit Card”.

Also make sure to map these fields below to create recurring payments.

       Frequency AND

       Billing Token (credit card token)