Can different entities use different charts of accounts?

On Ramp, each entity can maintain its own chart of accounts, and transactions automatically sync to the correct accounting system using the chart configured for that entity.

How different charts of accounts affect multi-entity accounting

When entities use different charts of accounts, transactions must be coded and reported within each entity’s unique ledger structure. This creates flexibility at the entity level but adds overhead during consolidation.

In practice, this means:

• Each entity maintains its own general ledger with distinct account codes and hierarchies
• Transactions are coded against the entity’s chart of accounts at the time of spend
• Consolidation requires mapping entity-level accounts to a standardized reporting structure
• Month-end close takes longer due to reconciliation and validation across entities

The more divergence between charts, the more manual effort is required to align reporting across the organization.

How Ramp supports entity-specific charts of accounts

Ramp is designed to support multi-entity organizations where each entity operates its own accounting system and chart of accounts.

Entity-level accounting setup

• Multiple entities in your Ramp account connect to a single ERP instance (NetSuite, Sage Intacct, Microsoft Dynamics, Workday, Oracle Fusion, or Universal CSV)
• Each Ramp entity maps to a corresponding entity or subsidiary within your ERP
• Each entity/subsidiary within your ERP can use its own chart of accounts and coding structure
• Entities can maintain separate approval policies, coding rules, and required fields in Ramp

Transaction-level enforcement

• Every card, bill, and reimbursement is assigned to a specific entity
• Transactions inherit the chart of accounts tied to that entity
• GL coding rules apply based on the entity rather than the organization as a whole

Accurate syncing and reconciliation

• Transactions sync to the correct accounting system using entity-specific account mappings
• Each entity can use its own bank account for bill payments, reimbursements, and statement payments
• Consolidated reporting can be viewed in Ramp while entity-level detail is preserved

When a transaction occurs, Ramp routes it to the assigned entity and applies that entity’s chart of accounts automatically during the accounting sync.

Best practices for managing different charts of accounts

To reduce consolidation friction when entities use different charts:

• Standardize where possible. Use a shared chart of accounts unless regulatory or operational needs require differences
• Document mapping logic. Maintain clear, consistent mappings from entity accounts to consolidated reporting accounts
• Default entity assignment. Assign entities at the card and vendor level to reduce manual coding
• Audit classification consistency. Regularly review how similar expenses are coded across entities
• Plan close timelines accordingly. Account for additional reconciliation time during month-end and quarter-end close