Skip to main content

5 docs tagged with "customers"

View all tags

Customer Invites and Authentication

FAR provides two mechanisms for granting access to customer accounts: invites for onboarding human users, and authentication credentials for programmatic access. A third entity, merchant credentials, handles the reverse direction — storing credentials that let the platform connect to external merchant systems on behalf of a customer.

Customer Sites and Site Uses

Customers often operate at multiple locations, and each location may serve a different business purpose — one site for billing, another for shipping, a third for both. FAR handles this with a two-level hierarchy: customer sites and customer site uses.

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.

FAR Data Model Overview

The FAR data model is built around three core areas — Customers, Transactions, and Receipts — with supporting entities for payment terms, customer sites, and authentication. Understanding how these relate is the key to understanding how Raytio tracks accounts receivable.

Financials – Accounts Receivable (FAR)

Raytio's Financials – Accounts Receivable (FAR) module manages customer accounts, invoicing, and payment collection. It tracks who your customers are, what they owe, and how payments are received and applied.