--- title: "Point of Sale Related System Settings" canonical: "https://kb.myframeworks.com.au/space/FRAM/28391162/Point%20of%20Sale%20Related%20System%20Settings" format: markdown --- # Overview The Frameworks** Point of Sale (POS)** module can be customised to meet your business's specific needs. In order to do this various system settings and flag are required to be defined to turn on or off different functionality. > ⚠️ **Important**: Only users with the appropriate security access are able to make changes to the system tables. ### Click on the required system setting code for more information. *Tip: Press Ctrl + f to use your browsers search function to find the system setting you are looking for.* > Macro (toc) # System Settings - Flags The following system flags are related to all areas of Point of Sale. > ✅ Refer to [Amounts](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=Amounts) for more information on how to edit and maintain system flags. ## BranchMask **Flag/Setting Purpose**: Only Display Products that exist in Users Branch   - When enabled, the **Stocked Only** checkbox is enabled by default in the **Product Finder/Product Multi Selection** screen and only products in stock are retrieved. - When disabled, the **Stocked Only** checkbox is disabled by default in the **Product Finder/Product Multi Selection** screen and all products are retrieved, regardless of if they are in stock or not. --- ## ExtCommPOS **Flag/Setting Purpose: **Print extended product comments on POS - When enabled, this allows comments to print on star dockets. - When disabled, comments will not be printed on star dockets. --- ## FWDcktUuid **Flag/Setting Purpose: **Use a UUID in the file name for POS dockets  - When enabled: - When disabled: - if browser printing is enabled via **[FWBrwrPrnt](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=FwBrwrPrnt)**, the print spool file is named with the user’s device ID, concatenated with a UUID. - if browser printing is disabled via **[FWBrwrPrnt](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=FwBrwrPrnt)**,, the print spool file will not have the UUID concatenated onto the end of the file name. > ℹ️ The default setting for this flag is enabled. > ✅ **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173536](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173536) --- ## FWDelFeeLock **Flag/Setting Purpose: **Lock delivery fee field - When enabled, the **Delivery Fee** Field in the** Delivery Details tab** is disabled. No values can be entered and existing values cannot be changed. - When disabled, users will still be able to change the default delivery fee in the **Delivery Fee** field. --- ## FWManCusOr **Flag/Setting Purpose: **Mandatory customer purchase order numbers in use - When enabled, specific custom formats are activated for a Customer Order number. For example fields like Order No., Unit No., Address, Name and Job Number are used to make up the order number. Each field has certain requirements around length and input format as well as being optional or mandatory. These values must conform to the rules defined against each prompt. > ℹ️ To configure these custom formats, refer to **Order No. rules** in **Customer Maintenance** for further information. ![image](media://6375c967-cd79-4b5a-9487-b813e0134f80) - When disabled, custom formats for Customer Order numbers are not activated. --- ## FWNwgWarn **Flag/Setting Purpose: **Enable Warning Product with Insufficient Stock On POS/SOP - When enabled, a warning ⚠ will appear next to the **Product** field, when entering a product that has insufficient **Quantity Available to Pick ***(stock on hand - interim invoices - qty picked = Qty Available to Pick)*. If the product is still added to the POS or SOP transaction the **Qty **field will be highlighted red. This will be for all current orders with a product that has insufficient stock available to pick. ![image-20251021-044010.png](media://76865a32-59af-41a9-bcf8-f01d4e8cd3f1) ![image-20251021-051337.png](media://53db3cb7-9ef8-4651-82b0-d8f4781fe1aa) > ℹ️ - This **does not** stop you from adding the product to the sales order transaction. > ℹ️ - This validation does not apply to Type 6 **Miscellaneous Products**. - **When disabled**, there will be no notifications, however, stock levels will still be shown in the **Product Finder/Product Multi Selection** window or via the [Purchase Sales Information](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30507618/Viewing+Purchase+Sales+Information#Navigating-the-Purchase-Sales-Information-Window) window. --- ## FWOrdDays* **Flag Purpose**: Change the visible sales history period for a product - When enabled, you have the ability to click a product hyperlink to see the sales history of this product up to 365 days. - When disabled, you have the ability to click a product hyperlink to see the sales history of this product up to 90 days. --- ## FWPosCshPass **Flag/Setting Purpose: **Require password for Cash Customers - When enabled, Cash Customers will be prompted for a password (when one exists on their account) when finalising cash sales in POS. ![image](media://32875e7c-142e-4b61-9eb3-f62777e8271c) - When disabled, the password is not required to complete the POS sale. > ℹ️ Customer passwords can be set in **Customer Maintenance** under the **More Data** tab. > ℹ️ > ℹ️ If a password is set, the **Password** field is visible in the **Tendering** window but, a password isn't required to complete the sale unless this flag is enabled. --- ## FWPosPrint **Flag/Setting Purpose: **Show printing options on POS Tender - When enabled, printing options for account customers including Prices or Un-priced Dockets, Retail Prices, Trade Prices, Delivery Dockets and Preliminary Invoice/s will be available from within the Point of Sale tendering screen. > ⚠️ **Notes**: > ⚠️ > ⚠️ - This does not apply to cash sales. > ⚠️ - If the **[PosQckTnd](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=PosQckTnd)**** **flag is enabled, when clicking the documents which are set to print by default will be printed. > ℹ️ **Priced Docket:** > ℹ️ > ℹ️ - If **Retail Prices** is enabled, **Priced Docket** will be automatically enabled. Frameworks will not allow Priced Docket to be disabled when Retail Prices is enabled. > ℹ️ - When the **Priced Docket** is disabled, all the pricing (unit price, Line price and total prices) will be excluded from the docket. > ℹ️ - If the original docket was unpriced, the **last docket** print will also be unpriced. - When disabled, no extra printing options will be available for account customers from within the Point of Sale tendering screen (only POS docket printing). --- ## FWPosRefReq **Flag/Setting Purpose: **In POS, reference field is mandatory for customer type A - When enabled, the **Reference** field in the **Point of Sale** header is required for transactions for type A (standard debtor) customers. - When disabled, the **Reference** field is not a mandatory requirement for type A (standard debtor) customers. --- ## FWReqMobN **Flag/Setting Purpose: **Require mobile number on Cash Accounts - When enabled, the customer's mobile number field,** Phone (M),** mandatory when creating a new customer in SOP. - When disabled, the customer’s mobile number field is not a mandatory field when creating a new customer in SOP. --- ## FWSopQtDelDBlank **Flag/Setting Purpose: **Allow blank delivery date on Frameworks Quotes - When enabled, the **Delivery Date** is allowed to NOT be set when working with Quotes. - When disabled, the Delivery Date field is required to be populated when working with Quotes. --- ## FWSopQtDespBlank **Flag/Setting Purpose: **Allow blank despatch method on Frameworks Quotes - When enabled, the **Despatch Method **is allowed to NOT be set when working with Quotes. - When disabled, the Despatch Method** **must be populated when working with Quotes. --- ## FWSPECPOS **Flag/Setting Purpose: **Enable the Create of Special product popup for POS - When enabled, a **Special Product **button will be available from the Point of Sale screen. This is accessible from the **Actions** menu in the bottom right corner of the screen. - When disabled, the **Special Product** button is hidden from view on the Point of Sale screen. > ✅ Refer to [Special Product Creation](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30520386) for more information on Special Products. --- ## FWTenBlnk **Flag/Setting Purpose: **Frameworks Tender type to default to blank - When enabled, sets the **Tender type** field to default to blank and requires you to select an appropriate option. If an option is not selected, an error message appears "You must select a payment". ![image](media://c206a33b-a5d1-4ddd-bd8b-f63be785e6ef) --- ## GPLinePOS **Flag/Setting Purpose: **Allow GP per Line in SOP - When enabled, Frameworks allows you to reprice an individual product line based on a new GP% entered by a user. Repricing an individual product will re-price the product sell based on the current unit cost of the product line. Any previously existing discounts will be overridden as part of this process. For example, if a product had an existing *Discount %* of 10% and you applied a new *GP%*, the *Discount %* resets to 0. - When disabled, the ability to reprice an individual product line based on a new GP is not shown to the user when editing a Sales Order line. > ✅ Refer to cheat sheet: [How to reprice an individual product in POS based on a new GP%](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30515334) for more information. --- ## OrdAprNum **Flag/Setting Purpose: **Approval Number is mandatory within the Approval Details screen of Point Of Sale - When enabled, the **Approval Number **field will visible and required in the **Approval Details** screen when a customer is exceeding the credit limit in POS. - When disabled, the **Approval Number **field will NOT visible or be required in the **Approval Details** screen when a customer is exceeding the credit limit in POS. --- ## OrdDelFee **Flag/Setting Purpose: **Customer Delivery Fee overrides Area Selected Fee - When enabled, the **Customer Delivery Fee** overrides the **Area Selected Fee**. - When disabled, the Area Selected Fee overrides the Customer Delivery Fee. --- ## OrdReasOpt **Flag/Setting Purpose: **Price override reason is optional for FW Sales Order - When enabled, the** Override Reason** field is set as **optional**. - When disabled, the** Override Reason** field is set as **mandatory**. --- ## OrdReasOp2 **Flag/Setting Purpose: **Make the price override reason optional only on price increases in SOP (works with **[OrdReasOpt](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=OrdReasOpt)**). - When enabled, the** Override Reason** field is set as **optional** only for price increases, increased via the **Unit Price** field in SOP, POS and Interim Invoices. - If **OrdReasOpt** is disabled, for price decreases, the **Override Reason** field is still mandatory. A message “***A price override reason must be selected***” or “***You must enter a valid price override reason***” is displayed. --- ## OrdNegSell **Flag/Setting Purpose: **Allow negative sell prices to be entered in both POS and SOP - When enabled, negative sell prices are allowed to be entered for products on POS and SOP transactions. - When disabled, you are prevented from being allowed to enter a negative sell price of a product on POS and SOP transactions. --- ## OrdNegQty **Flag/Setting Purpose: **Allow negative quantity to be entered in POS - When enabled, negative product quantities are allowed to be entered into a point of sale transaction. A warning is shown to advise that “*The Quantity is Negative”*. - When disabled, you are prevented from being able to add a negative qty of a product into a point of sale transaction. > ⚠️ This will work inline with **[OrdNegSell](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=OrdNegSell)**. Disable both to prevent both the negative quantities and sell prices. > ⚠️ > ⚠️ **NOTE**: If the **OrdNegQty** is enabled and **[OrdNegSell](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=OrdNegSell)** is disabled, then a negative sell will still be used, however, you will NOT be able to enter a negative sell price. > ℹ️ **Related Flags:** [https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186781](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13186781) --- ## POSCODKeep **Flag/Setting Purpose: **Create Cash and COD accounts as permanent accounts - ie Not Casual - When enabled, the **Casual Account** option is disabled by default when adding a new customer in POS. - When disabled, the **Casual Account** option is enabled by default when adding a new customer in POS. --- ## POSHideBal **Flag/Setting Purpose: **Hide Balances and Discount during cash receipt - When enabled, ALL users will NOT be able to see the customers balance within the Customer Payments window at POS. > ⚠️ If the  **POSHidBal **flag is enabled, the customer's balance within the Customer Payments window at POS will be based on the users individual **Can View Account Balances **flag within User Maintenance. - When disabled, ALL users will see the customers balance within the Customer Payments window at POS. --- ## POSHideBlU **Flag/Setting Purpose: **Hide Balances driven by user security - When enabled, users will be able to see the customers balance within the Customer Payments window at POS based on the users individual **Can View Account Balances **flag within **User Maintenance**. > ℹ️ The **POSHidBal **flag is required to be enabled for the **Can View Account Balances **flag within **User Maintenance** to be functional. - When disabled, users will be able to see the customers balance within the Customer Payments window at POS bases on the **POSHidBal** flag. > ✅ Refer to **Can View Account Balances**, under the** Sales **section the [User Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28378032) User Manual for more information. --- ## PosMiscCostEdit **Flag/Setting Purpose: **Allows editing of cost on miscellaneous items in the** Point of Sale** screen. - When enabled, it allows editing of cost on miscellaneous items in **Point of Sale**. This means that once a miscellaneous product is added to the POS grid, users can click the **Pencil** icon to edit the transaction line. A popup will appear with the **Unit Cost** field visible and enabled for editing, provided the user has the necessary permissions to view costs. ![POSMiscCostEdit.png](media://a3302e61-a2d2-49f1-af1e-4b1a0ee05360) > ℹ️ For non-miscellaneous products added or edited on the transaction, the **Cost** field will not be visible or enabled. This restriction ensures that only miscellaneous items can have their costs edited. - When disabled, the cost field is not visible or editable for miscellaneous products in **Point of Sale**. --- ## PosNegCom **Flag/Setting Purpose: **Require mandatory comment for negative payments - When enabled, upon tendering a negative account payment, a comment is required in order to finalise the payment. - When disabled, a comment is not required to finalise the payment. --- ## POSNegCshR **Flag/Setting Purpose: **Restrict negative POS cash receipts for accounts - When enabled, account payments below zero are disallowed. When a negative value is entered, the user is presented with the following warning: - When disabled, negative account payments are allowed. > ℹ️ A negative payment limit can be set for users via the **Maximum POS Payment Refund** field under **Accounts Receivable** in User Maintenance. --- ## POSProdImgShow **Flag/Setting Purpose: **Display the product image during entry in Point of Sale. - When enabled, Frameworks displays the product’s **Main Image**, as defined in **Product Maintenance** under **General Information**, in the product entry section of Point of Sale. - When disabled, Frameworks does not display the product image during entry, regardless of whether a Main Image is defined. --- ## POSProdInfoShow **Flag/Setting Purpose: **Show product information text on Point of Sale. - When enabled, Frameworks displays the **Product Information **text in the product entry section of Point of Sale, if the **Info at POS** checkbox is selected for the product in **Product Maintenance** (under **General Information**). You can enter the **Product Information** text in the **Key Details** section of **Product Maintenance**. - When disabled, Frameworks does not display the **Product Information** text, even if the **Info at POS** checkbox is selected. --- ## PosQckTnd **Flag/Setting Purpose: **Quick Tendering Buttons Visible in Point Of Sale - When enabled, the **Quick ACCOUNT** and **Quick EFTPOS** buttons will be visible at the bottom of the Point of Sale screen and available to use. - When disabled, the **Quick ACCOUNT **and **Quick EFTPOS **buttons will be hidden at the bottom of the Point of Sale screen. > ✅ Refer to [Processing a Quick POS Sale](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30529128) for more information. --- ## RecCashEml **Flag/Setting Purpose: **Force collection of email address when creating cash card customers in POS and SOP - When enabled, it forces the sales person to collect an email address when creating cash card customers in Point of Sale (POS) and SOP. - When disabled, transactions in Point of Sale (POS) and SOP behave as normal for cash card customers. --- ## SLYPMobile **Flag/Setting Purpose: **Enable Mobile Phone for Slyp Receipt - When enabled, a Mobile Phone Number can be entered in the Tender Receipts screen, allowing you to send a Smart Receipt to the customer’s Smartphone. - When disabled, Slyp will send only Bank Receipts, if the Slyp API is enabled and you are using Windcave Eftpos. > ℹ️ **Important: **The **System Setting - General** Slyp API configuration values are required to be configured for Smart Receipts to be enabled. --- ## SopPurUom **Flag/Setting Purpose: **Suppress the purchase UOM as a selling UOM - When enabled, Point of Sale automatically populates with the EA UOM. - When disabled, Point of Sale automatically opens the UOM finder (both EA and BX UOM) screen when there is a different purchasing UOM available. --- ## SpcItmBcode **Flag/Setting Purpose: **Controls whether the Barcode field is required when creating a Special Product in Sales Order Processing (SOP) and Point of Sale (POS). **Possible Values:** - When set to **Not Required**, the Barcode field does not appear in the Special Product creation window. - When set to **Optional**, users may enter a barcode or leave the field blank. - When set to **Mandatory**, a barcode must be provided before the Special Product can be saved. If the auto-generation flag ([SpcItmGenBcode](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=SpcItmGenBcode)) is enabled, the system will generate a unique barcode automatically. --- # SpcItmGenBcode **Flag/Setting Purpose:** Automatically generates a unique barcode for Special Products when they are created in Sales Order Processing (SOP) or Point of Sale (POS). > ⚠️ If [SpcItmBcode](https://sterlandsupport.atlassian.net/wiki/pages/createpage.action?spaceKey=CIL&title=SpcItmBcode) is set to "Not Required," this flag has no effect (the field is hidden) **When Enabled:** - The system automatically fills the Barcode field for new Special Products. - If a supplier barcode exists, it is used; otherwise, a unique barcode is generated. - Ensures every Special Product has a barcode, supporting EDI and reducing manual entry. **When Disabled:** - You must enter the Barcode manually if required by SpcItmBcode. - No automatic barcode generation occurs. --- ## TendCrdBal **Flag/Setting Purpose: **Use credit balance as tender at POS? - When enabled, a Cash or COD customer is allowed to pay with any outstanding credit that has accumulated on their account. The credit balance available is shown as a field (*Credit Balance Avail.* field) on the POS tendering screen and if the customer wishes to use this amount, the credit balance option is a selectable tender type in the normal drop down selection. Once a customer payment has been made using a credit balance, the **Current Transactions** tab in the Customer Dashboard displays the payments and adds a *"Credit balance tendered for nnnn"* (where *nnnn* = the POS transaction no) as a reference. Account customers and standard debtors cannot use outstanding credit to pay for purchases. > ℹ️ Only unassigned and outstanding credit balance/s can be used as a valid payment type in a POS transaction. > ⚠️ **Pre-Requisites:** > ⚠️ > ⚠️ 1. A value must be created for the **CrdBalCode** flag/code which defines the tender type value as a credit balance. For example, in the screenshot below, the code for a Credit Balance is **CRBAL**. CRBAL is then used to create the new tender type in step 2 below. Following the creation of the new tender type, CRBAL is then available as a valid tender type when processing POS payments. > ⚠️ > ⚠️ - Refer to **System Settings - General** to create this value. > ⚠️ > ⚠️ 2. The Credit Balance tender type must first be created with *Clearing Accounts* defined for the applicable Branch/s (required for all POS transactions) & the *Non Physical Tender* check box field enabled. > ⚠️ > ⚠️ - Refer to **Tender Types** for further information. - When disabled, Cash or COD customers cannot use their outstanding credits on the system to pay for POS transactions.
Example POS tendering screenshots & further information: If the available credit on the customer's account is equal to or greater than the transaction balance, then only the value of the transaction is displayed in the Credit Balance Avail. field. That is, this field does not provide the full credit balance on the customer's account, only the credit balance available for this transaction. ![image](media://c49efc0c-5d14-4c9d-b9e2-0441fbf96017) If the available credit on the customer's account is less than the transaction balance, only the available credit balance is displayed in the Credit Balance Avail field. Other payment methods will be required to finalise this transaction. ![image](media://89c21d04-cc2b-48a6-9fca-c53a7fc2546c)
Example Current Transactions screen (via the Customer Dashboard): Once a customer payment has been made using a credit balance, the [Current Transactions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28378786) tab in the Customer Dashboard displays the payments and adds a *"Credit balance tendered for nnnn"* (where *nnnn* = the POS transaction no) as a reference. ![image](media://4408a79d-597f-49d5-977a-02e98dad5fc8) The customer's balance will also be reduced in the [Credit Information](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28378802) section.
--- ## TimVal **Flag/Setting Purpose: **Timber length validation by product - When enabled, it validates product timber lengths either at the system level or at the product level. If a timber length is invalid, an error message “***Invalid Product Length (.nn)*****” **appears. If timber lengths are defined at both the system and product level, the product level takes precedence. - When disabled, no validation occurs when adding timber lengths. --- # System Settings - Numeric The following system numeric settings are related to all areas of Point of Sale. > ✅ Refer to [System Settings - Numeric](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28401694) for more information on how to edit and maintain system numeric settings. --- ## LstPrdSrch **Setting Purpose**: This specifies the number of characters of the last product id entered to use as the search text in the product finder.  If System setting **LstPrdSrch **has been setup, entering a backslash into the **Product** field will bring up the previous Product ID used on the last sale. System setting **LstPrdSrch **specifies the number of characters of the last Product id entered to use as the search text in the Product Finder. --- ## QtyOrdDays **Setting Purpose**: Future days to accumulate on-order qty In the **Value** field. enter the number of days into the future the scheduled task QtyOnOrder will search to find Products on an order. --- # System Settings - General The following general system settings are related to all areas of Point of Sales. > ✅ Refer to [System Settings - General](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28382808) for more information on how to edit and maintain general system settings. --- ## CompDefReason **Settings Purpose**: Default reason code for price override when composite product id is scanned Enter the **Default Override Reason **into the **Value** field. This will be added to the product when added via a composite barcode. If no value has been entered a price **Override Reason **will need to be selected. > ℹ️ In Point of Sale composite barcodes can be scanned or entered which allows for one barcode to populate the Product ID, Quantity and Unit Price, using a pipe ( | ) delimited, for example, Product code | quantity | Price. --- ## POSDefDesp > Macro (include) --- ## PosDefEft **Setting Purpose**: Default Card Type for Quick Tendering Enter the default **Card Type** into the **Value** field. This will be applied when processing an EFTPOS sale and will allow you to skip the requirement for selecting the card type.  > ✅ Refer to the miscellaneous table **System - Credit Card Type Codes **for a list of your Card Type codes. --- ## PosQckEft **Setting Purpose**: Default Eft Host for Quick Tendering Enter the default integrated EFTPOS host into the **Value** field.  > ⚠️ To use Windcave EFTPOS as the default for quick tendering, enter **Windcave** as the value. > ✅ Refer to [Tender Types](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28385410) for EFTPOS host code. --- ## SopDrctDel > Macro (include) --- ## SOReqTime **Flag/Setting Purpose:** Default requested time for Sales Orders - Enter a **Requested Delivery Times code** into the **Value** field. This will set a default value in the **Requested Time** field when creating a new sales quote, order, or POS transaction. If this field is left blank, no default value will be set. > ℹ️ **Note:** Request Times MUST be defined first in the **Requested Delivery Times** table. --- ## SysRndGrp **Setting Purpose**: Cash Rounding For cash sales where rounding occurs, the variance will create a new line in the docket. This variance is also posted to the cash sale [General Ledger](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28377214) account that is associated with the product group assigned via the system code: '**SysRndGrp'**. --- # System Settings - Amount The following amounts system settings are related to all areas of Point of Sales. > ✅ Refer to [System Settings - Amounts](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28382798) for more information on how to edit and maintain amounts system settings. ## CshLndrLmt **Setting Purpose**: Cash tender limit for anti-money laundering rules Enter the cash tendering limit into the **Value (Amount) **field. You will be able to tender cash amount about this limit, however, the Customer Name, Address, Suburb and States is required to complete the transaction. > ❌ Check with your counties Anti-Money Laundering Laws to ensure you comply to the correct amount. ---