Skip to main content

Supplier Transactions

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.

Transaction types​

FAP supports four supplier transaction types:

TypeMeaning
INVOICEStandard supplier invoice — an obligation to pay
CREDIT_MEMOCredit issued by the supplier — reduces the amount owed
DEBIT_MEMODebit raised against the supplier — increases the amount owed
PREPAYMENTAdvance payment to a supplier before goods or services are received

Transaction headers​

A Transaction Header represents a single financial document. Each header records:

  • Transaction number — a supplier-provided reference (up to 64 characters), unique per supplier
  • Transaction type — the document type (see above)
  • Transaction status — the current lifecycle state
  • Approval status — whether the transaction has been approved for payment
  • Transaction date — when the document was issued by the supplier
  • Transaction currency — the currency for all amounts on the document

Transaction number​

The transaction number is supplier-provided and must be unique for each supplier. This protects against accidentally entering the same supplier invoice twice.

When the transaction number is left blank, Raytio generates one automatically in the standard platform code format.

Party references​

Each transaction header references the billing supplier:

  • Bill-from supplier — the supplier sending the document (required)
  • Bill-from supplier site — the specific site the document is from (optional)
  • Bill-from supplier contact point — the contact at the supplier site (optional)

Optional ship-from references can also be recorded for the party, party site, and contact point that physically shipped the goods — these reference PRM directly rather than FAP supplier records.

Payment information​

Transaction headers also carry:

  • Payment term — defines when the transaction amount is due; resolved from the supplier site use or supplier level
  • Supplier reference — the supplier's own reference number for the transaction
  • Our PO number — the buyer's purchase order reference

Transaction lifecycle​

Transaction headers move through the following lifecycle:

StatusMeaning
DRAFTThe transaction has been entered but not yet validated
VALIDATEDThe transaction has been validated; payment schedules are generated at this point
CANCELLEDThe transaction has been cancelled

Update controls​

Once a transaction moves past DRAFT, most fields are locked to protect data integrity. Header fields such as supplier, transaction number, transaction type, date, and currency can no longer be changed once the status is VALIDATED or CANCELLED. Only status transitions, approval status changes, and metadata updates are permitted on non-draft transactions.

Approval status​

The approval status is tracked separately from the transaction status:

Approval statusMeaning
REQUIREDApproval is required before the transaction can be paid
APPROVEDThe transaction has been approved
REJECTEDThe transaction has been rejected

A transaction is payable only when it is VALIDATED, APPROVED, and has no open holds.

Transaction lines​

Transaction Lines hold the individual items on a financial document. Each line records:

FieldPurpose
Line numberUnique sequence within the transaction
Line statusTracks the line's lifecycle independently of the header
Bill-from supplierThe supplier the line is billed from
ItemOptional reference to an inventory item in GPM
Item descriptionFree-text description of the goods or services
QuantityNumber of units
Unit of measureHow the quantity is measured
Unit list priceStandard price per unit
Unit transaction priceActual price per unit on this transaction
Extended list priceList price × quantity
Extended transaction priceTransaction price × quantity

Authorisation​

Reading supplier transactions and their lines requires at least the Accounts payable viewer role; creating and updating them requires Accounts payable user. This mirrors the pattern used by FAR for customer transactions.

Further reading​