sawwiapp
Start free

Microsoft Dynamics 365 Business Central reconciliation

Pull sales and purchase documents from Business Central and reconcile them against customer payments, deliveries, marketplace settlements and supplier invoices, without copying data between spreadsheets.

Start free

Connect Business Central, or upload the exports

Read-only connector: Microsoft Dynamics 365 Business Central

Sawwi's Business Central connector signs in with a Microsoft Entra app registration (client credentials) and reads twelve reports through the Business Central API v2.0: sales invoices, sales invoice lines, sales credit memos, open sales order lines, sales shipment lines, open purchase order lines, purchase receipt lines, purchase invoice lines, posted sales invoices and credit memos for web orders (those carrying a store order number in External Document No.), the same invoices in document and local currency, and items with their inventory and unit price. It only reads.

It works with Business Central online. The reports come in with fixed column names, so they map onto the templates without questions. The connector is new; you can always export the same lists to Excel and upload them instead.

14 Business Central reconciliations

Matching is done by Sawwi's own rules engine on keys, amounts and dates, never by AI, so the same files always give the same report.

Customer payments vs. open invoices

Apply each business customer's payment to the invoices it settles. Flag short payments, overpayments and receipts nobody has applied.

Files you need

  • Open invoices / AR register: Invoices raised to business customers, from your ERP or accounting system.For example: Odoo / Zoho / SAP B1 / Tally AR ageing, Customer invoice register.
  • Customer receipts: Payments received from customers. A bank statement or a receipts register from your ERP both work.For example: Bank statement (credits), ERP customer receipts register, Remittance advices.

The Microsoft Dynamics 365 Business Central connector can fill: Open invoices / AR register.

What Sawwi checks

  • Unapplied receipt: Money received that can't be tied to any invoice.
  • Short paid: Customer paid less than the invoice. Often a deduction, discount taken or bank charge.
  • Overpaid / duplicate payment: Paid more than invoiced, or paid the same invoice twice.
  • Overdue invoices: Open beyond credit terms, with ageing buckets.

Sales orders vs. deliveries vs. invoices

Three-way order-to-cash check: everything delivered was invoiced, and nothing was invoiced that wasn't delivered.

Files you need

  • Sales orders: Confirmed customer orders (POs received).For example: ERP sales order lines, B2B portal orders.
  • Delivery notes / POD: What was actually delivered and signed for.For example: Delivery notes, Proof-of-delivery report, Courier/fleet delivery log.
  • Invoice lines: Invoice lines raised against the orders.For example: ERP invoice lines, Sales register (line level).

The Microsoft Dynamics 365 Business Central connector can fill: Sales orders, Delivery notes / POD, Invoice lines.

What Sawwi checks

  • Delivered, not invoiced: Unbilled revenue: goods left the warehouse but no invoice.
  • Invoiced, not delivered: Customer billed for goods without a delivery record, which leads to disputes.
  • Quantity mismatch: Invoiced quantity differs from delivered quantity.
  • Open order backlog: Ordered but not yet delivered, past the promised date.

Purchase orders vs. goods received vs. supplier invoices

Three-way match before you pay a supplier: only pay for what you ordered, at the PO price, and actually received.

Files you need

  • Purchase order lines: What you ordered from suppliers, line by line, with the agreed price.For example: ERP purchase order lines, Odoo / Zoho purchase orders export, PO tracker spreadsheet.
  • Goods received notes (GRN): What your warehouse actually received and accepted against each PO.For example: ERP goods receipt / GRN lines, Warehouse receiving log, 3PL inbound receipt report.
  • Supplier invoice lines: Supplier bills booked in your AP, at line level with the PO reference.For example: ERP vendor bill lines, AP invoice register (line level), Supplier invoice scan to Excel.

The Microsoft Dynamics 365 Business Central connector can fill: Purchase order lines, Goods received notes (GRN), Supplier invoice lines.

What Sawwi checks

  • Invoiced, not received: Supplier billed for goods with no goods received note. Hold payment.
  • Invoiced more than received: Invoiced quantity is above the accepted quantity (received minus rejected).
  • Billed above PO price: Line amount is higher than invoiced qty × the PO unit price.
  • Invoice without a PO: Invoice line whose PO and SKU aren't on any purchase order.
  • Duplicate supplier invoice: The same supplier invoice number and SKU is booked more than once.
  • Received, not invoiced: Goods received with no supplier bill yet. Accrue as GRNI (goods received not invoiced).
  • Received more than ordered: Warehouse accepted more units than the PO allows.
  • Receipt without a PO: Goods received against a PO number or SKU that isn't on any purchase order.
  • PO overdue, nothing received: Expected date has passed and nothing has been received.
  • Partly received: Open PO balance: fewer units received than ordered so far.
  • Billed below PO price: Usually a discount or a wrong PO price. Check before the PO is reused.

Store invoices vs. ERP posted invoices

Check every invoiced webstore order reached your ERP once, as a posted invoice with the same total, VAT and customer.

Files you need

  • Webstore invoices: Invoices your store created for paid or delivered orders in the period.For example: Magento 2 / Adobe Commerce invoices, Shopify orders export (paid), WooCommerce orders.
  • ERP posted sales invoices: Sales invoices posted in your ERP for web orders, with the store's order number as their external reference.For example: Business Central posted sales invoices, Odoo customer invoices, Zoho Books invoices.

The Magento 2 / Adobe Commerce connector can fill: Webstore invoices. The Microsoft Dynamics 365 Business Central connector can fill: ERP posted sales invoices.

What Sawwi checks

  • Not posted in the ERP: The store invoiced the order, but the ERP has no posted invoice for it: the sync failed or is stuck.
  • Posted twice: The same order was posted more than once for the same amount, so revenue and VAT are overstated.
  • Total differs: The ERP's invoice total differs from the store's.
  • VAT differs: VAT posted in the ERP differs from the VAT on the store invoice.
  • Different customer: The ERP invoice carries another customer e-mail than the store order, e.g. posted to a guest or the wrong account. Ignore it if you post every web order to one customer.

Listed for you to review (not calculated automatically yet): posted without a store invoice.

Store refunds vs. ERP credit notes

Check every refund your webstore issued was posted in your ERP once, as a credit note for the same amount and VAT.

Files you need

  • Webstore credit memos (refunds): Credit memos your store created in the period, including shipping and goodwill refunds.For example: Magento 2 / Adobe Commerce credit memos, Shopify refunds export, WooCommerce refunds.
  • ERP posted credit notes: Sales credit memos posted in your ERP for web refunds, with the store's order number as their external reference.For example: Business Central posted sales credit memos, Odoo credit notes, Zoho Books credit notes.

The Magento 2 / Adobe Commerce connector can fill: Webstore credit memos (refunds). The Microsoft Dynamics 365 Business Central connector can fill: ERP posted credit notes.

What Sawwi checks

  • Refund not posted in the ERP: The store refunded the customer, but the ERP has no credit note for that order: revenue and VAT are overstated.
  • Credit note posted twice: The same refund was posted more than once for the same amount.
  • Amount differs: The ERP credited a different amount than the store refunded for that order.
  • VAT differs: VAT on the ERP credit note differs from the VAT the store refunded.

Listed for you to review (not calculated automatically yet): credit note without a store refund.

Store stock vs. ERP inventory

Compare what your webstore offers for sale per SKU with the inventory your ERP holds: catch overselling and stock hidden from shoppers.

Files you need

  • ERP item inventory: Your ERP's items with the quantity on hand right now.For example: Business Central items (inventory), Odoo stock on hand, Zoho Inventory items.
  • Webstore stock by source: The quantity your store can sell per SKU, one row per stock location if there are several.For example: Magento 2 MSI source items, Shopify inventory levels, WooCommerce stock export.

The Magento 2 / Adobe Commerce connector can fill: Webstore stock by source. The Microsoft Dynamics 365 Business Central connector can fill: ERP item inventory.

What Sawwi checks

  • Store sells more than you hold: The store offers more units than the ERP has on hand, so shoppers can buy stock you don't have.
  • Stock hidden from the store: The ERP holds more than the store offers: a source set out of stock, or a sync that didn't run.
  • Sold online, unknown to the ERP: The store has sellable stock for a SKU the ERP doesn't have, so its sales can't be posted.

Listed for you to review (not calculated automatically yet): in the erp, not in the store.

Store prices vs. ERP prices

Check each SKU's webstore price against your ERP's price, and catch special prices left running past their end date.

Files you need

  • Webstore prices: Your store's catalogue: price per SKU, with any special (sale) price and its dates.For example: Magento 2 product prices with special prices, Shopify products export, WooCommerce products export.
  • ERP item prices: The selling price your ERP holds per item, on the same VAT basis as the store.For example: Business Central items (unit price), Odoo product sales price, Zoho Inventory items.

The Magento 2 / Adobe Commerce connector can fill: Webstore prices. The Microsoft Dynamics 365 Business Central connector can fill: ERP item prices.

What Sawwi checks

  • Price differs from the ERP: The store's regular price isn't the ERP's price, so orders are invoiced at a different price than the shopper paid.
  • Special price past its end date: A special price whose end date has passed is still set. Magento stops applying it, but it's stale: remove it or extend it on purpose.
  • Special price above the regular price: The sale price is higher than the regular price, usually a typo.
  • Priced online, unknown to the ERP: A SKU the store sells that has no item in the ERP.

Multi-currency store invoices vs. ERP

For each store view and currency, check the ERP booked every invoice in the right currency and at the base value Magento recorded, within an FX tolerance.

Files you need

  • Webstore invoices by store and currency: Invoices from every store view in the period, with the order currency, the base currency total and the exchange rate the store recorded.For example: Magento 2 invoices with base and order currency, Shopify Markets orders export (shop and presentment currency).
  • ERP posted invoices in two currencies: Posted sales invoices for web orders with their currency, the amount in that currency and in your local currency, and the store they belong to (a dimension).For example: Business Central posted sales invoices with currency and dimension, ERP sales register with FCY and LCY amounts.

The Magento 2 / Adobe Commerce connector can fill: Webstore invoices by store and currency. The Microsoft Dynamics 365 Business Central connector can fill: ERP posted invoices in two currencies.

What Sawwi checks

  • FX difference above tolerance: The ERP's local-currency amount differs from the base value the store recorded by more than 1.00: a different rate, or a different amount.
  • Posted in the wrong currency: The ERP invoice is in another currency than the store order.
  • Not posted in the ERP: A store invoice with no posted ERP invoice.
  • Store missing from the ERP: No ERP invoice carries this store's code in its dimension: the store isn't connected to the ERP, or its dimension isn't set.

Customer returns vs. credit notes

Make sure every goods return from a business customer has the right credit note, and every credit note has a return or an approved reason.

Files you need

  • Goods returns (GRN / RMA): Returns received from business customers.For example: Goods return notes, RMA register, WMS returns inward.
  • Credit notes: Credit notes issued to business customers.For example: ERP credit note register.

The Microsoft Dynamics 365 Business Central connector can fill: Credit notes.

What Sawwi checks

  • Return without credit note: Goods came back but the customer hasn't been credited, so expect a short payment.
  • Credit note without return: Credit issued with no goods received or approval reason.
  • Value mismatch: Credit amount differs from the value of the returned goods.

Invoiced prices vs. customer price list

Check every invoice line against the customer's agreed price, discount and validity dates.

Files you need

  • Invoice lines: Line-level sales invoices for the period.For example: ERP invoice lines, Sales register (line level).
  • Customer price list / contract: Agreed prices or discounts per customer and SKU.For example: Customer price lists, Contract pricing sheet.

The Microsoft Dynamics 365 Business Central connector can fill: Invoice lines.

What Sawwi checks

  • Billed above agreed price: Risk of customer dispute or short payment.
  • Billed below agreed price: Revenue leakage.
  • Expired or future price used: The invoice date is outside the price's validity window.
  • No agreed price: SKU sold to a customer with no contract price on file.

Settlement vs. sales invoices

Check every invoiced order was paid out by the marketplace, net of the fees you agreed to.

Files you need

  • Order / sales invoice register: Your record of what was sold and invoiced, from your ERP, accounting system or the marketplace order report.For example: Marketplace order report, ERP sales register, Zoho / Odoo / Tally sales export.
  • Marketplace settlement / payout statement: The line-level payout statement the marketplace gives you for each settlement period.For example: Amazon settlement report (flat file), Noon statement of account, Namshi payout report.

The Microsoft Dynamics 365 Business Central connector can fill: Order / sales invoice register.

What Sawwi checks

  • Invoiced but not settled: Order is in your sales register but has no settlement line yet.
  • Short paid: Principal settled is lower than the invoice amount.
  • Settled but not invoiced: Marketplace paid for an order missing from your register.
  • Settled twice: The same order and SKU appear in more than one settlement.
  • Ageing beyond payout cycle: Unsettled orders older than the marketplace's normal payout cycle.

B2B invoices vs. payment release

Track B2B marketplace invoices through to payment release: short pays, held amounts and reserves.

Files you need

  • B2B invoice register: Tax invoices raised to business buyers through the marketplace.For example: Amazon Business invoice report, ERP B2B invoices.
  • Payment release / remittance report: What the marketplace released against B2B orders, including holds and reserves.For example: Marketplace B2B payment report, Remittance advice export.

The Microsoft Dynamics 365 Business Central connector can fill: B2B invoice register.

What Sawwi checks

  • Overdue for release: Past payment terms and not fully released.
  • Held or in reserve: Part of the amount is held. Shows how long and why.
  • Released short: Released + held + deductions is less than the invoice.
  • Unexplained deduction: Deduction with no matching credit note or fee.

Customer ledger vs. customer statement

Compare your ledger for a customer with their statement or balance confirmation, and explain every difference in the closing balance.

Files you need

  • Your customer ledger: The customer's account in your books for the period.For example: ERP customer ledger / statement of account, AR sub-ledger export.
  • Customer's statement / confirmation: The supplier ledger or balance confirmation your customer sent you.For example: Customer's supplier ledger (Excel/PDF to Excel), Balance confirmation.

What Sawwi checks

  • Not booked by customer: Invoice or credit note in your books that's missing from theirs.
  • Not booked by you: Payment or debit note in their books that's missing from yours.
  • Amount differs: Same document, different amount.

Listed for you to review (not calculated automatically yet): timing difference.

Supplier ledger vs. supplier statement

Compare your payables ledger for a supplier with their statement of account, and explain the balance difference before you pay.

Files you need

  • Your supplier ledger: The supplier's account in your books (bills, payments, debit notes).For example: ERP vendor ledger, AP sub-ledger export, Zoho / Odoo vendor statement.
  • Supplier's statement of account: The statement or balance confirmation the supplier sent you.For example: Supplier SOA (Excel / PDF to Excel), Balance confirmation.

What Sawwi checks

  • Bill not booked by you: Invoice on the supplier's statement that's missing from your books.
  • Not on supplier's statement: Payment or debit note in your books that the supplier hasn't recorded.
  • Amount differs: Same document, different amount.
  • Bill booked twice: The same supplier document number appears more than once in your ledger.

Listed for you to review (not calculated automatically yet): timing difference.

How it works

  1. 1

    Pick the reconciliation

    Each one knows which files it needs and what to check.

  2. 2

    Add the files

    Upload exports as they are, or pull them from a connection. Columns are mapped for you and remembered.

  3. 3

    Work the exceptions

    Every exception with its value, ranked by what it costs you, and every table downloads to Excel.

Questions

What does Sawwi need to connect to Business Central?
Your IT admin registers an app in Microsoft Entra, gives it a client secret, and enables it in Business Central with a read-only permission set. You then enter the tenant, environment, client ID and secret in Sawwi. The secret is stored encrypted.
Does it work with Business Central on-premises?
The connector uses the Business Central online API. For on-premises installations, export the same lists to Excel and upload them.
Can Sawwi read customer and vendor ledger entries?
Not through the connector: Business Central's standard API v2.0 doesn't expose them. For customer and supplier statement reconciliations, export the ledger from Business Central and upload it.
Can Sawwi check that our web store's orders reach Business Central?
Yes, for Magento 2. Sawwi compares Magento's invoices and credit memos with the posted sales invoices and credit memos that carry the Magento order number in External Document No., and flags documents that never synced, were posted twice, or whose totals, VAT or customers differ. It also compares Magento's sellable stock and prices per SKU with Business Central's inventory and unit prices. Price list lines aren't in Business Central's standard API, so special prices are checked on the Magento side only.
Is this a replacement for bank reconciliation in Business Central?
No. Sawwi focuses on the reconciliations around your sales and purchases: payments against invoices, orders against deliveries and invoices, POs against receipts and supplier bills, and marketplace payouts against sales.

Related reconciliations

Bring last month's exports and see what's missing.

Setup takes two minutes. Or try the demo store with invented data first, no sign-up.

Create your workspace