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.
The big picture
Customers
A Customer is the central FAR entity. Each customer references a party in the PRM (Party Relationship Management) module, linking the financial relationship to the broader party record. Customers carry classification attributes — type, class, status, and approval status — along with default freight terms, payment terms, and an optional price list version.
For full detail on classification and approval, see Customers.
Customer sites and site uses
Customers can operate at multiple locations. A Customer Site links a FAR customer to a PRM party site, while a Customer Site Use defines the business purpose of that site (bill-to, ship-to, etc.) and can override the customer-level defaults for freight terms, payment terms, and price lists.
See Customer Sites and Site Uses for the full explanation.
Transactions
Transactions follow a header/line pattern. A Transaction Header represents a financial document — typically an invoice, credit memo, or debit memo — with references to the sold-to customer, ship-to party, salesperson, payment terms, and currency. Transaction Lines hold the individual line items with quantities, pricing, and optional inventory item references.
See Customer Transactions for the full lifecycle.
Cash receipts and receipt schedules
Cash Receipts record incoming payments with amount, currency, date, and status. Receipt Schedules reconcile receipts against transactions, tracking original amounts, applied amounts, adjustments, and disputes.
See Cash Receipts and Receipt Schedules for the complete model.
Customer invites and authentication
FAR supports two forms of access:
- Customer Invites — email-based invitations for users to join a customer's team with specified permissions
- Authentication Credentials — API keys (prefixed
sk-cust-) for programmatic access, plus merchant credentials for connecting to external payment systems
See Customer Invites and Authentication for the onboarding and access model.
Payment terms
Payment Terms define when and how payments are due. Each payment term has one or more Payment Term Lines that specify relative amounts, due dates, and due-day calculations. Payment terms can be set at the customer level, overridden at the site-use level, and referenced on individual transactions.
Table inventory
| Entity | Purpose |
|---|---|
| Customer | Central customer account linking to a PRM party |
| Customer Site | Links a customer to a PRM party site |
| Customer Site Use | Defines business purpose (bill-to, ship-to) for a site with optional term overrides |
| Transaction Header | Financial document header (invoice, credit, debit) with party references and payment details |
| Transaction Line | Line item on a transaction with quantity and pricing |
| Cash Receipt | Incoming payment record with amount, currency, and status |
| Receipt Schedule | Reconciliation record linking transactions to receipts with applied amounts and adjustments |
| Payment Term | Named payment term with i18n support |
| Payment Term Line | Instalment definition within a payment term |
| Customer Invite | Email invitation for a user to join a customer team |
| Customer Authentication Credential | API key for programmatic customer access |
| Merchant Authentication Credential | OAuth/API credentials for connecting to external merchant systems |
Multi-tenancy
The entire FAR model is tenant-scoped. Every customer belongs to a tenant and an organisation, and access controls ensure that users only see data belonging to their own tenant. Within a tenant, authorisation is managed through the platform's permissions system, with object-level permissions flowing from customer records down to related entities.