Financials Preferences

Financials preferences control the reusable accounting setup behind sales, purchases, payments, expenses, and contact behavior. These settings affect what users see on forms, which defaults are applied automatically, and how money-related transactions are categorized.

Financial Settings Areas

The Financials settings UI includes:

General Setting
Sales Order Setting
Invoice Setting
Credit Note Setting
Purchase Order Setting
Bill Setting
Vendor Credit Setting
Expense Setting
Customer Settings
Vendor Settings
Payment Received Setting
Payment Made Setting

Some sections contain specific form settings, and others are primarily used for custom fields.

General Setting

The General Setting page contains the core reusable accounting configuration used throughout the app.

Tax

Use the Tax setting to create and maintain tax rates.

Field	What it does
`Name`	The tax label users will see in selections such as VAT, GST, or Sales Tax.
`Rate`	The percentage rate applied when the tax is selected.
`Compound tax`	Marks the tax as a compound tax, meaning an additional tax is charged on top of the primary tax.
`Status`	Activates or deactivates the tax for future use.

These tax records are reused across invoices, sales orders, purchase documents, and other tax-enabled transactions.

Payment Terms

Use Payment Terms to define due-date offsets for receivables and payables.

Field	What it does
`Name`	The visible term name, such as `Net 7`, `Net 15`, or `Due on Receipt`.
`Days`	The number of days added to determine the due date.
`Status`	Activates or deactivates the payment term.

This helps teams standardize credit periods without entering due-date rules manually on every document.

Payment Modes

Use Payment Modes to define how customers or users can pay.

Field	What it does
`Name`	The payment method label, such as `Cash`, `Bank Transfer`, `Card`, or `Wallet`.
`Status`	Controls whether the mode is active for general use.
`Show in E-commerce`	Controls whether the payment mode is shown in ecommerce flows.

These payment modes are reused in forms and also feed POS payment mapping.

Payment Reminder

Payment reminders are organization-wide reminder rules used on invoices.

Field	What it does
`Reminder Name`	The internal name of the reminder rule.
`Days`	The number of days before or after the reference point.
`Schedule`	Whether the reminder is triggered `Before` or `After`.
`Based On`	The reference point for the reminder. The current UI uses `Due Date`.
`Send Via`	The channel used to send the reminder. The current options are `Email` and `SMS`.
`Enable Reminder`	Turns the reminder on or off.

The UI explicitly notes that this reminder is applied to all invoices.

Shipping Charges

Use this section when shipping should be treated as a configurable accounting component.

Setting	What it does
`Enable Shipping Charges`	Turns shipping charge handling on or off.
`Shipping Charge Account`	The account used to record shipping charges when the feature is enabled.
`Enable Shipping Charge Tax`	Turns tax handling for shipping charges on or off.
`Shipping Charge Tax Account`	The account used for shipping charge tax when that tax toggle is enabled.

Transaction Charges

Use this section when payment collection or payout methods create bank or service charges.

Setting	What it does
`Enable Transaction Charge for Receiving Payment`	Enables transaction charge handling on incoming payments.
`Transaction Charge Account for Payment Received`	The account used for charges tied to payment collections.
`Enable Transaction Charge for Payment Sent`	Enables transaction charge handling on outgoing payments.
`Transaction Charge Account for Payment Sent`	The account used for charges tied to vendor or outgoing payments.

Organization Branding

This setting controls whether your organization branding is shown on documents and reports.

Setting	What it does
`Disable Organization Branding`	Removes organization branding from reports, invoices, sales orders, and similar outputs.

This option is shown only when branding control is available for the subscription.

Sales Order Setting

The Sales Order Setting page currently contains:

Default Terms and Conditions
custom fields for Sales Orders

The default terms text is saved as the standard legal or commercial note inserted into sales orders. Use it for:

delivery terms
return policy references
quotation conditions
order acceptance notes

Invoice Setting

The Invoice Setting page currently contains:

Default Terms and Conditions
custom fields for Invoices

Use the default invoice terms field for standard billing notes such as:

payment clauses
banking instructions
tax disclaimers
late-payment notes

Customer Settings

The customer settings page includes both behavior control and custom fields.

Credit Limit

Setting	What it does
`Enable Soft Credit Limit`	Allows customers to go beyond their credit limit with softer control instead of a strict block.

Use this when you want users to be warned or guided rather than fully blocked at the transaction level.

Customer Custom Fields

Add customer-specific custom fields when you need extra CRM or finance metadata such as:

customer tier
account owner
PAN or tax reference
internal segmentation

Vendor, Credit Note, Purchase Order, Bill, Vendor Credit, Expense, Payment Received, and Payment Made

These settings pages are currently used mainly for custom fields tied to each document type or contact type.

Use them when your organization needs extra fields on specific records, for example:

internal approval reference
branch cost center
payment source note
supplier classification
refund reason code

Custom fields are helpful when the standard form is not enough, but the added data must still be searchable, visible, or reportable.

Best Practice

Keep tax names and payment terms standardized before onboarding more users.
Add only the payment modes your teams actually use.
Use shipping and transaction charge accounts deliberately so reporting stays clean.
Put legal boilerplate in default terms fields instead of retyping it on every document.
Use custom fields for structured data, not for one-off notes.