Share
Report
I'm trying to figure out how to setup our contract system to work more effectively but am hitting a snag.
The issue is for manually generated SOP, it pulls the tax schedule from the customer master card, whereas the contract pulls from the line tax scheduleID, which if left blank still pulls from that field so makes it blank; then uses this to compare to the item taxability.
The way our company processes exemptions is to create a tax schedule on the customer master which defines their exemptions. ex. NO ONPST(No Ontario Retail Sales Tax) which is then assigned all tax details other than ORST(S-ON-PST for us). If we setup the contract lines to NO ONPST then this means that whenever a change occurs to a clients taxability, we need to also update ALL lines in all active contracts with that customer as again if we just leave it blank it doesn't grab the schedule from the customer master. This works great for manual SOP, but a nightmare for contracts.
Do I have this setup wrong? Or is there a better way?
*This post is locked for comments
All responses (
Answers (
2,250
