What are all the impacts of enabling the Consolida...
# administration
a
What are all the impacts of enabling the Consolidated Payments feature? What are some gotchas and side effects that could potentially affect our accounting, our users, the way we use transactions, our scripts and other processes, or our data? Our account is multi-subsidiary, and we're trying to query the following fields, which we are told aren't available without the Consolidated Payments feature, so we're considering turning it on for the main reason of just being able to query those fields: SELECT balance, currency, customer, depositbalance, overduebalance, overridecurrencyformat, unbilledorders FROM customercurrencybalance
m
You don't meed the consolidated payments feature for that table. You also have "Customer-Subsidiary Relationship" in a saved search, which let you see customer balances on customer per subsidiary.
a
Thanks!
including the overduebalance column causes the query to take what seems like 5-10 minutes, then throws an error. I get similar results when including this column in a saved Customer search if I tell it to only include customers whose overdue balance is not zero or empty, or their parent customer's overdue balance is not zero or empty, or their child customer's overdue balance is not zero or empty. I believe this is causing one of our integrations to be unable to process. I need to tell our integration admin that enabling Consolidated Payments will not necessarily fix this problem. But then, I need to find a way to get the info needed by the integration without causing timeouts and errors. I'll see if I can find out why they need the overduebalance, and if "Customer-Subsidiary Relationship" will give them what they need.