pixi enables you to import payments and match those payments with invoices or orders for bookkeeping purposes. In the Import Payments wizard you can import the following bank file types:
Import Payments from CSV File
Import ESR/ISR Payments in camt.053 Format (only Switzerland)
Mapping of Bank Accounts with Bookkeeping Accounts
For importing bank files you have the option to match bank accounts with bookkeeping accounts. To enable this matching set the Query and use bookkeeping bank account option in pixi Control Center > Database Settings tab > Payments folder > DATEV export folder. When enabled, the Import Payments wizard contains an additional step, where user has to review the accounts matching information and specify missing information. The accounts matching information is stored in the Mapping of bank accounts to bookkeeping accounts setting. When disabled, the bank accounts are not matched to bookkeeping accounts and this step is skipped in the Import Payments wizard.
Warning: This setting will work correctly only if all data in the bank file is related to a single bank account. In case there are multiple accounts in one file, only the first bank account found will be matched.
The values for matching a bank account to a bookkeeping account are stored with the Mapping of bank accounts to bookkeeping accounts setting. Note that these values can also be saved if a pixi user selects the option Save matching information in the Import Payments wizard.
Note: If a user does not enter the bookkeeping account, the bank file will not be matched to any bookkeeping account number.
Import Payments from Bank Files
You can import payments to pixi in the pixi Payments application. To open the Import Payments wizard click Import on the right side of the All Payments tab.
Step 1 - Choose import type
In the Import Payments wizard select the option Import from a local file and click Next.
Step 2 - Add files
Click Add… to select the bank file to import. You can also import a batch of files. The file type is set automatically.
Select Payment Currency. This currency will be added to all payments in this file where the currency is not provided by the bank.
Click Next.
Step 3 - Bank accounts
Review the information for matching the bank accounts to the bookkeeping accounts. In case of missing matching information, manually enter the required Bookkeeping Account number. To save the account matching information for future imports, click the option Save matching information. Note that if account matching is not required, this step is skipped. Then click Next.
Note: The Bank account – Bookkeeping account pairs are saved in the form 123456, 0987654; 3456789, 0987654. Number 123456 is the first bank account and is separated from the first bookkeeping account 0987654 with a comma (,). The next account pair is separated from the previous one with a semicolon (;).
Step 4 - Start import
-
Select additional import options as required:
Move to »\processed« subfolder – A new folder is created and all processed files are moved to that location.
Add ».timestamp.done« suffix to filename – A timestamp is added to the filename.
Close window upon successful completion – Automatically close the wizard if the import is completed. The import log file is not displayed. In case of errors with the import, the log file is displayed.
Refilter payments in main window when closing – After the wizard closes, the payments view in the main window is refreshed to display the newly imported payments.
Click Next to start the import process.
Step 5 - Import
The progress of the import process is displayed. Note that the import cannot be canceled for files that have already been imported or for the ones that is currently in progress. You can only cancel the import for files that are still waiting in queue.
Step 6 - Import completed
When the import process is completed, the log file is displayed. Click Finish to exit the wizard. Note that if you selected the Close window upon successful completion option, the wizard closes without displaying the log after successful import.
Import of SEPA Payments via MT940 Format
When you import SEPA payments via MT940 format, IBAN and BIC will be transferred to the transaction details of the payment.
When SEPA payments are matched to an order or an invoice, the BIC and IBAN will be transferred to the order/invoice details in pixi Customer Service. pixi supports import of IBAN and BIC from the following positions in the SEPA payment file: ?30, ?31, ?20, ?21, ?22+?23. The following combinations are possible:
?30?31 – Example: ?30ABCD1234?31DE123456789000000000
?20?21 – Example: ?20ABCD1234?21DE123456789000000000
-
If „BIC“/„BIC:“ or „IBAN“/“IBAN:“ is written in the file, pixi also recognizes the following combinations:
?21IBAN DE123456789000000000?22BIC ABCD1234?23(leer)
?21BIC: ABCD1234?22(leer)?23IBAN: DE123456789000000000
?30IBAN: DE123456789000000000?31BIC: ABCD1234
To improve compatibility with changes for SEPA 2014, import of payment data has been enhanced for LOU Update 19 and ELI Update 11. SEPA allows one unstructured reference of 140 characters (SVWZ - SEPA-Verwendungszweck). In MT940, each field can have max. 27 characters - this means that the 140 characters of the SEPA reference need to be distributed to the MT940 fields. Based on the keyword ‘SVWZ’ which refers to the reference text of a payment, all necessary fields from the MT940 bank file that contain the reference text are imported to ‘Text data – 01’ in Transaction properties > General tab.
When using MT940 files to import SEPA payments, the reference fields (?20-29) are used for information that is specific for SEPA format:
MREF - Mandate reference (Mandatsreferenz)
EREF - End-to-end reference (Ende-zu-Ende-Referenz)
KREF - customer reference (Kundenreferenz)
CRED - creditor ID or DEBT - Debitor ID
SVWZ - SEPA unstructured reference (max. 140 characters) (SEPA-Verwendungszweck)
ABWA - Different payment initiator (Abweichender Auftraggeber)
ABWE - Different payment receiver (Abweichender Empfänger)
Transaction signature (PIXIX…) which is transferred within the SEPA XML for direct debits in the end-to-end reference (EREF) to the bank, is imported from bank file (MT940 format) to field ‘Text data – 02’ in transaction properties > General tab. This assures proper automatic matching and moving SEPA/DTAUS records from “Sent to Bank” to “Completed” folder. This functionality is available from pixi LOU Update 21 and pixi ELI Update 12.
If keywords SVWZ or EREF are not included, everything stays as it is - we import fields:
text1 = field ?20
text2 = field ?21
-
text3 = fields ?22+?23
Note: From pixi LOU Update 30 and AVA Update 6 ‘Text data – 03’ contains the complete text from fields ?20 to ?29 in order to assure that all information from the payment file is available for payment matching.
bank code/BIC = field ?30
account nr/IBAN = field ?31
customer name = fields ?32+?33
Import of Payments in ESR/BESR Format
A payment file in ESR/BESR format contains only one dataset, which is approximately looking like this:
0020100092577372500999900000001012860340000003280110397606514110314110414110400000000000000000000000
If you choose a payment file with this information, the import is done as follows.
The old format was renamed to "ESR/BESR (old)" and a new format was added "ESR/BESR". When ESR/BESR format is identified at bank file import, the old format "ESR/BESR (old) is used by default. The new version "ESR/BESR" has to be manually selected from the drop-down list.
Text 03 = Characters 13-18 (737250) [Client ID]
Text 02 = Characters 19-38 (09999000000010128603) [Invoice / Reference Code]
Text 01 = Text 03 + Text 02 + Character 39 (737250099990000000101286034) [Reference Code incl. Client ID + Check Digit]
Amount = Characters 40-49 (0000003280); this equals 32.80 CHF
Date = Characters 72-77 (141104) in format YYMMDD