QuotaPath's integration with Rillet lets you bring your accounting and revenue data — customers, contracts, invoices, payments, credit memos, and more — into QuotaPath to determine payout eligibility and, if needed, to create deals.
Like other accounting integrations (e.g. QuickBooks, Campfire), Rillet is most commonly used as a payouts eligibility source — for example, to release a commission once an invoice is paid — rather than as the source that creates deals. In fact, Rillet is itself typically fed by your CRM (opportunities/deals sync into Rillet as contracts), so deals almost always originate in the CRM.
Integration Requirements
A Rillet account with API access enabled. Rillet is cloud-based; QuotaPath connects over Rillet's API.
A Rillet API key, created in Organization Settings → API access (app.rillet.io/settings/api-access).
Confirm environment. Rillet provides separate Production (api.rillet.com) and Sandbox (sandbox.api.rillet.com) environments, QuotaPath can connect to either.
QuotaPath can read Rillet data but cannot write any data back into Rillet.
How to connect Rillet
In Rillet, ensure API access is enabled (contact your Rillet team), then create an API key in Organization Settings → API access and copy it.
In QuotaPath, go to Integrations and find the Rillet card. Click Connect.
Paste your Rillet API key. Click Next.
Set your sync schedule.
Select necessary objects to sync and choose Sync Now. See supported objects below.
Select only the objects that directly contain the data needed for deal creation or payout eligibility. it's always best practice to minimize the data that you are ingesting and consistently syncing to speed up app performance and minimize data errors.
Once you have successfully connected Rillet, on the Integrations page, you will see a Rillet connection card where you can click to either "Manage" the integration or manually Sync and Refresh (start a sync outside of the scheduled cadence).
If you have created a new field within Rillet on any object that is synced into QuotaPath, and you want to pull that field into QuotaPath to use for mapping or eligibility, you will need to:
Click Manage on your connection card.
Go to the Manage Source tab.
Scroll down to click Reset Data. This will refresh your entire data schema, pulling in new fields. The standard sync and refresh button that you see in a couple different places in the app will not detect new fields.
Supported objects
Invoices (most common)
Invoice Payments
Credit Memos
Customers
Contracts (and Draft Contracts)
Products
Vendors
Vendor Credits
Custom Fields
How to set up for Payouts Eligibility
This is the most common way to use Rillet: deals are created in your CRM, and Rillet data determines when a commission becomes payable. This means that two integrated sources will be used. You cannot use one Data Source for component mapping and another for Payout Terms (i.e. Payout eligibility).
To enable this multi-source eligibility setup, you must have a connecting ID (e.g. Deal ID) or field that exists in Rillet AND on your deal create data source records. QuotaPath will work with you to join your Rillet data needed to determine eligibility to the Deal Create source records, enabling you to use one source object for your mapping and eligibility, as is required. Work with your Customer Success Manager or Account Manager to build this data connection.
Important: You must have a connecting ID between your two data sources. This may involve adding and backfilling new fields in Rillet.
Once you have Rillet data joined to your deal create source data:
Map your component(s) to your Deal Create source first (e.g. Hubspot, Salesforce).
Click Setup Payout Terms on your component(s) and add a Payout Eligibility rule using one of the two options: By Invoice or By Date. Common fields used for each are:
Paid Amount to release the payout when (or in proportion to how much of) the invoice is paid (Rillet tracks invoice payments and remaining balance).
Due Date or Invoice Date
For 1:many deals (one deal → several invoices/payments), reach out to QuotaPath support, combining those records may need assistance. Typically Eligibility by Invoice: Paid Amount is used to aggregate all paid amounts as they come in. As the Paid Amount grows in proportion to the total Deal Amount, the Commission amount eligible to be paid out will grow in the same proportion. For example, if each invoice is 25% of the total deal amount, each paid invoice will make 25% of the earnings eligible for payout until 100% of the invoice is paid the entire payout is eligible.
Note: Only confirmed/active Rillet contracts drive invoicing and revenue. If a deal's Rillet contract is still a draft awaiting review, it won't have invoices to key eligibility off yet.
How to set up for Deal Create only
Note: It is rare — and somewhat circular — to use Rillet as the deal-create source, because Rillet contracts usually originate from your CRM in the first place. Use this only if Rillet records should generate deals directly.
In your QuotaPath plan, on your component click Map Data Source.
Click Create New Mapping (or choose an existing Rillet mapping to use or edit)
Choose Rillet as your data source, and choose the correct object
Map the required deal fields:
QuotaPath field | Rillet source | Notes |
Deal Name | contract name or invoice_number | Whatever value is most helpful to identify a deal in QuotaPath. Can also be joined from another data sources in some situations. |
Deal Amount | contract total / invoice amount | {amount, currency}; amount_paid / amount_due also available |
Deal Date | contract start date / invoice_date | due date / paid date also available |
Deal Owner | custom field (rep email) | see Setting up Deal Owner |
Define your deal stages (a "closed won" equivalent is required; pipeline and closed-lost stages are optional). For Rillet, this maps to contract status (draft vs active) or invoice status / paid state. Remember: a draft contract is not yet "real" — only a promoted/active contract should count as closed-won.
Lastly, on the Filters page of the mapping modal, set any needed filters to ensure you are mapped to the right set of Rillet records. For more information on mapping, see our mapping overview.
Troubleshooting
Connection fails right after entering the key: confirm API access is enabled for your org, the key was copied in full, you're pointed at the right environment (prod vs sandbox), and the key hasn't been revoked or rotated in Rillet.
A record isn't syncing: incremental syncs only pull records changed since the last run; check the record's updated date against your Start Date, and confirm the object is in the launch scope. For old records, a small change on the Rillet record can update the date to be captured after a fresh QuotaPath sync.
Records aren't attributed to a rep: confirm the Rillet custom field holds the rep's email, is populated on the record, and is mapped to Deal Owner.
A closed-won deal has no payable invoice yet: its Rillet contract may still be a draft awaiting review, so no invoices exist to key eligibility off.