PayMaker 2 Release Notes
2.3.7 Build #2030700 – Released on 16/05/2024
Fixed
- If a non-standard QR code is scanned, an invalid payment file may be created.
2.3.6 Build #2030600 – Released on 07/03/2024
New
- PayMaker displays an error message if the IBAN is not compatible with the specified reference when entering a payment.
Fixed
- If the time format is set to 12 hours in the system settings, then invalid payment files are created.
Improved
- The recognition of QR codes in multi-page PDF files works better.
- Payment orders are printed in landscape format so that the IBAN and recipient address are not cut off.
2.3.5 Build #2030502 – Non-public version from 14/03/2022
New
- PayMaker supports external cameras connected to the computer for scanning QR codes.
Fixed
- When providing payments that have been imported from CSV files, the error message "The operation couldn’t be completed. (PayMaker_2.ISO20022SerializationError error 7.)".
- For international payments, Switzerland and Liechtenstein cannot be selected as the country for the recipient address. This must be possible for companies based in Switzerland with accounts abroad.
- The display of payments with long accounting text is poor.
2.3.4 Build #2030400 – Released on 10/01/2021
New
- PayMaker is a universal binary that runs natively both on Macs with Intel processors as well as Apple Silicon.
- The application icon is adapted to Apple's design specifications for macOS 11.
- On macOS 11, the layout of the main window corresponds to the Big Sur standard.
Fixed
- Under macOS 10.14, texts are cut off in the left column of the main window, even if the column is made wide enough.
- The symbol for selecting variables is not displayed on the respective buttons.
- If multiple databases are open, smart folders cannot be created.
- Changes in the export settings are not always applied immediately.
2.3.3 Build #2030300 – Released on 07/11/2020
Fixed
- If there is only a space character in the "Additional Information" field in the QR code of a QR invoice, an invalid payment file is created.
- When creating a new database from a Windows PayMaker database, QR payments are imported as ISR (orange payment slip).
2.3.2 Build #2030200 – Released on 10/09/2020
Fixed
- The export of payment files with custom export scripts does not work.
2.3.1 Build #2030100 – Released on 07/09/2020
Fixed
- When the app starts, the update of the SEPA banks and the international IBAN formats does not work.
- In smart folders with multiple conditions linked by "or", payments that do not meet any of the conditions are also displayed.
Improved
- The app displays more detailed error messages if you submit an image to the app with a QR code that does not belong to a QR bill or that is incorrect.
- Reminders for payments not submitted are only generated if they are in the future. Previously only the day was checked, now the time is also checked.
- When importing Windows PayMaker/BusinessMaker databases, the conversion from unstructured to structured addresses can be skipped. This simplifies the import of large databases with many addresses.
- A possibly existing info window is only shown at program start if you have not seen it yet.
2.3.0 Build #2030005 – Released on 29/06/2020
Important
- This update may be subject to charge.
- We have adapted the database model to include new functions. All PayMaker documents are automatically converted when they are first opened. After that they can no longer be opened with older versions of the app. We recommend that you make a backup copy of the documents before opening them with version 2.3.0.
New
- Support of QR bills. There are the following possibilities to read QR codes into PayMaker:
- Via CREALOGIX PayEye. This device can recognise QR codes as well as code lines on legacy orange payment slips.
- Via Continuity Camera from an iOS device (macOS 10.14 Mojave and newer).
- Via dragging PDF or image files containing a QR code onto the main window of PayMaker (macOS 10.14 Mojave and newer).
- Via the computer's built-in camera.
- In the preference pane, you can choose to be notified when an execution date is approaching and the entered payments have not yet been submitted to the financial institution. The notification can be made via the Message Center and / or via the Reminders app.
- Manage table configurations for the main window: Until now, you could configure the table in the main window relatively freely; you could choose which payment attributes were displayed in which order and with which sorting. This setting then applied to all groups. Now you can save customized table configurations and – if desired – assign a different table configuration to each group, smart folder and label folder.
- PayMaker can be individually extended by plug-ins. Two types of plug-ins are supported: Plug-ins for additional export scripts and plug-ins for customized print output.
- PayMaker can create a new PayMaker macOS database from Windows PayMaker/BusinessMaker databases of versions 4.x and 5.x.
2.2.4 Build #2020400 – Released on 27/04/2020
Fixed
- If you tick the Salary payment checkbox in a new payment with a red payment slip and then change the payment type to orange payment slip, PayMaker will generate an „orange“ payment with a salary payment indicator, which is not correct.
- When editing a payment template, the editing window is sometimes not displayed in the right place or not at all.
Improved
- The appearance of the list of payment files is clearer.
2.2.3 Build #2020300 – Released on 03/09/2019
Fixed
- UBS does not accept XML payment files created with PayMaker Mac 2 if they contain international SEPA payments.
Improved
- When exporting payments to Numbers, the application also exports posting account numbers.
2.2.2 Build #2020200 - Released on 12/08/2019
Fixed
Various display errors:
- On older macOS versions (< 10.14): When changing the width of the main window, a grey bar appears and the left column can not be widened.
- The position of the window for new payments is not always correct; it sometimes appears in the lower half of the screen.
- The initial size of the preferences window is not correct.
2.2.1 Build #2020100 - Released on 04/07/2019
Fixed
2.2.0 Build #2020002 - Released on 24/06/2019
Important
- An update fee may be charged to use this version.
- We have adapted the database model to include new functions. All PayMaker databases are automatically converted the first time they are opened. After that, they can no longer be opened with older versions of the app. We recommend that you create a backup copy of the databases before opening them with version 2.2.0.
New
- Smart folders for filtering payments.
- For addresses, the street and house number can be entered in separate fields; this corresponds to the ISO 20022 standard. Existing addresses are not converted automatically.
- Simplification when entering accounting texts: When you start typing, the app will display matching accounting texts, which you can easily select.
- For international payments, the app indicates whether the payment is SEPA compatible.
- For international payments, the country of the beneficiary and the country of the financial institution may be selected separately.
- In the main window you can tag payments via drag & drop.
- In the main window you can assign payments to another debit account via drag & drop.
- Optionally the app can display the Save as... dialog when making payments.
- When printing payment lists, the name of the database can be printed.
Improved
- In the lower part of the main window, you can see whether you have selected one or more payments.
- The length restriction for address fields has been removed. If you enter more characters than allowed by the standard, the input field is highlighted in orange. The app saves the input completely in the database, but when creating the payment file it shortens the data to the maximum allowed length.
- The Create or Save button is always active.
- The maximum execution date is checked depending on the bank of the debit account.
- During import, the data is checked more strictly for correctness.
Fixed
- Only four-digit IIDs can be entered in the IBAN calculation dialog.
- Payments may not be sorted correctly in the main window.
2.1.9 Build #2010900 – Released on 07/05/2019
Fixed
- When creating a payment in „Dark“ appearance, the execution date is displayed with white text on white background.
2.1.8 Build #2010801 – Released on 26/04/2019
This maintenance release prepares PayMaker for future extensions.
New
- New application icon.
- The application is notarised by Apple.
Improved
- The position and appearance of startup windows has been unified.
- The software update functionality and licensing system have been revised.
Fixed
- It is not possible to enter special characters in the creditor account field of international payments.
2.1.7 Build #2010700 – Released on 05.02.2019
Improved
- When importing CSV files, the field delimiter can be chosen.
2.1.6 Build #2010600 – Released on 11/12/2018
Fixed
- When importing CSV files, the salary payment flag is not set if the payment type is "2".
2.1.5 Build #2010500 – Released on 26/11/2018
New
- Payments import from CSV files.
- Type 7 code lines (longer code lines) on red payment slips are interpreted.
- Dark mode support in macOS Mojave.
- Automatic fixing of corrupted PayMaker databases (if possible).
Improved
- Handling of unexpected application errors.
- Behavior of the app when horizontally resizing the payment and payment files windows.
2.1.4 Build #2010400 – Released on 09/08/2018
Important: We had to update the database model in order to implement new features. All PayMaker documents are updated automatically when they are first opened. After that, they can not be opened with previous versions of the app. We recommend to create a backup copy of the database before opening them with version 2.1.4.
New
- In the debit account master data, the type of advice (no advice, single advice, collective advice with or without details) can be defined if the payment file format is ISO 20022 (XML).
- For PostFinance debit accounts, a separate account number for fees can be defined.
- In the general preferences, "PayPen II" can be selected as pen software which is automatically started.
Improved
- In the main window's first column, the payment's status is displayed (new, archived, faulty).
- Editing the reference number on orange payment slips is easier.
- In the payment editing window, IBAN are displayed formatted.
- The printout of payment lists and of the contents of payment files is more condensed.
Fixed
- Under macOS 10.12.x, the "New Payment" window is not opened automatically when you use the ScanMouse or PayPen to scan a code line.
- When scanning a code line, the app may insert the wrong creditor into the new payment. This happens if there already are one or more payment templates with creditors who have accounts at the same bank and the new payment is done for a so far unknown creditor with an account at this bank.
2.1.3 Build #2010300 – Released on 12/07/2018
This build replaces the one from 11/07/2018 – the version number and release notes remain the same.
New
- When creating debit accounts, the app accepts Liechtenstein IBAN.
- In the filter column of the main window, the "Prepared" group is now called "Archive"; "Deleted" is now "Trash".
- The app accepts additional common keyboard shortcuts such as cmd-D for duplicating payments, cmd-F for Find and cmd-Return (or Enter on keyboards with a ten-key pad) to save payments.
Improved
- Previously, payments that could not be prepared were displayed with a warning symbol in the main window only. Now the app also displays the cause of the warning by writing the incorrect fields in red.
- In the main window, payments with deactivated debit accounts are displayed as well.
- There are several improvements regarding the handling of deactivated debit accounts.
Fixed
- The payment editing window may close automatically about ten seconds after being opened. Any changes are lost.
- In the payment editing window, deactivated accounts appear in the debit account selection button.
- If the app does not accept a payment, the incorrect fields are not properly highlight.
- When creating a new payment, the debit account saved in a payment template has higher priority than the preferences setting regarding new payments. Solution: The app sets the debit account according to the choice made in the preferences.
2.1.2 Build #2010200 – Released on 03/07/2018
Fixed
- Databases that have been used with PayMaker Mac version 2.0.0 to 2.0.8 but have not been opened since then may not be opened with version 2.1.1. The app displays a message claiming that the database has been opened with a newer version of the app – this message is incorrect.
2.1.1 Build #2010100 – Released on 26/06/2018
This version mainly resolves faults that have been detected since the release of version 2.1.0. Important: We updated the database model. All PayMaker documents are updated automatically when they are first opened. After that, they can not be opened with previous versions of the app. We recommend to create a backup copy of the database before opening them with version 2.1.1.
Improved
- In the Payment files window, payments that belong to a payment file can be deleted.
Fixed
- After entering a code line (manually or with PayPen / ScanMouse) for an orange payment slip, the app does no longer fill out any known addresses. This only concerns orange payment slips with both a creditor agent as well as a creditor.
- The app does not display the account number for orange payment slips with creditor agent and creditor in the Payment templates window.
- The app may not show the filter column in the Payment files window even though multiple debit accounts are defined.
- When entering a search term in the main window's search field, the app may display an internal error alert.
2.1.0 Build #2010000 – Released on 13/06/2018
Important:We had to update the database model in order to fix faults with the CLX.PayMaker OSX 1.x import. All PayMaker documents are updated automatically when they are first opened. After that, they can not be opened with previous versions of the app. We recommend to create a backup copy of the database before opening them with version 2.1.0.
New
- The app can import (Windows) UBS Pay databases.
- Prepared payments can be deleted and edited.
- Payments that have the current date as execution date can be marked as "express" when preparing the payments file.
Improved
- When preparing ISO 20022 files, the app uses "single entry" as posting type. With that, every payment should appear separately on the account statement (although there may be bank-specific exceptions).
- When importing CLX.PayMaker OSX 1.x databases, the app always selects ISO 20022 as payment file type.
Fixed
- It is not possible to create payments for creditors with an IBAN of the Principality of Liechtenstein. Solution: Payments with IBAN to the Principality of Liechtenstein can either be created as domestic payments or by using the red payment slip.
- The import of international payments from CLX.PayMaker OSX 1.x is incorrect. If such a payment is duplicated and prepared, an invalid ISO 20022 file is created. Solution: The app assigns the correct payment type during the import.
- When importing CLX.PayMaker OSX 1.x databases, the app includes deleted recipients. Solution: The app does not import deleted recipients.
- With macOS 10.12 (Sierra), the app preferences are not displayed correctly – it is not possible to change them. Solution: The app does no longer animate the size change when switching preference panes in macOS 10.12.
2.0.8 Build #2000800 – Released on 04/05/2018
New
- There is an item "License …" in the PayMaker 2 menu. This opens a window that shows information about the license and allows to enter a new license key.
- The trial period for PayMaker 2 is 60 days from the first launch of the app.
- There is a preference pane to set default values for new payments: The debit account to use, payment type, execution date and posting account.
- The app checks if the execution date is a bank holiday. Bank holidays are the dates that can be found on SIX Interbank Clearing AG's website.
Improved
- When searching for payments in the main window, payments from both the "New" and "Prepared" groups are displayed. Previously, only payments of the selected group were displayed.
Fixed
- When importing red payment slip payments from CLX.PayMaker OSX 1.x, the app assigns the wrong payment type if the debit account is a bank account. If you duplicate such a payment and prepare an ISO 20022 file, then this file is invalid. Solution: The app assigns the correct payment type during import.
2.0.7 Build #2000700 – Released on 14/03/2018
New
- PayMaker 2 is scriptable: It is possible to open and read data from PayMaker databases through AppleScript.
- Export of payments for import in accounting applications:
- Supported formats: BudgetfM, iCash, LoopsFinanz single and collective entry, MedioFibu, MedioKassabuch, Minibüro, Numbers, QIF, ShakeHands Kontor and ShakeHands PowerBiz.
- The export format, the storage location and a template for the name of the export files can be defined in the app's preferences.
- The posting accounts can be defined by updating the debit accounts.
- It is possible to open the e-banking website of the financial institute directly from the payment files window. In order to use this functionality, the link to the login website and the browser must be defined by updating the debit accounts.
- In the general preferences, CLX.ScanMouse can be chosen as pen support software – if the application is installed.
Improved
- There is a new menu item "Payment files" that includes all operations that can be done on payment files.
- The generation of a payment file is now called "Prepare" (instead of "Export") and is represented by a new icon in the toolbar. This was necessary to make a clear distinction between generating a payment file and the new export functionality for accounting applications.
- It is possible to open multiple "New payment" windows at the same time.
Fixed
- If the option "Show this window when PayMaker 2 launches" on the database manager has been deselected, then the app may crash during startup.
- If the storage location for payment files which is defined for each debit account no longer exists, then the following happens: The system displays a misleading error message, no payment file is generated but the payments are nevertheless marked as "prepared". Solution: The app displays a meaningful error message and the payments are not marked as "prepared".
- If two addresses have been given on an orange payment slip (both for the financial institute as well as the creditor), then the financial institute's address is exported to ISO 20022 payment files – with the result that on the account statement, the creditor is not shown. Solution: When generating the payment file, the creditor's address is stored.
- If a payment contains a character that can not be encoded with Latin 1 encoding (e.g. ℅), then the system shows an error message when generating a DTA payment file. Solution: Die App exports only characters that are accepted by the ISO 20022 standard. Invalid characters are replaced by a space; leading and trailing spaces are removed.
- If an ISR payment imported from PayMaker 1.x which contains a reference number with less than 27 digits is duplicated, then an invalid ISO 20022 payment file is generated.
2.0.6 Build #2000600 – Released on 17/02/2018
Fixed
- Creating an international payment where the street is missing from the creditor's address results in the generation of an invalid ISO 20022 file.
Improved
- Printing of payments is only enabled if at least one payment has been selected in the payments window.
2.0.5 Build #2000500 – Released on 07/02/2018
Important: We have updated the database model in order to fix an error and to prepare for future functionality. All PayMaker documents will be updated when they are opened for the first time. Afterwards, they can no longer be opened with older versions of the app. We recommend to create a backup copy of the documents before opening them with version 2.0.5.
New
- Payments selected in the main window can be duplicated via the "Payments" menu or the context menu.
- We have removed the archive functionality because it caused more confusion than it was actually useful. Previously archived payments are now displayed in the "Sent" group.
Fixed
- When using the "Change date" function in the main window, the app does not accept today as execution date.
- Saving the assignment of tags to payments does not work correctly.
- When deleting a payment instruction the included payments are moved to the "Prepared" group. Solution: The payments are moved to the trash.
- The panel that shows search results in the payment editing window appears with red background color and an error message.
Improved
- The year of invoice dates is displayed with four digits.
2.0.4 Build #2000400 – Released on 23/01/2018
Fixed
- If multiple payments files are transferred to PostFinance which include payments with the same debtor account and execution date, then only the payments of the first file are executed. The payments in the other files are suspended. Solution: Payments get order ids that are always unique, not just within the same payments file.
- The app creates an invalid ISO 20022 file if the payment information contains characters that are not allowed, e.g. ℅. Solution: Characters that are not allowed are replaced by a space. Spaces at the beginning and end of texts are removed.
- The app creates an invalid ISO 20022 file for some account numbers on red and orange payment slips.
- The app does not accept today as execution date.
Improved
- When entering postal codes, the limit is now 10 characters everywhere (it used to be 4 for national payments).
2.0.3 Build #2000300 – Released on 18/01/2018
New
- Display of the number of payments and the total amount in the main window.
- When creating debit accounts, the file extension for payment files is chosen automatically according to the selected format: .xml for ISO 20022, .dta for DTA.
Fixed
- Potential crash of the app during the import of PayMaker OS X 1.5 files.
- The app creates an invalid ISO 20022 file for orange payments without a creditor name.
- The possibility to create tags with the same name.
- The window for editing payments is too large to be shown completely on devices with lower resolution screens.
2.0.2 Build #2000200 – Released on 09/01/2018
Fixed
- Swiss IBAN with expired IID are not accepted.
2.0.1 Build #2000100 – Released on 30/12/2017
Printing, enhanced search and bug fixes.
New
- Printing of the payments in the main window.
- Printing of payment instructions.
Improved
- Searching in the main window includes the execution date.
Fixed
- Invoice information (invoice number and date) are not displayed correctly.
- Variables in accounting texts are not replaced when displaying payment instructions.
- Application hangs if the client database is closed immediately after the last data entry.
Open items
The following items will be implemented in a future update:
- The application is not yet scriptable.
- The help is incomplete.
2.0.0 Build #2000006 – Released on 22/12/2017
First published version.