Skip to main content

2 docs tagged with "holds"

View all tags

FAP Data Model Overview

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.

Transaction Holds

Transaction holds are a mechanism for blocking payment of a supplier transaction when a problem is identified — for example, a pricing discrepancy, a quantity mismatch, or a manual review requirement. FAP records each hold separately, so multiple issues can be tracked independently on a single transaction.