Rekey information for double verification (By other user)

I am working on a system where if one operator(let's say Operator A) enters the details of a payment manually, another operator(Operator B) needs to view and verify it. For some domain-based reasons, Operator B also needs to re-enter some of the information Operator A already entered without seeing them.

I am attaching some simplified wireframes. Screen 1 is how Operator B views the payment to be verified. Information is distributed on the screen on different tables and the fields that need to be rekeyed can be scattered among the screen. Also, some information is showed inside drawers and there can be fields to be rekeyed inside these drawers too. (If you click the "Other Values" link on the first screen, the drawer on the 2nd screen shows up.) The number of fields that needs to be rekeyed is changeable according to the payment type.

I was thinking a flow like this: User clicks Verify -> We ask them to re-key needed information (like the 3rd screen) -> Verification gets complete if the information is correct. But I got the comment from stakeholders that Operator 2 might need to check other information on the payment or might use the navigation bar (We have some quick search functionality there) to search for information to be able to fill these fields. So I need something that is filled before clicking the Verify button and something that could be opened and closed many times until all the fields get filled.

I could trigger this pop-up with another button on the payment screen but then I am not sure when to run validation for these rekeyed fields. And also I am not satisfied with taking these fields from different parts of the screen and combining them as then they might lose their context. I don't want to let the user rekey them just where they are on the payment screen cause then they need to be able to notice all of these fields among the screen (this screen might be a bit longer and there might be scrollable tables inside)

I would be happy if I could get any comments on my thoughtsenter image description here, how would you approach something like this or any other system recommendations to examine that comes to your mind that uses a similar verification approach to examine.