How to Manage GL Transaction Config

Last reviewed: June 9, 2026

llms-full.txt
On this page

Use this workflow to change the account mapped to an existing GL transaction configuration row.

When to use this workflow

Use this workflow only when accounting has approved a change to the account used by a configured automated transaction type.

Do not use this workflow to correct a single historical transaction. Changing GL Transaction Config affects future automated postings that use the mapping.

Before you start

You need:

  • admin or executive access.
  • The transaction type and debit/credit side to change.
  • The approved replacement account.
  • Confirmation that the replacement account exists in the chart of accounts.

Screen path

Dashboard > System Settings > Accounting > GL Transaction Config

Steps

  1. Open System Settings.
  2. In Accounting, select GL Transaction Config.
  3. Find the row by Transaction Type and Debit/Credit.
  4. Confirm the row description matches the posting behavior you intend to change.
  5. Select Edit.
  6. Select the replacement account from the Account dropdown.
  7. Select Save.
  8. Review the row and confirm the account number and description are correct.

What happens behind the scenes

PAX sends the selected account number to the GL transaction config endpoint. The backend verifies that the account exists, then updates the config row.

Automated posting functions that reference the transaction name can use the new account for future journal entries.

PAX does not recalculate or move journal entries that were already created. Use the appropriate finance correction workflow if a historical posting needs correction.

Troubleshooting

Save fails after selecting an account

Likely cause: The account does not exist, the account was not submitted correctly, or permissions blocked the update.

Safe fix: Confirm the account exists in Chart of Accounts and retry as an admin or executive.

Contact support if: The account exists and the save still fails.

The transaction type is inactive

Likely cause: The configuration row is retained but marked inactive.

Safe fix: Do not assume an inactive row controls current posting. Confirm with accounting or support before changing it.

Contact support if: A posting workflow appears to depend on an inactive row.

I need a new transaction type

Likely cause: This screen edits existing rows only.

Safe fix: Do not add a workaround row from the UI. A new transaction type requires coordinated database and posting-function work.

Contact support if: A new automated posting behavior is needed.

Was this page helpful?

Vote *