AccountingModelConfig Metadata Type in SFDX

Architectural Overview#

The AccountingModelConfig metadata type defines the foundational rules for a Salesforce Accounting Subledger configuration. When enterprises bridge operational CRM workflows (such as donations, tuition billing, or order lifecycle management) with external Enterprise Resource Planning (ERP) general ledgers, AccountingModelConfig governs how and when Salesforce translates operational records into double-entry or single-entry accounting artifacts.

Architects use AccountingModelConfig to version-control critical financial boundaries: the earliest transaction date eligible for ledger generation, expected payment write-off states, cash versus accrual recognition behavior, and scheduled batch processing toggles.

Directory and File Conventions#

In SFDX source format, AccountingModelConfig files reside inside the accountingModelConfigs folder.

Key Metadata Fields#

The following XML elements control AccountingModelConfig behavior in API version 68.0:

Declarative XML and Package Manifest Examples#

The following example defines an accrual-based accounting model configuration with an explicit go-live cutoff date and automated job execution disabled for initial UAT validation:

<?xml version="1.0" encoding="UTF-8"?>
<AccountingModelConfig xmlns="http://soap.sforce.com/2006/04/metadata">
    <earliestStartDate>2026-01-01</earliestStartDate>
    <expectedPayDateField>CloseDate</expectedPayDateField>
    <financeBookName>Corporate_General_Ledger</financeBookName>
    <isActive>true</isActive>
    <masterLabel>Enterprise Accrual Model</masterLabel>
    <paidStageList>Closed Won,Committed</paidStageList>
    <runJobAutomatically>false</runJobAutomatically>
    <writeOffStage>Closed Lost</writeOffStage>
</AccountingModelConfig>

Package Manifest (package.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Enterprise_Accrual_Model</members>
        <name>AccountingModelConfig</name>
    </types>
    <version>68.0</version>
</Package>

SOQL Queries and CLI Automation#

Inspect configured accounting models using SOQL or manage them via Salesforce CLI:

SELECT Id, DeveloperName, MasterLabel, IsActive,
       EarliestStartDate, RunJobAutomatically, FinanceBookName
FROM AccountingModelConfig
ORDER BY IsActive DESC, DeveloperName ASC

# Retrieve all AccountingModelConfig definitions
sf project retrieve start --metadata "AccountingModelConfig:*"

# Deploy the Enterprise_Accrual_Model configuration
sf project deploy start --metadata AccountingModelConfig:Enterprise_Accrual_Model

Architect Best Practices and Gotchas#

• Sandbox Refresh Safety: Keep runJobAutomatically set to false in base sandbox branches or use environment-specific replacements so freshly refreshed Full Sandboxes do not immediately burn asynchronous Apex batch limits generating subledger rows.
• Stage Picklist Alignment: Values specified in paidStageList and writeOffStage must exactly match the API names of picklist values on your target transaction object. Mismatched stage names silently prevent ledger entry generation.
• Prerequisite Settings: The target org must have Accounting Subledger enabled via AccountingSettings and appropriate PSL (Permission Set License) entitlements before deploying AccountingModelConfig.

Frequently asked questions

What is the role of AccountingModelConfig in Salesforce Accounting Subledger?

AccountingModelConfig defines the top-level rules for generating accounting records, including whether the org uses a cash or accrual model, which record states trigger ledger creation, and whether the model is active.

Can multiple AccountingModelConfig definitions be active simultaneously?

Depending on your Accounting Subledger edition and license, you can configure multiple accounting models, but you must carefully partition entry criteria so the same transaction does not generate duplicate ledger entries.

What happens when you deactivate an AccountingModelConfig in production?

Deactivating an AccountingModelConfig stops the scheduled subledger job from processing new CRM records under that model, while leaving previously generated TransactionJournal and LedgerEntry records intact.

How does AccountingModelConfig relate to AccountingFieldMapping?

AccountingModelConfig acts as the parent configuration referenced by child AccountingFieldMapping components that define field-by-field data transfer from operational records to ledger records.