Business requirement to manually match one sided transaction

Summary:

Business requirement to have one sided matching created manually by user when there is no transaction on other side flowing

Content (please ensure you mask any confidential information):

Is it possible to match one side of the transaction when there is absolutely no transaction flowing in on the other side? This is essentially the case in historical transaction load, where transaction from one side is loaded manually from past period and the period is not configured in ARC. For instance transaction might be from 2023 and since this period is not configured in ARC, and there are no match found, users want to manually match, what would be the best practice in this situation