Settings


Settings

Require Attachment on New Expenses

Description: This setting controls whether users are required to attach a supporting file when creating a new expense.

Key: require_attachment_on_new_expenses

Location: Control Panel > Admin Menu > Settings

Possible Values:

  • "true": Users must attach at least one file when creating a new expense. The system will not allow saving the expense without an attachment.
  • Any other value (empty, "false", etc.): Users can create new expenses without attaching files.

Functionality:

When enabled ("true"), this setting enforces stricter documentation by requiring an attachment for every new expense entry. This helps ensure all expenses are supported by receipts or other relevant files.

Disable Copy Option in Expenses

Description: This setting controls whether users can copy existing expenses to create new ones.

Key: disable_copy_buttons_in_expenses

Location: Control Panel > Admin Menu > Settings

Possible Values:

  • "true": The "Copy" option is hidden in all expense records. Users cannot duplicate expenses.
  • Any other value (empty, "false", etc.): The "Copy" option remains visible, allowing users to create new expenses based on existing ones.

Functionality:

When enabled ("true"), this setting removes the "Copy" button from the expense module to avoid accidental or repeated entries. This helps maintain cleaner records and reduce unnecessary duplicates.

Default “Our Company” (Client) in New Expenses

Description: Defines which Our Company record (i.e., the company representing your own organization - the client side in the expense) is automatically pre-selected when creating a new expense.

This is different from the “Supplier” field, which pulls from the Companies module and represents the external vendor providing the service or product.

Key: expenses_our_company_default

Location: Control Panel > Admin Menu > Settings

Possible Values:

  • Company ID (integer): The id value from the Our Companies module. The corresponding company will be set as default in the “Our Company” (client) field when a new expense is created.
  • Empty or null: No company will be pre-selected. Users must manually select the correct “Our Company.”

Functionality:

When this setting contains a valid Our Company ID, every new expense automatically fills the “Our Company” (client) field with that record. If the setting is empty, the field remains blank, and the user must select the company manually.

This ensures consistent reporting of which internal company (client entity) the expense belongs to, especially useful when working with multi-company setups in OBS2GO.

Block Editing Expenses Older Than (Years)

Description: This setting controls how many years back users are allowed to create, edit, or delete expenses. Any expense older than the specified number of years becomes locked and cannot be modified.

Key: expenses_edit_lock_years_back

Location: Control Panel > Admin Menu > Settings

Possible Values:

  • 0 or empty: No restriction. Users can create, edit, and delete expenses from any year.
  • Positive integer (e.g., 1, 2, 3): Defines how many years back expenses remain editable.

Functionality:

When this setting contains a positive number, the system prevents any changes to expenses older than that number of years.

For example, if the value is set to 3 and the current year is 2026, users will only be able to modify expenses from 2024 onward.

Default Invoice Template (Bulgarian and Foreign Clients)

Description: These two settings define the default invoice template. The system chooses the template of every invoice automatically, each time the invoice is saved. The template cannot be picked by hand on the invoice itself.

Keys:

  • bg_invoice_template: the default template for Bulgarian clients.
  • en_invoice_template: the default template for all other (foreign) clients.

Location: Control Panel > Admin Menu > Settings

Possible Values:

  • Template name (text): The exact name of a template from the Templates module, for example “Invoice Square BG”. Spaces at the start or end are ignored.
  • Empty, missing, or a name that does not exist: No error is shown. The default is simply skipped, and if nothing else applies the system uses the last-resort rule (step 4 below).

Functionality:

Every time an invoice is saved, the system looks for its template in this order. The first match wins.

  1. Contract. If the invoice belongs to a contract and the contract has an invoice template filled in, that template is used. This always wins. A contract without a template does not block the next steps.
  2. Client company. If the client’s company record has an invoice template filled in, that template is used.
  3. Settings (the two keys above). Otherwise the default is used: bg_invoice_template for a Bulgarian client, en_invoice_template for any other client.
  4. Last resort. If still no template was found (for example, the setting is empty), the system takes the first template (lowest id) that is attached to the Invoices module.
  5. Error. If there is no such template either, the invoice cannot be saved and the message “invoice template is not configured” is shown.

Who is a “Bulgarian client”? A client is treated as Bulgarian when any of these is true:

  • The company’s VAT number starts with “BG”.
  • The company has no VAT number at all and its country is Bulgaria.
  • The invoice has no client company.

Everyone else is treated as a foreign client.

Examples:

  • A German client, no template on the company and no contract → the template from en_invoice_template.
  • A Bulgarian client, no template on the company and no contract → the template from bg_invoice_template.
  • A Bulgarian client whose company has template “A” → “A”, because the company beats the settings.
  • The same client, but the invoice belongs to a contract that has template “B” → “B”, because the contract beats the company.

Good to know:

  • Changing the template directly on an invoice does not stick. It is recalculated every time the invoice is saved.
  • To give one client another template, fill in the invoice template on that client’s company record. To give one contract another template, fill it in on the contract (the contract has priority).
  • Old invoices: saving an old invoice again recalculates its template by today’s rules and refreshes the stored template content from the current template.
  • Typos are not reported. If the name in a setting does not match any template exactly, the system silently moves to the last-resort rule (step 4). Always copy the name exactly as it appears in the Templates module.
  • Two templates with the same name cause an error when an invoice is saved. Keep template names unique.