// FLOW

Three practical steps to produce your report

This is the same fast path used on the Home page, expanded with full detail below.

may-2026-oncall-finance.xlsx

On-Call Compensation Report - Alex Johnson (alex.johnson@example.com)

Total Earnings: $772.29 │ Total Callouts: 6 │ Total Hours Worked: 6.00May 2026
DateDay typeStipendsCalloutGrand Total
05/03/2026Week Day$25.40-$25.40
05/04/2026Week Day$25.40$57.15$122.36
05/05/2026Week Day$25.40$57.15$122.36
05/06/2026Weekend$44.45$114.30$238.38
05/07/2026Weekend$44.45$57.15$141.41
05/08/2026Week Day$25.40$57.15$122.36
TOTAL$772.29
Ready

How it works

CalloutPay is built for one job: producing accurate on-call compensation reports for teams using PagerDuty, quickly and clearly.

01
STEP 01

Connect PagerDuty

Click Connect PagerDuty and approve read-only access via OAuth. CalloutPay stores the access token encrypted at rest and uses it on your behalf — no API key to copy or manage. You can disconnect any time from the report page or your account.

02
STEP 02

Enter reporting period

Choose the start and end dates for the report month or date range.

03
STEP 03

Identify user

Provide a PagerDuty user email or ID for individual reports, or pick a team or organisation scope for multi-user reports.

04
STEP 04

Enter pay settings

Set hourly rate, stipends, callout fee, and bank holiday region based on your policy.

05
STEP 05

Generate spreadsheet

CalloutPay prepares a finance-ready sheet with stipend, callout, minimum-hours, and totals.

06
STEP 06

Export and send to finance

Download the report and send a clean summary directly to payroll/finance.

// EXAMPLE REPORTS

See exactly what you'll get

Download a real example of each report type — pre-filled with typical data, formatted exactly as CalloutPay produces them.

Individual report

One engineer, one month. Finance sheet with stipends, callouts, and totals.

Team report POPULAR

11 engineers. Team Summary + Detail sheets + Rates tab for per-person hourly rates.

Organisation report

13 engineers across the org, April 2026 including bank holidays. Rates tab pre-filled.

Settings sync across your devices

You don't need to re-enter everything each time you generate a report. Most fields — including your hourly rate, stipend amounts, callout fee, and user email — have a Remembertoggle. Tick it once and CalloutPay saves that value to your account, so it's there next time you sign in — on the same machine, your phone, or a different laptop. Only your reporting date range needs updating each run.

Connecting PagerDuty

CalloutPay connects to PagerDuty via OAuth — the recommended way. One click, no API key to copy or paste.

  1. 1Sign in to CalloutPay and open the report generator.
  2. 2In the PagerDuty connection card, click Connect PagerDuty.
  3. 3You'll be redirected to PagerDuty to authorise access. Sign in if you're not already, then approve.
  4. 4The requested scope is read — CalloutPay only reads schedule and incident data, never writes.
  5. 5You'll be returned to the report page with a green "PagerDuty connected" indicator. The report can now be generated without any further token handling.
  6. 6The access token is encrypted at rest using AES-128 (Fernet) before being stored, and is never returned to the browser in plaintext.
  7. 7You can revoke access at any time by clicking Disconnect on the report page or on your account page.

Optional: connect with a manual API key

OAuth is the recommended route, but if your organisation requires using a Read-only API key (e.g. for review/audit purposes), you can paste one in instead by clicking Use a manual API key instead beneath the connection card.

  1. 1Log into PagerDuty.
  2. 2Go to Integrations → API Access Keys.
  3. 3Click Create New API Key.
  4. 4Give it a name (for example: CalloutPay Reporting).
  5. 5Select Read-only API Key — CalloutPay only reads schedule and incident data, so full access is not needed.
  6. 6Create the key and copy it.
  7. 7In CalloutPay, expand the manual API key field and paste it. Tick Remember to save it (encrypted) for future reports.

Whether you use OAuth or a manual key, the credential is encrypted at rest using AES-128 (Fernet) and never included in exported files.