> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/accounting/common-issues/unable-to-create-or-modify-ar-ap-journal-entries.md).

# Unable to Create or Modify AR/AP Journal Entries

### Issue

Users may face issues when:

* Creating Journal Entries in AR or AP
* Editing system-generated invoices or bills
* Voiding credit memos or vendor credits

***

### Cause

In XoroERP, when AR or AP accounts are used in a Journal Entry:

* The system automatically creates **linked accounting documents**.
* These documents are **controlled by the Journal Entry**.

Because of this relationship, they **cannot be edited or voided independently**.

***

### Common Issues and Solutions

#### Issue 1: Cannot Edit Invoice / Credit Memo

**Reason**

The document was automatically created from a **Journal Entry**.

**Solution**

Locate and edit the **linked Journal Entry** instead.

***

#### Issue 2: Cannot Void Credit Memo or Bill

**Reason**

System-generated documents cannot be voided directly.

**Solution**

1. Go to **Journal Entry module**
2. Locate the **linked JE**
3. Void the **Journal Entry**

The related document will **automatically be voided**.

***

#### Issue 3: Currency Mismatch Error

**Reason**

The following currencies must match:

* Account currency
* Entity currency
* Journal Entry currency

**Solution**

Ensure the **Customer or Vendor currency matches the Account currency**.

***

### Best Practices

✔ Always verify **Entity selection (Customer/Vendor)** when using AR or AP.\
✔ Ensure **currencies match** before creating the JE.\
✔ Use Journal Entries only when necessary to **correct variances or adjustments**.


---

# 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.xorosoft.com/xoroerp-1/accounting/common-issues/unable-to-create-or-modify-ar-ap-journal-entries.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.