Is there a design strategy or standard for storing dynamic data transformation logic?

Question

I am designing an ETL job. Peculiar thing about this job is that target database schema remains constant as usual but the source file structure and data format is very dynamic.<