Skip to main content
SourceTrustSign in

Help center

Guides for SourceTrust: Importing dependencies, reviewing licenses, external obligations, publishing attestation pages, billing, plain-language license explainers, and procurement-oriented explainers for common open-source licenses.

Staff Console revenue and scan health

← All articles

How Revenue separates seller earnings, customer charges, and tax. And when Health flags a stuck scan.

The SourceTrust Staff Console is available only to staff accounts. Revenue separates modeled recurring revenue from observed Paddle payment totals.

Revenue terms

  • Recognized revenue: seller earnings when Paddle provides them, then the pre-tax subtotal. Legacy rows without a breakdown fall back to the customer charge.
  • Customer charges: the tax-inclusive amount paid by customers.
  • Tax collected: tax and VAT from Paddle's breakdown. It is shown separately and is not seller revenue. Legacy rows may not include it.
The Revenue chart shows customer charges and refunds. The Pulse chart shows recognized revenue.

Stuck scans

Health marks queued or running scans as stuck after 15 minutes. The Stuck scans table shows the organization, scan status, and start time so staff can investigate without confusing a live scan with a completed failure.

Catalog health

Health > Catalog shows each job separately: weekly catalog updates, canonical text fills every six hours, and daily package suggestions with named source outcomes. Failures are flagged even when some work succeeds. A completed text fill with nothing pending is healthy; no recorded run means its status is unknown.

A job becomes overdue after eight days for weekly updates, seven hours for text fills, or 26 hours for package suggestions. The card checks elapsed time every minute while open. Text counts describe the selected batch, not the entire pending catalog.