What would be the impacts of moving an AR Mapping Set from Ship-To to Bill-To?

Summary: For AR Invoices, we are using Ship-To to derive GL/program values from a Mapping Set. For AR Credit Memos, we are doing the same but it is using Bill-To. I dont know the reason they were set up differently but we would like to stop using Ship-To, by creating a new Mapping Set for Invoices using Bill-To but Im trying to understand any down stream implications (other than SLA updates) to making this type of change.

Content (please ensure you mask any confidential information):

26C provided functionality to make populating Ship-To on a grants contract as optional, we would like to take advantage of this and stop populating Ship-To on all grants contracts but we have a mapping set tied to Ship-To. I am unable to determine if this was intentional or what the implications would be if we disabled that one and created a new Mapping set for AR Invoices using Bill-To.