Sure. For example, in uPlan, the primary table or recipient schema is linked to your recipient list (eg the sample recipient list that the customer would upload).
You can then connect another secondary database to the plan. I would use that to create a userview so you can capture all the other fields for the address in one query.
Of course, it relies on the customer uploading a list where the key that is used in the query is good. I mean that they are not going to mistype the office ID or branch location that is used to query the address details.