The SEPAFAST software has a free and two paid version, in all three cases there is a need for registration.

The file that is produced complies with SEPA standards and is therefore compatible with all home banking platforms of any bank.

The data saving function does not exist but the XML file that is created by the procedure can be directly re-imported through the IMPORT section present in the flow creation mask.

No, SEPAFAST does not need to install software on your PC, it runs directly on the web browser window.

Yes, the email + password combination applies to both services, however the services can be requested and activated with different levels according to the customer's needs (eg SCT with SMART level + SDD with FREE level etc ..).

Only when the file is created are the data stored on the server and subsequently deleted for privacy / security reasons.

The sepafast.com platform uses the Secure Sockets Layer (SSL) protocol.

Yes, by importing this file it is possible to see if the form on the SCT credit transfers page fills correctly.

Absolutely nothing, the program will be updated as soon as possible to be compatible with the new standard again.

It is likely that the browser in use is not compatible with the automatic data saving function, at this point you can proceed to make a manual "copy / paste" of the content that appears on the screen mask on a text file created at the

No, being a program created for a web platform, a particular operating system is not necessary, just one equipped with any web browser for internet browsing compatibility.

Home banking programs vary from bank to bank, however we have experienced that it is usually possible to leave the standard settings without having to enter -Type length- or -Type file-.

The 'Support name' field is an alphanumeric data that distinguishes the flow of dispositions created.
The system already proposes an alphanumeric code in correspondence with the 'Support name' field which we recommend leaving unchanged.

The automatic updating of the fields -number of dispositions- and -total dispositions- is automatically activated -on exit- of the cursor from the amount field of each single disposition.

We invite you to contact us via the "contact us" link at the bottom of this page, we will look for a customized solution for your needs.

Yes, only for the SCT wire transfers section, it is possible to convert cbi -> xml using the "import cbi file" button and then the "generate flow" button.

From 01/02/2014 the new SEPA system has replaced the old CBI system for all the banking orders issued electronically.

The CBI Unique Code (CUC) is an 8-character code that is assigned by the banking system.

No, according to the new regulations it is mandatory to enter the IBAN code.

The difference is obtained by selecting the right item from the drop-down menu -Causal Bank- present in the -debit details- section.

They are bank transfers that are processed intraday by the Bank and have the following limitations:
1. the flows must contain only 1 bank transfer;
2. the payment method must be compulsorily 'TRA' i.e. 'SEPA transfer with outcome to the sender' (usually the sepa flows are of the 'TRF' type or 'Sepa transfer without outcome to the sender');
3. some reasons (e.g. 'SALA' Salary Payment) may not be compatible at interbank level with the urgent settlement request;
4. for urgent transfers, the indication of the origin of the recipient BIC code is recommended (field present in the form but not usually mandatory);
5. for urgent transfers, the management of the case of a Country Code other than IT is left to bilateral agreements.
We specify that higher fees may be applied to urgent transfers by your Bank.
Urgent transfers are processed by the Bank intraday (approximately every 2 hours) and have shorter cut-off times (they may vary from bank to bank), usually the flows must be sent by 1.00 pm. All flows arranged by customers after the cut-off time are considered by the Bank as "received" on the following business day.

It is possible that when uploading files with many provisions the system may take a few seconds longer than expected, therefore it is appropriate to answer NO to the error warning so as to allow the browser to wait for the end of the upload and execution

In this case, we recommend clearing the system cache data.
Da Chrome: Menù->Impostazioni->Cronologia->Cancella dati della navigazione->Cancella dati di navigazione

First of all, the Excel file must be of extension .xls and respect the fields as shown below:

Carefully read the following points:
- the excel file has column headers, therefore row number 1 will NOT be imported
- the column headings can have any value, the important thing is to respect the order of the fields
- sheet1 (sheet1) contains the list of provisions
- sheet2 contains the sender's data in one single line (number 2). This sheet may not even be present in the file but, if present, it must contain the real data
- column F of sheet 1 shows the amounts of credit transfers that must have the point as a decimal separator
- column F of sheet 2 shows the date of execution of the transfers which must be expressed in the format yyyy-mm-dd
- column J of sheet2 shows the service level which can have the value: null (empty), URGP (for urgent transfers)
- automatic formatting of excel cells (eg date, number with decimals, etc.) is not recommended, better if left all as "text"
Se vuoi scaricare un file di esempio: download file example excel - xml sepa credit transfers SCT

the SEPA Direct Debit (SDD) is a method for pre-authorized collection through a debit mandate requested by the debtor in favor of his creditor.

** CREDITOR FIELDS **
Company name = name of the company that owns the credit checking account
City = city of the creditor company
Tax Code / VAT = tax ID of the creditor company
Address = address of the creditor company
Support name = bill reference (we recommend leaving unchanged), there is a specific FAQ in the GENERAL INFO section
Postal code = postcode of the creditor company
Execution date = date requested by the sender for the collection of funds from the debtor;
CUC Code = The Unique CBI Code (in acronym CUC) is an 8-character code (see specific FAQ)
Identif.Credit.Sepa = Creditor identification code, also called ICS (see specific FAQ)
Credit IBAN = creditor's current account, where the amounts withdrawn by the debtors will be credited
Type of credit = specifies the method of crediting the creditor's account, it can be made with "a single overall credit of all the SDDs present in the list" or "one credit for each direct debit"
Creditor BIC = BIC / SWIFT code that identifies the creditor's bank and / or the branch (8 or 11 alphanumeric characters) (optional field)
ABI code = ABI code that identifies the creditor's bank (5 numbers) (mandatory field only if file type = Standard CBI XML SEPA 01.01)
Direct debit type = can be CORE or B2B (specific FAQ exists)
** DEBTOR FIELDS **
Nr. = Univocal progressive of the collection inside the bill (not modifiable)
EteId = internal collection reference (cannot be changed)
Country = reference country of the debtor
TipSeq = specifies the type of operation / frequency of collection;
Signature date = date on which the debtor signed the debit mandate (must be earlier than today)
UMR mand.
Iban debtor = debit current account
Debtor name = name and surname, or company name, of the debtor (holder of the debit current account)
Amount = must be between 0.01 and 999999999.99;
Reason for payment = payment information communicated by the creditor to the debtor (example: monthly fee)
Mod. = Used to declare that the mandate contains a modification, this option activates 5 subsequent fields.
VarBank = [MOD.1] is used to declare that the debtor's bank has changed.
ICS old = [MOD.2] contains the old Identif.Credit.Sepa of the creditor, what has changed (example: following the company merger / incorporation)
NomeAzOld = [MOD.3] contains the creditor's old company name, the one that has changed (example: following the company merger / incorporation)
UMR old = [MOD.4] contains the old mandate number (if changed)
Iban debtor old = [MOD.5] contains the iban of the old current account on which the mandate was debited and was subject to change, the change in this field is to be used only if the debit bank has not changed
Tax Code / VAT no. = tax code or VAT number of the debtor signing the debit mandate
BIC debit. = BIC/SWIFT code identifying the debtor's bank and/or branch (8 or 11 alphanumeric characters)
Debtor city = debtor's city name

The substantial difference between the two versions refers to the nature of the eligible debtors, at the time within which the debtor is entitled to request a refund of the charge, to the possibility of refusing / reversing the collection.
Regarding the SDD Core service: 1. creditors can collect from any type of debtor (Consumer, Non consumer, Microenterprise);
As regards, however, the B2B SDD: 1. creditors can only collect from debtors belonging to the Non consumer or Microenterprise categories;
For SDD B2B charges, for its own protection, the debtor must communicate in advance to his Bank (or in any case confirm) the data referring to each new Mandate signed.
For both products (Core and B2B), the debtor can still request his Bank to inhibit a priori any SDD-type charge on his account, to withdraw his consent to be charged for a single SDD debit request and can define a
In order to be able to cash in via the SEPA Direct Debit service, the creditor must first receive the authorization to debit (signing the Mandate) directly from the debtor.

The execution date is the date on which the debtor will be charged;

The UMR (unique mandate reference) field is a mandatory field and indicates the unique reference of the mandate.
It is a coding that allows identifying each credit as the "Creditor Identification Code (ICS)" combined with the "UMR" are unique in the SEPA space.

The ICS value contains only uppercase letters and numbers, where:
- the first two characters are letters and correspond to the ISO code of the country (e.g. IT)
- the third and fourth characters are numbers and are a control key
- the fifth, sixth and seventh characters must be alphanumeric and correspond to a code indicated by the Creditor for business needs (if not used it is valued with ZZZ)
- the remaining 16 characters correspond to the national tax code
It is the responsibility of the banks to release this data or provide it to their customers if they do not have one.

The CBI Unique Code (abbreviation CUC) is an 8-character code assigned by the banking system. You can request it from your bank branch by providing the SIA code.
For SDD files, the CUC is mandatory (if you do not have the CUC code, enter the ICS Creditor Identifier SEPA code in the field).
It is recommended not to write the CUC code with lowercase letters.

AC01 Invalid or missing account number
AC02 Invalid or missing debtor account number
AC05 Account of the closed debtor
AG01 Transaction prohibited on this account
AG03 Unauthorized transaction on this account
AG07 Generic cancellation (also a lack of funds disguised for privacy purposes)
AM04 Insufficient funds
MD01 Mandate revoked or never implanted
MS03 Reason not specified by the bank of the debtor or creditor
RC01 The BIC of the debtor's bank is incorrect

During the flow generation phase it is mandatory to choose the format of the file to be generated which can be:
"Standard CBI XML SEPA 01.01" or "Standard pain 008.001.08"
They are both valid standards, the one used by your own must be selected Bank being imported.

First of all, the Excel file must be of extension .xls and respect the fields as shown below:

Carefully read the following points:
- the excel file has column headers, therefore row number 1 will NOT be imported
- the column headings can have any value, the important thing is to respect the order of the fields
- sheet1 (sheet1) contains the list of receipts
- sheet2 (sheet2) is optional and contains the sender's data in one and only line (the number 2)
- column B of sheet 1 shows the type of sequence which must report one of the following values: FRST, RCUR, FNAL, OOFF
- column G of sheet 1 shows the amounts of receipts which must have the point as a decimal separator
- column L of sheet 1 shows the variation of the mandate (optional) which must possibly include a capital S
- column M of sheet 1 shows the change of the debit bank (optional) which must possibly include a capital S
- column F of sheet 2 shows the date of execution of the charges which must be expressed in yyyy-mm-dd format and must be later than today's date
- column I of sheet 2 shows the type of credit, selectable exclusively via the drop-down menu
- column K of sheet 2 shows the type of charge, selectable exclusively via the drop-down menu
- automatic formatting of excel cells (eg date, number with decimals, etc.) is not recommended, better if left all as "text"
If you want to download an example file:download file example excel - xml sepa recessed SDD

In the case of non-EURO currencies or credits beyond European borders, the Foreign Bank Transfer is used which passes through the SWIFT (Society for Worldwide InterBank Financial Telecommunication) network.
The data between banks is exchanged via MTxxx messages. For example, the MT101 message is the transfer order.
A non-SEPA transfer is also defined as a SWIFT transfer, because it relies on a telecommunications system between banks (called Society for Worldwide InterBank Financial Telecommunication) which makes transfers extra-continental (and even continental ones, if we are talking about those few countries that do not fall within the SEPA area) easier to access. Not all nations in the world are part of the SWIFT protocol, which however includes more than 10,000 banks in over 200 countries, that is, almost all, with very few exceptions.

The Sepa area includes 36 countries: the 20 EU countries that use the euro (Austria, Belgium, Cyprus, Croatia, Estonia, Finland, France, Germany, Greece, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Portugal, Slovakia, Slovenia, Spain); the 8 EU countries that use a currency other than the euro on their national territory but still make payments in euros (United Kingdom, Sweden, Denmark, Poland, Czech Republic, Hungary, Bulgaria, Romania); 8 other non-EU countries that make payments in euros and have adopted SEPA payment schemes: San Marino, Iceland, Liechtenstein, Norway, Switzerland, the Principality of Monaco, the Principality of Andorra and the Vatican City.

Bosnia-Herzegovina, Serbia, Montenegro, North Macedonia, Albania, Russia, Moldova, Ukraine, Belarus, to which non-European countries must obviously be added, always bearing in mind that there may be specific agreements with some of these which make it more facilitate banking operations.

Yes, but only if the beneficiary has an IBAN corresponding to a country outside the SEPA area.

No, the currency is unique within the single transfer flow.

DEBT, if the sender wants to pay the commission charges of both the domestic bank and the foreign bank. In this case all the commission costs will be attributed to the sender in a debit following the issuing of the bank transfer;
CRED, if the sender wishes to have the commission costs paid solely to the beneficiary. In this case the amount of the transfer will reach the recipient already deprived of all commission costs;
SHAR, if the sender and recipient wish to split the payment of commission costs. The beneficiary pays the foreign bank's commission costs, while the sender pays the domestic bank's commissions.

If you only have the nr. of the beneficiary's account and you do not have the IBAN code (some countries, for example the United States, do not use the IBAN code), the flag must be set.

First of all, the Excel file must necessarily have an .xls extension and respect the fields as shown below:

Read the following points carefully:
- the excel file has column headers, therefore row number 1 will NOT be imported
- the column headers can have any value, the important thing is to respect the order of the fields
- sheet1 contains the list of beneficiaries of foreign bank transfers
- sheet2 (sheet2) is optional and contains the sender's data in a single line (number 2)
- column B of sheet 1 shows the country code of destination of the transfer (as defined in the ISO 3166 standard, Alpha-2 code)
- column F of sheet 1 reports the amounts of the transfers which must necessarily have the dot as the decimal separator
- column F of sheet 2 reports the date of execution of the transfers which must be expressed in yyyy-mm-dd format
- column J of sheet 2 reports the service level which can have the following value: null (empty), URGP (for urgent transfers)
- column K of sheet 2 reports the currency of execution of the transfers which will be unique for all the provisions of the file (ISO 4217 standard)
- column L of sheet 2 shows the type of commission charge chosen from: DEBT, CRED, SHAR (for further details see dedicated FAQ)
- column M of sheet 2 shows the option which specifies that only the bank account numbers and not the IBAN will be indicated in the IBAN field of the beneficiaries in the grid. Select S from the drop-down menu to activate this functionality, or leave the field blank to not activate it.
We do not recommend automatic formatting of Excel cells (e.g. date, number with decimals, etc.), it is better to leave everything as "text".

If you want to download a sample file: download excel example file - foreign bank transfers xml

It is a code that will be requested before each flow generation recovery pin code.

Check in the SPAM folder, in any case insert info@sepafast.com among the safe senders.

In case of transition from FREE to SMART level or from FREE to PRO level, you must not register again but follow the instructions on the page renewal / upgrade.