Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Record matching
Customer / Customers
Compare whether Rillet Customer and Sage Intacct Customers describe the same customer in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Sage Intacct
- Object support to establish
- 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 documentation
Record matching
Invoice / AR Invoices
Compare whether Rillet Invoice and Sage Intacct AR Invoices describe the same customer invoice in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Sage Intacct
- Object support to establish
- 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 documentation
Record matching
Bill / AP Bills
Compare whether Rillet Bill and Sage Intacct AP Bills describe the same supplier bill in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Sage Intacct
- Object support to establish
- 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.
References: Rillet: Bill documentation
Record matching
Invoice Payment / Payments
Compare whether Rillet Invoice Payment and Sage Intacct Payments describe the same payment or settlement in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Sage Intacct
- Object support to establish
- 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.
References: Rillet: Invoice Payment documentation
Record matching
Vendor / Vendors
Compare whether Rillet Vendor and Sage Intacct Vendors describe the same supplier or vendor in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Sage Intacct
- Object support to establish
- 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 documentation
Record matching
Journal Entry / Journal Entries
Compare whether Rillet Journal Entry and Sage Intacct Journal Entries describe the same journal or ledger entry in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Rillet
- Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
- Sage Intacct
- Object support to establish
- Record identity
- Retain journal ID and line IDs within the legal entity and accounting period.
- Field ownership
- The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row.
Fields to include
- Source journal ID
- Account references
- Debit/credit amounts
- Entity
- Accounting period
- Record dependencies
- Resolve chart-of-account, currency, entity, and dimension references before lines.
- Validation
- Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
- Recovery
- Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.
References: Rillet: Journal Entry documentation
