exc Help: GL Account Mapping

• GL Account Mapping

  Each Expense must be mapped to a GL Account when posting. This can be done using the Expensify ‘Category’ or the Expensify ‘Category GL Code’ by changing the ‘GL Account Mapping’ in the ‘Policy’ setup in the Connector.

  • Map Category to GL Account
    The ‘Category’ in Expensify must exactly match the name of the GL Account in Accounting Seed.
  • Map Category GL Code to GL Account
    The ‘Category GL Code’ in Expensify must exactly match the name of the GL Account in Accounting Seed. This enables you to make the Category names more user friendly.
  • Map Category GL Code to GL Account UID
    The ‘Category GL Code’ in Expensify must exactly match the ‘Expensify UID’ field in the GL Account in Accounting Seed. This means you can tweak the names without breaking the mapping.
  • Map Category to GL Account UID
    The ‘Category’ in Expensify must exactly match the ‘Expensify UID’ field in the GL Account in Accounting Seed. This means you can have ‘user friendly’ Category names, but still map to GL Account. Category GL Codes are only available in Expensify with a ‘Control’ Policy, so this may help you save money!
  • Map Category GL Code to GL Account Id
    The ‘Category GL Code’ in Expensify must exactly match the Salesforce ID for the GL Account in Accounting Seed. This means you can tweak the names without breaking the mapping, but will break if you try to use it in a sandbox.

  (NB: Category GL Codes are only available with the ‘Control’ Policy Type)

<– Return to Expensify Connector Help