> For the complete documentation index, see [llms.txt](https://dev.ropo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ropo.com/guides/basics/invoice/examples-of-invoice-accountings.md).

# Examples of invoice accountings

Use `accountdate` and `accountrow` when you export invoice accounting entries to your ERP.

### accountdate

`accountdate` controls the accounting period in your ERP.

It is not the same as the invoice date (`billdate`).

If you omit `accountdate`, the service uses `billdate`.

Send it under the invoice `dataset`.

```json
{
  "accountdate": "2026-02-18"
}
```

### accountrow

`accountrow` is an array of accounting rows for the invoice.

Each row typically maps to one debit or credit entry in your chart of accounts.

Send it under the invoice `dataset`.

#### Dimensions

You can pass dimensions using:

* `servicecode_name`
* `type`, `type2`, …, `type10`

`type`…`type10` are strings with max length 10.

### Example: Debit invoice (total 1250.00)

Expected behavior:

* Receivable on the debit side.
* Sales on the credit side.
* `netamount` and `vatamount` are positive.
* Use the same dimensions, VAT data, and tax rate on both entries.

```json
{
  "accountrow": [
    {
      "accountid": 1701,
      "desc": "Invoice line",
      "debit": 1250.0,
      "credit": null,
      "netamount": 1000.0,
      "vatamount": 250.0,
      "taxpr": 25,
      "vatcode": 3,
      "servicecode_name": "10000",
      "type": "XYZ",
      "type2": null,
      "type3": null,
      "type4": null,
      "type5": null,
      "type6": null
    },
    {
      "accountid": 3000,
      "desc": "Invoice line",
      "debit": null,
      "credit": 1250.0,
      "netamount": 1000.0,
      "vatamount": 250.0,
      "taxpr": 25,
      "vatcode": 3,
      "servicecode_name": "10000",
      "type": "XYZ",
      "type2": null,
      "type3": null,
      "type4": null,
      "type5": null,
      "type6": null
    }
  ]
}
```

### Example: Credit invoice (total -1250.00)

Expected behavior:

* Receivable on the credit side.
* Sales on the debit side.
* `netamount` and `vatamount` are negative.
* Use the same dimensions, VAT data, and tax rate on both entries.

```json
{
  "accountrow": [
    {
      "accountid": 1701,
      "desc": "Invoice line",
      "debit": null,
      "credit": 1250.0,
      "netamount": -1000.0,
      "vatamount": -250.0,
      "taxpr": 25,
      "vatcode": 3,
      "servicecode_name": "10000",
      "type": "XYZ",
      "type2": null,
      "type3": null,
      "type4": null,
      "type5": null,
      "type6": null
    },
    {
      "accountid": 3000,
      "desc": "Invoice line",
      "debit": 1250.0,
      "credit": null,
      "netamount": -1000.0,
      "vatamount": -250.0,
      "taxpr": 25,
      "vatcode": 3,
      "servicecode_name": "10000",
      "type": "XYZ",
      "type2": null,
      "type3": null,
      "type4": null,
      "type5": null,
      "type6": null
    }
  ]
}
```

{% hint style="info" %}
`vatcode` is an accounting VAT code. Map it to your ERP’s VAT logic.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.ropo.com/guides/basics/invoice/examples-of-invoice-accountings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.