Skip to main content

Billing 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.

Monetary amounts are managed by FAR (Financial Accounts Receivable). PBM's transaction history connects subscriptions to the invoices they produce.

How transactions are generated​

Invoice generation is processed asynchronously by the billing engine. The billing flow:

  1. Detects when a subscription becomes BILLABLE.
  2. Calculates the charge for each subscription line.
  3. Creates the invoice lines in FAR.
  4. Stores the resulting transaction links for auditability.

What a transaction record contains​

Each transaction record captures:

  • Which subscription line generated the transaction
  • Which FAR transaction line was created as a result
  • The billing period (start and end dates) that the charge covers
  • Optional metadata for additional context

Relationship to other billing records​

A single subscription line can produce multiple billing transactions over time, usually one per billing cycle. Each billing transaction links to exactly one FAR invoice line.

Period tracking​

The start and end dates on each transaction record indicate the billing period that the charge covers. This is distinct from when the record was created — a monthly subscription billed on the 1st would produce a transaction covering the period from the 1st of the current month to the 1st of the next month, regardless of exactly when the job ran.

Access control​

Users can only view billing transactions for tenants and customers they are authorised to access.