Universal Provider ISO 8601 Support
Business Value
When transactions are imported through the Universal Banking Provider, the date format of the CSV file is defined in the setup. The existing formats assume a plain date with a fixed separator – such as DD.MM.YYYY or YYYY-MM-DD.
Many payment service providers and banks, however, export full ISO 8601 timestamps such as 2026-03-24T13:49:46+00:00. The value does start with a date, but continues with a time and a time zone offset and could therefore not be read. Such files had to be reformatted before the import.
Feature Description
The Date Format field in the CSV setup of the Universal Banking Provider offers the additional value ISO 8601 (Date/Time). It extracts the date part from an ISO 8601 value; the time and the time zone offset are ignored.
The available options are therefore:
| Date format | Example |
|---|---|
| DD.MM.YYYY | 24.03.2026 |
| YYYY-MM-DD | 2026-03-24 |
| MM/DD/YYYY | 03/24/2026 |
| DD/MM/YYYY | 24/03/2026 |
| ISO 8601 (Date/Time) | 2026-03-24T13:49:46+00:00 |
| Custom | through a regular expression |
Custom formats through a regular expression
For formats that match none of the presets, the new Custom Date Regex field replaces the previous Custom Date Pattern field. Instead of a fixed separator you supply a regular expression, which must contain the named capture groups day, month and year, for example:
Code
This makes it possible to extract the date from composite values as well. The field is only used when Date Format is set to Custom.
Migrating existing setups
The previous Custom Date Pattern field is marked as obsolete and will be removed in a future version. If you use a custom format, store it as a regular expression in the Custom Date Regex field.
For more information, see Retrieve Universal Transactions.