Skip to content


How to import SOP Transactions with taxes using SmartConnect

Importing SOP transactions with taxes requires adding a sequence number to the source file in order to link the correct tax detail to the correct line item.

Taxes Use the XML node to control how taxes are calculated.

To use header level taxes, set the header level taxes (USINGHEADERLEVELTAXES) element to 1.

To use detailed taxes, set USINGHEADERLEVELTAXES to 0. The default value for USINGHEADERLEVELTAXES is 0. If you set USINGHEADERLEVELTAXES to 1, be aware of the following: Header level taxes only specify tax information when the line sequence element of the XML node is set to 0.

To use header level taxes when the tax is set as “tax included in item price”, you must include a sequence number in the tax node. eConnect automatically creates the 0 sequence number tax layer. As a result, the tax amount is not passed to either the header or the line, and it does not reduce the document amount or the subtotal. You must manually calculate the tax amount and specify that along with the reduced sales amount in the XML node.

To simplify using “tax included in item price” you should set the CREATETAXES element of the node to 1. This allows eConnect to autocreate taxes. The following display how to populate select elements when using header level taxes and a tax detail of “tax include in item price”:
LNITMSEQ = 16384 /*Required-Line item sequence*/
TAXDTLID = ‘TAX IN ITEM’ /*Required-the example uses 10% tax included in item price */
SALESAMT = 454.55,
STAXAMNT = 45.45
<taSopHdrIvcInsert> TAXAMNT = 0,
SUBTOTAL = 500 /*Required*/
DOCAMNT = 500 /*Required*/
You can use header level taxes with invoices that will be posted without being transferred, or with orders that will be fully transferred to invoices and then posted. When an order is partially transferred to invoices or back orders, the tax is recalculated. There are no details with header level taxes so when taxes are recalculated on a partially transferred order, the tax information is lost and not carried forward. If you do not use the miscellaneous tax (MSCTXAMNT) and freight taxes (FRTTXAMNT) elements in the XML node, you must set the sales tax amount (STAXAMNT) element with the actual sales tax amount. If MSCTXAMNT and FRTTXAMNT are used, STAXAMNT is not used. If you use the XML node to manually update components, the update does not automatically recalculate taxes.

To ensure the update recalculates taxes, include the node, and set the CREATETAXES element to 1. Tax engine eConnect includes a tax engine that allows you to automatically create taxes. If you use the tax engine, you no longer need to specify tax information in the tax nodes. The XML node contains six elements that control the tax engine.

To use the tax engine, be aware of the following: Set the create taxes flag (CREATETAXES) element to 1 to use the tax engine. If you are integrating your own taxes, set CREATETAXES to 0. The freight tax schedule (FRTSCHID) and miscellaneous tax schedule (MSCSHID) elements mirror the tax schedule ID (TAXSCHID) element. If the default tax schedule flag (DEFTAXSCHDS) element is set to 0, you must populate the TAXSCHID, FRTSCHID, and MSCSHID elements of the XML node. You must also set the item tax schedule ID (ITMTSHID) and the delivery method tax schedule ID (TAXSCHID) elements of the XML node. If the DEFTAXSCHDS element is set to 1, the tax schedule defined by setup will be the default. You must specify the shipping method (SHIPMTHD) element to provide the schedules used to create freight and miscellaneous tax for the SOP header. In addition, the ITMTSHID and TAXSCHID element of the XML node must be excluded from the XML node or set to null. If you populate these two elements as blank (‘ ‘) it will blank out the schedules and no taxes will be created. The freight taxable (FREIGTBLE) and miscellaneous amount taxable (MISCTBLE) elements in the XML node default to 0. Use these elements to indicate whether freight or miscellaneous charges are taxable. You set these elements to indicate whether these charges are taxable, nontaxable, or based on the customer’s tax schedules. These are the same options available in the Microsoft Dynamics GP client. The inventory item taxable (IVITMTXB) element of the node defaults to 0. You use this element to indicate whether the individual freight charge is taxable, nontaxable or based on the customer’s tax schedule. These are the same options available in the Microsoft Dynamics GP client. You may still use the tax nodes to calculate taxes. However, you no longer need to pass a sequence record of zero through the tax nodes. You only need a sequence record of zero when header level taxes are used. If you specify the taxes, the CREATETAXES element must be set to 0.


Configuring Salesforce Integration User
Business Central Extension Publish Error
Re-registering a Change Data Source in Business Central on
Moving SmartConnect 21 to a new server
eConnect error 4628 - The Tracking Number (Tracking_Number) is empty


SSL Security error using OLEDB Connection
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms
Removed Part: /xl/vbaProject.bin part. (Visual Basic for Applications (VBA))
The server process could not be started because the configured identity is incorrect.
Using WINSCP and a task to upload or download files from an SFTP site



Business Central CRM D365 Business Central Dynamics 365 dynamics crm Dynamics GP Dynamics NAV Econnect Employee Spotlight eone eOne News error Error Message Events Excel Excel Report Builder Extender Flexicoder GP integration Map Microsoft dynamics crm Microsoft Dynamics GP Navigation List Builder Office Relationships Partner All Hands Call Popdock promotions release Salesforce SmartConnect SmartConnect Bootcamp SmartConnect Maps SmartConnect Office Hours SmartList SmartList Builder SmartPost SmartView SQL Tech Tuesday Templates training Zendesk

Integrate & Automate without Any Code.

SmartList Data has Never Been Faster.

The Easiest Way to Report on GP Data.