FAH:Create Accounting with ProcessEvents-InvalidAccounts(Suspense)not working for BSV CVR Violations

Summary:

Business Requirements:

While processing the passthrough file, we want any CVR (Cross-Validation Rule) violations — such as when intercompany segment values are defaulted while using intercompany specific natural accounts — to push the affected line to suspense instead of invalidating the entire file.

We’ve implemented the process by running Create Accounting with Process Events as Invalid Accounts, which correctly pushes the entire code combination to suspense for non-BSV segment violations.

However, this approach is not working for BSV (Balancing Segment Value) violations.

For example, in our client setup, we have three BSVs — Company, Department, and Branch — and CVR rules specify that certain Departments (e.g., 1000–1999) should only be used with Company 101. When a transaction comes in with 101–20001 (which is a CVR violation), then