GL Matching Dashboard Management

The GL Matching Dashboard enables you to search for matchable transaction lines using various search filters. The transaction lines in the Search Results list can then be viewed, edited, matched, or unmatched. When you complete a match, the SuiteApp assigns a matching code and matching status depending on the total balance of the group: Matched or Partially Matched.

To access the GL Matching Dashboard, go to Transactions > Financial > GL Matching Dashboard (Administrator). For non-Administrator roles, such as Accountant, Bookkeeper, among other roles that use the Accounting Center, go to Financial > Other Transactions > GL Matching Dashboard.

To use the GL Matching Dashboard, read the following topics:

GL Matching Terminology

The following terms are used when referring to GL Matching:

  • Group – Refers to a group of transaction lines that the SuiteApp has matched and assigned a matching code.

  • Transaction Lines – Refers to the lines of transactions that constitute one transaction record. Each transaction line has a debit or credit value. The GL Matching SuiteApp matches transaction lines, not transactions as a whole.

  • Matching Status – Refers to the state of the matching process:

    • None – These transaction lines have not yet been matched. That means, no matching code has been assigned to them yet.

    • Matched – These transaction lines are already a part of a group. In every such group, the sum of the credit entries is equal to the sum of the debit entries. Each group has an assigned matching code.

    • Partially Matched – These transaction lines have already been added to a group and assigned a matching code. However, this group is not yet complete. This means, that the sum of the credit entries in it is not equal to the sum of the debit entries. Additional transaction lines have to be added to achieve a zero balance.

  • Matching Code – A string of letters unique for every combination of account, subsidiary, and accounting book that is assigned to a Matched or Partially Matched group.

  • Match – Refers to the action of reconciling or evaluating the debit and credit values of transaction lines, thus forming a group with a matching code.

  • Unmatch – Refers to the action of undoing a group. The SuiteApp removes the matching code and matching status.

  • Unmatched Debit/Unmatched Credit – Refer to debit and credit amounts that have not yet been reconciled.

Matchable Transactions

The GL Matching SuiteApp can match the following transaction types:

  • Advanced Intercompany Journal

  • Intercompany Journal

  • Assembly Build

  • Assembly Unbuild

  • Cash Refund

  • Cash Sale

  • Check

  • Credit Card Charge

  • Credit Card Refund

  • Credit Memo

  • Customer Deposit

  • Customer Refund

  • Currency Revaluation

  • Deposit

  • Deposit Application

  • Expense Report

  • Finance Charge

  • GL Impact Adjustment

  • Inventory Adjustment

  • Inventory Cost Revaluation

  • Inventory Transfer

  • Invoice

  • Item Fulfillment

  • Item Receipt

  • Journal

  • Book Specific Journal

  • Payment

  • Tax Liability

  • Vendor Bill

  • Vendor Credit

  • Work Order Close

  • Work Order Completion

  • Work Order Issue

  • Store Pickup Fulfillment

Note:

The GL Matching SuiteApp does not match transactions as a whole. It matches transaction lines. Every transaction consists of multiple transaction lines. The GL Matching Dashboard will display each of these lines as a separate search result and you can match different lines from the same transaction separately.

Including Custom Transactions in GL Matching

The GL Matching SuiteApp also supports the matching of custom transactions. To learn more about the custom transactions in NetSuite, see the help topic Custom Transactions.

To make a custom transaction matchable:

  1. Go to Customization > Scripting > Scripts.

  2. Next to the GLM - UE - Custom Transaction script, click Edit.

  3. On the Scripts page, click the Deployments subtab.

  4. From the list in the Applies To column, select your custom transaction, and then click Add.

  5. Click Save. Your custom transaction now appears in the Applies To column.

  6. Click the custom transaction. The Script Deployment page appears.

  7. Set the Audience for your custom transaction to All roles.

    Important:

    If you limit the Audience to certain roles only, it might lead to inconsistencies in matching data.

  8. Set the Status of your custom transaction to Released.

  9. Click Save.

Note:

It usually takes up to 10 minutes for your newly added custom transaction to appear in the Transaction Types list of the GL Matching Dashboard.

Including Accounts in GL Matching

By default, the Accounts filter on the GL Matching Dashboard contains only Accounts Receivables (A/R) and Accounts Payables (A/P) account types. GL Matching is primarily used for the reconciliation of these account types as a requirement for a complete and orderly accounting. For this reason, too, it is not possible to exclude A/P and A/R accounts from GL Matching.

If you want to match other account types besides A/P and A/R, you can choose to include them in the Accounts filter on the GL Matching Dashboard.

To include an account in GL Matching:

  1. Go to Setup > Accounting > Manage G/L > Chart of Accounts.

  2. Click Edit next to the Account name that you want to include in GL Matching.

  3. Check the Include in GL Matching box on the right side of the page.

  4. Click Save.

You can toggle to exclude or include an account in GL Matching by clearing or checking the Include in GL Matching box.

Note:

You cannot include the Non-Posting account type in GL Matching. The Include in GL Matching box is also disabled for A/P and A/R accounts because they are included in GL Matching by default.

Related Topics

General Notices