--- title: "General settings for Financial" description: "Overview of the basic financial settings in Financial: auto save, warnings, discount strategy, product instances, used VAT and product lookup on sales documents." url: https://support.sapera.io/en/articles/193-general-settings-for-financial collection: "Financial" updated: 2026-07-07 language: en alternates: [da] --- # General settings for Financial Overview of the basic financial settings in Financial: auto save, warnings, discount strategy, product instances, used VAT and product lookup on sales documents. This article reviews the basic settings that control the behaviour across the document and sales screens in Financial. The settings cover, among other things, auto save and warnings about unsaved changes, requirements for information when creating customers and debtors/creditors, how discounts are selected, as well as a range of options for handling serial-number items (serial number items), used VAT and product lookup on sales documents. In the user interface the labels are shown in English. Below, each setting is described with both the Danish name and the English label, so it is easy to find on screen. ## How to find the settings Open the hamburger menu in the top left corner and select **Financial**. Then go to **Setup** and **Settings**. Find the category **Financial** and select the subcategory **Financial**. Note that changing settings normally requires administrator or setup permissions. Contact your administrator if you do not have access. ## Save and warnings ### Auto save Specifies whether changes in the screens are saved automatically, without you having to manually press **Save**. **Yes:** changes are saved automatically. **No:** changes are only saved manually. The default is **No**. ### Warn on discard Specifies whether a warning is shown when you leave a screen with unsaved changes. **Yes:** a warning is shown so you do not unintentionally lose changes. **No:** no warning is shown. The default is **No**. ## Creating customers, debtors and creditors ### Force select debtor/creditor category Determines whether selecting a category is required when a debtor or creditor is created. **Yes:** a category must be selected. **No:** the category is optional. The default is **No**. ### Expect phone number on customer creation Specifies whether a phone number is expected to be filled in when creating a new customer. **Yes:** a phone number is required. **No:** a phone number is optional. The default is **No**. ### Contact person role (override) Overrides which contact person role (a text value, not a specific person) is used when a contact person is selected on a document. The field is empty by default, which means the default behaviour is used. ## Discounts ### Discount selection strategy Controls how Sapera chooses between several possible discounts when more than one can be applied at the same time. **Best for customer:** selects the discount that gives the customer the greatest saving. **Best for shop:** selects the discount that gives the smallest saving (best for the shop). **Ordered:** applies the discounts in the order they are specified. The default is **Best for customer**. ## Serial-number items, used VAT and stock ### Is purchasing serial-number item with used vat supported Specifies whether the system supports purchasing serial-number items (serial number items) with used VAT. **Yes:** supported. **No:** not supported. The default is **Yes**. ### Support purchasing back with used VAT from customer organizations with CVR Specifies whether buy-backs with used VAT may be created from business customers (organizations) with a CVR number. **Yes:** allowed. **No:** not allowed. The default is **No**. ### Is returning serial-number item supported Determines whether it is possible to return serial-number items (serial number items). **Yes:** returns are possible. **No:** returns are not possible. The default is **Yes**. ### Disallow selling not available instance in other OU Determines whether a serial-number item that is not available in the current organizational unit (OU) may be sold. **Yes:** instances that are not available in the current OU cannot be sold. **No:** instances can be sold across OUs. The default is **No**. ### Prompt for location on purchase Specifies whether the user must specify a stock location on a purchase, i.e. where the item is received. **Yes:** the user is asked to select a location. **No:** no prompt is shown. The default is **Yes**. ## Product lookup on sales documents ### Show sold instances in sales entities lookup Determines whether already sold serial number items (instances) are shown in the product lookup on sales documents. **Yes:** sold instances are shown. **No:** sold instances are hidden. The default is **Yes**. ### Show availability filter in sales entities lookup (only show products on stock) Determines whether a filter is shown in the product lookup on sales documents, so you can limit it to items that are in stock. **Yes:** the filter is shown. **No:** the filter is not shown. The default is **No**. ## Addresses and dispatches ### Store financial addresses Determines whether separate financial addresses (e.g. invoice or delivery addresses) are stored. **Yes:** financial addresses are stored. **No:** only default addresses are used. The default is **Yes**. ### Support dispatches Specifies whether dispatches are supported in the financial flow. **Yes:** dispatches are supported. **No:** dispatches are not supported. The default is **Yes**. ## Product IDs ### Text Product Id Here you specify the product ID for a text product — a non-stocked item used for free-text lines on documents, e.g. for subscription and lease contract invoicing. The field is not set by default. ### Unknown Product Id Product ID used if a product cannot be identified. Typically used in error scenarios or in connection with integrations. The field is not set by default. ## Integrations ### Is YAMAHA integration supported Enables support for the YAMAHA integration. **Yes:** the integration is enabled. **No:** the integration is turned off. The default is **No**. Note that this setting can only be changed by Cloud Retail Systems' support. * * * **Want to know more?** Read more in these related articles: [ Financial setup The financial setup determines which financial accounts and posting journals Sapera uses when the system automatically generates entries for sales, purchases, cash register closing, stock adjustment and year-end closing. Here you configure default accounts, journals and integration settings per organizational unit. ](https://support.sapera.io/en/articles/68.md)[ User interface settings User interface settings collect the settings that control Sapera's user interface — including rounding of amounts in the display as well as the subcategories for user and actor preferences. ](https://support.sapera.io/en/articles/422.md)