Firstly, what's been done with those 2.1 million rows?
Try creating this index
BD1_A_SALFLDG ([ACCNT_CODE], [AUTHORISTN_IN_PROGRESS], [PERIOD],[CONV_CODE])
Post new exec plan if it makes any difference.
The reason those clustered index seeks are taking a long time is the shear amount of data being returned. 1.4 GB of data from one, 0.9 GB of data from the other. Regardless of what type of index, that's not going to be quick
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability