5 Common Accounting Challenges in POS and Business Central Integration

Common accounting challenges when integrating POS with Business Central: merchant fees, tax, COGS, gift cards and rounding
Five accounting challenges in a POS and Microsoft Dynamics 365 Business Central integration

Business Central POS accounting problems rarely show up at the register. They show up weeks later in the General Ledger (G/L), as a clearing account that never reaches zero or a tax total that is off by a few dollars. Integrating a point-of-sale system with Microsoft Dynamics 365 Business Central (BC) is meant to give a retailer one version of the truth. It takes more than connecting two APIs, because every POS transaction has to land in the right account with the right amount. These are the five accounting challenges we see most, and how to deal with each.

By the x2x eCommerce team. Updated November 2026.

Which ledger symptom points to which problem?

1. Payment reconciliation and merchant fees

Matching POS payments to bank deposits is one of the most tiresome jobs in a retail finance team. Say the POS sends a $100 credit card sale to a clearing account in Business Central. The bank deposit that arrives is $97.50, because the processor kept $2.50 in fees. If the integration does not account for those fees, the clearing account carries a small difference that grows with every sale.

Settlement timing adds a second problem. Processors often batch weekend sales into one Monday deposit, while Business Central records sales day by day. The fix is to post processing fees to their own expense account and to reconcile the clearing account against settlement batches instead of calendar days.

2. Tax jurisdictions and compliance

A POS can be set up for state, county and city taxes. Trouble starts when that setup does not line up with Business Central’s tax configuration. The usual causes are exemptions on items such as food, different rates for alcohol and clothing, and destination-based sales tax on web orders. If the POS calculates tax from the store’s location and Business Central uses the customer’s, the G/L will not match the POS.

Choose one source of authority for tax, either the POS or Business Central, and make the other follow it. Your accountant should confirm which one suits your jurisdictions.

3. Inventory valuation and cost of goods sold

Syncing sales is the easy half. The harder half is accounting for what each sale does to inventory, and timing matters. If the POS sells an item that Business Central shows as out of stock, so inventory goes negative, Business Central temporarily records a zero or estimated cost. When the stock is received and invoiced, Business Central calculates the real cost and adjusts the G/L. If the integration skips that adjustment, or the two systems use different costing methods, inventory valuation ends up wrong.

Three habits help. Receive stock in Business Central before it sells whenever you can. Use the same costing method on both sides, with Business Central as the master. Schedule the cost adjustment so it runs on its own. Microsoft’s documentation explains how to adjust item costs and how to schedule jobs to adjust and reconcile inventory cost. For multi-store setups, see real-time inventory sync between RMH and Business Central.

4. Gift cards and unearned revenue

In accounting terms, selling a gift card is not a sale. The business takes cash and owes the customer goods later, which is a liability. A common integration mistake is treating the sale as ordinary revenue, which overstates sales in Business Central.

Map gift card sales to a dedicated liability G/L account. When a customer redeems the card, the POS should tell Business Central, so the amount moves from the liability account to revenue at that point.

5. Rounding and cent differences

Fractions of a cent cause more trouble than their size suggests. Take a “3 for $10” promotion. The POS spreads the price as $3.33 per item, which totals $9.99, one cent short of the $10.00 the customer paid. If the POS and Business Central round differently, the document totals disagree and the posting can fail. In countries that use cash rounding, both systems must round the same way.

Build a rule into the integration that sends leftover cents to a dedicated rounding G/L account. That keeps each posting balanced without hiding the difference. Our guide to handling discounts, returns and negative amounts covers the related promotion cases.

Frequently asked questions about Business Central POS accounting

Why does my POS clearing account not balance in Business Central?

The usual causes are processing fees that are not posted and batch settlements that arrive on a different day from the sales. Post fees to their own expense account and reconcile the clearing account by settlement batch.

Should the POS or Business Central calculate sales tax?

Either can, but only one should. If both calculate tax with different rules, such as store location versus customer location, the G/L will not match the POS. Confirm the choice with your accountant.

How should gift cards be recorded in Business Central?

Book gift card sales to a liability G/L account, not revenue. When the card is redeemed, move the amount from the liability account to revenue.

Why do POS sales post with the wrong cost in Business Central?

If an item sells before its stock is received, Business Central temporarily uses a zero or estimated cost. The cost is corrected after the purchase is received and invoiced, as long as the cost adjustment runs and both systems use the same costing method.

How do I handle rounding differences between a POS and Business Central?

Make both systems round the same way, and send any leftover cents to a dedicated rounding G/L account so each posting balances.

Next step

For the design side of these problems, read how to prevent accounting errors when integrating POS transactions with Business Central. If you run Retail Management Hero (RMH), see the RMH Dynamics 365 Business Central integration or book a free x2x demo to review your own setup.