Company preferences: consistent defaults and understandable numbers

Preferences establish common choices that make records easier to read and prepare. They can include company identity, currency presentation, decimal precision, dates and language. A default saves effort, but it does not replace a business decision when a particular transaction requires different treatment.

Consistency is especially important for numeric information. Price, quantity, rate and percentage precision serve different purposes. A displayed rounded value can differ from the precision used in an underlying calculation, so the meaning of the field must remain clear.

Preferences in DNA

DNA's Company Preferences page loads and saves preferences through its service. The form validates the company name and the format of supplied contact details, checks edit permission, sends the update and reloads the saved preferences.

The configuration includes home currency, precision and number-format settings, date format, timezone and language, alongside company and business defaults. These settings should reflect the intended company context. Their presence does not prove that every external document or historical transaction is rewritten when they change.

Currency and language have different purposes

The home currency provides a reporting reference; a language choice affects presentation. Changing language is not an exchange conversion, and changing a currency symbol is not proof that stored monetary values were converted.

Choose the company’s home currency according to its approved financial reporting requirements.

Review defaults with their consequences

A default payment term or credit limit is a starting value, not evidence of an agreement with every customer. Emily should understand where a default is used before changing it to solve one exceptional transaction.

After changing preferences, review the saved values and representative outputs. A successful save establishes that the request completed; the resulting forms and documents establish how the configuration is applied in the relevant workflow.