AUDIT FRAMEWORK

Chargebee Deep Audit

Comprehensive infrastructure, implementation, data quality, and Salesforce integration audit — 139 validation checks across 14 domains.

139
Total Audit Items
0
Completed
0
Issues Found
0% complete 0 of 139 reviewed

01Platform Foundation & Configuration

11 items
ItemObjectSub-Item
Chargebee Version
Site Config
Product Catalog Version
What We Look For
Confirm running Product Catalog 2.0 (not legacy 1.0). Check API version.
Best Practice
All new implementations should be on PC 2.0. Legacy sites should have a migration plan.
Clickpath
Settings → Configure Chargebee → Site Info; API docs version header
Status
Findings
Site Configuration
Site Config
Site Name & Region
What We Look For
Verify site name, data center region, and timezone settings match business requirements.
Best Practice
Use region closest to primary customer base. Timezone should match finance/accounting team.
Clickpath
Settings → Configure Chargebee → Site Info
Status
Findings
Site Configuration
Site Config
Business Entity Setup
What We Look For
Check if multi-entity is configured for businesses with multiple legal entities.
Best Practice
Use Business Entities for separate invoicing, tax, and payment processing per entity.
Clickpath
Settings → Configure Chargebee → Business Entities
Status
Findings
Currency Configuration
Site Config
Multi-Currency
What We Look For
Verify base currency and all enabled currencies. Check exchange rate source and update frequency.
Best Practice
Base currency = primary reporting currency. Enable only currencies you actively bill in.
Clickpath
Settings → Configure Chargebee → Currencies
Status
Findings
Billing Settings
Site Config
Billing Date & Proration
What We Look For
Review billing date logic, proration settings, calendar billing alignment.
Best Practice
Calendar billing simplifies revenue recognition. Proration should match customer contract terms.
Clickpath
Settings → Configure Chargebee → Subscription Settings → Billing Date
Status
Findings
Billing Settings
Site Config
Metered Billing Config
What We Look For
If usage-based: verify metered billing setup, usage aggregation rules, and reporting periods.
Best Practice
Metered charges should have clear aggregation rules (sum, max, last) and defined billing periods.
Clickpath
Settings → Configure Chargebee → Metered Billing
Status
Findings
Notification Settings
Site Config
Email Notifications
What We Look For
Review all email notification templates (invoice, payment, dunning, subscription changes).
Best Practice
Customize all templates with brand. Disable unused notifications. Test deliverability.
Clickpath
Settings → Configure Chargebee → Email Notifications
Status
Findings
Custom Fields
Site Config
Custom Field Inventory
What We Look For
Catalog all custom fields across objects (Customer, Subscription, Plan, etc.). Check usage.
Best Practice
Custom fields should have clear naming conventions, be documented, and actively used. Remove orphaned fields.
Clickpath
Settings → Configure Chargebee → Custom Fields
Status
Findings
API Configuration
Site Config
API Keys & Webhooks
What We Look For
Inventory all API keys (full access vs read-only). Review webhook endpoints and event subscriptions.
Best Practice
Minimize full-access keys. Use read-only where possible. Webhooks should have retry logic and monitoring.
Clickpath
Settings → Configure Chargebee → API Keys; Settings → Webhooks
Status
Findings
User Access
Site Config
Roles & Permissions
What We Look For
Review all Chargebee user accounts, assigned roles, and permission levels.
Best Practice
Follow least-privilege principle. Remove inactive users. Separate admin from operational roles.
Clickpath
Settings → Configure Chargebee → Users & Roles
Status
Findings
Audit Trail
Site Config
Activity Logs
What We Look For
Verify audit logging is enabled. Check retention period and what actions are tracked.
Best Practice
All billing-critical actions should be logged. Logs should be retained per compliance requirements.
Clickpath
Settings → Configure Chargebee → Activity Logs
Status
Findings

02Product Catalog & Pricing

10 items
ItemObjectSub-Item
Item Families
Item Family
Family Structure
What We Look For
Review item family hierarchy. Check if families logically group related products.
Best Practice
Item families should map to product lines or business units. Keep hierarchy clean and intuitive.
Clickpath
Product Catalog → Item Families
Status
Findings
Items (Products)
Item
Item Inventory
What We Look For
Catalog all items. Check for duplicates, orphaned items, and naming consistency.
Best Practice
Consistent naming convention (e.g., product-tier format). Archive unused items vs deleting.
Clickpath
Product Catalog → Items
Status
Findings
Items (Products)
Item
Item Types
What We Look For
Verify correct item types assigned (Plan, Addon, Charge). Check for misclassified items.
Best Practice
Plans = recurring base. Addons = optional recurring/one-time. Charges = one-time fees.
Clickpath
Product Catalog → Items → [Item] → Details
Status
Findings
Item Prices
Item Price
Pricing Models
What We Look For
Review pricing model per item price (flat, per-unit, tiered, volume, stairstep). Validate accuracy.
Best Practice
Pricing model should match contractual terms. Document any complex pricing logic.
Clickpath
Product Catalog → Items → [Item] → Item Prices
Status
Findings
Item Prices
Item Price
Currency & Frequency
What We Look For
Check that each item price has correct currency and billing frequency combinations.
Best Practice
Every sellable currency/frequency combo should have an item price. No gaps in pricing matrix.
Clickpath
Product Catalog → Items → [Item] → Item Prices → [Price]
Status
Findings
Item Prices
Item Price
Trial Configuration
What We Look For
Review trial periods attached to item prices. Check trial duration and post-trial behavior.
Best Practice
Trial periods should match sales commitments. Auto-convert or cancel behavior should be explicit.
Clickpath
Product Catalog → Items → [Item] → Item Prices → Trial Period
Status
Findings
Coupons
Coupon
Coupon Inventory
What We Look For
List all active coupons. Check discount type (%, fixed), duration, redemption limits, and expiry.
Best Practice
Coupons should have expiry dates and redemption limits. Track revenue impact. Archive expired coupons.
Clickpath
Product Catalog → Coupons
Status
Findings
Coupons
Coupon
Coupon Usage & Abuse
What We Look For
Analyze coupon redemption rates. Look for excessive or unexpected usage patterns.
Best Practice
Monitor coupon usage in reporting. Set up alerts for unusual redemption volume.
Clickpath
Product Catalog → Coupons → [Coupon] → Redemptions; Reports → Revenue
Status
Findings
Addons
Addon
Addon Configuration
What We Look For
Review all addons — recurring vs one-time, mandatory vs optional, pricing accuracy.
Best Practice
Addons should have clear attachment rules. Mandatory addons should auto-attach to relevant plans.
Clickpath
Product Catalog → Items (filter: Addon type)
Status
Findings
Entitlements
Entitlement
Feature Entitlements
What We Look For
If using entitlements: verify feature-to-plan mapping is accurate and complete.
Best Practice
Entitlements should be the source of truth for feature access. Sync with product feature flag system.
Clickpath
Product Catalog → Entitlements
Status
Findings

03Customer Management

7 items
ItemObjectSub-Item
Customer Records
Customer
Data Completeness
What We Look For
Audit a sample of customer records for completeness: name, email, billing address, tax ID.
Best Practice
All customer records should have: company name, primary email, billing address, payment method.
Clickpath
Customers → [Customer] → Details
Status
Findings
Customer Records
Customer
Duplicate Detection
What We Look For
Search for duplicate customer records (same email, company name, or billing info).
Best Practice
Implement duplicate prevention rules. Merge duplicates when found. Use unique identifiers.
Clickpath
Customers → Search/Filter; API: list customers with filters
Status
Findings
Customer Records
Customer
Customer ID Convention
What We Look For
Review customer ID format. Check if auto-generated or custom. Verify consistency.
Best Practice
Use meaningful ID convention (e.g., company prefix). Align with CRM record IDs if integrated.
Clickpath
Customers → [Customer] → ID field; Settings → Configure Chargebee → ID Generation
Status
Findings
Contacts
Contact
Contact Hierarchy
What We Look For
Verify primary contact is set. Check for orphaned contacts or missing email addresses.
Best Practice
Every customer should have a primary contact with valid email for billing communications.
Clickpath
Customers → [Customer] → Contacts tab
Status
Findings
Billing Info
Customer
Payment Methods
What We Look For
Audit payment method coverage. Check for expired cards, missing payment methods.
Best Practice
All active subscription customers should have a valid, non-expired payment method on file.
Clickpath
Customers → [Customer] → Payment Methods; Reports → Payment Methods
Status
Findings
Billing Info
Customer
Billing Address & Tax
What We Look For
Verify billing addresses are complete. Check tax ID/VAT numbers where required.
Best Practice
Billing addresses must be complete for tax calculation accuracy. Validate against tax jurisdiction requirements.
Clickpath
Customers → [Customer] → Billing Address
Status
Findings
Customer Segmentation
Customer
Tags & Custom Fields
What We Look For
Review how customers are segmented (tags, custom fields, metadata). Check consistency.
Best Practice
Establish a tagging taxonomy. Use custom fields for structured data, tags for flexible grouping.
Clickpath
Customers → [Customer] → Custom Fields & Tags
Status
Findings

04Subscription Management

9 items
ItemObjectSub-Item
Active Subscriptions
Subscription
Status Distribution
What We Look For
Pull distribution of subscription statuses (Active, Trial, Cancelled, Paused, Non-Renewing).
Best Practice
Healthy distribution: majority Active, small Trial %, low Non-Renewing. Investigate anomalies.
Clickpath
Subscriptions → Filter by Status; Reports → Subscription Overview
Status
Findings
Active Subscriptions
Subscription
Plan Distribution
What We Look For
Analyze subscription count by plan. Identify concentration risk or underutilized plans.
Best Practice
Understand revenue mix by plan. Flag plans with <5 subscriptions for potential deprecation.
Clickpath
Subscriptions → Filter by Plan; Reports → Subscription Analytics
Status
Findings
Subscription Lifecycle
Subscription
Trial-to-Paid Conversion
What We Look For
Measure trial conversion rate. Check trial expiry handling (auto-cancel vs auto-charge).
Best Practice
Industry avg trial conversion: 15-25%. Auto-charge with notification is higher converting.
Clickpath
Reports → Trial Conversions; Settings → Subscription Settings → Trial End Action
Status
Findings
Subscription Lifecycle
Subscription
Upgrade/Downgrade Handling
What We Look For
Review how plan changes are processed — immediate vs end-of-term. Check proration logic.
Best Practice
Define clear upgrade/downgrade policy. Proration should be transparent to customers.
Clickpath
Settings → Subscription Settings → Plan Change; Subscriptions → [Sub] → Change History
Status
Findings
Subscription Lifecycle
Subscription
Cancellation Flow
What We Look For
Audit cancellation workflow. Check if Chargebee Retention is enabled. Review cancel reasons.
Best Practice
Enable Chargebee Retention for cancellation deflection. Capture cancel reason data.
Clickpath
Settings → Retention; Subscriptions → Cancelled → Cancel Reasons; Reports → Churn
Status
Findings
Subscription Lifecycle
Subscription
Pause/Resume Configuration
What We Look For
Check if subscription pausing is enabled. Review pause duration limits and billing behavior.
Best Practice
Pausing should have a max duration. Billing stops during pause. Auto-resume at end.
Clickpath
Settings → Subscription Settings → Pause
Status
Findings
Subscription Terms
Subscription
Contract Terms & Commitments
What We Look For
Review contract term settings: minimum commitment, auto-renewal, cancellation notice period.
Best Practice
Contract terms should match sales agreements. Auto-renewal should be default for B2B.
Clickpath
Subscriptions → [Sub] → Contract Term; Product Catalog → Item Prices → Contract Terms
Status
Findings
Subscription Ramps
Subscription
Scheduled Price Changes
What We Look For
If using subscription ramps: verify ramp schedules match contractual pricing escalations.
Best Practice
Ramps should match signed contract terms exactly. Test ramp execution before go-live.
Clickpath
Subscriptions → [Sub] → Subscription Ramps
Status
Findings
Advance Invoicing
Subscription
Advance Invoice Config
What We Look For
Check if advance invoicing is used. Verify billing-in-advance vs billing-in-arrears alignment.
Best Practice
Annual contracts should use advance invoicing. Monthly SaaS typically bills in advance.
Clickpath
Settings → Subscription Settings → Advance Invoicing
Status
Findings

05Invoicing & Billing

8 items
ItemObjectSub-Item
Invoice Configuration
Invoice
Invoice Numbering
What We Look For
Check invoice number format, prefix, and sequencing. Verify no gaps in sequence.
Best Practice
Sequential numbering with meaningful prefix (e.g., INV-2024-0001). No gaps for audit compliance.
Clickpath
Settings → Invoice Settings → Invoice Number
Status
Findings
Invoice Configuration
Invoice
Invoice Template & Branding
What We Look For
Review invoice template: logo, company info, payment terms, footer notes, legal text.
Best Practice
Invoice should include: logo, legal entity name, address, tax ID, payment terms, bank details.
Clickpath
Settings → Invoice Settings → Invoice Template
Status
Findings
Invoice Configuration
Invoice
Consolidated Invoicing
What We Look For
Check if consolidated invoicing is enabled for multi-subscription customers.
Best Practice
Enable consolidated invoicing to reduce invoice volume for multi-subscription customers.
Clickpath
Settings → Invoice Settings → Consolidated Invoicing
Status
Findings
Invoice Lifecycle
Invoice
Outstanding Invoices
What We Look For
Pull aging report: overdue invoices by 30/60/90+ days. Identify concentration.
Best Practice
Overdue invoices >60 days should trigger escalation. Total outstanding should be <10% of MRR.
Clickpath
Reports → Accounts Receivable; Invoices → Filter: Overdue
Status
Findings
Invoice Lifecycle
Invoice
Voided Invoices
What We Look For
Review voided invoice volume and reasons. Check for patterns suggesting process issues.
Best Practice
Void rate should be <2% of total invoices. High void rate = pricing errors or process gaps.
Clickpath
Invoices → Filter: Voided
Status
Findings
Credit Notes
Credit Note
Credit Note Volume & Reasons
What We Look For
Analyze credit note volume, amounts, and reasons. Check approval workflow.
Best Practice
Credit notes should require approval for amounts over threshold. Track reasons for patterns.
Clickpath
Credit Notes → All; Reports → Credit Notes
Status
Findings
Tax Configuration
Tax
Tax Setup
What We Look For
Verify tax config: tax provider (Chargebee Tax, Avalara, TaxJar), tax profiles, exemptions.
Best Practice
Use automated tax provider for multi-jurisdiction. Maintain exemption certificates. Regular audit.
Clickpath
Settings → Taxes; Settings → Tax Provider Integration
Status
Findings
Tax Configuration
Tax
Tax Rates & Applicability
What We Look For
Validate tax rates for primary selling regions. Check product taxability settings.
Best Practice
Tax rates should auto-update via provider. Each item should have correct tax category.
Clickpath
Settings → Taxes → Tax Rates; Product Catalog → Items → Tax Category
Status
Findings

06Payment Processing

6 items
ItemObjectSub-Item
Payment Gateway
Gateway
Gateway Configuration
What We Look For
Inventory all connected payment gateways. Check primary vs backup gateway setup.
Best Practice
Have primary + backup gateway for redundancy. Smart routing if multiple gateways.
Clickpath
Settings → Payment Gateways
Status
Findings
Payment Gateway
Gateway
Gateway Health
What We Look For
Review payment success rates by gateway. Check for gateway-specific decline patterns.
Best Practice
Payment success rate should be >95%. Investigate gateway-specific issues if <93%.
Clickpath
Reports → Payments → Success Rate; Gateway dashboard
Status
Findings
Payment Methods
Payment Method
Accepted Methods
What We Look For
Verify all required payment methods are enabled (card, ACH, PayPal, SEPA, etc.).
Best Practice
Enable payment methods used by your customer base. Card + ACH minimum for US B2B.
Clickpath
Settings → Payment Gateways → [Gateway] → Payment Methods
Status
Findings
Payment Methods
Payment Method
Card Updater
What We Look For
Check if automatic card updater (Account Updater) is enabled for expired/replaced cards.
Best Practice
Enable card updater to reduce involuntary churn from expired cards.
Clickpath
Settings → Payment Gateways → [Gateway] → Card Updater
Status
Findings
Payment Processing
Transaction
Failed Payment Volume
What We Look For
Analyze failed payment rate, decline codes distribution, and recovery rate.
Best Practice
Failed payment rate <5% of attempts. Top decline codes should have specific handling.
Clickpath
Reports → Payments → Failed; Reports → Dunning Recovery
Status
Findings
Payment Processing
Transaction
Refund Process
What We Look For
Review refund workflow: who can issue, approval requirements, refund methods, and volume.
Best Practice
Refunds should require approval over threshold. Track refund rate (should be <3% of revenue).
Clickpath
Invoices → [Invoice] → Refund; Reports → Refunds
Status
Findings

07Dunning Management & Revenue Recovery

6 items
ItemObjectSub-Item
Retry Configuration
Dunning
Smart Retry Logic
What We Look For
Review retry schedule: number of retries, timing, and smart retry enablement.
Best Practice
Enable Smart Retry (ML-based optimal timing). 3-5 retries over 14-21 days minimum.
Clickpath
Settings → Retry Settings
Status
Findings
Retry Configuration
Dunning
Hard vs Soft Decline Handling
What We Look For
Verify separate handling for hard declines (do not honor) vs soft declines (insufficient funds).
Best Practice
Hard declines: stop retrying, request card update. Soft declines: retry with escalating intervals.
Clickpath
Settings → Retry Settings → Decline Classification
Status
Findings
Dunning Emails
Dunning
Email Sequence
What We Look For
Review dunning email sequence: timing, content, tone, and escalation.
Best Practice
3-5 email sequence. Friendly → Urgent → Final Notice. Include direct payment update link.
Clickpath
Settings → Email Notifications → Dunning Emails
Status
Findings
Dunning Outcomes
Dunning
Recovery Rate
What We Look For
Measure dunning recovery rate (% of failed payments recovered). Compare to benchmark.
Best Practice
Industry benchmark: 50-70% recovery. Chargebee Smart Retry targets 25%+ improvement.
Clickpath
Reports → Dunning → Recovery Rate
Status
Findings
Dunning Outcomes
Dunning
Subscription Cancellation on Failure
What We Look For
Check what happens when dunning exhausts: cancel, pause, or mark non-renewing.
Best Practice
For B2B: consider pausing instead of auto-cancelling. Notify account owner before final action.
Clickpath
Settings → Retry Settings → After Max Retries
Status
Findings
Payment Update Page
Dunning
Self-Service Update
What We Look For
Verify payment update page is branded, functional, and included in dunning emails.
Best Practice
Custom-branded payment update page. Direct link in all dunning emails. Mobile-responsive.
Clickpath
Settings → Hosted Pages → Payment Update
Status
Findings

08Revenue Recognition

5 items
ItemObjectSub-Item
RevRec Configuration
RevRec
ASC 606 / IFRS 15 Setup
What We Look For
Verify RevRec module is enabled and configured for correct accounting standard.
Best Practice
Enable RevRec if compliance is required. Configure for ASC 606 (US) or IFRS 15 (intl).
Clickpath
Settings → Revenue Recognition
Status
Findings
RevRec Rules
RevRec
Recognition Rules
What We Look For
Review recognition rules per product: point-in-time vs over-time, performance obligations.
Best Practice
Each product should have explicit recognition rules aligned with accounting policy.
Clickpath
Revenue Recognition → Rules → [Product]
Status
Findings
RevRec Rules
RevRec
Contract Modifications
What We Look For
Check how upgrades, downgrades, and cancellations are handled in RevRec.
Best Practice
Modifications should follow ASC 606 guidance: prospective vs cumulative catch-up adjustment.
Clickpath
Revenue Recognition → Rules → Modification Handling
Status
Findings
RevRec Reporting
RevRec
Deferred Revenue Accuracy
What We Look For
Validate deferred revenue balance matches expectations. Reconcile with GL.
Best Practice
Monthly reconciliation of Chargebee deferred revenue to GL. Investigate variances >1%.
Clickpath
Revenue Recognition → Reports → Deferred Revenue; Compare to accounting system
Status
Findings
Accounting Integration
RevRec
GL Sync
What We Look For
Check accounting system integration (NetSuite, Intacct, QBO, Xero). Verify journal entries.
Best Practice
Automated journal entry sync. Monthly reconciliation. Clear CB-to-GL account mapping.
Clickpath
Settings → Integrations → Accounting; Revenue Recognition → Journal Entries
Status
Findings

09Reporting & Analytics

5 items
ItemObjectSub-Item
MRR/ARR Tracking
Reports
MRR Accuracy
What We Look For
Validate MRR calculation matches expected value. Check for discrepancies with finance.
Best Practice
MRR should reconcile with finance within 2%. Investigate new/expansion/contraction/churn.
Clickpath
Reports → Revenue → MRR; RevenueStory dashboard
Status
Findings
MRR/ARR Tracking
Reports
MRR Movement Analysis
What We Look For
Review MRR waterfall: new, expansion, contraction, churn, reactivation.
Best Practice
Track all MRR movement categories monthly. New + Expansion should exceed Contraction + Churn.
Clickpath
Reports → Revenue → MRR Movement
Status
Findings
Churn Analytics
Reports
Churn Rate Tracking
What We Look For
Verify customer churn and revenue churn are tracked separately. Check methodology.
Best Practice
Track both logo churn and revenue churn. Net revenue retention >100% target.
Clickpath
Reports → Churn; RevenueStory → Churn Metrics
Status
Findings
Custom Reports
Reports
Report Configuration
What We Look For
Inventory custom and scheduled reports. Check if key stakeholders receive automated reports.
Best Practice
Finance, Sales, and Ops should each have automated weekly/monthly reports.
Clickpath
Reports → Scheduled Reports; Reports → Custom Reports
Status
Findings
Data Export
Reports
Export & BI Integration
What We Look For
Check data export capabilities: CSV, API, warehouse integration (Snowflake, BigQuery).
Best Practice
For mature orgs: pipe data to warehouse. API-based extraction > manual CSV.
Clickpath
Settings → Data Export; API documentation
Status
Findings

10Integrations (Non-Salesforce)

6 items
ItemObjectSub-Item
Integration Inventory
Integration
Connected Apps
What We Look For
Catalog all connected integrations. Check status (active, stale, broken).
Best Practice
Review each integration quarterly. Remove unused connections. Document purpose.
Clickpath
Settings → Integrations; Apps → Marketplace
Status
Findings
Webhooks
Webhook
Webhook Configuration
What We Look For
Inventory all webhook endpoints. Check event types, retry config, and failure rates.
Best Practice
Webhooks: HTTPS endpoints, retry on failure, monitoring/alerting, dead letter queue.
Clickpath
Settings → Webhooks
Status
Findings
Webhooks
Webhook
Webhook Reliability
What We Look For
Review webhook delivery success rate. Check for persistent failures or timeouts.
Best Practice
Webhook success rate should be >99%. Failed webhooks should trigger alerts.
Clickpath
Settings → Webhooks → [Endpoint] → Logs
Status
Findings
Accounting Integration
Integration
Accounting System Sync
What We Look For
Verify accounting integration (NetSuite, Intacct, QBO, Xero). Check sync and mapping.
Best Practice
Monthly reconciliation between Chargebee and accounting system.
Clickpath
Settings → Integrations → [Accounting App]
Status
Findings
CRM Integration
Integration
CRM Sync (non-SF)
What We Look For
If using HubSpot or other CRM: verify bidirectional sync, field mapping, and freshness.
Best Practice
CRM should reflect current subscription status within minutes.
Clickpath
Settings → Integrations → [CRM]
Status
Findings
Customer Success
Integration
CS Tool Integration
What We Look For
Check if CS tools (Gainsight, Totango, Custify) are connected for health scoring.
Best Practice
Subscription data should flow to CS platform for health scoring and churn prediction.
Clickpath
Settings → Integrations → [CS Tool]
Status
Findings

11Security & Compliance

5 items
ItemObjectSub-Item
Access Control
User
User Inventory
What We Look For
List all Chargebee users. Identify inactive accounts, over-privileged users, shared accounts.
Best Practice
No shared accounts. Remove departed users. Admin role limited to 2-3 people.
Clickpath
Settings → Users & Roles
Status
Findings
Access Control
User
Role Configuration
What We Look For
Review custom roles and permissions. Check for overly broad permissions.
Best Practice
Custom roles for: Finance (invoices/payments), Sales (subs/customers), Ops (full admin).
Clickpath
Settings → Users & Roles → Roles
Status
Findings
API Security
API Key
Key Management
What We Look For
Inventory all API keys. Check key types, last used dates, and associated applications.
Best Practice
Rotate API keys annually. Use read-only keys where possible. Label keys with purpose/owner.
Clickpath
Settings → API Keys
Status
Findings
PCI Compliance
Security
PCI DSS Status
What We Look For
Verify PCI compliance status. Check if using Chargebee.js or direct API for payments.
Best Practice
Use Chargebee.js (hosted pages) for PCI SAQ-A. Direct API requires SAQ-D (higher burden).
Clickpath
Settings → Hosted Pages; Security documentation
Status
Findings
Data Privacy
Security
GDPR/Privacy Compliance
What We Look For
Check data retention policies, consent management, and data deletion capabilities.
Best Practice
Enable data export/deletion for GDPR. Set appropriate retention periods.
Clickpath
Settings → Data Privacy; Customers → [Customer] → Delete/Export
Status
Findings

12Data Quality & Hygiene

7 items
ItemObjectSub-Item
Customer Data
Customer
Email Validity
What We Look For
Check for invalid/bounced email addresses across customer base.
Best Practice
Run email validation. Remove/update invalid emails. Flag customers without emails.
Clickpath
Customers → Export → Validate emails; Email bounce logs
Status
Findings
Customer Data
Customer
Duplicate Records
What We Look For
Search for duplicate customers by email, company name, and billing info.
Best Practice
Implement dedup rules before creation (API-level). Merge existing dupes.
Clickpath
Customers → Search; API: list customers with filters
Status
Findings
Subscription Data
Subscription
Orphaned Subscriptions
What We Look For
Check for subscriptions without valid customer records or incomplete data.
Best Practice
Every subscription must have valid customer link, plan, and billing info.
Clickpath
Subscriptions → Filter; API: list subscriptions with missing fields
Status
Findings
Subscription Data
Subscription
Status Accuracy
What We Look For
Verify subscription statuses reflect reality (no active subs for churned customers).
Best Practice
Status should match actual service delivery. Reconcile quarterly.
Clickpath
Subscriptions → Cross-reference with product/service delivery data
Status
Findings
Financial Data
Invoice
Invoice-Payment Reconciliation
What We Look For
Reconcile invoices with payments. Identify mismatched amounts or unlinked transactions.
Best Practice
Every paid invoice should have a matching payment. Monthly reconciliation required.
Clickpath
Reports → AR; Invoices → Paid → Cross-check with Payments
Status
Findings
Metadata
All Objects
Custom Field Completeness
What We Look For
Audit fill rates for custom fields across all objects.
Best Practice
Required custom fields >95% fill rate. Optional fields with <10% fill = remove or require.
Clickpath
API: export objects → analyze custom field population rates
Status
Findings
Historical Data
All Objects
Data Migration Integrity
What We Look For
If migrated: verify record counts, balances, and subscription states match source.
Best Practice
Post-migration checklist: customer count, active sub count, MRR, outstanding AR.
Clickpath
Compare Chargebee reports with source system reports
Status
Findings

13Salesforce Integration — Deep Dive

48 items
ItemObjectSub-Item
Connection & Authentication
Connection Health
SF Connection
Connection Status
What We Look For
Verify Chargebee-Salesforce connection is active and authenticated.
Best Practice
Connection should show Connected status. Use dedicated integration user.
Clickpath
Chargebee → Settings → Integrations → Salesforce → Connection Status
Status
Findings
Connection Health
SF Connection
Integration User
What We Look For
Identify the SF user account used for integration. Dedicated or shared?
Best Practice
Dedicated SF user (e.g., chargebee-integration@company.com). Not a personal account.
Clickpath
Chargebee → Settings → Integrations → Salesforce; SF → Setup → Users
Status
Findings
Connection Health
SF Connection
Package Version
What We Look For
Check installed Chargebee for Salesforce package version. Is it current?
Best Practice
Run latest package version. Check for updates monthly. Current: v2.0+.
Clickpath
SF → Setup → Installed Packages → Chargebee for Salesforce
Status
Findings
Permission Sets
SF Connection
Permission Set Assignment
What We Look For
Verify ChargebeeForSalesforceAdminUser and ChargebeeForStandardUsers assigned correctly.
Best Practice
Admin PS to integration admins only. Standard PS to users who view CB data in SF.
Clickpath
SF → Setup → Permission Sets → ChargebeeFor... → Manage Assignments
Status
Findings
Permission Sets
SF Connection
Object-Level Access
What We Look For
Verify profiles/permission sets grant appropriate CRUD access to CB custom objects.
Best Practice
Sales: Read. Finance: Read/Edit. Admins: Full CRUD. No one deletes CB records in SF.
Clickpath
SF → Setup → Profiles → [Profile] → Object Permissions → CB objects
Status
Findings
Customer ↔ Account Mapping
Customer-Account Mapping
Customer / Account
1:1 Mapping Integrity
What We Look For
Verify every Chargebee customer maps to exactly one SF Account. Check unmapped customers.
Best Practice
100% mapping for active customers. No orphaned Chargebee customers without SF Account.
Clickpath
Chargebee → Customers → SF section; SF → Account → Chargebee section
Status
Findings
Customer-Account Mapping
Customer / Account
Account Record Type
What We Look For
Check which SF Account record types are used for Chargebee-linked accounts.
Best Practice
Define which record type(s) map to CB customers. Exclude non-customer types from sync.
Clickpath
SF → Object Manager → Account → Record Types; Chargebee SF Settings
Status
Findings
Customer-Account Mapping
Customer / Account
Field Mapping — Standard
What We Look For
Audit standard field mappings: Company Name, Email, Phone, Billing Address.
Best Practice
All standard fields should be mapped and syncing bidirectionally. Verify data matches.
Clickpath
Chargebee → Settings → Salesforce → Field Mappings; Compare both systems
Status
Findings
Customer-Account Mapping
Customer / Account
Field Mapping — Custom
What We Look For
Review Additional Field Mappings for customer-to-account custom field sync.
Best Practice
Map all business-critical custom fields. Document mappings. Test with sample records.
Clickpath
Chargebee SF Settings → Additional Field Mappings (in Salesforce)
Status
Findings
Customer-Account Mapping
Customer / Account
Sync Direction Validation
What We Look For
Verify bidirectional sync: changes in SF update Chargebee and vice versa.
Best Practice
Test both directions: update SF Account → verify CB; update CB Customer → verify SF.
Clickpath
Modify field in SF → Check CB; Modify in CB → Check SF
Status
Findings
Customer-Account Mapping
Customer / Account
Mapping Conflicts
What We Look For
Check for mapping conflicts or sync errors on customer/account records.
Best Practice
Zero mapping conflicts. Resolve field type mismatches (picklist vs text, dates).
Clickpath
Chargebee SF Settings → Sync Logs → Filter: Customer/Account errors
Status
Findings
Subscription Mapping
Subscription Mapping
CB_Subscription__c
Object Existence
What We Look For
Verify CB_Subscription__c custom object exists in SF with all expected fields.
Best Practice
Auto-created during package install. All standard CB fields should be present.
Clickpath
SF → Setup → Object Manager → CB_Subscription__c → Fields & Relationships
Status
Findings
Subscription Mapping
CB_Subscription__c
Sync Coverage
What We Look For
Compare active subscription count in Chargebee vs CB_Subscription__c records in SF.
Best Practice
1:1 match. Zero gaps between Chargebee subscriptions and SF records.
Clickpath
Chargebee → Subscriptions → Count; SF → CB Subscriptions → List View → Count
Status
Findings
Subscription Mapping
CB_Subscription__c
Status Field Accuracy
What We Look For
Verify subscription status in SF matches Chargebee (Active, Trial, Cancelled).
Best Practice
Status should update in near real-time. Spot-check 10 records across statuses.
Clickpath
SF → CB_Subscription__c → Status; Compare with Chargebee → Subscriptions
Status
Findings
Subscription Mapping
CB_Subscription__c
Account Lookup
What We Look For
Verify CB_Subscription__c has valid lookup to Account. Check for orphaned records.
Best Practice
Every record should have a populated Account lookup. Zero orphans.
Clickpath
SF → Report: CB Subscriptions where Account = blank
Status
Findings
Subscription Mapping
CB_Subscription__c
Plan/Price Details
What We Look For
Check that plan name, price, billing frequency, and MRR are accurately synced.
Best Practice
MRR on SF record should match Chargebee exactly. Plan and frequency must be current.
Clickpath
SF → CB_Subscription__c → Plan, MRR, Frequency fields
Status
Findings
Subscription Mapping
CB_Subscription__c
Custom Field Sync
What We Look For
Audit custom fields on CB_Subscription__c mapped from Chargebee.
Best Practice
Document all custom subscription field mappings. Verify accuracy on samples.
Clickpath
Chargebee SF Settings → Additional Field Mappings → Subscription
Status
Findings
Invoice & Line Item Mapping
Invoice Mapping
CB_Invoice__c
Object & Fields
What We Look For
Verify CB_Invoice__c exists with fields: Number, Date, Due Date, Total, Status, Amount.
Best Practice
Standard fields present and populated. Object auto-created during install.
Clickpath
SF → Setup → Object Manager → CB_Invoice__c → Fields & Relationships
Status
Findings
Invoice Mapping
CB_Invoice__c
Sync Direction
What We Look For
Confirm invoices sync one-way: Chargebee → SF only. SF edits don't push back.
Best Practice
Invoices are read-only in SF. Source of truth is Chargebee. SF = visibility.
Clickpath
Chargebee SF Settings → Sync Configuration → Invoice direction
Status
Findings
Invoice Mapping
CB_Invoice__c
Count Reconciliation
What We Look For
Compare invoice counts between Chargebee and SF for a given period.
Best Practice
Counts should match 100% for synced periods. Check date range alignment.
Clickpath
Chargebee → Invoices → Count; SF → Report: CB Invoices → Count
Status
Findings
Invoice Mapping
CB_Invoice__c
Account Lookup
What We Look For
Verify every CB_Invoice__c links to the correct SF Account.
Best Practice
Every invoice should have valid Account lookup matching CB customer mapping.
Clickpath
SF → Report: CB Invoices where Account = blank
Status
Findings
Invoice Line Items
CB_Invoice_Line_Item__c
Line Item Sync
What We Look For
Verify line items sync with correct amounts, descriptions, quantities.
Best Practice
Line items should match Chargebee detail: description, qty, unit price, amount.
Clickpath
SF → CB_Invoice__c → Related CB Invoice Line Items
Status
Findings
Invoice Line Items
CB_Invoice_Line_Item__c
Parent Relationship
What We Look For
Confirm lookup from CB_Invoice_Line_Item__c to CB_Invoice__c is intact.
Best Practice
Every line item references parent invoice. Zero orphaned line items.
Clickpath
SF → Report: CB Invoice Line Items where Invoice = blank
Status
Findings
Credit Notes & Coupons
Credit Note Mapping
CB_Credit_Note__c
Credit Note Sync
What We Look For
Verify credit notes sync from Chargebee to SF. Check amounts, dates, linked invoices.
Best Practice
All credit notes in SF with correct amounts. Linked to originating invoice and account.
Clickpath
SF → CB_Credit_Note__c → List View; Compare with Chargebee
Status
Findings
Coupon Mapping
CB_Coupon__c
Coupon Sync
What We Look For
Verify coupons sync from Chargebee to SF. Check discount values and expiry.
Best Practice
Active coupons visible in SF for sales reference. Status reflects current state.
Clickpath
SF → CB_Coupon__c → List View; Compare with Chargebee
Status
Findings
Item Price Mapping
Item Price Mapping
CB_Item_Price__c
Item Price Sync
What We Look For
Verify CB_Item_Price__c records match Chargebee item prices.
Best Practice
All active item prices in SF. Sales uses for quoting — must be accurate.
Clickpath
SF → CB_Item_Price__c → List View; Compare with Chargebee
Status
Findings
Item Price Mapping
CB_Item_Price__c
Price Accuracy
What We Look For
Spot-check 10+ item prices: amount, currency, billing period, trial config.
Best Practice
Zero discrepancies. Any mismatch = sales quoting risk.
Clickpath
SF → CB_Item_Price__c → [Record]; Chargebee → Product Catalog → [Item] → [Price]
Status
Findings
Sync Health & Monitoring
Sync Health
Sync
Health Dashboard
What We Look For
Review Sync Health Dashboard: current status, last sync time, error counts.
Best Practice
All green, last sync <15 min ago, zero pending errors.
Clickpath
Chargebee SF Settings (in SF) → Sync Health Dashboard
Status
Findings
Sync Health
Sync
Sync Logs (30 Days)
What We Look For
Pull sync logs for last 30 days. Categorize errors by type, object, frequency.
Best Practice
Zero recurring errors. Errors resolved within 24 hours. Weekly log review.
Clickpath
Chargebee SF Settings (in SF) → Sync Logs
Status
Findings
Sync Health
Sync
Sync Latency Test
What We Look For
Create/update record in Chargebee, measure time to appear in SF.
Best Practice
Updates appear in SF within 1-5 minutes. >15 min = investigate.
Clickpath
Create test record in Chargebee → Monitor SF → Measure elapsed time
Status
Findings
Sync Health
Sync
Error Resolution Process
What We Look For
Check if documented process exists for resolving sync errors. Who owns it?
Best Practice
Designated owner. Weekly review cadence. Escalation path for persistent errors.
Clickpath
Internal documentation; Sync Logs → Error records
Status
Findings
Sync Health
Sync
Retroactive Sync Limitations
What We Look For
Confirm understanding: config changes don't retroactively update synced records.
Best Practice
Document limitation. Plan manual remediation when mappings change. Test in sandbox.
Clickpath
Chargebee documentation; Field Mapping change log
Status
Findings
Chargebee Actions in SF
CB Actions in SF
CB Actions
Available Actions
What We Look For
Inventory which Chargebee actions are available within Salesforce.
Best Practice
Enable actions aligned to sales workflow: create sub, add addon, apply coupon.
Clickpath
SF → Account → Chargebee Actions; Chargebee SF Settings → Actions
Status
Findings
CB Actions in SF
CB Actions
Action Permissions
What We Look For
Verify which SF users/profiles can execute Chargebee actions.
Best Practice
Only authorized roles execute billing actions. Sales: limited. Finance: broader.
Clickpath
Chargebee SF Settings → Actions → Permissions; SF → Permission Sets
Status
Findings
CB Actions in SF
CB Actions
Action Audit Trail
What We Look For
Check if SF-originated actions are logged in Chargebee with originating user.
Best Practice
All SF actions appear in Chargebee activity logs with integration user attribution.
Clickpath
Chargebee → Activity Logs → Filter: Salesforce-originated
Status
Findings
Data Quality — SF Side
SF Data Quality
All CB Objects
Record Count Reconciliation
What We Look For
Full record count comparison: Customers vs Accounts, Subs vs CB_Subs, Invoices vs CB_Invoices.
Best Practice
Counts match within 1% (timing ok). >2% gap = sync issue.
Clickpath
SF → Reports on each CB object; Chargebee → Dashboard → Counts
Status
Findings
SF Data Quality
All CB Objects
Orphaned Record Audit
What We Look For
Search for CB custom object records without parent Account lookups.
Best Practice
Zero orphaned records. Any found = mapping error. Fix root cause.
Clickpath
SF → Reports: CB objects where Account = blank
Status
Findings
SF Data Quality
Account
Unmapped Accounts
What We Look For
Identify SF Accounts that should have CB customers but don't.
Best Practice
All paying accounts should have a Chargebee mapping. Identify gaps.
Clickpath
SF → Report: Accounts where CB Customer ID = blank AND Type = Customer
Status
Findings
SF Data Quality
CB_Subscription__c
Stale Subscription Data
What We Look For
CB_Subscription__c records not updated in >30 days despite Active status.
Best Practice
Active subs should show recent sync. Stale records = broken sync.
Clickpath
SF → Report: CB Subs where Status = Active AND Last Modified > 30d ago
Status
Findings
SF Data Quality
CB_Invoice__c
Financial Data Accuracy
What We Look For
Spot-check invoice amounts, tax, totals between Chargebee and SF.
Best Practice
Zero financial discrepancies. Amounts, tax, totals must match exactly.
Clickpath
SF → CB_Invoice__c → Recent records → Compare with Chargebee
Status
Findings
SF Data Quality
All CB Objects
Field-Level Freshness
What We Look For
Compare last-modified timestamps on CB objects in SF vs Chargebee.
Best Practice
SF records update within minutes. Systematic lag = sync config issue.
Clickpath
SF → CB object → Last Modified; Chargebee → Object → Updated At
Status
Findings
SF Reporting on CB Data
SF Reporting
SF Reports
Standard Reports
What We Look For
Check for reports: Active Subs by Account, MRR by Account, Invoices by Date.
Best Practice
Build core library: MRR by Account, Sub Status, Invoice Aging, Churn by Rep.
Clickpath
SF → Reports → New Report → Select CB custom objects
Status
Findings
SF Reporting
SF Reports
Dashboard Availability
What We Look For
Verify SF dashboards showing Chargebee data for sales and CS teams.
Best Practice
Dashboards: Revenue by Account, Sub Health, Renewal Pipeline, Expansion Opps.
Clickpath
SF → Dashboards → Chargebee Data dashboards
Status
Findings
SF Reporting
SF Reports
Report Accuracy Validation
What We Look For
Cross-validate SF report totals with Chargebee native reports.
Best Practice
Reports match within 1%. Discrepancies = sync gaps or calculation differences.
Clickpath
Run same report in both systems → Compare totals
Status
Findings
SF Workflow Integration
SF Workflows
SF Automation
Process Builder / Flows
What We Look For
Inventory SF automations triggered by CB object changes.
Best Practice
Document all automations on CB objects. Ensure no conflict with Chargebee sync.
Clickpath
SF → Setup → Process Builder; SF → Setup → Flows → Filter: CB objects
Status
Findings
SF Workflows
SF Automation
Validation Rules
What We Look For
Check for validation rules on Account or CB objects that could block sync.
Best Practice
Validation rules on synced objects can break sync. Test rules against sync ops.
Clickpath
SF → Setup → Object Manager → Account / CB objects → Validation Rules
Status
Findings
SF Workflows
SF Automation
Trigger Conflicts
What We Look For
Check for Apex triggers on Account or CB objects that could interfere.
Best Practice
Apex triggers should be sync-aware. Avoid modifying CB-synced fields on inbound.
Clickpath
SF → Setup → Object Manager → Account / CB objects → Triggers
Status
Findings
SF Workflows
SF Automation
Field Update Rules
What We Look For
Check for workflow field updates that overwrite Chargebee-synced data.
Best Practice
Never auto-update CB-synced fields from SF workflows. Creates data ping-pong.
Clickpath
SF → Setup → Workflow Rules → Actions on Account or CB objects
Status
Findings

14Operational Readiness

6 items
ItemObjectSub-Item
Documentation
Process
Billing Operations Runbook
What We Look For
Check for documented billing ops procedures: common tasks, escalation, troubleshooting.
Best Practice
Runbook: new sub setup, plan changes, refunds, dunning escalation, sync errors.
Clickpath
Internal documentation / wiki / Confluence
Status
Findings
Documentation
Process
Integration Architecture Diagram
What We Look For
Verify up-to-date architecture diagram of all Chargebee integrations and data flows.
Best Practice
Diagram: Chargebee ↔ SF, Chargebee ↔ Accounting, ↔ Gateways, webhooks.
Clickpath
Internal documentation / architecture docs
Status
Findings
Sandbox/Testing
Environment
Sandbox Environment
What We Look For
Check if Chargebee test site exists and is actively used for testing.
Best Practice
All config changes tested in sandbox before prod. Sandbox should mirror prod.
Clickpath
Chargebee → Test Site; SF → Sandbox with Chargebee package
Status
Findings
Sandbox/Testing
Environment
Change Management Process
What We Look For
Verify change management process for Chargebee configuration changes.
Best Practice
Sandbox test → peer review → prod deploy → post-deploy verification.
Clickpath
Internal change management process
Status
Findings
Monitoring & Alerting
Operations
Proactive Monitoring
What We Look For
Check for monitoring: sync failures, payment decline spikes, webhook failures.
Best Practice
Alerts for: sync error rate >1%, payment failure spike >2x, webhook failure >1%.
Clickpath
Internal monitoring; Chargebee Webhooks → Alerts; Gateway dashboards
Status
Findings
Disaster Recovery
Operations
Backup & Recovery Plan
What We Look For
Verify data backup strategy for Chargebee data. Check recovery procedures.
Best Practice
Regular data exports as backup. Documented recovery. Test recovery annually.
Clickpath
Settings → Data Export; Internal DR documentation
Status
Findings