> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/integrations/crm/hubspot/sync-hubspot-deals-and-approving-contracts-in-rillet.md).

# Sync HubSpot Deals and Approving Contracts in Rillet

HubSpot deals sync into **Rillet** as contracts once marked **Closed Won**. Synced contracts carry a **Pending Approval** status and have no impact on financial statements or metrics until they are approved.

### HubSpot to Rillet Field Mapping

The integration maps HubSpot records to Rillet as follows:

| HubSpot    | Rillet                                                               |
| ---------- | -------------------------------------------------------------------- |
| Companies  | [**Customers**](https://app.rillet.io/accounts-receivable/customers) |
| Products   | [**Products**](https://app.rillet.io/accounts-receivable/products)   |
| Deals      | [**Contracts**](https://app.rillet.io/accounts-receivable/contracts) |
| Line Items | Contract Line Items                                                  |

These mappings apply automatically once a HubSpot deal syncs into Rillet as a contract.

### Sync HubSpot Deals Into Rillet

With the HubSpot integration connected to Rillet, mark the deal as Closed Won in HubSpot to sync it into Rillet as a contract with status Pending Approval, which you can then locate and review in the Pending Approval listing.

### View Synced Contracts

You can view synced contracts in Rillet using either of these methods:

| Method             | How to Access                                                                                                                                               |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Launchpad**      | Go to [**Contracts to be Approved**](https://app.rillet.io/) under **Needs Action** from the Launchpad.                                                     |
| **Contracts List** | Go to the [**Contracts List**](https://app.rillet.io/accounts-receivable/contracts?startDate=2024-08-30\&sources=HUBSPOT) and filter by the HubSpot source. |

Deals sync every 30 minutes, creating Customers and Products in Rillet only when associated with a Closed Won deal, and once you locate a synced contract, you can review and approve it as described in the next section.

### Approve a Synced Contract

Follow these steps to approve a synced contract:

1. Select the contract to review from [**Contracts to be Approved**](https://app.rillet.io/accounts-receivable/contracts?startDate=2024-08-30\&statuses=PendingReview) under **Needs Action**.

   <figure><img src="/files/PZayA5C2XZjYBWWw5IFV" alt=""><figcaption></figcaption></figure>
2. Review the contract details:
   * **General Details:** Deal name, Closed date, Start date, End date.
   * **Products:** Verify line items; add or edit products as needed.
   * **Invoicing:** Review invoice schedule and payment terms.
   * **Revenue:** Review automated revenue schedules and adjust if needed.
3. Click **Confirm Contract** to finalize the contract.

   <figure><img src="/files/CnL6zcJEPQJPIhXryhnh" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:**&#x20;

Confirming creates the contract journal entries, invoices, and updates metrics.
{% endhint %}

Once approved, the contract's financial activity is fully reflected in Rillet's statements and metrics.

### See Also&#x20;

To learn more about managing CRM integrations in Rillet, review these articles:

* [**Sync Stripe Customers into Rillet**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/billing-and-subscription-management/stripe-billing/stripe-billing-integration-overview/sync-stripe-customers-into-rillet.md)
* [**Hubspot**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/crm/hubspot.md)
* [**Salesforce Integration**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/crm/salesforce-integration.md)
* [**Salesforce Bi-Directional Sync: Invoices, Contracts, and Customers**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/crm/salesforce-integration/salesforce-bi-directional-sync-invoices-contracts-and-customers.md)
* [**Salesforce Managed Package Integration Overview**](/EjmEP4KZ9BVp9j2ho4Mh/integrations/crm/salesforce-integration/salesforce-managed-package-integration-overview.md)
* [**Add a Contract**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-receivable/contracts/add-a-contract.md)
* [**Managing Contracts**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-receivable/contracts/managing-contracts.md)
* [**How to Create an Auto-Renewing Contract**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-receivable/contracts/how-to-create-an-auto-renewing-contract.md)
* [**View GL Impact for Usage Cycles**](/EjmEP4KZ9BVp9j2ho4Mh/accounts-receivable/contracts/view-gl-impact-for-usage-cycles.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/integrations/crm/hubspot/sync-hubspot-deals-and-approving-contracts-in-rillet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.