Configuring Multi-Vendor Allocations by Province

Overview

Organizations operating payroll across multiple Canadian provinces often require separate Workers’ Compensation liability tracking by jurisdiction.

This new functionality introduces Multi-Vendor Allocation support that allows Workers’ Compensation liabilities to automatically post to different payroll vendors and balance sheet accounts based on the employee’s payroll province.

This enhancement is especially useful for organizations using separate provincial authorities such as:

• WCB Alberta
• WorkSafeBC
• WSIB Ontario
• CNESST Quebec

If a province-specific vendor mapping exists, the system will use the liability account configured on the payroll vendor. Otherwise, the default liability mapping configured on the Pay Component Subtype will continue to apply.

This helps simplify remittance processing, improve liability reconciliation, and reduce manual journal adjustments for multi-jurisdiction payroll environments.

📊 How Multi-Vendor Posting Logic Works

During payroll processing, the system evaluates the employee’s payroll province and splits the journal entry into distinct debit and credit behaviors:

The Rule of Precedence

When multi-vendor allocations are active, the system enforces a strict hierarchy for liability postings:

• Vendor Override takes Priority: The vendor balance sheet mapping takes absolute precedence over any balance sheet allocations configured through expense grouping or general Pay Component Subtype overrides.

• Fallback Behavior: “If no province-specific vendor mapping exists, the system will continue using the default balance sheet account configured on the Pay Component Subtype.

This strict precedence ensures that no matter how complex your organizational expense groupings are, your statutory provincial liabilities remain perfectly separated by jurisdiction.

🛠️ Step-by-Step Configuration Guide

Follow these three steps to configure multi-vendor routing for your organization:

Step 1: Create and Configure Your Provincial Payroll Vendors

You must first establish your distinct provincial authorities as payroll entities:

1. Create a separate vendor record for each authority required (e.g., WCB Alberta, WorkSafeBC, WSIB Ontario, CNESST Quebec). If you need assistance with the foundational step, please review our guide on How to Create a Vendor Record

2. Within the vendor record, enable the option indicating that this is a Payroll Vendor.

3. Assign the specific Balance Sheet Account where that province's liabilities should post. This account will automatically be used during payroll posting when an employee belongs to the corresponding province.

Step 2: Configure Your Default Fallback Mapping

Ensure your core setup has a baseline account in case a province isn't mapped:

1. Navigate to: Payroll Administration > Payroll Setup > Pay Component Subtypes.

2. Open the applicable Pay Component Subtype (such as Workers’ Compensation).

3. Map your standard GL accounts:

   • Expense Account (P&L): Captures the debit side of the calculation.

   • Balance Sheet Account: Captures the credit side to act as the default fallback liability account.

💡 Viewing Tip: To see the details clearly, click directly on the video to expand it, or right-click and select "Open link in new window" to watch it in full size side-by-side.

Step 3: Map Provinces to Their Vendors

Link your jurisdictions to the vendors you created in Step 1:

1. In the same Pay Component Subtype record, open the CA Config section.

1. Add a row for each operating province/jurisdiction.

2. Assign the corresponding payroll vendor to each province (e.g., Alberta → WCB Alberta, British Columbia → WorkSafeBC).

3. Save your changes.

📖 Real-World Example (WCB Use Case)

Here is how the system automatically handles a transaction for an employee based on this multi-vendor framework:

• The Scenario: An organization processes payroll for an employee whose payroll province is Alberta.

• The Backend Mapping: The Workers' Compensation PCST is mapped to the Workers’ Compensation Expense account. Under the CA Config section, the Alberta jurisdiction is mapped to the WCB Alberta vendor —which is tied to its own WCB Alberta Payable liability account.

• The Overriding Logic: Because a province-specific vendor mapping exists, the system completely ignores the default balance sheet account configured on the PCST. The credit entry is entirely driven by the vendor's profile.

• The Resulting GL Impact: The general ledger automatically processes the entry without any manual intervention, bypassing the PCST liability line entirely:

  • Debit (P&L): Workers’ Compensation Expense

  • Credit (Balance Sheet): WCB Alberta Payable (Pulled directly from the Vendor, ignoring the PCST fallback) 

🔍 Quick Troubleshooting Checklist

If your payroll liabilities are still routing to your generic fallback account or an incorrect account, verify these four settings:

• [ ] Employee Profile: Is the employee's profile assigned to the correct payroll province?

• [ ] CA Config Mapping: Is the province-to-vendor relationship explicitly filled out in the Pay Component Subtype's CA Config section?

• [ ] Vendor Flag: Is the assigned vendor record actually marked as a Payroll Vendor?

• [ ] Vendor GL Account: Is there a valid, active Balance Sheet Account populated on the vendor record itself?

💡 Beyond WCB: Additional Use Cases

The power of this release lies in its adaptability. While tracking provincial Workers' Compensation is the most common use case, this identical multi-vendor configuration framework can be applied across any Pay Component Subtype that requires vendor-specific liability allocations.

Professional Services teams and system administrators can use this exact same framework to support:

• Different Workers’ Compensation structures by province.

• Separate liability mappings by jurisdiction for other provincial deductions or taxes.

• Province-specific payroll reporting requirements.

This framework provides ultimate flexibility, ensuring cleaner liability segregation and significantly reducing manual journal reclassification requirements for your accounting teams.