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.
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:
This makes it much easier to identify exactly which categories need attention and which clients are affected.
Once mapped, LedgerSync will be able to push transactions categorized under that rule into the correct QBO account going forward.
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.