Omniboost to Accounting | Payment Entry Not Posting to Debtor Ledger Account

Omniboost accounting integrations that synchronise data via an API connection to your accounting platform may occasionally return an error indicating that a payment entry could not be posted to a ledger account of the type Debtors or Accounts Receivable. This error typically occurs when the integration attempts to record a payment against a ledger account that your accounting system does not permit for direct posting, as accounts of this type are often system-managed and restricted to entries generated through specific workflows such as invoicing or customer receipt allocation.

This article explains the underlying cause of this error, outlines why certain accounting platforms enforce these restrictions, and provides possible solutions to resolve the issue within your integration mapping.

The specific error message returned for this issue will vary depending on your accounting platform, but generally takes one of the following forms:

In this case, "X" refers to the ledger account in your chart of accounts that has been assigned the type Debtors or Accounts Receivable.

Alternatively, your accounting platform may return an error similar to:

Both of these messages indicate that the accounting system requires additional information, such as a customer or contact reference, when posting entries to a ledger account of this type. Because the integration posts journal entries rather than customer-specific invoices or receipts, this requirement cannot be fulfilled, which results in the posting failure.

This error indicates that your Omniboost accounting integration is unable to post a payment amount to the specified ledger account in your accounting platform.

More specifically, the error occurs when the integration attempts to create a journal entry that includes a posting to a ledger account that has been assigned the type Debtors or Accounts Receivable within your chart of accounts. Ledger accounts of this type are designed to track outstanding customer balances, and as a result, your accounting platform requires that debtor or customer information is included with any entry posted to these accounts.

Because the Omniboost integration posts consolidated journal entries rather than individual customer transactions, it does not include debtor information in the posting. When the integration encounters a ledger account of this type without the required customer reference, the accounting platform rejects the entry and the error message is returned.

Below is an example demonstrating how this error can occur in practice, using an integration between Mews PMS and Exact Online as the accounting platform.

Please note that while this example is specific to Mews and Exact Online, the same logic applies to any PMS to accounting integration regardless of the platforms involved.

In this scenario, the ledger account code 1300 in Exact Online has been mapped to an accounting category named "Debiteuren" within Mews:

As a result, the Omniboost accounting integration will attempt to post any entries that fall under the accounting category "Debiteuren" in Mews to ledger account 1300 in Exact Online.

When the integration attempts to post an entry to this ledger account, the following error is returned by the accounting platform:

This error confirms that ledger account 1300 is configured as a Debtors or Accounts Receivable type within Exact Online. As explained above, this means the accounting platform requires debtor information to be included with any entry posted to this account.

To identify the root cause, we look up the entries posted under the accounting category "Debiteuren" within the PMS system and verify whether debtor information is present for each entry:

Any entries assigned to the accounting category "Debiteuren" that do not contain debtor information will trigger this error. For example:

In the images above, we can see that an external invoice payment of EUR 5,50 is present under this category. However, this entry is not treated as an actual invoice within Mews. This is because there is no open balance associated with it, as indicated by the EUR 0,00 amount. Since there is no outstanding balance, the entry does not contain any debtor information, and the customer "Paymaster GBS" is not considered a debtor in this context.

As a result, the integration attempts to post this entry to ledger account 1300, but the accounting platform rejects it because the required debtor information is missing from the entry

There are several solutions available to resolve the issue described above. The appropriate solution will depend on your specific accounting platform, your PMS configuration, and how your chart of accounts has been structured.

Below we outline the most common approaches to ensure that payment entries can be posted successfully without encountering ledger account restrictions.

The first solution involves remapping the payment entries that do not contain debtor information to a different accounting category within your PMS system. This is typically done within the accounting configuration section of your PMS.

The payment entries that are causing the issue should be assigned to either an existing accounting category that is already mapped to a suitable ledger account, or to a newly created accounting category. The key requirement is that the ledger account code associated with this alternative accounting category must not be of the type Debtors or Accounts Receivable in your chart of accounts. If it is, the same error will occur.

Applied to the practical example in this article, this would mean that the "External invoice payments" entry, which caused the error because no debtor information is attached to it, should be moved to a different accounting category within Mews. That different accounting category should then be mapped to a ledger account code other than 1300, and the selected ledger account must not be of the type Debtors or Accounts Receivable.

An alternative solution is to change the ledger account code that is mapped to the accounting category in question within your PMS system. Rather than moving specific payment entries to a different category, you change the destination ledger account for the entire category.

Applied to the practical example above, this would mean changing the ledger account code mapped to the accounting category "Debiteuren" in Mews from 1300 to a different ledger account code. As with the first solution, the replacement ledger account must not be of the type Debtors or Accounts Receivable in your chart of accounts, otherwise the same error will persist.