Postings

This page explains the matching and mapping fields that you can use while importing postings. This page serves purely as a reference and it assumes that you already have a basic understanding of the import tool.

Use this import type to import bank postings and manual postings into your system. After importing them, the postings can be processed like other payments as well. For example, as soon as you have imported the postings into your system, the are automatically assigned to orders.

Practical example: Importing new postings

You can find further information about importing and updating postings in the practical example Importing new postings.

1. Matching fields

Table 1 explains the fields that are available for matching posting data. During the import, PlentyONE checks if the imported data record already exists based on the matching field.

Table 1. .Matching fields for importing postings
Setting Explanation

Payment ID

Which column of your CSV file lists the data which is to be used to match the postings? Choose this column here. If the corresponding data already exist in the system, they are updated.
If the data don’t exist yet, the posting is created with the new import data. If you are importing new postings that do not yet exist in the system, you don’t have to select anything for the matching. The postings are then imported without.
Note that with this import, only bank postings and manual postings are imported. Payments of payment providers, as e.g. PayPal or Klarna, are not imported.

2. Mapping fields

This chapter explains the fields that are available for mapping postings. Use these fields to specify which column of your file corresponds to which data field in your system.

Basic procedure:

  1. In your CSV file: Enter a valid import value into a column.

  2. In PlentyONE: Assign this column to the appropriate mapping field.

  3. After the import: Check the result in the back end.

No mapping field? Default value applies!

If you don’t include a certain piece of information in your CSV file, i.e. if you don’t use a certain mapping field, then the posting will be given the default value.

2.1. Payment

2.1.1. Amount posted

Required field

Which posting amount is to be assigned to the payment? Enter this amount into your CSV file.

Default value: No default value

Permitted import values: Numeric

2.1.2. Currency

Which currency is to be assigned to the payment? Enter the currency as ISO code into your CSV file.

Default value: EUR (Euro)

Permitted import values: Alpha-numeric

2.1.3. Posting date

Which posting date is to be assigned to the payment? Enter the posting date into your CSV file. Enter the date in the format you selected in the matching settings for the field Date format in the Import options.

Default value: Day of the import

Permitted import values: Numeric (format as selected in matching settings)

2.1.4. Contact ID

Which contact is to be assigned to the payment? Enter the ID of the contact into your CSV file.

Default value: No default value

Permitted import values: Numeric

2.1.5. Type (Credit/Debit)

Is the posting a credit or debit posting? Enter credit or debit into your CSV file. If you are only importing credit postings, you don’t have to select this matching field. In this case, all amounts are imported as credit postings.

Default value: No default value

Permitted import values: Alpha-numeric

2.2. Payment property

2.2.1. Value

Which payment property is to be assigned to the payment? Enter the value of the selected property into your CSV file.
The following properties are available:
* booking text
* name of sender
* email of sender
* bank code of sender
* account number of sender
* IBAN of sender
* BIC of sender
* name of receiver
You can add the matching field Payment property / Value more than once and then select different properties. Which fields you should add depends on the data in your CSV file.

Default value: No default value

Permitted import values: Alpha-numeric