# TQ Setup

After installation, navigate to the TradeQloud Setup under **TradeQloud > Setup > Setup**

## Setup - Sales Costs 

\
**Enable Sales Costs** \
Enables the Sales Cost Functionality

***

**Sales Cost Transactions**\
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.

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

***

**Sales Cost Subsidiaries**\
Select the Subsidiaries that Sales Cost should execute on.

***

**Sales Cost Locations**\
Select the Locations that Sales Cost should execute on.

***

**Sales Cost Rounding**\
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.

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

***

**Default Sale Cost PO Creation Method** \
The Cost PO Creation Method defines the standard procedure for generating Purchase Orders (POs) for costs.
 This setting determines the default value on Customer / Sales Cost Budget / Transaction Cost records but can be changed as required.\
\
 [For more information, click here](https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/sales-costs-setup/po-creation-methods).

***

**Default Sales Cost Processing Method** \
The Sales Cost Processing defines the strategy for how the Sales Cost Record is transacted. For more information on each method, please refer to the User Manual.\
\
 [For more information, click here](https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/sales-costs-setup/sales-cost-processing-methods).

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

***

**Default Sales Cost Custom Price Handling Method** \
This setting allows for the differentiation between custom pricing derived from customer master data and custom pricing set on a transaction by a user.\
\
 [For more information, click here.](https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/sales-costs-setup/sales-cost-custom-price-handling)

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

***

**Default Percentage Rate Calculation Method**\
With this setting you can set the default value that's used as the starting value when a percentage Sales Cost is used to increase/decrease the rate. \
\
[For more information, click here.](https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/sales-costs-setup/sales-cost-percentage-change-method)

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

***

**Automatically Process Sales Cost Variance**\
This setting allows you to automatically create a Journal when a Sales Cost PO with a variance is billed.

***

## Setup - Landed Costs

**Enable Landed Costs** \
Enables the Landed Cost Functionality

***

**Landed Cost Transactions**\
Select the supply transactions to which sales costs can 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 to a transaction.

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

***

**Landed Cost Subsidiaries**\
Select the Subsidiaries that Landed Cost should execute on.

***

**Landed Cost Locations**\
Select the Locations that Landed Cost should execute on.

***

**Landed Cost Rounding**\
Allows 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.

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

***

**Update IR Rate Saved Search**

Specifies 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.

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

***

**Update IR Rate based on Vendor Bill Rate**

With this setting, when a Vendor Bill is saved, the rate between the Vendor Bill and the Item Receipt will be compared. Any variance rates will be updated on the Item Receipt.

***

**Default Landed Cost PO Creation Method** \
The Cost PO Creation Method defines the standard procedure for generating Purchase Orders (POs) for costs.
 This setting determines the default value on Vendor / Landed Cost Budget / Transaction Cost records but can be changed as required.\
\
 [For more information, click here](https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/landed-costs-setup/po-creation-methods).

***

**Default Primary Landed Cost Variance Method** \
The Primary method for handling variances (i.e. discrepancies) between budgeted and actual landed costs.

[For more information, click here](https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/landed-costs-setup/primary-landed-cost-variance-method).

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

***

**Default Secondary Landed Cost Variance Method** \
The 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.

[For more information, click here](https://docs.tradeqloud.com/qloud-margin-control/using-qmc/setup-guides/landed-costs-setup/secondary-landed-cost-variance-method).

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

***

**Automatically Process Landed Cost Variance**\
This setting allows you to automatically create a Journal when a Landed Cost PO with a variance is billed.

{% hint style="info" %}
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 
{% endhint %}

***

## Need Assistance?

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

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 %}