> This page is for Product Documentation.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# POS Posting Setup troubleshooting

> Refer to the POS Posting Setup troubleshooting guide if you encounter related issues.

If POS entries cannot be posted and Business Central shows errors such as **"POS Posting Setup is missing for Payment"** or **"POS Posting Setup is missing for POS Balancing Line"**, the affected combination is missing in **POS Posting Setup**.

Typical error details include a combination of:

* **POS Store Code**
* **POS Payment Method Code**
* **POS Payment Bin Code**

Example:

* POS Store Code = `SB`
* POS Payment Method Code = `BAR`
* POS Payment Bin Code = `SB06`

## Symptoms

You may see one or more of the following:

* POS entries remain unposted.
* Balancing entries remain unposted.
* Manual posting fails with a missing setup error.
* Some entries post after rerunning the job queue, while others remain blocked because specific posting combinations are missing.

## Cause

The posting logic depends on the combination of **store**, **payment method**, and optionally **payment bin**. If the required combination is not present in **POS Posting Setup**, posting fails for that entry.

This is especially relevant for cash-related scenarios where balancing lines and bin-specific postings are involved.

## Resolution

1. Open **POS Posting Setup** in Business Central.
2. Identify the missing combination from the error message.
3. Create the required setup line for that exact combination.
4. Repeat this for all missing combinations shown in the posting errors.
5. Post the remaining POS entries again.
6. When all affected entries are cleared, refresh the posting job by deleting the current job queue entry and creating a new **NPR POS Post GL Entries** job queue entry with the same setup.

## Important note about existing entries

Changing the current POS unit or cash drawer setup does **not** change already-created POS entries.

Existing entries must be posted with a setup that matches the **actual unit / payment bin combination stored on the entry**.

## Temporary workaround for historical entries

If entries were created with a combination that should not normally be used anymore, it is possible to:

1. Temporarily create the required **POS Posting Setup** combination.
2. Post the affected historical entries.
3. Remove the temporary setup again afterwards.

Use this only if you are sure the setup should not be available for future transactions.

## Cash drawer / wrong layout scenario

If the wrong layout was selected during the sale and this caused cash payments to be registered on a unit without the intended cash drawer:

* create the missing posting setup for the combination that is actually stored on the entry,
* post the affected entries first,
* then use a cash transfer process to move the amount to the drawer/bin where the cash physically ended up.

Do **not** expect a later setup change on the POS unit alone to fix already-created entries.

## Prevention

Before going live or adding new units / drawers / layouts, verify that **all expected combinations** exist in **POS Posting Setup**, especially for:

* each POS Store Code,
* each payment method used for posting,
* each payment bin used for cash handling or balancing.

This is particularly important when using store-specific and bin-specific posting rules.

## Misleading "missing dimension" error when posting

When posting a POS entry fails with a message such as *"A dimension used in Gen. Journal Line , , 30000 has caused an error…"*, the line number (`10000`, `20000`, `30000`, …) refers to the **general journal line generated internally during posting** — **not** the POS entry sale line with the same number. Checking that sale line will look fine; Business Central cannot map the number back to the source line, so it is misleading.

The real cause is usually a **mandatory dimension** missing on a posting-relevant account or line:

* a **default dimension** on the target **G/L account** set to **Code Mandatory** (for example, `AFDELING`),
* a dimension missing on a **generated line** (VAT, rounding, payment, discount, or balancing), or on the POS entry **header**.

Comment lines are excluded from posting and never create a G/L entry, so their dimensions do not affect posting.

To fix it, on the **POS Entry Card** use the add/modify dimension function on the sales detail line to set the missing value, then post again. Header dimensions can be corrected from the **POS Entry List** → **Actions** → **Dimensions**. For general guidance, see [<ins>Correct dimensions</ins>](https://learn.microsoft.com/en-us/dynamics365/business-central/finance-troubleshooting-correcting-dimensions).

## Related links

* [<ins>POS posting setup</ins>](/product/retail-posting-setup-pos-posting-setup)
* [<ins>Different combinations and priority rules for posting</ins>](/product/retail-posting-setup-different-posting-rules)
* [<ins>POS entry list - posting setup</ins>](/product/retail-posting-setup-pos-entry-list-posting-setup)
* [<ins>Manually post POS entries and check if they are posted</ins>](/product/retail-posting-setup-manually-post-pos-entries)
* [<ins>Set up job queue to post POS entries</ins>](/product/retail-posting-setup-job-queue)
* [<ins>Transfer cash with the POS Payment Bin Transfer Journal</ins>](/product/retail-pos-processes-transfer-cash-bc)