Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Developer Resources
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model context protocol)

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Invoices, Credit Notes and Quotes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Managing payments with ChargebeeJS
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Order Management
  • Mobile Subscriptions (Legacy)
  • Other Integrations
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Integrations
  3. Articles and FAQ
  4. Sage Intacct
  1. Billing
  2. Integrations
  3. Articles and FAQ
  4. Sage Intacct

Intacct customer ID character limit

Problem Statement

You need to know whether long Chargebee customer IDs are truncated when syncing to Intacct and how to keep the full ID in Intacct.

Solution

By default, the Chargebee–Intacct integration syncs only the first 17 characters of the Chargebee customer ID to Intacct. If the ID is longer (e.g. Hr5511rRKlNuLS1T2O), Intacct will store Hr5511rRKlNuLS1T2. Intacct allows up to 20 characters, but we use 17 so the last 3 can be used for suffixes (e.g. _2, _3) when the same ID already exists in Intacct and we need to avoid duplicates.

To keep the full customer ID in Intacct, Chargebee can map the Chargebee customer ID to a custom field in Intacct (no 17-character limit there). Contact support to set this up.

Steps to Set It Up

  1. In Intacct, create a custom field for Customers of type String/Text.
  2. Get the destinationFieldID of that custom field from Intacct.
  3. Send the destinationFieldID to support. Chargebee will map the Chargebee customer ID to this custom field so the full ID is synced.

Related Articles

Multiple base currency support in Intacct Integration
What is Sage intacct integration?
How to change sync rules in Intacct integration?

Was this article helpful?