# Report code 163 (jaarrekening)

**URL:** <https://community.silverfin.com/t/report-code-163-jaarrekening/1845>\
**Category:** Insights\
**Created:** [July 14, 2020, 9:35am UTC](https://community.silverfin.com/t/report-code-163-jaarrekening/1845 "2020-07-14T09:35:04Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![sven](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/sven/32/1495_2.png) [@sven](https://community.silverfin.com/u/sven)\
**Post date:** [July 14, 2020, 12:23pm UTC](https://community.silverfin.com/t/report-code-163-jaarrekening/1845/6 "2020-07-14T12:23:47Z")

</div>

Ah, I see… But that’s a result tag probably not linked to that specific code (but I see the confusion).

You know, if you really want to call upon result tags from a paid package (like the Annual Accounts), you can always use the **debugmode** , as explained here:

> [@CASE: use debug mode](https://community.silverfin.com/t/case-use-debug-mode/1591):
>
> On company level, you can use the debug mode for any account or reconciliation template. This is greatly beneficial in order to have more detailled info on what a template is doing, without having to dive into the code without seeing the output (on firm level, you’ll never see that). How to activate? When you are on company level within the page that show the output of the template (account or reconciliation, so when you are viewing the details of those), simply add ?debug=1 at the end of the …

This will give you all result tags with their outcome. But I’m guessing that what you needed is the result tag called `vol_163`, no?

However, in case of the Annual Accounts: these codes are mostly linked to ranges anyway, so you can rebuilt it as a formula also.

Hope this helps you forward @sylvia.debaeremaeker

---

_[View the full topic](https://community.silverfin.com/t/report-code-163-jaarrekening/1845)._