Usage and billing
What was metered, what is billable, and why the numbers on this page do not add up
Usage is what your organization metered and what it costs. It is a different question from Analytics, which is about how well the integration is working.
The billing unit is the verification
One verification session is one billable unit, whatever happens inside it. The individual checks are metered too, but for visibility rather than for pricing, and they are not charged separately.
This is why the breakdown does not add up
The verification row is the per-session anchor. Every other row in the breakdown is a check that ran inside those verifications. Adding the rows together counts the same sessions several times over, which is expected and is not an error in the figures.
What the page shows
Verifications and billable across the period, with the billable share as a percentage. Period cost applies your per-verification price. Month to date counts billable verifications since the start of the calendar month, which is the figure that matches an invoice.
Usage over time charts daily verifications alongside daily check operations.
Breakdown by operation lists each operation with its total, its billable and non-billable split, and its share.
Billable versus non-billable exists mostly because of one rule: sandbox traffic is metered but never billed, so all of it lands on the non-billable side. A large non-billable share usually means somebody has been testing, not that you are getting something free.
Monthly quota shows billable verifications this calendar month against your included allowance. If no quota is set for your organization, the page says so and nothing is being counted down. Talk to us if you want one applied.
Who can see it
Owners, review managers and developers. A developer can also export the metering rows for reconciliation, because they carry no applicant data at all. Reviewers do not have this page.