> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/changelog/october-2024/4th-october.md).

# 2024-10-04

## Systems

### :screwdriver: New

<table><thead><tr><th width="339">System</th><th>Functionality</th></tr></thead><tbody><tr><td>Fortnox</td><td>Post Journal Attachment</td></tr><tr><td>Visma e-conomic</td><td>Trial Balances</td></tr></tbody></table>

### :wrench: Improved

| System         | Functionality                                                                                 |
| -------------- | --------------------------------------------------------------------------------------------- |
| Billy          | Can now see invoice isSent status                                                             |
| Procountor     | Can now see invoice isSent status                                                             |
| Visma Netvisor | Can now see invoice isSent status                                                             |
| File.1         | Ability to filter invoices by created/last modified date                                      |
| All Systems    | Standardize invoice amount to be always positive for invoices and negative for credit invoice |
| All Systems    | Account Balances with no results now returns an empty dataset instead of a 4xx response       |

## Platform

### Client Portal

* Ability to update System Settings:
  * File.1
* Remove the option to create an API Key that does not expire

### General

* Security patches
* Stability fixes


---

# 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://docs.zwapgrid.com/changelog/october-2024/4th-october.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.