GL Transaction Config maps automated PAX transaction types to chart of accounts numbers.
What this screen is for
Use GL Transaction Config when an automated posting configuration needs to point to a different GL account.
This screen is not for manual journal entries. Use Journal Entries Overview for manual entries.
Only admin and executive users see this setting in System Settings.
Screen path
Dashboard > System Settings > Accounting > GL Transaction Config
Key areas
| Area | What it shows |
|---|---|
Active Configurations |
Active debit and credit mapping rows used by automated transaction posting. |
Inactive Configurations |
Inactive mapping rows retained for reference. |
| Row columns | Config ID, Transaction Type, Description, Debit/Credit, Account, and Actions. |
Each automated transaction type normally has one debit row and one credit row. The row tells PAX which account to use for that side of the posting.
Main actions
Edit: Opens the account selector for one configuration row.Save: Saves the selected account number for that row.Cancel: Leaves edit mode without saving.
This screen edits account mappings only. It does not create new transaction types, edit transaction names, or activate/deactivate rows.
What happens behind the scenes
PAX loads GL transaction configuration rows and the active chart of accounts.
When a row is saved, PAX verifies the selected account exists in the chart of accounts, then updates the row's account number and timestamp.
Automated posting logic can read gl_transaction_config to decide which debit and credit accounts to use. Changing a mapping affects future automated postings that use that transaction name. It does not rewrite historical journal entries that have already posted.
Troubleshooting
Invalid account number
Likely cause: The selected or submitted account number does not exist in the chart of accounts.
Safe fix: Add or reactivate the account in Chart of Accounts Settings Overview, then edit the GL config row again.
Contact support if: The account exists but the GL config save still fails.
I do not know which account to choose
Likely cause: GL transaction mappings control automated accounting behavior.
Safe fix: Pause and confirm the mapping with accounting leadership before saving.
Contact support if: The correct mapping is unclear or the transaction type is not documented internally.
A transaction posted to the old account
Likely cause: The transaction may have posted before the mapping changed.
Safe fix: Review the journal entry date and reference. Do not manually alter historical entries without using the approved correction workflow.
Contact support if: A transaction posted after the mapping change but still used the old account.