The result tag is used to reference values across templates.

Define a result tag

If you want to reference a certain value or variable from reconciliation template A in another template, it can be done with the so-called result tags in Silverfin templating language (further on - STL).

{% result 'name' content %}

This is how a result is defined. The name can be freely chosen, but should be unique for that template A. The content is the value or variable you want to reference to.

Let’s say we have stored a calculation of taxes in register $1 and we want to put it into a result tag. The code can look like this:

{% result 'tax_calculation' $1 %}


Result tag in a loop

Result tag can be also used in a loop, to reference the value of each loop in the result. In that case the name of the result tag will be changed with each iteration.

To make sure the result tag is working correctly, remove the brackets around the name of the tag, i.e. {% result name content %}.

For more information, please see the case on our Community page.

Access a result value

If we make the assumption that the handle of template A is template_A (handles make each template unique, and we need it to tell STL what template we need to reference from), the code to retrieve the result value from template A, where our tax calculation is stored, would look like this:

{{ period.reconciliations.template_A.results.tax_calculation }}


  • Please note that the result tag cannot be used to reference to a variable that was made within the same template; result tags are only used to reference across different reconciliation templates.

  • Circular references should not be made. Circular references occur when template A calls a result value from template B, while template B references a result value from template A.

  • Please note that there is no need to make result tags for input-objects, since they are stored in the database. You can reference to them with {{ period.reconciliations.template_A.custom.some.variable }}. Besides that it is easier to code, it makes your code cleaner and leads to better results performance wise.