> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/integrations/integrations/eboekhouden/troubleshoot-eboekhouden.md).

# Troubleshoot eBoekhouden

Use the log in the eBoekhouden settings to review imports, exports, and errors.

Each log entry shows when the sync ran and what happened.

{% stepper %}
{% step %}

### Open the eBoekhouden settings

Go to **Settings → General → Software integrations**.

Open **eBoekhouden**.
{% endstep %}

{% step %}

### Open the log

Scroll to the log section or open the **Log** tab.

Then review the latest entries.
{% endstep %}

{% step %}

### Open the error details

If an entry shows a warning or error icon, open it.

Use the full message to find the exact cause.
{% endstep %}

{% step %}

### Refresh and retry

Click **Refresh** to load the latest entries.

After you fix the cause, run a manual sync again.
{% endstep %}
{% endstepper %}

### Quick checks first

Check these points before you go deeper:

* the login details are still valid
* the invoice template name matches exactly
* the payment term is filled in
* the default general ledger account exists in eBoekhouden
* the relation exists in eBoekhouden or can be exported

### Common error messages

<details>

<summary>The API settings are not valid</summary>

The username or one of the security codes is wrong.

Open the login settings and enter the details again.

</details>

<details>

<summary>Too many records or the 2,000-record limit is reached</summary>

eBoekhouden only returns up to 2,000 records per request.

This limit comes from eBoekhouden.

OutSmart cannot bypass it.

</details>

<details>

<summary>SOAP call limit reached (E003.1)</summary>

eBoekhouden limits the number of API calls in a short time.

Wait a while.

Then run the sync again.

</details>

<details>

<summary>Relation not known in eBoekhouden</summary>

The customer on the work order or invoice does not exist in eBoekhouden.

Turn on **Export relations** or create the relation in eBoekhouden first.

</details>

<details>

<summary>Invoice template not found (CFACT028)</summary>

The template name in OutSmart does not match a template in eBoekhouden.

Use the exact template name from eBoekhouden.

</details>

<details>

<summary>Payment term not filled in (CFACT014)</summary>

The payment term is empty.

Fill in the number of days in the export settings.

</details>

<details>

<summary>Counter account code not filled in (CFACT040)</summary>

A material does not have the required counter account code.

Check whether the material came from eBoekhouden.

Also check the first two free fields on the material card.

</details>

<details>

<summary>VAT code not filled in (CFACT038)</summary>

A material or hour type does not have a valid VAT code.

Check the item in eBoekhouden and in OutSmart.

</details>

<details>

<summary>Invalid material code (CFACT037)</summary>

A material code on the invoice does not exist in eBoekhouden.

Check whether the material code still matches the code in eBoekhouden.

</details>

<details>

<summary>Counter account code unknown (CMUT012)</summary>

The default general ledger account does not exist in eBoekhouden.

Check the account code in the export settings.

</details>

<details>

<summary>No order lines on the work order (CFACT006)</summary>

The work order does not contain materials or hour types.

Add at least one invoice line before exporting.

</details>

### Frequently asked questions

<details>

<summary>Why does the same error keep coming back?</summary>

The sync retries the same data until the cause is fixed.

Fix the source issue first.

Then run a manual sync.

</details>

<details>

<summary>Can I export again after I fix an error?</summary>

Yes.

Run the export again after you correct the relation, item, or settings.

</details>

<details>

<summary>Where do I start when the log is unclear?</summary>

Start with the login details, relation, invoice template, payment term, and general ledger account.

These are the most common causes.

</details>

### Related topics

* [**eBoekhouden**](/integrations/integrations/eboekhouden.md)
* [**Set up eBoekhouden**](/integrations/integrations/eboekhouden/set-up-eboekhouden.md)
* [**Configure eBoekhouden exports**](/integrations/integrations/eboekhouden/configure-eboekhouden-exports.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 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://knowledge.out-smart.com/integrations/integrations/eboekhouden/troubleshoot-eboekhouden.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.