Global Categories Not Mapped

Global Categories Not Mapped

Overview

For Global Rules to work correctly in LedgerSync, each Global Category must be mapped to the corresponding category in each client's QuickBooks Online (QBO) account. Without this mapping, LedgerSync has no way to know where to push transactions for that client — even if the rule itself is configured correctly.

For example, you may create a Global Category called Meals Expense in LedgerSync. But until that category is mapped to the equivalent QBO account category for each client, LedgerSync cannot push matching transactions into QBO for those clients.

What Happens When a Global Category Is Not Mapped

Previously, when a Global Category was missing its client mapping, the transaction would simply not categorize — and nothing in the interface indicated why. Users were left wondering why their rules weren't working, with no clear signal pointing to the unmapped category as the cause.

LedgerSync has now improved this experience. When a Global Category is missing its mapping for a client, LedgerSync will:

  • Display a suggested Global Category in red on the transaction
  • Signal clearly that the mapping needs to be completed before the rule can take effect

This makes it much easier to identify exactly which categories need attention and which clients are affected.


How to Fix an Unmapped Global Category

  1. Navigate to the Rules Engine in the top menu
  2. Select Global Rules
  3. Click on Global Categories
  4. Locate the category shown in red on the transaction (e.g., Meals Expense)
  5. Click into that category and map it to the correct QBO account category for each applicable client
  6. Save your changes

Once mapped, LedgerSync will be able to push transactions categorized under that rule into the correct QBO account going forward.

Tips

  • If you see a category suggestion highlighted in red on a transaction, treat it as an action item — it means the Global Category exists but hasn't been mapped for that client yet.
  • A Global Category must be mapped for each client individually. Mapping it for one client does not automatically apply it to others.
  • After completing the mapping, re-sync or wait for the next transaction pull to confirm the rule is now applying correctly.

Related Articles

  • Article 15: Benefits of the LedgerSync Rules Engine
  • Article 17: Working with Global Rules and Global Categories

Need Help?

If you're unsure which category to map or need assistance setting up your Global Categories, contact our support team at support@ledgersync.com or reach out to your LedgerSync workflow specialist.