ETL is a complex area for most financial institutions, with regulatory issues continually looming. Not only is data lineage a hot topic of interest and change, but regulatory reporting including using ETL for XBRL regulatory reports is also causing some concern.

Advances in technology as well as changing needs for both customers and users of ETL means the area is ever changing and catching up with itself. We have conducted research to establish the current state of ETL, as well as maintenance and security issues amongst other elements of ETL.

Key areas covered are shown below.

1. Data sources drawing from
2. Types of data source
3. Why ETL is being used
4. Areas of usage
5. Limits/problems with ETL
6. How data lineage is handled
7. Confidence of where data has come from
8. Cost of maintenance of ETL
9. How to minimise ETL costs

10. Handling of large volumes of ETL rule changes
11. Regulatory reporting model maintenance
12. E/T for XBRL regulatory reports
13. Business-IT Tension
14. Desirable characteristics of ETL solution
15. Low code/no code advantages (if used)
16. Technical staff availability and impact
17. Buyers of the ETL tools in the organisation
18. Who uses the ETL tools (now and in the future)