> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/accounts/configuration/setup-journal-voucher-templates.md).

# Setup Journal Voucher Templates

Logic ERP has improved the **Script Editor**, the window where formulas are written. It opens from the **Add Formula** button of **Setup Journal Voucher Templates**, and it now also works on the web.

***

### **What's new**

* **On the web** - the editor opens full screen on a wide screen. **Hide fields** gives the whole width to the formula, and on a phone **Fields**, **Script** and **Results** switch between the parts.
* **Convert to VB.NET** - turns a formula written in VBScript or PowerShell into a **VB.NET** formula, so that it also works on the web and in the 64-bit version. The original is kept at the bottom as notes, and a division by zero gives 0 for that value.
* **Check & Fix** - finds the mistakes in a VB.NET formula, corrects the usual ones (a missing **End If** or **Then**, signs from other languages, a misspelt field name, a missing **Dim**) and lists the rest by line. It is also offered when **Script Watch** or **Save** finds a mistake.
* **Formulas are protected** - a VB.NET formula can no longer read or change records directly, use outside components or start another program. **Script Watch** and **Save** stop with **Not allowed in a formula** and show the lines concerned.
* **Layout kept** - the indentation and blank lines of a formula are kept when it is saved and opened again.
* **Examples** - a new page of ready-made VB.NET formulas, each tested, for anyone writing their first formulas.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/writing-formulas-in-the-script-editor.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/accounts/configuration/setup-journal-voucher-templates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
