# Reports

The Fours Salesforce App ships with a set of **Custom Report Types** and pre-built **Reports** that give your team out-of-the-box visibility into marketplace offers, entitlements, revenue, co-sell referrals, funding activity, and the partner contacts mapped to your accounts.

This page documents each report type — what object it's built on, what data it joins together, and what fields it exposes.

---

## Overview

If you manage marketplace sales across multiple cloud providers, reporting usually means switching between AWS, Azure, and GCP, exporting CSV files, and manually combining them into a single spreadsheet. This creates three common problems:

- Data is fragmented across different systems.
- Reports take hours to build and validate.
- It's hard to compare performance across clouds consistently.

Fours acts as the data layer between the cloud marketplaces and your CRM. It standardizes marketplace data from AWS, Azure, and GCP into a single structure before syncing it into Salesforce. Once connected, all marketplace activity shows up in one consistent format — regardless of which cloud it originated from — so you can report on it directly in Salesforce.

### How Fours Normalizes Marketplace Data

A common question from RevOps teams is whether they need separate reporting logic for each cloud. With Fours, the answer is no. Fours maps AWS, Azure, and GCP marketplace objects into a unified data model so they behave consistently inside Salesforce. This means:

- A deal from AWS looks the same as a deal from GCP.
- Fields and object types are consistent across all clouds.
- One reporting model works across all marketplace activity.

This removes the need to build and maintain cloud-specific reporting logic.

### Before vs. After Fours

| Reporting task | Without Fours | With Fours |
| --- | --- | --- |
| Track pipeline across clouds | Export separate reports from AWS, Azure, and GCP, then combine manually | View all marketplace opportunities in a single Salesforce dashboard |
| Monitor deal status | Check each cloud portal individually for updates | See real-time status updates directly in Salesforce |
| Build leadership reports | Download and merge multiple CSV files every reporting cycle | Run unified reports directly from Salesforce with standardized data |

---

## What Your Team Can Track

Once Fours is connected to Salesforce, marketplace data can be used directly in dashboards and reports.

### Sales and Growth

Use these to understand how your marketplace business is growing over time:

- Number of accepted offers per month
- Average time from offer creation to buyer acceptance
- Top customers ranked by marketplace revenue

Instead of waiting for a finance report at the end of the month, your sales team can see in real time which deals have closed and which are still pending buyer action.

### Funnel Performance

Use these to track how opportunities move through your co-sell pipeline:

- Volume of opportunities shared to cloud marketplaces (outbound referrals)
- Marketplace close rates by cloud provider
- Conversion metrics across AWS, Azure, and GCP side by side

If your team is co-selling with a cloud partner, these metrics tell you which partnerships are actually driving closed revenue and which ones need attention.

### Financial Health

Use these to stay on top of payment and contract status without chasing down individual deals:

- Overdue payments and past-due contract flags
- Refund trends over time
- Transaction volume broken down by country or region

Your Finance team gets a live view of payment health instead of waiting for end-of-month reconciliation.

---

## Where to Find Reports

1. In Salesforce, click **Reports** in the App Launcher.
2. Open the **All Folders** view and look for:
   - **Suger Reports** — pre-built dashboards and reports for co-sell and marketplace activity.
   - **Suger Marketplace Operations Reports** — operations-focused reports (offers, entitlements, revenue).
3. To build your own report, click **New Report** and search for any report type with the **"Suger"** prefix.

To view pre-built dashboards:

1. Go to the **Dashboards** section in Salesforce.
2. Search for Suger dashboards (for example, marketplace or co-sell dashboards).
3. Apply filters such as date range or cloud provider.
4. Drill into individual reports to explore deal-level details.

:::info
If dashboards or reports are not visible, your team may need to complete the initial CRM integration setup. See [Integrate Salesforce with Fours](/integrations/salesforce/).
:::

---

## Custom Report Types

All Fours report types are listed below grouped by primary domain. Field coverage notes refer to which Fours custom-object fields are queryable; standard Salesforce system fields (`Id`, `Owner`, `Name`, `CreatedDate`, `LastModifiedDate`, etc.) are included on every report type and are not listed individually.

### Marketplace Report Types

| Report Type | Label | Base Object | Joined Objects | Purpose |
| ----------- | ----- | ----------- | -------------- | ------- |
| `Suger_Offers` | Suger (Offers) | `Offer__c` | — | Single-object report on marketplace offers. Includes status, type, buyer info, dates, approval status, AWS Net Payment Term, and external IDs from each cloud marketplace. |
| `Suger_Offers_with_Dimensions` | Suger Offers and Offer Dimensions | `Offer__c` | `OfferDimension__c` (child) | Offers, including AWS Net Payment Term, joined to their metering dimensions. Use when you need per-dimension pricing (Rate, Key, Plan) alongside offer attributes. |
| `Entitlements_Suger` | Cloud Entitlements (Suger) | `Entitlement__c` | — | Single-object report on customer entitlements. Includes financial roll-ups (Invoiced, Collectable, Disbursed amounts), product, offer, and buyer linkage, and the entitlement's **AWS Net Payment Term**. |
| `Suger_Entitlements_and_Revenue_Records` | Suger Entitlements and Revenue Records | `Entitlement__c` | `RevenueRecord__c` (child) | Entitlements joined to their per-transaction revenue records. Use for revenue breakdown by entitlement, invoice date, or disbursement period. Also exposes the linked **Account** — the lookup itself plus **Account Name** and **Account ID** via lookup — so revenue can be grouped and filtered by customer account. The entitlement's **AWS Net Payment Term** is available too. |
| `Suger_Revenue_Records` | Suger Revenue Records | `RevenueRecord__c` | — | Revenue transactions tracking payments from buyers and disbursements from cloud partners. Includes invoice amount, collectable amount, disburse amount, and partner fees. |
| `Suger_Offer_Payment_Installments` | Suger Offer Payment Installments | `OfferPaymentInstallment__c` | — | The payment schedule behind an offer, with the parent offer reachable through the Offer lookup. Exposes Charge Date, Amount, Original Amount, Discount Percentage, Credit, and Currency — use it to report on prepay schedules and negotiated free credit rather than on offer totals. |
| `Suger_Fundings` | Suger (Fundings) | `Funding__c` | — | AWS Funding requests, including status, opportunity linkage, approval workflow, and claim amounts, plus the cash request's PO number and payee profile, the ACE opportunity ID, the AWS account, issued amount, expiration date, fulfillment types, and partner contact emails. |

### Co-Sell Report Types

| Report Type | Label | Base Object | Joined Objects | Purpose |
| ----------- | ----- | ----------- | -------------- | ------- |
| `Cloud_Referrals` | Cloud Referrals (Suger) | `Referral__c` | — | Single-object report on all co-sell referrals. Includes common fields plus all AWS, Azure, and GCP cloud-specific fields (`AWS_*`, `AZURE_*`, `GCP_*`). |
| `Opportunities_with_Cloud_Referrals` | Opportunities with Cloud Referrals | `Opportunity` | `Referral__c` (via `Referrals__r`) | Salesforce Opportunities joined to their Fours referrals. Useful for measuring opportunities that have an associated co-sell referral. |
| `Cosell_Opportunities_with_Cloud_Referrals` | Co-Sell Opportunities with Cloud Referrals | `Opportunity` | `Referral__c` (via `Referrals__r`) | Variant of the above scoped to co-sell-tagged opportunities. |
| `opportunities_trending` | Co-Sell Opportunities Trending | `Opportunity` | `Referral__c` (via `Referrals__r`) | **DEPRECATED.** Earlier version of the Opportunities-with-Referrals report type. Kept for backwards compatibility with existing dashboards. Use `Opportunities_with_Cloud_Referrals` for new reports. |

**Invitation Message** (`AWS_InvitationMessage__c`) is selectable as a column on the referral report types — the covering note the sender attached to an AWS engagement invitation. It is an invitation-only field, so it stays populated after acceptance and is one way to identify, after the fact, that a referral arrived as an inbound invitation.

### Partner Contact Report Types

These report on the partner contacts — such as the AWS, Azure, and GCP sellers on your deals — mapped to your Accounts, so partner-seller activity can be lined up against your own accounts and campaigns.

| Report Type | Label | Base Object | Joined Objects | Purpose |
| ----------- | ----- | ----------- | -------------- | ------- |
| `Accounts_with_Suger_Partner_Contacts` | Accounts with Suger Partner Contacts | `Account` | `Contact_Account__c` (via `Contact_Accounts__r`, with or without) | Accounts and the partner sellers mapped to them, including accounts with no open opportunities. Carries the **Collaboration Score**. |

:::note
**Three partner-contact report types are no longer installed with the package.** **Opportunities with Suger Partner Contacts**, **Suger Partner Contact Accounts**, and **Suger Partner Contact Opportunities** — with the **[Suger] Partner Contacts by Opportunity** report built on the first — were taken out because every packaged custom report type counts against your org's custom report type limit, and orgs already at that limit could not upgrade. An org that installed them earlier keeps them; new installs do not get them.
:::

Group or filter on **Link Source** to keep confirmed referral activity (`Referral`) apart from domain matches Fours inferred (`Predicted`) and mappings an admin uploaded (`Upload`). The contact's name, email, role, and partner are copied onto each row, because an Account- or Opportunity-based report cannot reach the partner contact record itself — see [Contact_Account__c](/salesforce-app/salesforce-app-custom-objects/#contact_account__c) for every field and for when rows are written. Every Fours user, co-sell, marketplace, and funding permission set can read these objects, so anyone with one of those sets can run the reports.

### Cross-Domain Report Types

| Report Type | Label | Base Object | Joined Objects | Purpose |
| ----------- | ----- | ----------- | -------------- | ------- |
| `Opportunities_Suger` | Opportunities - Offers (Suger) | `Opportunity` | `Offer__c` (via `Offers__r`) | Opportunities joined to their Fours offers, including AWS Net Payment Term. Useful when an Opportunity drives one or more marketplace offers and you want both on a single row. |
| `Opportunities_with_Suger_Entitlements` | Opportunities with Suger Entitlements | `Opportunity` | `Offer__c` → `Entitlement__c` (two-level join via `Offers__r.Entitlements__r`) | Opportunities all the way through to fulfilled entitlements, with AWS Net Payment Term available from the offer. Tracks the full sales-to-fulfillment lifecycle on one report. |

---

## Pre-Built Reports

The Fours app installs two folders of pre-built reports:

### Suger Reports

Focused on co-sell activity and pipeline health:

- **All Co-Sell Opportunities** — every opportunity tagged with a referral
- **All Co-Sell Opportunities by Week** — co-sell volume trend
- **Inbound / Outbound Co-Sell Opportunities by Week** — directional volume trends
- **Win Ratio (Current FY)** — co-sell-influenced win rate
- **CoSell Opportunity Leaderboard** — leaderboard by opportunity owner
- **CoSell Opportunities by AWS AM / AWS ISM / Sales Stage / Referral Type / PTB** — segmentation breakdowns
- **Days to Close** (Opportunity Created Date / Referral Created Date) — cycle-time metrics
- **Inbound CoSell Opportunities by AWS AM / MS Contact** — partner-rep attribution
- **MS All Referrals by MACC Eligibility** — Microsoft MACC eligibility breakdown
- **Opportunities without CoSell** — uncovered pipeline
- **[Suger] Partner Contacts by Account** — the partner sellers mapped to each account, grouped by **Link Source**, including accounts with no open opportunities
- **[Suger] Partner Contacts by Opportunity** — the partner sellers associated with each opportunity, grouped by **Link Source**, with the opportunity amount summed. No longer installed with the package; see [Partner Contact Report Types](#partner-contact-report-types)

This folder also carries a few marketplace reports alongside the co-sell ones:

- **All Marketplace Offers** — offer-level inventory of all marketplace activity, with **AWS Net Payment Term** included as a column
- **All Active Entitlements Report** — the contracts currently running
- **Opportunities with Suger Entitlements** — opportunities followed through to fulfilled entitlements
- **Suger Revenue Records** / **Suger Entitlements and Reveue Records** — transaction-level revenue

### Suger Marketplace Operations Reports

Focused on marketplace transactions and revenue ops. The folder installs sixteen reports:

| Report | What it answers |
| --- | --- |
| **Current FY Accepted Private Offers** | Private offers accepted so far this fiscal year. |
| **Current FQ Accepted Private Offe** | The same, scoped to the current fiscal quarter. |
| **FQ Accepted Private Offers SUM** | Fiscal-quarter accepted private offers, summed. |
| **All Time Accepted Private Offers** | Every private offer ever accepted. |
| **Private Offers Expiring This Week** | Offers whose acceptance window closes within the week. |
| **Contracts Expiring this Month** | Entitlements reaching their end date this month. |
| **Active Public Offers Over Time** | Public (listing) offer volume as a trend. |
| **Accepted Offer Distribution by Country** | Where accepted offers are coming from geographically. |
| **Current FY Pipeline by Cloud** | This fiscal year's marketplace pipeline split by cloud. |
| **Current FY Sum/Average Deal Size** | Deal-size totals and averages for the current fiscal year. |
| **Previous FY Sum/Average Deal Size** | The same for the prior fiscal year, for comparison. |
| **Marketplace Average Deal Size (12 month)** | Rolling twelve-month average deal size. |
| **Average for Offer Acceptance** | How long buyers take to accept. |
| **Marketplace Revenue by Product and Cloud** | Revenue broken out by product and cloud. |
| **Marketplace Leaderboard** | Ranking by marketplace activity. |
| **Past-Due Marketplace Disbursements** | Disbursements the cloud partner has not paid on time. |

**AWS Net Payment Term** is a selectable column in two places. The offer's field is on the four Offer/Opportunity report types that reach an offer — `Suger_Offers`, `Suger_Offers_with_Dimensions`, `Opportunities_Suger`, and `Opportunities_with_Suger_Entitlements`. The entitlement's own copy is on `Entitlements_Suger` and `Suger_Entitlements_and_Revenue_Records`. Both are off by default; add them from the field list. The revenue-record **Payment Terms** field is separate: on an AWS record it follows the accepted AWS net payment term, and otherwise counts the days from invoice date to payment due date — see [Custom Objects](/salesforce-app/salesforce-app-custom-objects/).

You can clone any pre-built report and adapt it; the underlying Custom Report Types listed above are the foundation.

---

## Building Your Own Report

To build a custom report using Fours data:

1. In Salesforce, go to **Reports → New Report**.
2. In the report type picker, search for **"Suger"** to filter to Fours report types.
3. Select the report type matching the data you need (see the tables above).
4. Add columns from the available fields. All custom fields on the base object (and joined child objects, where applicable) are queryable.
5. Apply filters and groupings as you would with any Salesforce report.

:::tip
For complex multi-object analysis (e.g., Opportunity → Offer → Entitlement → Revenue), start with the highest-level joined report type (`Opportunities_with_Suger_Entitlements`) — it gives you the longest reach into the data model in a single report.
:::

---

## Field Reference

For per-field definitions, see the [Custom Objects](/salesforce-app/salesforce-app-custom-objects/) page — every field exposed in a report type is documented on its parent object's table.