SEPA aims to improve the efficiency of cross-border payments and turn the fragmented national markets for euro payments into a single domestic one. It enables customers to make cashless euro payments to anyone located anywhere in the area, using a single bank account and a single set of payment instruments. Therefore it will replace the existing DTAUS standard for direct debits and credits. The DTAUS file format will be replaced by the ISO SEPA XML format based on European standard ISO 20022.
pixi supports both transaction types, DTAUS and SEPA as part of the pixi Payments application. Records for DTAUS or SEPA direct debits are automatically created, when an invoice with payment type "Direct Debit" is scanned for ship out in the pixi Shipping application. Additionally records for credits are created, when return cases are created and the invoice amount is refunded.
All important information about the SEPA introduction in 2014 as well as detailed version information you can find here: SEPA Introduction 2014
Configuration and Setup
Settings for DTAUS Export
Settings for DTAUS Export can be changed in Control Center > Database Settings tab > Payments folder > DTAUS Export subfolder:
Account name for DTAUS: enter here the name of your shop, this value will be shown as recipient of the payment in case of direct debits or as sender of the payment in case of credits.
Account nr. for DTAUS: bank account number for DTAUS transactions
BLZ (Bankleitzahl) for DTAUS: Bank code number (branch exchange code)
City for DTAUS: city of the branch of the bank where you opened your bank account
Default LS method: Select a default payment request method. It is used where payment method is not directly specified on the record. Possible values are Debit and Collecting.
DTAUS Include order number: When turned on, in addition to the customer (account) name also the order number(s) will be exported to the DTAUS file.
Reason for DTAUS/SEPA – A text that is displayed for this transaction on customer's balance sheets. It can be a short note to give the customer a clue who and why debited his bank account, e.g. "Thank you for shopping at www.pixi.com."
The setting DTAUS / SEPA by Shop defines if separate files are created for each shop. If enabled, DTAUS / SEPA export creates separate DTAUS or SEPA files for each included shop and uses the specific settings available in the Shops table. If the values in the Shops table are not set, the corresponding values from the Database Settings > Payments > DTAUS / SEPA export folder are used. If disabled, DTAUS / SEPA export creates a single DTAUS or SEPA file for all included shops and uses the values from the Database Settings > Payments > DTAUS / SEPA export folder.
Settings for SEPA Export
The introduction of SEPA standard influences the processing of direct debits and credits in pixi. To include all necessary information into the SEPA XML file, creditor ID, IBAN and BIC of the shop need to be defined in the pixi Control Center. Please also check information in SEPA Introduction 2014.
If you have only one shop or use the same bank account for all the shops, you can enter the creditor ID, IBAN and BIC to the Database Settings (in pixi Control Center > Database Settings tab > Payments folder > DTAUS/SEPA Export sub-folder):
Enter your creditor ID to the Shop Creditor ID setting.
Enter the BIC and the IBAN of your shop's bank account to the Shop BIC and Shop IBAN settings.
Set the setting DTAUS / SEPA by Shop to OFF.
If you use different bank accounts for your shops:
The creditor ID, IBAN and BIC for each shop must be entered to the pixi Control Center > tab Tables > Shops table. Please contact pixi Support since you cannot edit entries in the table Shops.
Set database setting DTAUS / SEPA by Shop to ON to create separate SEPA files per shop.
Note: Currently SEPA XML file per Shop cannot be created if DTAUS values for a shop are left empty. This is fixed in pixi AVA Milestone 3, but not on LOU and ELI versions.
Mandate reference
You can use the mandate reference via the SEPA - Mandate reference (pixi Control Center > Database Settings > Payments > DTAUS / SEPA Export) database setting in addition to the IBAN, the DATEV account number and the customer number for exporting a SEPA file.
Direct Debit Type, Collection date and Execution date
The following direct debit types are available:
CORE - B2C (Business to Consumer) direct debit.
COR1-related to CORE DD type, but with a shorter time cycle (minimum 1 day).not supported anymore; replaced with COREB2B - Business to Business direct debit.
You can choose your direct debit type per shop on your own. Enter the direct debit type in pixi Control Center > tab Tables > table Shops in the column "SEPA Direct Debit Type" (use short names as listed above, e.g. "COR1"). This setting also needs to be set in case you're exporting one file for all shops ("DTAUS / SEPA by Shop" set to OFF) - please set the same value for all shops in that case to prevent issues when creating the SEPA XML file.
Version information: In versions before pixi LOU Update 19 and ELI Update 11 only CORE is supported, from LOU Update 19 and ELI Update 11 on, it is COR1. In versions from ELI Update 15 on, the direct debit type can be selected by shop, editable by the pixi administrator.
The collection date for direct debits and the execution date for credits are automatically calculated by pixi:
For manual credits, manual refunds and returns, the execution date is the date the SEPA XML was created on.
The collection date for direct debits is calculated based on the invoice date. To follow the SEPA standards, a default execution time can be defined which is then added to the invoice date. The Default Execution Time is defined pixi Control Center > Tables tab > table Shops > column "SEPA direct debit - Execution Time". By default an execution time of 5 days is set. The pixi administrator can edit this value.
Note: In versions before pixi ELI Update 15 the default execution time is set per payment type in the table Payment Types. Please contact pixi Support if you want to change a value or update to a newer pixi version.
Reference for SEPA payments
It is possible to define the content of the reference of SEPA direct debits and credits created with pixi. The database setting SEPA Include Order Number in pixi Control Center > Database Settings tab > Payments folder > DTAUS / SEPA export enables you to additionally include the external order number from shop in the SEPA export file (reference field).
The reference of SEPA transactions therefore contains the following information:
Order number external (if DB setting ‘SEPA include order number’ is enabled),
invoice/credit number (from Customer account reference),
Customer name.
Note: Until pixi AVA Update 1 and pixi LOU Update 25, it is not possible to adapt the reference for SEPA payments by using the setting "Reason for DTAUS/SEPA" in table Shops or database settings. If you want to inform your customers about the name of your shop and therefore prevent confusion on the customer's side about the recipient of a direct debit, you can use the setting "Account name for DTAUS" as described in DTAUS settings.
Batch booking
Batch Booking is defined with a tag <BtchBookg> within the SEPA XML file.
Batch booking = true: The transaction is a single consolidated debit or credit (sum of all of the payments).
Batch booking = false: Included transactions are processed separately, as multiple debits or credits (for each payment within the file).
Most banks default this value (in case the batchbooking tag is not included in the SEPA xml) to give you a consolidated transaction, but other banks may default it to multiple individual transactions (check with your bank if/how they have it). In case the bank’s default value doesn’t match your requirements, you can control the value of the batch booking tag in SEPA XML files created by pixi with a setting in pixi Control Center > Database Settings > Payments > DTAUS/SEPA Export folder:
SEPA - Debits - Batch booking mode: When on, the batch mode for SEPA credits is activated (XML Tag <BtchBookg>true</BtchBookg>).
SEPA - Credits - Batch booking mode: When on, the batch mode for SEPA credits is activated (XML Tag <BtchBookg>true</BtchBookg>).
In case the SEPA Direct Debit XML is created with batch mode enabled, then the earliest collection date of any included debits is used for the whole batch. Please note: many banks require a special agreement to be signed in order for the batch mode to be possible to use.
Create and transfer Direct Debits and Credits to the bank
If an invoice with payment type Direct Debit is scanned at Ship Out, a new entry is created automatically in table "Data Preparation - Charge". If a return is created in pixi Customer Service or a manual refund, a new entry is created in table "Data Preparation - Credit".
A DTAUS/ SEPA record is created, if
invoice with payment type Direct Debit is scanned at ship out in pixi Shipping,
an invoice has status EIN and is older than 3 days,
a return is created and the refund is created.
Data preparation
The data preparation in pixi Payments > tab Batch Bank Transfer (DTAUS/SEPA) is separated into 2 parts:
Folder Data Preparation - Charge for direct debits. Here you find all records for customer payments which need to be charged from customers bank account.
Folder Data Preparation - Credit for credits. Here you find all records for open payments that need to transferred to the customers bank account, e.g. in case of overpayment by the customer or in case of a refund.
All transactions that were not transferred to the bank, yet, are shown here. Select multiple lines with CTRL + click on mouse or SHIT + up/down.
Refresh
Update list of transactions:
Refresh data after a change was made to an existing transaction.
Refresh data if new transactions have been created.
Delete
Select a transaction in grid and click on Delete button in toolbar. Only transactions with status "pixi data error" and "Ready for bank" can be deleted.
Create DTAUS LS and Create SEPA LS
Selected transactions are saved to bank file. Before saving, an error check is performed. If an error is found, the creation of the file fails. You can create a file and save it in DTAUS or SEPA format:
LS (Lastschrift) - direct debit: Customer owes money to company, it will be withdrawn from his bank account.
GS (Gutschrift) - credit: Customer returned items etc., so money will be returned to his bank account.
Properties
You can edit properties of selected transaction(s). Error check is performed each time before saving. Changes are saved. Errors are also saved, but you have to confirm warning pop-up window before saving.
History – You have an overview or every change that has been made to the selected DTAUS transaction.
Matches – No matches exist in this phase because DTAUS/SEPA files were not created yet.
Create a Bank File
Are all records ready to be transferred to the bank, you can create a bank file:
Select a transaction from table "Data Preparation - Charge" or "Data Preparation - Credit". Only status “Ready for Bank” is accepted.
If you want to create a DTAUS file, click on "Create DTAUS LS" button for direct debits or "Create DTAUS GS" button for credits.
If you want to create a SEPA file, click on "Create SEPA LS" button for direct debits or "Create SEPA GS" button for credits.
Save the created bank file to a hard disk or any other storage device. Successfully saved transactions are put to "Sent to Bank" status.
The SEPA XML does not allow any special characters. Therefore, they are removed or replaced before the creation of the XML from ELI Update 14 on:
Replacements: ü, ö, ä and ß ->ue, oe, ae and ss
Allowed characters: ['0'..'9'] + ['A'..'Z'] + ['a'..'z'] + [' ', '.', ',', '&', '-', '/', '+', '*', '$', '%']
Match successful credits and debits
List of transactions that were sent to the bank and are now waiting to be auto-matched or manually matched with selected payment are displayed in "Sent to Bank" table. See also documentation for payment import and payment matching.
When the DTAUS file is formed, each record receives an automatically generated signature. The signature is placed to DTAUS/SEPA file so that the bank sends it back in the information about the transactions that happened - the bank import file. The system is then able to find that signature and match the payment to the transaction.
Auto Matching
Button "Auto Match" starts automatic matching between imported payment files and DTAUS/SEPA transactions. Please note that you can define with the setting "Run DTAUS match automatically at 1am" (pixi Control Center > tab Database Settings > folder Payments > DTAUS/ SEPA Export) that matching is done every night automatically.
Note: Please note a special change because of SEPA introduction 2014: 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.
New Match (manually)
Manually select DTAUS/SEPA request to match with bank statement:
Select a transaction from the grid. Only status »Sent to Bank« is accepted.
Click on the New Match button on the toolbar.
-
Enter search criteria:
Customer name is already prefilled. You can delete existing text or extend or enter your text to limit search results.
Date from – Date to: Select date and mark the checkbox to make date criteria active.
Amount from – Amount to: Amount to is already prefilled (copied from transaction) and cannot be changed.
Text: There are three text fields in the payments file for comments.
Imported from file: Enter the name of the file from which payment was imported.
Press Search button.
Select a matching result and press OK.
Reprocess
In case the matching process was not successful, you can move the transaction back to the Data Preparation page.
Note: You can only select records with status Refused by bank. Records with other statuses will be ignored.
Properties
You can check DTAUS request properties.
History – You have an overview or every change that has been made to the selected DTAUS transaction.
Matches – Transactions that are still in process do not have assigned matches.
Completed transactions
Only transactions that have been successfully matched and then confirmed by the bank are displayed here.
Delete Match
Remove all matches to selected transaction. Transaction is sent back to "Sent to Bank" page (In process).
Properties
You can check DTAUS request properties. Each completed DTAUS request has its match which is displayed here.
History - You have a complete overview or every change that has been made to the selected DTAUS transaction
Matches - Currently matched payment details are displayed here: Bank date, Payment amount, Matched amount, Customer, Manual or automatic match, Business code, Import date; Bank file location and comment are also displayed on Matches tab.
Search
You can search for completed transactions. Results can be limited by defining entry date, amount (from – to) and account details (account name, account number, BLZ, customer name).
Handle payments refused by the bank
Example: The bank approves the transaction and sends you the bank file that you can match with DTAUS/SEPA request. The transaction is marked as completed and stays in the Completed folder. If the bank later discovers that the customer has no money in his account or if the customer refuses to pay for any reason, the bank can withdraw the money from your account. In that case, they send a new bank file which includes the data about rejected transactions for the same request that was previously approved. Such DTAUS/SEPA request is now moved from Completed to Refused by bank.
SEPA XML – examples for direct debits and credits
XML structure for direct debits
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.003.02"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.008.003.02
pain.008.003.02.xsd">
<CstmrDrctDbtInitn>
<GrpHdr>
<MsgId>20140605084436662</MsgId>
<CreDtTm>2014-06-05T08:44:36.662Z</CreDtTm>
<NbOfTxs>1</NbOfTxs> <!-- number of transactions within the whole SEPA xml file -->
<CtrlSum>10.00</CtrlSum> <!--total of all transactions, from AVA Update 3 on-->
<InitgPty>
<Nm>[DTAUS Konto Name (DB setting)]</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>20140605084436662</PmtInfId>
<PmtMtd>DD</PmtMtd>
<BtchBookg>false</BtchBookg> <!-- defined by setting “SEPA - Debits - Batch booking mode”-->
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
<LclInstrm>
<Cd>COR1</Cd> <!-- Direct Debit Type -->
</LclInstrm>
<SeqTp>FRST</SeqTp> <!-- Sequence Type -->
</PmtTpInf>
<ReqdColltnDt>2014-06-10</ReqdColltnDt> <!-- Required Collection Date, calculated by pixi: Invoice date + default execution time; can be manually edited in pixi Payments Application -->
<Cdtr>
<Nm>DTAUS Account Name</Nm> <!--From shops table in pixi Control Center-->
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>NE97373632628292920</IBAN> <!-- IBAN of the shop as defined in shops table or in Control Center setting -->
</Id>
</CdtrAcct>
<CdtrAgt>
<FinInstnId>
<BIC>BIC12456</BIC> <!-- BIC of the shop as defined in shops table or in Control Center setting -->
</FinInstnId>
</CdtrAgt>
<ChrgBr>SLEV</ChrgBr>
<CdtrSchmeId>
<Id>
<PrvtId>
<Othr>
<Id>DE02ZZZ01234567892</Id> <!-- Creditor ID of the shop as defined in shops table or in Control Center setting -->
<SchmeNm>
<Prtry>SEPA</Prtry>
</SchmeNm>
</Othr>
</PrvtId>
</Id>
</CdtrSchmeId>
<DrctDbtTxInf>
<PmtId>
<EndToEndId>PIXIX134X959353X</EndToEndId> <!--pixi transaction ID-->
</PmtId>
<InstdAmt Ccy="EUR">10.00</InstdAmt> <!--Direct Debit amount-->
<DrctDbtTx>
<MndtRltdInf>
<MndtId>DE8606546800000771569</MndtId> <!--mandate reference-->
<DtOfSgntr>2014-06-05</DtOfSgntr>
<AmdmntInd>true</AmdmntInd> <!-- from ELI Update 15 on: always 'false', section AmdmntInfDtls not included -->
<AmdmntInfDtls>
<OrgnlCdtrSchmeId>
<Nm>MADGENIUSES</Nm>
<Id>
<PrvtId>
<Othr>
<Id>DE02ZZZ01234567892</Id>
<SchmeNm>
<Prtry>SEPA</Prtry>
</SchmeNm>
</Othr>
</PrvtId>
</Id>
</OrgnlCdtrSchmeId>
</AmdmntInfDtls>
</MndtRltdInf>
</DrctDbtTx>
<DbtrAgt>
<FinInstnId>
<BIC>GENODEF1DL1</BIC> <!--Customer BIC-->
</FinInstnId>
</DbtrAgt>
<!--
If the BIC of the customer is not provided, the structure of the XML is different:
<DbtrAgt>
<FinInstnId>
<Othr>
<Id>NOTPROVIDED</Id>
</Othr>
</FinInstnId>
</DbtrAgt>
-->
<Dbtr>
<Nm>Max Mustermann</Nm> <!--Customer Name, from ELI Update 14 on: account owner (if empty: customer name)-->
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>DE8606546800000771569</IBAN> <!--Customer IBAN-->
</Id>
</DbtrAcct>
<UltmtDbtr>
<Nm>Max Mustermann</Nm> <!--Customer Name-->
</UltmtDbtr>
<RmtInf>
<Ustrd>Max Mustermann Ref. ZEB100256</Ustrd> <!--Reference: Customer Name + "Reason for DTAUS/SEPA" (taken from Shops table or Database Setting) + Invoice Nr. + Shop Order Nr.-->
</RmtInf>
</DrctDbtTxInf>
</PmtInf>
</CstmrDrctDbtInitn>
</Document>XML structure for credits
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.003.03"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.001.003.03
pain.001.003.03.xsd">
<CstmrCdtTrfInitn>
<GrpHdr>
<MsgId>20140605103101836</MsgId>
<CreDtTm>2014-06-05T10:31:01.836Z</CreDtTm>
<NbOfTxs>1</NbOfTxs> <!-- number of transactions within the whole SEPA xml file -->
<CtrlSum></CtrlSum> <!--total of all transactions, from AVA Update 3 on-->
<InitgPty>
<Nm>[DTAUS Konto Name (DB setting)]</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId>20140605103101836</PmtInfId>
<PmtMtd>TRF</PmtMtd>
<BtchBookg>false</BtchBookg>
<NbOfTxs>1</NbOfTxs>
<CtrlSum>11.00</CtrlSum>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
</PmtTpInf>
<ReqdExctnDt>2014-06-05</ReqdExctnDt> <!-- requested execution date -->
<Dbtr>
<Nm>DTAUS Account Name</Nm> <!--from table Shops in pixi Control Center-->
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>DE123456789987456321</IBAN> <!-- IBAN of the shop as defined in shops table or in Control Center setting -->
</Id>
</DbtrAcct>
<DbtrAgt>
<FinInstnId>
<BIC>12345698</BIC> <!-- BIC of the shop as defined in shops table or in Control Center setting -->
</FinInstnId>
</DbtrAgt>
<ChrgBr>SLEV</ChrgBr>
<CdtTrfTxInf>
<PmtId>
<EndToEndId>PIXIX130X709530X</EndToEndId> <!--pixi transaction ID-->
</PmtId>
<Amt>
<InstdAmt Ccy="EUR">11.00</InstdAmt> <!--credit amount-->
</Amt>
<CdtrAgt>
<FinInstnId>
<BIC>55555555554</BIC> <!--Customer BIC-->
</FinInstnId>
</CdtrAgt>
<!--If the BIC of the customer is not provided, the whole <CdtrAgt> block is removed-->
<Cdtr>
<Nm>Max Mustermann</Nm> <!--Customer Name-->
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>si989891111222aaa</IBAN> <!--Customer IBAN-->
</Id>
</CdtrAcct>
<RmtInf>
<Ustrd>Max Mustermann test 11</Ustrd> <!--Reference: Customer Name + "Reason for DTAUS/SEPA" (taken from Shops table or Database Setting) + Invoice Nr. + Shop Order Nr.-->
</RmtInf>
</CdtTrfTxInf>
</PmtInf>
</CstmrCdtTrfInitn>
</Document>