First, my question can be more broadly stated as "how can taxes be reliably calculated by a developer due to eConnect's lack of a tax engine for Payables?" I ask because my present understanding is that I am not going to be able to get eConnect to calculate taxes for me, I must calculate them myself and import using taPMTransactionTaxInsert.
Second, the link above was sent to me by more than one colleague stating "Here it is, David Musgrave has it figured out." Clearly, the post was not read before sharing because it does not describe the accurate calculation of the tax, only the tracking requirement of a Tax Invoice record.
So:
1. eConnect will not calculate taxes in Payables for me.
2. After taxes are imported I will have to implement Musgrave's post procedure described in the linked article.
Does this all mean that
3. I have to reverse engineer the settings described by a Tax Detail ID and write my own tax calculation logic?
Or
4. Is there some method where I can get GP business logic to calculate the tax for me?
Application background : I have an existing Windows Service app creating AP transactions. Written in C#.NET, it reads from a staging table on a time interval, turns those records into AP transactions and moves the staged records to a history table with the Payables transactions' key info. App performance is an essential consideration.
*This post is locked for comments