Feedback|info@sepaapp.eu
YouTubeEmail

FAQ

Home/FAQ

FAQ

In this FAQ (Frequently Asked Questions) you can find answers to your questions. If not, please contact us.

  • You are using a SEPAApp version without Java-Runtime Environment.
  • Solution 1: Download SEPAApp with an included Java-Runtime Environment and use that version (recommended).
  • Solution 2: Install your own version of Java and restart SEPAApp.


    • Windows message regarding missing Java

    Mac message regarding missing Java

  • Using Windows or Mac you get, at least at the first start of SEPAApp, a warning message regarding a not verified software or not identified developer. You can ignore that warning.


    Windows warning message (German version – you see it in your computers language)


    Mac warning message (English version – you see it in your computers language) (with Java Runtime-Environment)


    Mac warning message (English version – you see it in your computers language) (without Java Runtime-Environment)

  • This is possible under Windows as follows:

    Create a file “SEPAApp.l4j.ini” in the directory where the SEPAApp exe file is located.
    Use a text editor to write “-Duser.language = ‘en'” into this file and save it.
    Make sure that the file is created in Windows in ANSI format.

    Instead of ‘en’ you can also use the language abbreviation of any other language available in SEPAApp.

    Under Linux, enter the parameter “-Duser.language = ‘en'” directly to the Java call.

  • SEPAApp is available in the following languages:

    • German
    • English
    • Portuguese
    • Catalan
    • Frensh
    • Spanish
    • Italian

    The download packages contain all available languages (The language will be selected by the computer’s language automatically.) and templates for the import files in English and German.

  • No, please leave columns that you do not use empty. This applies to all optional columns, except the column BIC, for which we have templates with and without BIC.

  • The SEPA XML format has several restrictions, which characters are allowed. Also banks and banking software may add some more restrictions. It is safe to use only letters (A-Z, a-z) and numbers (0-9). In most cases the following special characters are also allowed: + ? / – : ( ) . , ‘

  • SEPAApp requires a screen-resolution of minimum 1024*768.

  • Only, if you want to uses Pro-features, a Pro-license must be entered. In this case a Pro-license has to be bought and entered into SEPAApp. Users of the Standard-version may use SEPAApp as usual without entering a Pro-license.

  • The price has to be paid only once (and includes all future updates)! There are no recurring license fees! Only upgrades like SEPAApp Standard to SEPAApp Pro are chargeable.

  • A common mistake is that the template with BIC is used and on the GUI an import without BIC is set, or, conversely, that the template without BIC is used and on the GUI an import with BIC is set.

  • Yes, if you buy a SEPAApp license, you can use all updates for free. Only upgrades like SEPAApp Standard to SEPAApp Pro are chargeable.

  • SEPAApp Pro has certain features needed for advanced use only. You will find the features marked as Pro-features in the list of features.

  • Yes, to use express credit transfers you just have to set the checkbox on the SEPAApp GUI. You will find details in the manual.

  • Yes, to use single-booking you just have to unset the according option field batch-booking on the SEPAApp GUI. You will find details in the manual. By default batch-booking is selected. Please note that many banks ignore the flag single-booking and always use batch-booking.

  • Yes, to use business direct debits (B2B) you just have to set the according option field on the SEPAApp GUI. This setting affects every direct debit in the generated SEPA XML file. You will find details in the manual. By default normal direct debits (CORE) are selected.

  • You can test SEPAApp 60 days for free without a license.
  • The button “Create SEPA file” will be enabled, after all mandatory fields on the GUI are filled – i.e. there are error messages – and a file with at least one valid data row was imported.

  • Please enter your VAT ID on the order form.

  • There are many reasons why your bank might not accept your SEPA XMl file.
  • Check the error messages from your bank. You might find a hint whats wrong.

  • SEPAApp recognizes credit transfers and direct debits in the template using the tables and starts reading automatically the right data.
  • Leave the eventually not needed table in the template and just insert your data in the other one.

  • No, SEPAApp recognizes empty rows as the end of a file. Remove all empty rows from your import file because all rows after an empty row will not be imported.

  • SEPAApp recognizes the template using header and example entry und starts reading from row 3.
  • Option 1: Leave header and example entry in the template and insert your data from row 3.
  • Option 2: Delete header and example entry in the template and insert your data from row 1.

  • Yes, to use express direct debits (COR1/D1-agreement) you just have to set the checkbox on the SEPAApp GUI. This setting affects every direct debit in the generated SEPA XML file. You will find details in the manual.

    Important note: As the deadline for CORE direct debits has been shortened, COR1 is no longer necessary and is no longer supported by many banks!

  • If you want to integrate the creation of SEPA files seamlessly into your own software to this example resell to customers or to use in customer systems, then we have SEPALib for you.

  • OpenOffice and LibreOffice store – particularly the new Excel format xlsx – not always correct.
  • The best way to use OpenOffice or LibreOffice is to use the ODF format (fiel extension *.ods for sheets) or the CSV format.

  • SEPAApp reads CSV, Excel and ODF files (*.ods) that you can create with a program of your choice (for example, Microsoft Excel, LibreOffice or OpenOffice).
  • If you downloaded the SEPAApp version without Java-Runtime Environment, you have to install a Java-Runtime Environment (Version 8 or higher) by yourself. We recommend using the SEPAApp version thats already has a Java-Runtime Environment included.

  • This is described in the manual.

  • This is described in the manual.

  • This is described in the manual.

  • This is described in the manual.

  • This is described in the manual.

  • This is described in the manual.

  • You miss a feature?
  • You have ideas for improvement?
  • Let us know your wishes on our feedback page! If possible, we will implement in the next version of SEPAApp.

  • SEPAApp generates the SEPA data format (XML format) based on the ISO standard 20022.
  • Direct Debits are generated in pain.008.003.02 or pain008.003.02, pain.008.001.02.austrian.003/004, pain.008.001.02.ch.01, CBISDDReqLogMsg.00.01.00 (sub) format.
  • Credit Transfers are generated in pain.001.003.03, pain001.001.03, pain.001.001.03.austrian.003/004, pain.001.001.03.ch.02, CBIPaymentRequest.00.04.00, pain001.001.02 (sub) format.
  • Further technical details can be found on the website of the German EBICS banking industry.

  • Yes, but a separate license must be purchased for each computer. You found more details about that on the page License Agreement.

  • Yes. All your data will remain on your computer and are not sent to any external server.

  • Operating Systems: Windows XP/Vista/7/8/10, Mac OS, Linux / Unix
  • CSV: all programs that can export CSV (eg Microsoft Excel, LibreOffice or OpenOffice).
  • Excel: any program that can export to Excel format (eg Microsoft Excel).
  • ODF: any program that can export to ODF format (eg LibreOffice or OpenOffice).

  • Enter direct debits and credit transfers in eg Excel.
  • Save the file as xls, xlsx or csv file.
  • Import the file into SEPAApp.
  • Enter your bank account data in SEPAApp.
  • Save the SEPA file.
  • Sent the SEPA file to your bank (eg via StarMoney or via the online banking portal of your bank).
  • This is described in detail in the manual.

Janus Software Solutions | Impressum | Haftungsausschluss | Datenschutzerklärung | Lizenzbestimmungen
YouTubeEmail