Hi Soumya,
Yes you are correct, this behavior is to be expected.
The Import action does not look at column headers, only column position in the template and imported file.
In your example, if the first column in the defined template is “Loan number” but in the imported file the first column is “Batch ID”, the import action will put the batch id’s in the object’s loan number attribute. In other words: column order is what matters.
Could you please formulate the example a bit more detailed? I am not sure if I understand you’re issue correctly.