Using the Magento 2 SnelStart CLI Command for Debugging and Validation

Using the Magento 2 SnelStart CLI Command for Debugging and Validation

Setting up the SnelStart accounting module in Magento 2 can be complex, especially when dealing with One-Stop-Shopping, various ledgers, and tax rules. Synchronization between Magento and SnelStart may encounter issues due to API limitations, incorrect configurations, or missing data.

A useful debugging method is to manually create a boeking (transaction) in SnelStart and then use the CLI command to retrieve and validate how it was processed by the SnelStart API.

Why Use This Command?

The accounting:check:snelstart command helps merchants and developers to:

• Retrieve and inspect a boeking from SnelStart.
• Verify that the correct grootboekrekening (ledger account) is assigned.
• Ensure transaction details such as factuurnummer (invoice number) and amounts are correct.
• Identify synchronization issues between Magento and SnelStart.

By using this command, you can compare expected vs. actual data, allowing for quick troubleshooting and adjustments.

How to Use the CLI Command

1. Getting the Boeking ID

Each boeking in SnelStart has a unique UUID available via the API. If you do not have this ID,
use the --top and --skip parameters to browse transactions.

Example: Fetch the Latest Boekingen

bin/magento accounting:check:snelstart --top=5

This retrieves the 5 most recent transactions, including their UUIDs. Use the ID with the --id parameter to get full details.

Example: Fetch the Next Set of Boekingen

bin/magento accounting:check:snelstart --top=5 --skip=5

Use --skip to offset results and retrieve the next batch.

Where to Find the Boeking UUID

The boeking UUID appears in the verkoopBoeking field:

"verkoopBoeking": {
    "id": "eb44fcaa-e160-4be7-aa92-7d6e298b5b30",
    "uri": "/verkoopboekingen/eb44fcaa-e160-4be7-aa92-7d6e298b5b30"
}

Fetching Details for a Specific Boeking

bin/magento accounting:check:snelstart --id=eb44fcaa-e160-4be7-aa92-7d6e298b5b30

Example Output

{
    "factuurdatum": "2022-07-28T00:00:00",
    "factuurnummer": "C000000061",
    "boekingsregels": [
        {
            "omschrijving": "Rival Field Messenger",
            "grootboek": {
                "id": "4cbe5132-377f-43a5-86da-6289e75ae93a",
                "uri": "/grootboeken/4cbe5132-377f-43a5-86da-6289e75ae93a",
                "name": "[8000] - Omzet hoog (productiegoederen)"
            },
            "bedrag": -47.9,
            "btwSoort": "Hoog"
        },
        {
            "omschrijving": "Mollie Payment Fee",
            "grootboek": {
                "id": "217b3143-603e-4883-bcb2-179308ef7d4a",
                "uri": "/grootboeken/217b3143-603e-4883-bcb2-179308ef7d4a",
                "name": "[8040] - Omzet nultarief (productiegoederen)"
            },
            "bedrag": -0.99,
            "btwSoort": "Geen"
        }
    ]
}

This output confirms that the transaction was successfully added and shows which grootboekrekening (ledger account) was assigned. Use these results to configure ledger mappings in Magento.

Retrieving the Correct Boeking ID

Follow these steps:

1. Run bin/magento accounting:check:snelstart --top=5 to fetch recent transactions.
2. Find the verkoopBoeking field in the response.
3. Copy the id and use it with --id.

Final Thoughts

The accounting:check:snelstart CLI command is a powerful tool for validating SnelStart transactions, debugging ledger assignments, and troubleshooting sync issues.

By manually creating a transaction in SnelStart and fetching it via this command, you can quickly diagnose and resolve configuration errors to ensure accurate financial records in Magento.