Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Customer identity
Customer / Account
Before linking Rillet Customer to Zoho CRM Account, check whether the customer is an individual or a company. Match the correct record type in each system.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Zoho CRM
- Documented record · ✅ Supported
- Record identity
- Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
- Field ownership
- Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
- Source customer ID
- Person/company classification
- Legal entity or business unit
- Destination identity reference
- Record dependencies
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Validation
- Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
- Recovery
- Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
References: Rillet: Customer documentationZoho CRM: Account documentation
Customer identity
Customer / Contact
Before linking Rillet Customer to Zoho CRM Contact, check whether the customer is an individual or a company. Match the correct record type in each system.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Zoho CRM
- Documented record · ✅ Supported
- Record identity
- Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
- Field ownership
- Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
- Source customer ID
- Person/company classification
- Legal entity or business unit
- Destination identity reference
- Record dependencies
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Validation
- Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
- Recovery
- Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
References: Rillet: Customer documentationZoho CRM: Contact documentation
Record matching
Invoice / Invoice
Compare whether Rillet Invoice and Zoho CRM Invoice describe the same customer invoice in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Zoho CRM
- Documented record · ✅ Supported
- Record identity
- Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
- Field ownership
- The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
Fields to include
- Source invoice ID
- Customer or supplier reference
- Line totals
- Currency
- Posting/payment status
- Record dependencies
- Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
- Validation
- Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
- Recovery
- Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
References: Rillet: Invoice documentationZoho CRM: Invoice documentation
Business process
Invoice / Sales Order
Order-to-invoice handoff: Zoho CRM Sales Order provides context for Rillet Invoice. These are related records, not equivalent entities.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Zoho CRM
- Documented record · ✅ Supported
- Record identity
- Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
- Field ownership
- Finance owns invoice posting; the order system supplies the approved commercial context.
Fields to include
- Source record reference
- Destination record reference
- Approved handoff state
- Duplicate-detection key
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
References: Rillet: Invoice documentationZoho CRM: Sales Order documentation
Record matching
Vendor / Vendor
Compare whether Rillet Vendor and Zoho CRM Vendor describe the same supplier or vendor in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Zoho CRM
- Documented record · ✅ Supported
- Record identity
- Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
- Field ownership
- Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.
Fields to include
- Source supplier ID
- Legal name
- Entity reference
- Payment terms
- Active status
- Record dependencies
- Resolve business-unit and payment-term references before purchasing transactions.
- Validation
- Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
- Recovery
- Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.
References: Rillet: Vendor documentationZoho CRM: Vendor documentation
