SnelStart Advanced Ledger Mapping for Magento 2

The standard ledger configuration maps ledgers by tax rate category (Hoog, Laag, etc.). Advanced Ledger Mapping lets you override this with rules based on line item type, tax rule, and country — giving you fine-grained control over which ledger account is used per invoice line.

Use cases:

• Different types of sales (e.g., shipping to Germany vs. products to Belgium) need different ledger accounts, even when they share the same tax rate
• Payment fees (iDEAL, Klarna, credit card surcharges) need to be booked to a separate ledger from regular product sales

Location: Stores → Configuration → Accounting → SnelStart → Advanced Settings → Advanced Ledgers

Prerequisites

Before configuring advanced ledger mapping:

1. Ledgers synced — Click "Sync Ledger & Costs from SnelStart" in the Ledger Accounts section
2. Tax Rate Mapping configured — See the Tax Rate Mapping documentation
3. Standard ledgers configured — Advanced mapping overrides standard mapping, but falls back to it when no rule matches

Enable Advanced Ledger Mapping

1. Go to Stores → Configuration → Accounting → SnelStart → Advanced Settings
2. Set Enable Advanced Ledger Mapping to Yes
3. The mapping table appears below

Mapping Table

Each row in the mapping table is a rule. When an invoice or credit memo is synced, the module checks each rule against every line item.

Wildcard Behavior

Type Values

How Matching Works

The module processes rules top to bottom. The first matching rule wins.

For each invoice/credit memo line item:

1. Check if Advanced Ledger Mapping is enabled
2. Loop through mapping rules in order
3. A rule matches when all non-empty columns match the line item
4. First match → use that ledger, stop checking
5. No match → fall back to standard tax-rate ledger mapping

Important: Rule order matters. Place more specific rules above general ones.

Examples

Example 1: Separate shipping ledger for German orders

Example 2: Different product ledgers by country

Example 3: Payment fees on a separate ledger

Example 4: Catch-all with specific overrides

Applying Changes to Existing Invoices

After updating your advanced ledger mapping rules, existing invoices in the queue are not automatically recalculated. You need to trigger a recalculation so the module re-evaluates which ledger each line item belongs to.

Steps

When to use Recalculate

Important notes

Relationship to Standard Ledger Configuration

When determining the ledger account for an invoice line item, the module checks the following sources in order of priority:

The first source that returns a result is used. If advanced mapping finds no match, the system automatically falls back to the next step.

Troubleshooting

Rule not matching as expected

Ledger not available in dropdown

Changes not reflected in SnelStart

Need More Help?

Documentation:

• All Help Articles - Complete documentation overview

Support:

• Contact Support - Get help from our team