Thanks for the reply. Actually, in this situation, the source data is coming in with an ICP partner (999) that is mapped ato [ICP None]. It's an exceptional case where the source data in this account contained an ICP partner that we already have mapped to ICP None, and it was not possible to go back and change the source data. BUT the source account has to be mapped to an IsICP account in HFM (one-off situation).
So we posted the journal to try to zero out the balance, and make additional entry in the journal to manually move the balance to an ICP partner.
I would think if the balance is 0.00 in the account, it would not try to validate the intersection in HFM. But it seems to be validating based on each individual source account, although they net out to zero in total for the HFM account.
I'm not sure if there is much we can do here. Just hoping maybe someone had run into the issue and could share how they resolved it...
Okay, that makes more sense as why a simple mapping won't fix this. While I've never run into this the only two suggestions I might have to avoid writing a script would be on the account map to map these two source accounts to "Ignore" (that's assuming they will always net to 0 in the future). And if that doesn't work, then maybe you would explore using logic accounts to aid in changing the ICP for mapping purposes.