Settings & Configuration

System Parameters

System parameters store key-value configuration pairs. They are used to customise Quickenerp's behaviour without writing code.

Navigation

Go to Settings > Technical > System Parameters (developer mode required).

Commonly Used System Parameters

Creating a System Parameter

1. Click Create.
2. Key – Use dot notation (e.g. mycompany.some_setting). Follow existing conventions for consistency.
3. Value – The string value. Quickenerp automatically parses booleans, integers, and floats.
4. Click Save. The parameter takes effect immediately (some may require a page reload).

Sequences

Sequences control auto-numbering of documents – invoice numbers, quotation numbers, order references, etc.

Navigation

Go to Settings > Technical > Sequences > Sequences (developer mode).

Sequence Structure

Each sequence has:

• Name – e.g. "Sales Order Sequence".
• Code – Internal code (e.g. sale.order for sales orders).
• Prefix – Text before the number: SO/{{year}}/ produces SO/2026/0001.
• Suffix – Text after the number.
• Padding – Number of digits (4 = 0001, 5 = 00001).
• Next Number – The next number in the sequence. You can manually change this.
• Reset Period – Reset the counter: No Reset, Daily, Monthly, Yearly.

Customising Numbering

Example: Change invoice numbering from INV/2026/0001 to INV-2026-00001:

1. Find the "Customer Invoice Sequence" in the sequence list.
2. Change Prefix from INV/{{year}}/ to INV-{{year}}-.
3. Change Padding from 4 to 5.
4. Save. The next invoice will be numbered INV-2026-00001.
5. Already-issued invoices are not affected.

Note: Some localisation packages set numbering according to legal requirements. In the EU, invoices must be numbered sequentially without gaps. Adjust with care.

Multi-Language Support

Quickenerp supports 50+ languages. The interface, reports, website, and customer portal can all be translated. Each user can choose their preferred language.

Installing a Language

1. Go to Settings > General Settings.
2. In the "Language/Translations" section, click Load a Translation.
3. Select the language from the dropdown (e.g. French, Spanish, German, Japanese).
4. Click Load. Quickenerp installs the translation pack – this may take a few minutes.
5. The language is now available for users to select in their preferences.

How Translations Work

Quickenerp uses a three-tier translation system:

1. Module Translations – Pre-built translation files shipped with each module. These translate standard interface terms (labels, buttons, messages).
2. User-Customised Translations – YOU can override any translated term. Go to Settings > Technical > Translations > Custom Translations (developer mode). This is useful when you prefer different terminology (e.g. "Clients" instead of "Customers").
3. Language-Specific Data – Some data records can have translated fields. For example, a product can have different names and descriptions per language. Enable "Translatable" on any text field in the field definition (Technical – Fields).

User Language Selection

Each user can set their own interface language:

1. Click the user avatar (top-right) – My Profile.
2. In the Preferences tab, select the Language field.
3. Save. The interface reloads in the selected language.

Fiscal Localisation Packages

Localisation packages include country-specific chart of accounts, taxes, fiscal positions, and report templates. Go to Accounting > Configuration > Settings – "Fiscal Localisation" section.

Select your country to install the appropriate localisation:

• United States – US chart of accounts, sales tax setup, 1099 reporting.
• United Kingdom – UK chart of accounts, VAT setup, MTD-compatible reports.
• India – GST-compatible chart, HSN/SAC codes, GSTR reports.
• France – French chart, VAT, FEC export.
• Germany – SKR03/SKR04 charts, GDPdU/GoBD compliance.
• UAE – VAT setup, FTA-compliant reports.

Each localisation package installs the chart of accounts, default tax templates, fiscal position rules for intra-community trading, and statutory report templates.

Automated Actions

Automated actions are server-side rules that trigger automatically when records are created, updated, or deleted. They are a powerful no-code automation tool.

Navigation

Go to Settings > Technical > Automated Actions (developer mode required).

Anatomy of an Automated Action

1. Name – A descriptive name (e.g. "Notify Manager on Large Order").
2. Model – The model to watch (e.g. Sale Order, Invoice, Lead).
3. Trigger – When to fire:

• On Creation – When a new record is created.
• On Update – When an existing record is modified.
• On Creation & Update – Both.
• On Deletion – When a record is deleted.

• Send an email (select an email template).
• Create a new record (e.g. create a task in Projects).
• Update a field on the current record (e.g. set a flag).
• Execute a server action (Python code or multi-step process).
• Add a follower to the record.
• Create an activity (e.g. schedule a follow-up call).

Practical Examples

Example 1: Notify Manager on High-Value Orders

• Model: Sales Order
• Trigger: On Creation & Update
• Condition: [('amount_total', '>', 50000)]
• Action: Send Email – use a template that emails the sales manager with order details.

Example 2: Flag Expired Credit Cards on Contacts

• Model: Contact (res.partner)
• Trigger: On Update (when credit card expiry changes)
• Condition: [('credit_card_expiry', '<', current_date)]
• Action: Update field – set "Credit Card Valid" to False, create an activity to call customer.

Example 3: Auto-Assign Salesperson on New Lead

• Model: CRM Lead
• Trigger: On Creation
• Condition: [('user_id', '=', False)] (not assigned yet)
• Action: Execute Python code – find the least-loaded salesperson in the lead's country team and assign them.

Testing Automated Actions

1. Create a test record that meets the condition.
2. Check that the action executed (email received, record created, field updated).
3. Check the server logs if the action didn't fire.
4. Remember that automated actions run synchronously – they execute immediately as part of the create/write operation. A slow action can make the UI feel sluggish.