Case: Configuration categories professional expenses 2.0 (Beroepskosten 2.0)

Silverfin provides 5 standard cost categories in the template Professional expenses 2.0

14

It’s fairly easy to provide new categories to this template. This is possible at office level by clicking template and choosing professional expenses 2.0. There you will find following configuration screen.

41

When entering following code

{% assign cost_categories_string = "Expense 1|Expense 2|Expense 3" %}

en press save we get following result:
52

This way you can enter your own categories. There’s no limit on the amount of categories you can add.

Attention: It’s important that the variabele is called cost_categories_string and that the categories are divided by a pipe |

we have followed the instructions regarding the professional expenses 2.0.
We don’t see the changes. Do we have to wait 24h before we see the changes?
thank you.

Hi Kelly

This should work right away.
Can you show me the variable you have made?
Maybe there’s a tiny error in it.

Kind regards
Sam

sam,

hereby I provide you with a detail of the changes we have made.

{% assign cost_categories_string = “BEHEERSKOSTEN”|BUREELKOSTEN|BEDRIJFSLOKALEN|KOSTEN VOERTUIGEN|VERZEKERINGEN|DIVERSE KOSTEN" %}

I only see BEHEERSKOSTEN in detail. I cannot find the other categories.

thank you

You put a quote too many just after BEHEERSKOSTEN.

Following code will solve it:

{% assign cost_categories_string = “BEHEERSKOSTEN|BUREELKOSTEN|BEDRIJFSLOKALEN|KOSTEN VOERTUIGEN|VERZEKERINGEN|DIVERSE KOSTEN" %}

Kind regards
Sam

ok that problem is solved.
the following is that We can not see the accounts in the sheet of professional expenses.
do you need a print screen?
we want to fill in the sheet of the professional expenses but we don’t see the accounts that belong to the different groups.
thank you

Hi Kelly

This seems to be a bug. Thanks for detecting and reporting it
We’ll try to fix it as soon as possible and let you know when it is fixed.

Kind regards
Sam

@Vanbriel

The issue should be fixed

Kind regards

We have a configuration in our template Professional expenses. With the activation of the silverfin assistant however, our custom categories are overruled by the default from the Auto Config.

How could we adapt our configuration? Would including our custom categories in a simple “if activate_sf-mapping” statement be sufficient?

Thanks for the help!

For our current configuration see below:


{% assign cost_categories_string = "Diensten en diverse goederen|Loonkosten|Afschrijvingen en waardeverminderingen|Diverse bedrijfskosten|Financiële kosten|Uitzonderlijke kosten|Belastingen" %}
{% assign cost_keys_string = "diensten|loonkosten|afschrijvingen|diversekosten|finkosten|uitzonderlijk|belastingen" %}
{% assign diensten_default = "610,611,612,613,614,615,616" %}
{% assign loonkosten_default = "62" %}
{% assign afschrijvingen_default = "63" %}
{% assign diversekosten_default = "64" %}
{% assign finkosten_default = "65" %}
{% assign uitzonderlijk_default = "66" %}
{% assign belastingen_default = "67" %}

{% assign activation_fiscal_year_sf_mapping = 2023 %}

Hi Jasper.

Thank you for your patience.

Unfortunately it is currently not possible to overrule the categories that are defined by the auto config.

This means that for periods where the auto configuration is applicable, the categories which were defined by the auto config can’t be altered.

The periods before the moment where auto configuration was made available should still be configured as in your example below.

Kind regards

Hi Robbe,

Thank you for the response.

Could you expand on the consequences if we change the period where the auto configuration is applied?
Does this impact the working of the silverfin assistant and the checks linked to the auto configuration?

Kind regards
Jasper

Hi Jasper

If you would change the period as from when the sf mapping is active. It means that this template will work in the same way as it did before. With the old configuration active.

It will indeed have some impact on the checks and the assistent. Because this is then again taking the previous way of how the template works into account.

Kind regards
Robbe