Rillet is a revenue recognition ERP. The connection is one way, from Zenskar to Rillet only. Zenskar exports customers, invoices, and credit notes to Rillet; nothing syncs back. A connection binds to exactly one Rillet subsidiary, so an organization with multiple subsidiaries needs one connection per subsidiary.
A Rillet account with API access, and an API key generated for it. Note whether the key is for Rillet’s sandbox or production environment, since each has separate keys.
A chart of accounts already set up in Rillet. The connector references accounts by their code and never creates them, so these must already exist: a sales or revenue account, a tax account of type Liability, and a discount account of type Income or Expense.
If the Rillet organization has more than one subsidiary, decide which one this connection maps to.
The subsidiary you map this connection to, together with the Zenskar entity, cannot be changed after you save the configuration. To point the connection at a different subsidiary or entity, delete the connection and create a new one.
Log in to Rillet to generate an API key. In Rillet, select the organization in the bottom left corner, go to Organization Settings > API Access, and click + Create API Key. Copy and save the key, since you cannot view it again after this step.
In Zenskar, go to More > Integrations > ERP, find the Rillet card, and click Connect.
On the Rillet page, click Connect to Rillet.
In the dialog, fill in the following fields, then click Connect:
Field
What to enter
Environment
sandbox or production, matching the Rillet API key generated in step 1.
API Key
The Rillet API key generated in step 1.
Zenskar validates the key against Rillet immediately. If the key is invalid, or does not match the environment entered, the connection does not save and Zenskar shows an error.
Zenskar redirects you to the Configuration screen.
Under Entity Sync Mapping, map the connection to a Rillet subsidiary and a Zenskar entity:
Field
What it does
Rillet Entity
The Rillet subsidiary this connection syncs to. Required.
Zenskar Entity
The Zenskar business entity mapped to that subsidiary. Required.
Under Data Sync Setup, enable the modules to sync. Every module is export only, from Zenskar to Rillet:
Customers
Sync direction
Export only
What it syncs
Zenskar customers, to Rillet.
Invoices
Sync direction
Export only
What it syncs
Approved Zenskar invoices, to Rillet, for revenue recognition.
Credit Notes
Sync direction
Export only
What it syncs
Zenskar credit notes, to Rillet, as credit memos.
Configure the account mapping and product settings for Invoices and Credit Notes. None of these have a default or recommended value, each account must already exist in Rillet, and Zenskar does not validate the account type until sync time:
Setting
Applies to
What it does
Sales Account for Invoices
Invoices
Required. Any Rillet account type.
Tax Account for Invoices
Invoices
Required. Must be a Liability account in Rillet.
Discount Account for Invoices
Invoices
Required. Must be an Income or Expense account in Rillet.
Sales Account for Credit Notes
Credit Notes
Required. Any Rillet account type. There is no separate tax or discount account for credit notes.
Auto-create Products
Invoices
Enabled by default. Creates the product in Rillet automatically when an invoice references a Zenskar product that is not yet mapped.
Default Revenue Pattern
Invoices
Even Period or Daily. Defaults to Even Period. Applied to auto-created products.
Include in ARR/MRR
Invoices
Enabled by default. Whether auto-created products count toward ARR and MRR.
Customers referenced by an invoice sync to Rillet during invoice sync, even if the Customers module is turned off.
Credit notes do not create the customer in Rillet. The customer must already be synced, or the credit note sync fails. The customer’s billing country must also be set, since it determines whether Rillet applies VAT or sales tax on the credit memo.
Click Save Configuration. The connection shows as Configured on the Rillet Connections tab.
Rillet is a revenue recognition ERP, and this shapes how every invoice syncs. Each invoice line carries a revenue period, taken from the line’s own service dates, or the invoice’s billing period if the line has none. Each product carries a recognition pattern, Even Period or Daily, and a flag for whether it counts toward ARR and MRR. Rillet builds its revenue schedules from this data natively. Zenskar does not post separate journal entries to Rillet.
Duplicate sync protection
Re-syncing an invoice or credit note that already synced is blocked. Zenskar never creates a duplicate record in Rillet.
Failed sync rollback
If an invoice sync fails partway, Zenskar rolls back the invoice it created in Rillet.
Closed period and due date checks
Rillet rejects posting into a closed accounting period, and rejects a due date earlier than the invoice date. Both surface as sync errors.
Payments
Not supported. The Rillet connector has no payment sync in either direction.
Journal entries
Not supported. Rillet performs revenue recognition natively, so Zenskar does not post journal entries to it.
Zenskar validates the key against Rillet immediately. If the key is invalid, or does not match the environment entered, the connection does not save and Zenskar shows an error.
