11 docs tagged with "transactions"

Billing subscription line transactions record the link between a subscription line and the invoice line generated from it. Each transaction represents one billing event for one subscription line in one billing period.

Customer transactions are the financial documents at the heart of accounts receivable — invoices, credit memos, and debit memos. FAR models these using a header/line pattern: a transaction header carries document-level details, while transaction lines hold the individual line items.

The FAP data model is built around three core areas — Suppliers, Transactions, and Payment Schedules — with supporting entities for supplier sites, site uses, and transaction holds. Understanding how these relate is the key to understanding how Raytio tracks accounts payable.

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.

Raytio's Financials – Accounts Payable (FAP) module manages supplier accounts, supplier transactions, and payment obligations. It tracks who your suppliers are, what you owe them, and how payment schedules are generated.

Funds account transactions record individual financial movements on an account. This is the most detailed entity in the FXM module, capturing transaction amounts, currency conversions, ISO 20022 categorisation codes, card instrument details, and a running balance snapshot.

Raytio's Funds Transfer Management (FXM) capability manages payment processing, externally connected funds accounts, and account transaction information within the platform.

Funds Transfer Management (FXM) manages payment processing, externally connected funds accounts, balances, and transaction information within the Raytio platform.

An instance transaction represents an approval or rejection action on a sharing instance. When shared data requires explicit consent or verification — from the data provider or another party — the system creates a transaction that must be resolved before the instance can proceed.

Supplier transactions are the financial documents at the heart of accounts payable — invoices, credit memos, debit memos, and prepayments received from suppliers. FAP models these using a header/line pattern: a transaction header carries document-level details, while transaction lines hold the individual line items. This mirrors the header/line pattern used for customer transactions in FAR.

The DSM includes a general-purpose transaction details ledger for recording quantitative transactions — such as reputation scores, payment tracking, or reviews. This ledger exists independently of the approval workflow and is designed for tracking cumulative or scored data rather than state-change events.