Today Sharifa and I spent hours battling against some fairly opaque error messages. In the end it turned out that adding a "branch name" for both the gift and the relationship was enough to push it through, but this has meant that our financial institution table is now polluted by some branch names that are just "branch" - clearly not ideal.

I think this must be because our financial institution table was already quite messy. When I look at the records that caused exceptions, it appears that they were all trying to use banks which either had a branch name in the financial institution table (but not in our data file) or were included in the financial institution table twice.

In the UK, a bank's sort code acts as a unique identifier. Consequently, it should be the only field required for ImportOmatic to try to find a match in the financial institution table.

I would suggest a bank selection dialogue similar to the constituent match dialogue. If the sort code matches one in the financial institution table, but the bank name and/or branch name don't match, this screen would allow the user to choose whether to match to the existing record or to create a new record. Likewise, if a sort code is in the table twice, this screen could allow the user to select which entry to match with, or to create a new one.