Skip to main content

Customers

A Customer is the central entity in the FAR module. It represents a financial relationship with a party — the entity you invoice, collect payment from, and manage receivables for. Every customer references a party in the PRM (Party Relationship Management) module, linking the accounts-receivable record to the broader party identity.

Party linkage​

Each customer record references a party in PRM. This means the customer's name, address, and contact details live in PRM, while FAR holds the financial classification, terms, and transaction history. A single party can exist in PRM without being a FAR customer — the customer record is created when the party enters a financial relationship.

Classification​

Customers are classified along four dimensions, each backed by a lookup table:

DimensionDefaultPurpose
Customer typeEXTDistinguishes external customers from internal entities
Customer classPROFITGroups customers for reporting (e.g. profit-centre analysis)
StatusAActive/inactive lifecycle state
Approval statusATracks whether the customer record has been approved

All four dimensions use code-based lookups with internationalisation (i18n) support, so display values can be translated without changing the underlying codes.

Default terms​

Each customer can carry default values that cascade to new transactions:

  • Freight term code — default shipping terms for the customer
  • Payment term — references a payment term record that defines when payments are due (e.g. Net 30, 2/10 Net 30)
  • Price list version — optional reference to a price list in PCM (Price and Catalogue Management), used when generating transaction line pricing

These defaults can be overridden at the customer site use level, giving different terms to different locations or billing purposes.

Customer code​

Every customer is assigned an auto-generated customer code on creation. This code provides a human-readable, unique identifier for the customer within the tenant.

Authorisation​

Access to customer records is managed through the platform's authorisation system. Permissions cascade to related entities — sites, transactions, receipts, and credentials — so that access to a customer implicitly grants visibility to its dependent records.

Further reading​