Accounting and finance / ERP · Two-way sync platform
Rillet and SuiteAnalytics integration
Bring supported SuiteAnalytics data into Rillet for your team's workflows and reporting. This connector supports updates from SuiteAnalytics to Rillet.
Built for teams where self-serve, reliability and scale matter
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Example workflow
Customer sync test
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting eventA change involving Rillet Customer or SuiteAnalytics Customer needs a defined result in the other system.
01
Start with Rillet Customer and SuiteAnalytics Customer. Use the record-matching and field-ownership rules from your mapping worksheet.
02
Resolve person or company type, legal entity, business role, and any billing account before transactions.
03
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Set up Rillet and SuiteAnalytics from Claude or ChatGPT
Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.
1. Add the Stacksync MCP server
Server URL
https://mcp.stacksync.com/mcp
In Claude
Open Customize → Connectors, select + Add, then Add custom connector.
Name it Stacksync and enter https://mcp.stacksync.com/mcp.
Select Connect, sign in to Stacksync and choose your workspace.
In ChatGPT
Open Settings → Apps → Advanced settings and turn on Developer mode.
Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
SuiteAnalytics recordCustomerDocumented record: Read: Supported. Write: see guide.
Record matchingDetermine 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 ownershipSeparate 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.
SuiteAnalytics recordContactDocumented record: Read: Supported. Write: see guide.
Record matchingDetermine 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 ownershipSeparate 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.
Record matchingRetain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Field ownershipThe financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect Rillet and SuiteAnalytics
Put your Rillet and SuiteAnalytics data to work
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Rillet and SuiteAnalytics workflow to test, define what success looks like, and decide who handles failed updates.
01
Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
02
Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
03
Join ERP data with CRM data in Postgres for quote-to-cash and revenue visibility
04
Give internal tools a read replica of item and inventory data without hitting SuiteScript governance limits
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Rillet
Read and write support varies by record
Record types covered in the setup guide
Record types
Coverage and requirements
Customer
Invoice
Vendor
Credit Memo
Bill
Journal Entry
Invoice Payment
Charge
Reimbursement
Custom Field
Incremental: Yes; historical: Yes; delete detection: Yes. Confirm field permissions and sync direction.
Account
Incremental: Yes; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
Subsidiary
Tax Rate
Product
Contract
Bank Account
Incremental: No; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
Bank Transaction
Incremental: No; historical: Yes; delete detection: Yes, every 4h. Confirm field permissions and sync direction.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Rillet
Integration interface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only to enable writes for two-way sync; check Read Only to prevent write-back
Change detection
Historical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
Generate an API key in Rillet Organization Setting > API Access.
For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.
Limitations to check
Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Rillet setup checklist
Generate an API key in Rillet Organization Setting > API Access.
For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Compare whether Rillet Customer and SuiteAnalytics Customer describe the same customer in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Rillet
Documented record · Incremental: Yes; historical: Yes; delete detection: Yes
SuiteAnalytics
Documented record · Read: Supported. Write: see guide.
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.
Before linking Rillet Customer to SuiteAnalytics Contact, check whether the customer is an individual or a company. Match the correct record type in each system.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Rillet
Documented record · Incremental: Yes; historical: Yes; delete detection: Yes
SuiteAnalytics
Documented record · Read: Supported. Write: see guide.
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.
Compare whether Rillet Invoice and SuiteAnalytics 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: Yes; historical: Yes; delete detection: Yes
SuiteAnalytics
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.
Compare whether Rillet Bill and SuiteAnalytics Vendor Bill describe the same supplier bill 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: Yes; historical: Yes; delete detection: Yes
SuiteAnalytics
Documented record · Supported
Record identity
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Field ownership
Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.
Fields to include
Source bill ID
Supplier reference
Entity
Line amounts and currency
Approval/posting state
Record dependencies
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Validation
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Recovery
Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.
Order-to-invoice handoff: SuiteAnalytics 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: Yes; historical: Yes; delete detection: Yes
SuiteAnalytics
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.
Compare whether Rillet Invoice Payment and SuiteAnalytics Customer Payment describe the same payment or settlement 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: Yes; historical: Yes; delete detection: Yes
SuiteAnalytics
Documented record · Supported
Record identity
Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents.
Field ownership
Keep payment authorization, settlement, and accounting allocation distinct.
Fields to include
Source transaction ID
Invoice references
Amount and currency
Settlement status
Reversal reference
Record dependencies
Resolve the affected invoices and cash/account references before allocating the payment.
Validation
Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.
Recovery
Look up the original transaction before retrying to prevent duplicate allocation or charging.
This pair can involve both record sync and process handoffs. Keep the Invoice / Sales Order relationship explicit: copying fields and creating a downstream business transaction require different validation.
Stacksync managed sync
Best fit
Source-to-destination updates for supported objects. Choose the records, writable fields, and permissions for your workflow.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Check record matching: 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. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
Best fit
A vendor-built integration may fit if it supports your Rillet and SuiteAnalytics record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify Customer / Customer, update direction, account tier, and related-record handling.
Custom API or workflow
Best fit
Consider explicit orchestration for the Invoice / Sales Order handoff.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
Best fit
Consider for a one-time Rillet / SuiteAnalytics migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Customer sync test
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Customer or Customer record needs a defined result in the other system.
Start with Rillet Customer and SuiteAnalytics Customer. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Customer sync test
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Customer or Contact record needs a defined result in the other system.
Start with Rillet Customer and SuiteAnalytics Contact. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Customer invoice sync test
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Invoice or Invoice record needs a defined result in the other system.
Start with Rillet Invoice and SuiteAnalytics Invoice. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Reconcile Rillet business records with SuiteAnalytics
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A finance-owned record in Rillet needs operational visibility through Customer or Vendor.
Select Customer or Vendor with the correct legal entity, period, and currency.
Define a reporting relationship in SuiteAnalytics; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Customer / Customer
Test case
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Expected result
The expected customer relationship is preserved with no duplicate action or unintended write.
Customer / Contact
Test case
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Expected result
The expected customer relationship is preserved with no duplicate action or unintended write.
Invoice / Invoice
Test case
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Expected result
The expected customer invoice relationship is preserved with no duplicate action or unintended write.
Bill / Vendor Bill
Test case
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Expected result
The expected supplier bill relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Verify read access in SuiteAnalytics and write access in Rillet. Test the permitted route without relying on a return sync.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated customer change
Investigate
Inspect Rillet Customer and SuiteAnalytics Customer, their IDs, and the destination error.
Next action
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Rejected or repeated customer change
Investigate
Inspect Rillet Customer and SuiteAnalytics Contact, their IDs, and the destination error.
Next action
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Rejected or repeated customer invoice change
Investigate
Inspect Rillet Invoice and SuiteAnalytics Invoice, their IDs, and the destination error.
Next action
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
A record type or update is unavailable
Investigate
Check the Rillet and SuiteAnalytics connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
How updates move between Rillet and SuiteAnalytics
See how each system detects changes and which updates the other system can receive.
Each direction has its own permissions and record requirements.
Rillet → SuiteAnalytics Direction not supported
Detect changesThis route requires read access from Rillet and write access to SuiteAnalytics; the documented connector restrictions do not permit it.
Apply updatesUse a supported direction or review a separate integration method for this requirement.
SuiteAnalytics → Rillet Timing depends on the connected systems
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesSelected writable fields update in Rillet. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Update timing and record limits
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
FAQ
Rillet and SuiteAnalytics integration FAQ
The documented direction is SuiteAnalytics to Rillet for supported objects. SuiteAnalytics is documented as a read-only connector, so it cannot receive write-back through this connector. Authorize both systems, map the selected fields, and validate the first load and later changes.
SuiteAnalytics is read-only through Stacksync. Two-way sync is not supported through these connectors; use a supported direction or review another implementation.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Customer in Rillet and Customer in SuiteAnalytics. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
This pair can involve both record sync and process handoffs. Keep the Invoice / Sales Order relationship explicit: copying fields and creating a downstream business transaction require different validation.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Generate an API key in Rillet Organization Setting > API Access. Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication. Use the pair worksheet to record ownership and acceptance criteria.
