Auto Matching rule invocation issue ( associated to defined match type) and Period Key mismatch

Summary

Hi There, We created custom match type based on net amount and attribute matching across Source & Sub System and were able to load premapped transactions.

Content

Hi There.. 

We ventured to create our custom match type based on net amount and attribute matching across Source & Sub System and were able to load pre-mapped transactions. However in the reconciliation associated with the profile  we still notice the loaded transactions being treated as under unmatched bucket despite the fact matches exists for both net balance and attribute key..  Any suggestions why the matching rule is not being invoked/considered post load.