FSM Journal Entry Model Reference
This reference is intended for administrators and developers who work with Journal Entry model mappings and defaults.
This Journal Entry model represents journalentry and uses Transaction behavior with its own body and lines map. The line map includes entity, account, Asset, Task, credit, debit, and memo, with department, class, and location when their features are enabled. Subsidiary is conditional. There is no additional Journal default object beyond inherited empty model defaults.
Standard default structure (JSON fragment):
{
"models/journal": {
"prototype": {
"record": "journalentry",
"map": {
"id": "*internalid",
"type": "recordtype",
"date": "trandate",
"lines": [
{
"entity": "entity|line.entity",
"account": "account|line.account",
"asset": "custcol_nx_asset|line.custcol_nx_asset",
"task": "custcol_nx_task|line.custcol_nx_task",
"credit": "creditamount|line.credit",
"debit": "debitamount|line.debit",
"memo": "memo|line.memo"
}
]
},
"defaults": {},
"syncentity": false,
"inventory": false
}
}
}
For the meaning of the inherited syncentity and inventory properties and guidance on changing these properties, see Transaction Mappings and Processing Properties.
The prototype.map.subsidiary mapping is "subsidiary" when Subsidiaries is enabled. Line mappings for department, class, and location are added when their respective features are enabled. These conditional entries are omitted from the fragment.
Use prototype.defaults.customform to supply the form for journal entries created through this model. For information about this setting, see Custom Forms for Record Creation. For accounting controls used by labor recovery, see Configuring FSM Project Labor Cost Posting. Changing Journal line mappings can alter accounting entries and Task or Asset attribution. Use the accounting feature and record topics for the resulting journal and costing relationships.