Using ARM and Suitebilling we have an instance were subscriptions were created with the parent Geography, I went in and added the new Geography and updated the source transactions to the new Geo, but creating the new arrangement it still pulls the Parent Geo. I think the arrangement is pulling the Geo from the element, is the only way to fix the Geo on the element a "Nuke and Repave"? or do we just reclass revenue for the next two years?