# Backup of TQ Setup

## Landed Costs

<table data-full-width="true"><thead><tr><th width="242">Field</th><th>Description</th></tr></thead><tbody><tr><td>Enable Landed Costs</td><td>Enable this feature to enhance the standard NetSuite landed cost functionality. Once enabled, it is possible to establish vendor landed cost budget records linked to vendors (master data).</td></tr><tr><td>Landed Cost Transactions</td><td>Select all supply transactions to which landed costs are to be applied. After selection, the application will generate Transaction Landed Cost Budget records on the record, or it will offer users the option to add these manually</td></tr></tbody></table>

{% hint style="info" %}
It is recommend that **Purchase Order** is populated in the Landed Cost Transactions field
{% endhint %}

<table data-full-width="true"><thead><tr><th width="245">Field</th><th>Description</th></tr></thead><tbody><tr><td>Landed Cost Rounding</td><td>Landed Cost Rounding allows for specifying the decimal rounding precision for calculated landed cost values. This setting determines how the system rounds off the final amounts of landed costs allocated to each item or transaction line, ensuring consistency and accuracy in financial reporting.</td></tr></tbody></table>

<table data-full-width="true"><thead><tr><th width="245">Field</th><th>Description</th></tr></thead><tbody><tr><td>Landed Cost Subsidiaries</td><td>Select the Subsidiaries that Landed Cost should execute on.</td></tr><tr><td>Landed Cost Locations</td><td>Select the Locations that Landed Cost should execute on.</td></tr></tbody></table>

{% hint style="success" %}
The recommend **Landed Cost Rounding** is 3 decimals
{% endhint %}

<table data-full-width="true"><thead><tr><th width="246">Field</th><th>Description</th></tr></thead><tbody><tr><td>Update IR Rate Based on Vendor Bill Rate</td><td>If this is checked, when a Vendor Bill is saved , the application will compare the rates Vendor Bill and Item Receipt rates. If there is a variance, the rate will be updated on the Item Receipt.</td></tr></tbody></table>

{% hint style="success" %}
It is recommend to **enable** this feature
{% endhint %}

<table data-full-width="true"><thead><tr><th width="254">Field</th><th>Description</th></tr></thead><tbody><tr><td>Update IR Rate Saved Search</td><td>Select the saved search used to identify any variances between the Item Receipt Rate and the Vendor Bill Rate. The saved search results identify which receipts are to be updated.</td></tr></tbody></table>

{% hint style="success" %}
It is recommended selecting the default saved search **FQ APM - Update Rate**, unless there are specific requirements for Item Receipts that should not be updated
{% endhint %}

<table data-full-width="true"><thead><tr><th width="256">Field</th><th></th></tr></thead><tbody><tr><td>Default Landed Cost PO Creation Method</td><td>Defines the standard action for generating POs (Purchase Orders) for Vendor, Item or Transaction Landed Costs (Budget) records. On individual records this setting can be changed as required.</td></tr><tr><td>Default Primary Landed Cost Variance Method</td><td>Select a Primary method for handling variances (i.e. discrepancies) between budgeted and actual landed costs.</td></tr><tr><td>Default Secondary Landed Cost Variance Method</td><td>Select a Secondary method for handling variances (i.e. discrepancies) between budgeted and actual landed costs. In case the Primary method is Update Inventory Cost (Open Period Only), this setting is mandatory.</td></tr></tbody></table>

{% hint style="success" %}
It is recommended to select **Update Inventory Cost (Open Period Only)** as **Default Primary Landed Cost Variance Method**&#x20;
{% endhint %}

{% hint style="success" %}
It is recommended to select **Journal to COGS** as the **Default Secondary Landed Cost Variance Method** field
{% endhint %}

<table data-full-width="true"><thead><tr><th width="260">Field</th><th>Description</th></tr></thead><tbody><tr><td>Automatically Process Landed Cost Variance</td><td>The application will when checked, after a Landed Cost Vendor Bill is processed, compare the rates between the Vendor Bill and Item Receipt.</td></tr></tbody></table>

If there is a variance, the variance will be automatically handled based upon the variance method on the transaction landed cost.&#x20;

{% hint style="success" %}
It is only recommend that the **Automatically Process Landed Cost Variance** is enabled after one month of transacting using QMC to ensure results are understood before impacting the general ledger&#x20;
{% endhint %}

***

## Sales Costs

<table data-full-width="true"><thead><tr><th width="261">Field</th><th>Description</th></tr></thead><tbody><tr><td>Enable Sales Costs</td><td>Enable this feature to track sales costs in addition to the cost of goods sold. Once enabled, it is possible establish Sales Cost Budget records (master data).</td></tr><tr><td>Sales Cost Transactions</td><td>Select the demand transactions to which sales costs can be applied. After selection, the application will generate Transaction Sales Cost Budget records on the transaction, or it will offer users the option to add these manually to a transaction.</td></tr></tbody></table>

{% hint style="success" %}
It is recommend that **Sales Order & Invoice** is populated in the Sales Cost Transactions field
{% endhint %}

<table data-full-width="true"><thead><tr><th width="245">Field</th><th>Description</th></tr></thead><tbody><tr><td>Sales Cost Subsidiaries</td><td>Select the Subsidiaries that Sales Cost should execute on.</td></tr><tr><td>Sales Cost Locations</td><td>Select the Locations that Sales Cost should execute on.</td></tr></tbody></table>

<table data-full-width="true"><thead><tr><th width="260">Field</th><th>Description</th></tr></thead><tbody><tr><td>Sales Cost Rounding</td><td>Allows specifying the decimal rounding precision for calculated sales cost values. This setting determines how the system rounds off the final amounts of Sales Costs allocated to each item or transaction line, ensuring consistency and accuracy in financial reporting.</td></tr></tbody></table>

{% hint style="success" %}
The recommend **Sales Cost Rounding** is 3 decimals
{% endhint %}

<table data-full-width="true"><thead><tr><th width="261">Field</th><th>Description</th></tr></thead><tbody><tr><td>Default Sales Cost PO Creation Method</td><td><p>Defines the standard action for generating POs (Purchase Orders) for costs. </p><p></p><p>This setting determines the default value on Customer, Item or Transaction Sales Costs (Budget) records. On individual records this setting can be changed as required.</p></td></tr><tr><td>Default Sales Cost Processing Method</td><td>The Sales Cost Processing defines the strategy for how the Sales Cost Record is transacted. </td></tr></tbody></table>

The available options for **Sales Cost Processing Methods** are:

<table data-full-width="true"><thead><tr><th width="264">Option</th><th>Description</th></tr></thead><tbody><tr><td>Add as Line Item - Individual</td><td>Will add each sales cost budget as a separate line item on the transaction.</td></tr><tr><td>Add as Line Item - Grouped</td><td>Will group each sales cost budget per sales cost and combines into a transaction line.</td></tr><tr><td>Add as Discount Item</td><td>Applies the sales cost as a discount item, inserting a discount line underneath each applicable line item. This can be an increase or decrease.</td></tr><tr><td>Change Rate with Custom GL Posting</td><td>Adjusts the rate on the transaction and posts the sales cost as a custom GL posting based on the item selected.</td></tr><tr><td>Change Rate</td><td>Changes (i.e. increases or decreases) the rate on the transaction to include the sales cost, directly altering the transaction amount.</td></tr><tr><td>Custom GL Posting</td><td>Posts the sales cost to the general ledger based on the item selected, without altering the transaction amount or rates.</td></tr><tr><td>No GL Posting</td><td>Processes the sales cost without posting any entries to the General Ledger, ensuring no financial impact.</td></tr></tbody></table>

{% hint style="success" %}
It is recommended that **Change Rate and Custom GL Posting** is set as the **Default Sales Cost Processing Method**
{% endhint %}

<table data-full-width="true"><thead><tr><th width="262">Field</th><th>Description</th></tr></thead><tbody><tr><td>Default Sales Cost Custom Price Handling Method</td><td><p>Allows for the differentiation between custom pricing derived from customer master data versus custom pricing set on a transaction (by a user or via integration e.g. EDI). This setting only applies when:</p><ul><li>The transaction line has the price level set to ‘Custom’</li><li>A Sales Cost applies that has ‘Change Rate’ set to TRUE </li></ul></td></tr></tbody></table>

The following **Custom Price Handling Methods** options are available:&#x20;

<table data-full-width="true"><thead><tr><th width="266">Field</th><th>Description</th></tr></thead><tbody><tr><td>Always Change Custom Rate</td><td>Sales Cost will modify the rate in all scenarios. </td></tr><tr><td>Change Manually Entered Rates Only</td><td>Sales Cost will modify the rate if a user/integration or script has (manually) changed the rate on the transaction.</td></tr><tr><td>Change Customer/Item Specific Custom Pricing</td><td>Sales Cost will modify the rate if the rate is sourced from the Customer Item Pricing record.</td></tr><tr><td>Never Change Custom Rate</td><td>Sales Cost will never modify the rate.</td></tr></tbody></table>

{% hint style="success" %}
It is recommend that **Always Change Custom Rate** is set as the **Default Sales Cost Custom Price Handling Method**&#x20;
{% endhint %}

<table data-full-width="true"><thead><tr><th width="268">Field</th><th>Description</th></tr></thead><tbody><tr><td>Default Percentage Rate Calculation Method</td><td>Select the default value to use as the starting value when a percentage Sales Cost is used to increase/decrease the rate.</td></tr></tbody></table>

&#x20;For above **percentage rate calculation methods** following options are available:

<table data-full-width="true"><thead><tr><th width="270">Option</th><th>Description</th></tr></thead><tbody><tr><td>Starting Rate</td><td>is the price (custom or price level) entered on the transaction line during creation of the transaction</td></tr><tr><td>Rate </td><td>is the calculated price after all sales costs set as 'Change Rate' = TRUE have been applied to the starting rate</td></tr><tr><td>Net Rate</td><td>is the calculated net margin after all sales costs set as 'Change Rate' = FALSE have been applied to the starting rate</td></tr></tbody></table>

{% hint style="success" %}
It is recommended that **Starting Rate** is used in **Default Percentage Rate Calculation Method** fields
{% endhint %}

<table data-full-width="true"><thead><tr><th width="260">Field</th><th>Description</th></tr></thead><tbody><tr><td>Automatically Process Sales Cost Variance</td><td>When a Sales Cost PO is billed, if there is a variance the script will automatically create a Journal for the variance.</td></tr></tbody></table>

***

## Need Assistance?

{% hint style="success" %}
If you continue to experience issues after following this guide, we recommend reaching out for further assistance.&#x20;

Please contact us at <support@tradeqloud.com> with a detailed description of the problem. Our dedicated support team is committed to helping you resolve any challenges you may encounter.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/backup-of-tq-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.