--- title: "LogiSense connector: setup and compatibility | Stacksync" description: "LogiSense integration guide: plan Invoice and Payment, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/logisense last_modified: 2026-09-15 --- Accounting and finance · Two-way sync platform # LogiSense integration. Connect your LogiSense workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Invoice, Payment and Contact. - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Account** - **Contact** - **Package and Service** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=logisense) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## LogiSense records to discuss. These LogiSense record examples help scope a technical review. They are not a list of verified Stacksync operations. Account Identify this record type and the operation you need to review with Stacksync. Contact Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Package and Service Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Account Service Identify this record type and the operation you need to review with Stacksync. Usage Identify this record type and the operation you need to review with Stacksync. Invoice Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. Connection setup ## LogiSense connection requirements. Review LogiSense access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the LogiSense account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for LogiSense, including read/write support, authentication, and initial-load limits. [Open the LogiSense vendor API reference](https://api.logisense.com/) ### LogiSense API reference - [LogiSense vendor API documentation](https://api.logisense.com/) Integration design ## Match records and fields for your LogiSense integration. Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks LogiSense **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. Load related records in the right order Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting. ### Mapping checks by record type #### Invoice Confirm object support with Stacksync Identity Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. Fields to consider Source invoice ID · Customer or supplier reference · Line totals · Currency · Posting/payment status Related records to resolve first Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting. Test before going live Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency. #### Payment Confirm object support with Stacksync Identity Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents. Fields to consider Source transaction ID · Invoice references · Amount and currency · Settlement status · Reversal reference Related records to resolve first Resolve the affected invoices and cash/account references before allocating the payment. Test before going live Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction. #### Contact Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the LogiSense integration in four steps. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. ### View the four setup tests and expected results 1. ### Verify LogiSense credentials and resource scope After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object. **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner. 2. ### Test record matching for Invoice Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. 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:** Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. 3. ### Test the operation your workflow needs Review one LogiSense record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your LogiSense integration. ### Diagnose record matching, delayed changes, and rejected operations A LogiSense record appears under the wrong destination record Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected LogiSense implementation’s change-detection method for Invoice, Payment and Contact. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific LogiSense object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your LogiSense workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=logisense) ## LogiSense integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide Two-Way Sync Field Mapping Workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) FAQ ## LogiSense connector FAQ ### How should I plan an integration with LogiSense? Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the LogiSense connector write changes back? Write-back support is not established for this connection. Review the LogiSense records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for LogiSense data? Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. ### Which related records should I load first for LogiSense? Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting. ### How do I validate LogiSense changes after the initial load? Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. ### What will we cover in a LogiSense integration demo? Start with one workflow and a sample record from Invoice, Payment and Contact. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. ## Explore LogiSense connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [LogiSense and Sage 100](https://www.stacksync.com/integrations/logisense-and-sage-100) - [LogiSense and NetSuite](https://www.stacksync.com/integrations/logisense-and-netsuite) - [Active Directory and LogiSense](https://www.stacksync.com/integrations/active-directory-and-logisense) - [JumpCloud and LogiSense](https://www.stacksync.com/integrations/jumpcloud-and-logisense) - [LogiSense and Seismic](https://www.stacksync.com/integrations/logisense-and-seismic) - [LogiSense and Okta](https://www.stacksync.com/integrations/logisense-and-okta) - [Intercom and LogiSense](https://www.stacksync.com/integrations/intercom-and-logisense) - [Ironclad and LogiSense](https://www.stacksync.com/integrations/ironclad-and-logisense) ### CRM · 27 - [LogiSense and Affinity](https://www.stacksync.com/integrations/affinity-and-logisense) - [LogiSense and Attio](https://www.stacksync.com/integrations/attio-and-logisense) - [LogiSense and Chorusai](https://www.stacksync.com/integrations/chorusai-and-logisense) - [LogiSense and Close](https://www.stacksync.com/integrations/close-and-logisense) - [LogiSense and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-logisense) - [LogiSense and Freshsales](https://www.stacksync.com/integrations/freshsales-and-logisense) - [LogiSense and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-logisense) - [LogiSense and Gong](https://www.stacksync.com/integrations/gong-and-logisense) - [LogiSense and Gorgias](https://www.stacksync.com/integrations/gorgias-and-logisense) - [LogiSense and HubSpot](https://www.stacksync.com/integrations/hubspot-and-logisense) - [LogiSense and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-logisense) - [LogiSense and Insightly](https://www.stacksync.com/integrations/insightly-and-logisense) - [LogiSense and Intercom](https://www.stacksync.com/integrations/intercom-and-logisense) - [LogiSense and Kommo](https://www.stacksync.com/integrations/kommo-and-logisense) - [LogiSense and Outreach](https://www.stacksync.com/integrations/logisense-and-outreach) - [LogiSense and Pipedrive](https://www.stacksync.com/integrations/logisense-and-pipedrive) - [LogiSense and Salesforce](https://www.stacksync.com/integrations/logisense-and-salesforce) - [LogiSense and Salesloft](https://www.stacksync.com/integrations/logisense-and-salesloft) - [LogiSense and SAP Sales Cloud](https://www.stacksync.com/integrations/logisense-and-sap-sales-cloud) - [LogiSense and Seismic](https://www.stacksync.com/integrations/logisense-and-seismic) - [LogiSense and Shopify](https://www.stacksync.com/integrations/logisense-and-shopify) - [LogiSense and SugarCRM](https://www.stacksync.com/integrations/logisense-and-sugarcrm) - [LogiSense and Veeva CRM](https://www.stacksync.com/integrations/logisense-and-veeva-crm) - [LogiSense and Vtiger CRM](https://www.stacksync.com/integrations/logisense-and-vtiger-crm) - [LogiSense and Xactly](https://www.stacksync.com/integrations/logisense-and-xactly) - [LogiSense and Zoho CRM](https://www.stacksync.com/integrations/logisense-and-zoho-crm) - [LogiSense and Zoho SalesIQ](https://www.stacksync.com/integrations/logisense-and-zoho-salesiq) ### ERP · 24 - [LogiSense and Acumatica](https://www.stacksync.com/integrations/acumatica-and-logisense) - [LogiSense and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-logisense) - [LogiSense and Cin7](https://www.stacksync.com/integrations/cin7-and-logisense) - [LogiSense and Dynamics 365 Business Central](https://www.stacksync.com/integrations/logisense-and-microsoft-dynamics-365-business-central) - [LogiSense and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-logisense) - [LogiSense and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-logisense) - [LogiSense and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-logisense) - [LogiSense and Linnworks](https://www.stacksync.com/integrations/linnworks-and-logisense) - [LogiSense and Microsoft Dynamics GP](https://www.stacksync.com/integrations/logisense-and-microsoft-dynamics-gp) - [LogiSense and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/logisense-and-microsoft-dynamics-nav) - [LogiSense and NetSuite](https://www.stacksync.com/integrations/logisense-and-netsuite) - [LogiSense and Odoo](https://www.stacksync.com/integrations/logisense-and-odoo) - [LogiSense and Plex ERP](https://www.stacksync.com/integrations/logisense-and-plex-erp) - [LogiSense and QAD ERP](https://www.stacksync.com/integrations/logisense-and-qad-erp) - [LogiSense and Sage 100](https://www.stacksync.com/integrations/logisense-and-sage-100) - [LogiSense and Sage 300](https://www.stacksync.com/integrations/logisense-and-sage-300) - [LogiSense and Sage Intacct](https://www.stacksync.com/integrations/logisense-and-sage-intacct) - [LogiSense and Sage X3](https://www.stacksync.com/integrations/logisense-and-sage-x3) - [LogiSense and SAP](https://www.stacksync.com/integrations/logisense-and-sap) - [LogiSense and SAP Business ByDesign](https://www.stacksync.com/integrations/logisense-and-sap-business-bydesign) - [LogiSense and SAP Business One](https://www.stacksync.com/integrations/logisense-and-sap-business-one) - [LogiSense and SAP S/4HANA](https://www.stacksync.com/integrations/logisense-and-sap-s4hana) - [LogiSense and Syspro](https://www.stacksync.com/integrations/logisense-and-syspro) - [LogiSense and TikTok Shop](https://www.stacksync.com/integrations/logisense-and-tiktok) ### Database · 12 - [LogiSense and Airtable](https://www.stacksync.com/integrations/airtable-and-logisense) - [LogiSense and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-logisense) - [LogiSense and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-logisense) - [LogiSense and Firebase](https://www.stacksync.com/integrations/firebase-and-logisense) - [LogiSense and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-logisense) - [LogiSense and MongoDB](https://www.stacksync.com/integrations/logisense-and-mongodb) - [LogiSense and MySQL](https://www.stacksync.com/integrations/logisense-and-mysql) - [LogiSense and Neo4j](https://www.stacksync.com/integrations/logisense-and-neo4j) - [LogiSense and PostgreSQL](https://www.stacksync.com/integrations/logisense-and-postgresql) - [LogiSense and SAP HANA](https://www.stacksync.com/integrations/logisense-and-sap-hana) - [LogiSense and SQL Server](https://www.stacksync.com/integrations/logisense-and-sql-server) - [LogiSense and Supabase](https://www.stacksync.com/integrations/logisense-and-supabase) ### Data warehouse · 8 - [LogiSense and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-logisense) - [LogiSense and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-logisense) - [LogiSense and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-logisense) - [LogiSense and BigQuery](https://www.stacksync.com/integrations/bigquery-and-logisense) - [LogiSense and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-logisense) - [LogiSense and Databricks](https://www.stacksync.com/integrations/databricks-and-logisense) - [LogiSense and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-logisense) - [LogiSense and Snowflake](https://www.stacksync.com/integrations/logisense-and-snowflake) ### Business productivity · 29 - [LogiSense and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-logisense) - [LogiSense and Asana](https://www.stacksync.com/integrations/asana-and-logisense) - [LogiSense and Atlassian](https://www.stacksync.com/integrations/atlassian-and-logisense) - [LogiSense and Braze](https://www.stacksync.com/integrations/braze-and-logisense) - [LogiSense and Campfire](https://www.stacksync.com/integrations/campfire-and-logisense) - [LogiSense and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-logisense) - [LogiSense and Docusign](https://www.stacksync.com/integrations/docusign-and-logisense) - [LogiSense and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-logisense) - [LogiSense and Front](https://www.stacksync.com/integrations/front-and-logisense) - [LogiSense and Gainsight](https://www.stacksync.com/integrations/gainsight-and-logisense) - [LogiSense and GitHub](https://www.stacksync.com/integrations/github-and-logisense) - [LogiSense and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-logisense) - [LogiSense and Ironclad](https://www.stacksync.com/integrations/ironclad-and-logisense) - [LogiSense and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-logisense) - [LogiSense and Microsoft 365](https://www.stacksync.com/integrations/logisense-and-microsoft-365) - [LogiSense and Microsoft Dynamics 365](https://www.stacksync.com/integrations/logisense-and-microsoft-dynamics-365) - [LogiSense and Microsoft Teams](https://www.stacksync.com/integrations/logisense-and-microsoft-teams) - [LogiSense and Monday](https://www.stacksync.com/integrations/logisense-and-monday) - [LogiSense and Notion](https://www.stacksync.com/integrations/logisense-and-notion) - [LogiSense and Quip](https://www.stacksync.com/integrations/logisense-and-quip) - [LogiSense and SendGrid](https://www.stacksync.com/integrations/logisense-and-sendgrid) - [LogiSense and ServiceMax](https://www.stacksync.com/integrations/logisense-and-servicemax) - [LogiSense and ServiceNow](https://www.stacksync.com/integrations/logisense-and-servicenow) - [LogiSense and Slack](https://www.stacksync.com/integrations/logisense-and-slack) - [LogiSense and Smartsheet](https://www.stacksync.com/integrations/logisense-and-smartsheet) - [LogiSense and SysAid](https://www.stacksync.com/integrations/logisense-and-sysaid) - [LogiSense and Twilio](https://www.stacksync.com/integrations/logisense-and-twilio) - [LogiSense and Wrike](https://www.stacksync.com/integrations/logisense-and-wrike) - [LogiSense and Zendesk](https://www.stacksync.com/integrations/logisense-and-zendesk) ### Accounting and finance · 13 - [LogiSense and Adyen](https://www.stacksync.com/integrations/adyen-and-logisense) - [LogiSense and Anaplan](https://www.stacksync.com/integrations/anaplan-and-logisense) - [LogiSense and BILL](https://www.stacksync.com/integrations/bill-and-logisense) - [LogiSense and Braintree](https://www.stacksync.com/integrations/braintree-and-logisense) - [LogiSense and Chargebee](https://www.stacksync.com/integrations/chargebee-and-logisense) - [LogiSense and Coupa](https://www.stacksync.com/integrations/coupa-and-logisense) - [LogiSense and Navan](https://www.stacksync.com/integrations/logisense-and-navan) - [LogiSense and QuickBooks](https://www.stacksync.com/integrations/logisense-and-quickbooks) - [LogiSense and Ramp](https://www.stacksync.com/integrations/logisense-and-ramp) - [LogiSense and Recurly](https://www.stacksync.com/integrations/logisense-and-recurly) - [LogiSense and Stripe](https://www.stacksync.com/integrations/logisense-and-stripe) - [LogiSense and Workday](https://www.stacksync.com/integrations/logisense-and-workday) - [LogiSense and Zuora](https://www.stacksync.com/integrations/logisense-and-zuora) ### Analytics · 2 - [LogiSense and Pendo](https://www.stacksync.com/integrations/logisense-and-pendo) - [LogiSense and Splunk](https://www.stacksync.com/integrations/logisense-and-splunk) ### E-commerce · 6 - [LogiSense and Akeneo](https://www.stacksync.com/integrations/akeneo-and-logisense) - [LogiSense and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-logisense) - [LogiSense and EasyPost](https://www.stacksync.com/integrations/easypost-and-logisense) - [LogiSense and Magento](https://www.stacksync.com/integrations/logisense-and-magento) - [LogiSense and Shipwire](https://www.stacksync.com/integrations/logisense-and-shipwire) - [LogiSense and Shopware](https://www.stacksync.com/integrations/logisense-and-shopware) ### Human resources · 12 - [LogiSense and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-logisense) - [LogiSense and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-logisense) - [LogiSense and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-logisense) - [LogiSense and Hibob](https://www.stacksync.com/integrations/hibob-and-logisense) - [LogiSense and Jobvite](https://www.stacksync.com/integrations/jobvite-and-logisense) - [LogiSense and Lever](https://www.stacksync.com/integrations/lever-and-logisense) - [LogiSense and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/logisense-and-oracle-fusion-cloud-hcm) - [LogiSense and Paylocity](https://www.stacksync.com/integrations/logisense-and-paylocity) - [LogiSense and SmartRecruiters](https://www.stacksync.com/integrations/logisense-and-smartrecruiters) - [LogiSense and Success Factors](https://www.stacksync.com/integrations/logisense-and-success-factors) - [LogiSense and UKG Pro](https://www.stacksync.com/integrations/logisense-and-ukg-pro) - [LogiSense and UKG Ready](https://www.stacksync.com/integrations/logisense-and-ukg-ready) ### Marketing · 8 - [LogiSense and Bingads](https://www.stacksync.com/integrations/bingads-and-logisense) - [LogiSense and Cvent](https://www.stacksync.com/integrations/cvent-and-logisense) - [LogiSense and Demandbase](https://www.stacksync.com/integrations/demandbase-and-logisense) - [LogiSense and Eloqua](https://www.stacksync.com/integrations/eloqua-and-logisense) - [LogiSense and Iterable](https://www.stacksync.com/integrations/iterable-and-logisense) - [LogiSense and Marketo](https://www.stacksync.com/integrations/logisense-and-marketo) - [LogiSense and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/logisense-and-salesforce-marketing-cloud) - [LogiSense and Twitter Ads](https://www.stacksync.com/integrations/logisense-and-twitter-ads) ### Security and identity · 6 - [LogiSense and Active Directory](https://www.stacksync.com/integrations/active-directory-and-logisense) - [LogiSense and Auth0](https://www.stacksync.com/integrations/auth0-and-logisense) - [LogiSense and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-logisense) - [LogiSense and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-logisense) - [LogiSense and Okta](https://www.stacksync.com/integrations/logisense-and-okta) - [LogiSense and OneLogin](https://www.stacksync.com/integrations/logisense-and-onelogin) SECURITY ## Security teams trust Stacksync 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. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### 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. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)