If your company supplies products or services to Naturals Salon Private Limited and maintains the customer account in Microsoft Dynamics NAV or Dynamics 365 Business Central, your finance team may periodically receive a ledger from Naturals Salon for reconciliation.

Your Dynamics customer ledger may contain a very detailed accounting record.

The Naturals Salon ledger may be much simpler.

For example, your Dynamics export may contain information relating to:

• Posting and document dates
• Document numbers
• External document numbers
• Customer account
• Original amount
• Remaining amount
• Due date
• Payment application
• TDS certificates
• Open-item status
• Dispute status
• Branch, cost centre and profit centre
• GST information
• Product and brand information

The Naturals Salon ledger may contain only:

• Date
• Particulars
• Voucher Type
• Voucher No.
• Voucher Ref. No.
• Gross Total

Despite the difference in complexity, both files ultimately represent the same commercial relationship.

The reconciliation requirement is:

Your Microsoft Dynamics Customer Ledger ↔ Naturals Salon Ledger

Cointab can compare the transactions and classify them into:

• Fully Matched
• Partially Matched
• Present in your Dynamics ledger but not found in Naturals Salon
• Present in Naturals Salon but not found in your Dynamics ledger
• Manually Matched

You can then investigate the exceptions, correct the relevant books, upload revised ledgers, and repeat the reconciliation whenever required.

---

Why reconcile your Naturals Salon customer account?

The balance shown against Naturals Salon in your accounting system may consist of many individual transactions.

These can include:

• Sales invoices
• Customer receipts
• Credit notes
• TDS-related entries
• Adjustments
• Previously outstanding invoices
• Transactions carried forward from earlier periods

Naturals Salon maintains its own view of the same account.

If both closing balances are different, simply knowing the total difference is not enough.

You need to understand:

• Which invoices exist in both books?
• Which invoice amounts agree?
• Which invoices are missing from Naturals Salon?
• Which transactions exist in Naturals Salon but not in your books?
• Has a receipt or adjustment already been applied?
• Is TDS responsible for part of the apparent difference?
• Which open transactions genuinely require customer follow-up?

A transaction-level reconciliation answers these questions.

---

Your Microsoft Dynamics NAV / Business Central customer ledger

Microsoft Dynamics can contain a large number of fields because the customer ledger is used for much more than reconciliation.

A typical export may include fields such as:

Your actual export may contain many additional accounting, GST, location, cost-centre, and product-related fields.

Most of those fields do not need to drive the primary invoice match.

They can remain available as supporting information when an exception needs investigation.

---

The Naturals Salon ledger is much simpler

The ledger received from Naturals Salon may contain:

This is a very different dataset from your Dynamics export.

One file may contain dozens of accounting attributes.

The other may contain only six relevant columns.

The reconciliation therefore should not depend on both datasets having the same structure.

It only needs to identify the information required to answer:

Do these two transactions represent the same invoice or customer entry?

---

You do not need to simplify your Dynamics file manually

A common approach would be to create another Excel workbook and manually reduce the Dynamics export to something like:

Then the finance team might clean the Naturals Salon file and create another similar table.

Only after that preparation would the actual reconciliation begin.

Cointab allows you to configure the relevant fields directly from each source file.

This means the reconciliation can work with:

Detailed Dynamics Ledger ↔ Simple Naturals Salon Ledger

without requiring both files to be converted into an identical template first.

---

How to reconcile Dynamics with Naturals Salon using Cointab

Start a new reconciliation in Cointab and select:

Customer Reconciliation

For this workflow:

• Side 1 = Your Microsoft Dynamics NAV / Business Central customer ledger
• Side 2 = Naturals Salon ledger

The process is:

Upload Dynamics Ledger → Upload Naturals Salon Ledger → Configure Fields → Run Reconciliation → Review Exceptions

---

Step 1: Upload your Dynamics customer ledger

Upload the customer ledger for Naturals Salon exported from Microsoft Dynamics.

Because the file may contain a very large number of columns, you only need to select the fields relevant to reconciliation.

Select the date

You may choose:

• Posting Date
• Document Date

depending on your reconciliation process.

Select transaction identifiers

Useful fields can include:

• External Document No.
• Document No.
• Custom Apply-to Doc.
• Narration
• Description

The exact choice depends on where your Naturals Salon invoice references are stored.

Select the amount

Configure the relevant amount field.

Depending on the export, this may include:

• Original Amount
• Amount
• Amount (LCY)

Cointab can then interpret the customer transactions without requiring the rest of the Dynamics columns to be removed.

---

Step 2: Upload the Naturals Salon ledger

Upload the ledger shared by Naturals Salon.

Select the date

Choose:

Date

Select transaction identifiers

Useful identifiers can include:

• Voucher Ref. No.
• Voucher No.
• Particulars
• Voucher Type

Select the amount

Configure:

Gross Total

as the relevant transaction amount.

The two files are now ready for comparison.

---

Step 3: Run Customer Reconciliation

Start the reconciliation.

Cointab analyzes the configured transaction references and financial values across both files.

The basic invoice-level logic is straightforward.

Fully Matched

The same invoice can be identified in both ledgers and the amounts agree.

Partially Matched

The invoice can be identified in both ledgers, but the amounts are different.

Unmatched

A corresponding transaction cannot be identified in the other ledger.

This turns a large customer ledger into a much smaller population of exceptions requiring investigation.

---

Fully Matched Naturals Salon invoices

Suppose your Dynamics ledger contains:

External Document No.: INV-48215

Original Amount: ₹1,80,000

The Naturals Salon ledger contains:

Voucher Ref. No.: INV-48215

Gross Total: ₹1,80,000

Both the reference and value agree.

Cointab classifies the transaction as:

Fully Matched

The finance team generally does not need to spend further time reconciling this invoice.

---

Partially Matched invoices

Suppose both ledgers contain:

INV-52784

but:

Microsoft Dynamics

Amount:

₹2,25,000

Naturals Salon

Gross Total:

₹2,20,000

The shared invoice reference tells Cointab that both records represent the same commercial transaction.

However, there is a:

₹5,000

difference.

The invoice is therefore:

Partially Matched

Your finance team can focus directly on understanding the ₹5,000 discrepancy.

---

What can cause an amount difference?

Possible causes include:

• Incorrect invoice value
• Credit note
• Debit adjustment
• Customer deduction
• TDS-related accounting
• Commercial adjustment
• Incorrect manual posting
• Different tax treatment
• Transaction recorded differently on the two sides

The useful part of Partial Match is that the invoice itself has already been located.

You only need to investigate why the amounts do not agree.

---

Invoice present in Dynamics but missing from Naturals Salon

Suppose your Dynamics ledger contains:

External Document No.: INV-68451

Original Amount: ₹3,10,000

but the Naturals Salon statement contains no corresponding Voucher Ref. No. or identifiable transaction.

Cointab reports:

Present in Your Ledger but not in Naturals Salon

Possible reasons include:

• Naturals Salon has not booked the invoice
• Invoice processing is pending
• Different reference was used
• Transaction belongs to another accounting period
• Invoice is under dispute
• Invoice was missed

You can share these specific transactions with the Naturals Salon finance team.

---

Transaction present in Naturals Salon but missing from Dynamics

The reverse situation can also occur.

Naturals Salon may contain:

Voucher Ref. No.: CN-4521

Gross Total: ₹28,000

while your Dynamics customer ledger contains no corresponding entry.

Cointab reports:

Present in Naturals Salon but not in Your Ledger

Your finance team can investigate whether:

• Credit note needs to be recorded
• Customer adjustment is missing
• Receipt has not been applied
• Transaction exists under another reference
• Naturals Salon's entry requires clarification

This gives you a clear internal action item.

---

External Document No. can be particularly useful for invoice matching

Your Dynamics ledger contains:

External Document No.

This can be one of the most useful fields for customer reconciliation.

The internal Dynamics:

Document No.

is generated by your own accounting system.

Naturals Salon may generate its own:

Voucher No.

These two internal numbers are not expected to match.

For example:

Microsoft Dynamics

Document No.:

SI-0098542

External Document No.:

INV-68214

Naturals Salon

Voucher No.:

PV-47528

Voucher Ref. No.:

INV-68214

The common commercial reference is:

INV-68214

not the internal voucher numbers.

---

Voucher Ref. No. can connect Naturals Salon back to your invoice

The Naturals Salon ledger includes:

Voucher Ref. No.

This field can provide the external invoice reference corresponding to your transaction.

For example:

Your External Document No.:

INV-74251

Naturals Salon Voucher Ref. No.:

INV-74251

Even if:

• Voucher numbers differ
• Document numbers differ
• Posting dates differ

the common invoice reference provides a strong basis for matching the two records.

---

Particulars can contain useful transaction references

Not every invoice number is always available in a clean reference field.

For example, Naturals Salon Particulars may contain:

Against invoice 75281

while your Dynamics Narration contains:

Naturals INV 75281

The common identifier is:

75281

A manual Excel process may require the finance team to:

• Search descriptions
• Split text
• Create helper columns
• Use text formulas
• Standardize references

Cointab can use AI-assisted processing to identify useful references contained inside the configured ledger fields.

---

AI-assisted identifier extraction reduces preparation work

Suppose your Dynamics narration contains:

NAT SALON INV NS/24/85621

while Naturals Salon Particulars contains:

Purchase Ref 85621

A strict exact-text lookup may not connect these records.

AI-assisted identifier extraction can help identify the underlying transaction reference from the descriptive fields and use it during matching.

This is useful when:

• Prefixes differ
• Invoice formatting differs
• Descriptions contain additional text
• Reference numbers are embedded in narration

---

Manual Match for transactions you know are the same

Some genuine transactions may still remain unmatched.

For example:

Dynamics

Narration:

Naturals Adjustment Aug

Amount:

₹32,500

Naturals Salon

Voucher Ref. No.:

DN-7842

Gross Total:

₹32,500

Your finance team may know from supporting documents that both records represent the same adjustment.

Cointab provides a:

Manual Match

option.

You can:

1. Select the Dynamics transaction.
2. Select the corresponding Naturals Salon transaction.
3. Review both entries.
4. Confirm the relationship.

The transaction is then recorded as manually reconciled.

---

Use the detailed Dynamics fields for investigation, not necessarily matching

One advantage of the detailed Dynamics file is that once an exception has been identified, your finance team has considerably more information available for investigation.

For example, an unmatched invoice may also show:

• Due Date
• Remaining Amount
• Open status
• Dispute Status
• Branch Code
• Location information
• External Document No.
• Apply-to document information

These fields may not be necessary to find the original match.

But they can help explain why the item remains unresolved.

---

Remaining Amount can show whether the invoice is still open

Microsoft Dynamics provides fields such as:

• Remaining Amount
• Remaining Amt. (LCY)

These can be very useful after invoice matching.

Suppose:

Original Amount

₹5,00,000

Remaining Amount

₹1,20,000

This tells you that part of the original transaction has already been applied or settled.

If Naturals Salon's ledger shows a different remaining economic position, the issue may relate to:

• Receipt allocation
• Credit note
• Customer deduction
• TDS
• Other settlement activity

The reconciliation therefore helps separate invoice recognition from open-balance investigation.

---

Open status tells you whether Dynamics still treats the transaction as outstanding

The Dynamics ledger can contain:

Open

This provides another useful clue.

An invoice can be:

Fully Matched

because both parties agree on the invoice number and amount.

But the Dynamics entry may still be:

Open

This means invoice reconciliation and payment settlement are two different questions.

Reconciliation asks:

Does Naturals Salon recognize the same invoice?

Receivables asks:

Has that invoice actually been settled?

Keeping these questions separate makes customer-account investigation clearer.

---

Due Date helps distinguish reconciliation from collections

The Dynamics file also contains:

Due Date

Suppose two invoices are Fully Matched.

Invoice A

Due Date: Next month

Invoice B

Due Date: 45 days ago

Both invoices reconcile correctly.

But Invoice B may require collection follow-up.

This means an outstanding invoice does not automatically represent a reconciliation error.

It may simply be an agreed customer receivable that has not yet been paid.

---

TDS can create differences between invoice and cash settlement

Your Dynamics customer ledger contains several TDS-related fields, including information such as:

• TDS Certificate Amount
• TDS Certificate Receivable
• TDS Certificate Received
• TDS Certificate Receipt Date
• TDS Section Code

These fields can become relevant when the amount ultimately received from the customer differs from the gross invoice value.

For example:

Invoice

₹1,00,000

Customer payment

₹98,000

TDS

₹2,000

The ₹2,000 difference may not represent a customer short payment.

It may represent withholding that needs to be accounted for separately.

This is why invoice reconciliation and cash-receipt matching should not always assume:

Invoice Amount = Cash Received

---

TDS certificate status can help explain old open balances

An invoice may be commercially settled while part of the balance remains associated with TDS accounting or certificate tracking.

Your Dynamics data may contain information indicating whether:

• TDS certificate is expected
• Certificate has been received
• Certificate amount has been recorded

This can help finance teams understand why a transaction still appears partly open or requires follow-up.

The Naturals Salon reconciliation therefore can lead to a more detailed internal review once the invoice-level match has been established.

---

Dispute Status can help prioritize reconciliation exceptions

The Dynamics ledger may also contain:

Dispute Status

This can help distinguish a simple unmatched accounting entry from a known commercial dispute.

For example:

Invoice A

Unmatched
Dispute Status: No dispute

Invoice B

Unmatched
Dispute Status: Under dispute

The investigation path for the two transactions may be different.

Invoice A may simply be missing from the customer's books.

Invoice B may already be part of an ongoing commercial discussion.

---

Custom Apply-to Doc. can help trace payments and adjustments

Dynamics may contain:

Custom Apply-to Doc.

or another application reference showing which transaction a receipt, credit, or adjustment has been applied against.

This can provide valuable information when the invoice exists in both systems but the open balances differ.

For example:

Invoice → Customer receipt → Applied document

Understanding the application relationship can help determine whether the difference is caused by:

• Missing receipt
• Incorrect allocation
• Credit applied against another invoice
• Customer-side adjustment

---

Example: invoice matches but remains partly open

Suppose:

Dynamics

External Document No.:

INV-58421

Original Amount:

₹2,00,000

Remaining Amount:

₹50,000

Naturals Salon

Voucher Ref. No.:

INV-58421

Gross Total:

₹2,00,000

The invoice itself is:

Fully Matched

because both parties agree that the original invoice value is ₹2,00,000.

The ₹50,000 remaining in Dynamics is a separate settlement issue.

The finance team can now investigate:

• Customer receipt
• TDS
• Credit note
• Adjustment
• Other outstanding component

without confusing it with the original invoice match.

---

Example: invoice is missing from Naturals Salon

Your Dynamics ledger contains:

External Document No.: INV-69425

Original Amount: ₹1,65,000

No corresponding Voucher Ref. No. or identifiable transaction exists in the Naturals Salon ledger.

Cointab reports:

Present in Your Ledger but not in Naturals Salon

You can share the invoice details with their finance team for investigation.

---

Example: same invoice but different gross amount

Suppose:

Dynamics

External Document No.:

INV-78214

Original Amount:

₹3,25,000

Naturals Salon

Voucher Ref. No.:

INV-78214

Gross Total:

₹3,18,000

The common reference identifies the transaction.

The:

₹7,000

difference means it is:

Partially Matched

The finance team can investigate the difference directly.

---

Example: different internal voucher numbers but same invoice

Your Dynamics file shows:

Document No.: SI-0085421

External Document No.: INV-85214

Naturals Salon shows:

Voucher No.: JV-75482

Voucher Ref. No.: INV-85214

The two internal accounting document numbers are unrelated.

But the common invoice reference makes the relationship clear.

This is why customer reconciliation should focus on the underlying commercial identifier instead of forcing internal voucher numbers to agree.

---

Example: Naturals Salon transaction missing internally

Suppose the Naturals Salon ledger contains:

Voucher Ref. No.: CN-7845

Gross Total: ₹40,000

but there is no corresponding transaction in your Dynamics ledger.

Cointab reports:

Present in Naturals Salon but not in Your Ledger

Your finance team can investigate:

• Is there a valid credit note?
• Is the adjustment already booked under another document?
• Is the customer's transaction incorrect?
• Does an internal accounting entry need to be created?

---

Why a large ERP file does not make reconciliation more difficult in Cointab

A Dynamics customer ledger may contain dozens of columns.

That does not mean your finance team should reconcile all of them.

Most reconciliation workflows need a smaller set of core information:

• Date
• Transaction identifiers
• Debit / credit or amount
• Supporting reference fields

The other columns remain useful when an exception needs explanation.

This means you can preserve the richness of your ERP export without forcing the reconciliation itself to become unnecessarily complicated.

---

From hundreds of ERP fields to a simple exception list

The practical objective is to reduce:

Detailed Dynamics Customer Ledger + Naturals Salon Statement

into:

• Invoices that agree
• Invoices with value differences
• Transactions missing from Naturals Salon
• Transactions missing from Dynamics
• Transactions requiring manual review

Your finance team can then use the richer Dynamics fields only for the exceptions that actually need investigation.

This is much more efficient than manually reviewing every ERP column for every transaction.

---

Know which party needs to take action

Once the reconciliation is complete, the unmatched transactions can be divided into two practical worklists.

Present in Dynamics but not in Naturals Salon

These may require customer-side follow-up.

For example:

• Invoice not booked
• Different invoice reference
• Entry pending
• Invoice under dispute

Present in Naturals Salon but not in Dynamics

These usually require internal investigation first.

For example:

• Credit adjustment missing
• Receipt not applied
• Customer-side deduction
• Accounting entry missing
• Transaction booked under another reference

The reconciliation becomes an action list rather than simply a report showing a balance difference.

---

Download the complete Naturals Salon reconciliation in Excel

Once you have reviewed the results, download the complete reconciliation working from Cointab.

The Excel output can contain:

• Fully Matched transactions
• Partially Matched transactions
• Unmatched transactions
• Manual Matches
• Relevant Dynamics fields
• Relevant Naturals Salon fields

The finance team can use the output for:

• Accounts receivable review
• Customer follow-up
• Month-end reconciliation
• Balance confirmation
• Internal accounting corrections
• Audit support
• Historical exception tracking

---

Use specific transaction differences when following up with Naturals Salon

Without transaction-level reconciliation, customer communication may simply say:

"Our balance does not agree with yours."

That can result in both finance teams comparing the entire ledger again.

With the reconciliation, you can instead say:

• Invoice INV-4521 does not appear in your ledger.
• Invoice INV-5842 differs by ₹7,000.
• Credit CN-7845 appears in your ledger but not ours.
• These three older invoices remain unmatched.

This makes customer follow-up considerably more precise.

---

Correct the books and run the reconciliation again

Once the differences have been investigated:

• Your Dynamics ledger may be updated
• Naturals Salon may correct an entry
• Missing invoice may be booked
• Credit may be recorded
• Payment may be applied
• TDS entry may be corrected

Upload the latest files to Cointab.

The reconciliation runs again using the revised information.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as both books become aligned.

---

Repeat the Naturals Salon reconciliation every month

If you transact regularly with Naturals Salon, the customer ledger continuously changes.

Each month can introduce:

• New invoices
• New payments
• Credits
• TDS-related entries
• Adjustments
• Previously open transactions

The same reconciliation can therefore be reused.

A typical monthly process becomes:

1. Export the latest Naturals Salon customer ledger from Dynamics NAV / Business Central.
2. Obtain the latest ledger from Naturals Salon.
3. Upload your Dynamics ledger to Cointab.
4. Select the relevant date, identifier, and amount fields.
5. Upload the Naturals Salon ledger.
6. Configure Voucher Ref. No., Particulars, and Gross Total.
7. Run Customer Reconciliation.
8. Review Fully Matched transactions.
9. Investigate Partially Matched invoices.
10. Review transactions present only in Dynamics.
11. Review transactions present only in Naturals Salon.
12. Complete Manual Matches where required.
13. Use Remaining Amount, Open Status, TDS, and Due Date for deeper investigation where relevant.
14. Download the reconciliation working.
15. Correct internal transactions.
16. Follow up with Naturals Salon on customer-side exceptions.
17. Upload revised ledgers and reconcile again.

---

Previously open items can reconcile in later periods

Timing differences are common in customer accounts.

For example:

July

You raise an invoice and record it in Dynamics.

Naturals Salon has not yet booked it.

The transaction appears unmatched.

August

The invoice appears in the latest Naturals Salon ledger.

Cointab can now reconcile it against the previously open Dynamics transaction.

The same can happen with:

• Customer receipts
• Credit notes
• TDS entries
• Adjustments

This allows the reconciliation to evolve as both accounting systems are updated.

---

Reconcile a detailed Business Central ledger with a simple customer statement

One of the main advantages of this workflow is that both files do not need to look alike.

Your Dynamics customer ledger may contain dozens of fields covering:

• Finance
• GST
• TDS
• Customer applications
• Product information
• Cost centres
• Locations
• Open items

Naturals Salon may send a six-column ledger.

Cointab lets you identify the relevant reconciliation fields from each dataset and compare them directly.

The reconciliation can therefore remain simple even when the underlying ERP is complex.

---

How Cointab helps reconcile Dynamics with Naturals Salon

Cointab's Customer Reconciliation workflow allows you to:

• Upload your Microsoft Dynamics NAV / Business Central customer ledger
• Upload the Naturals Salon ledger
• Work with different source-file structures
• Select only the Dynamics fields relevant for matching
• Use External Document No. as a commercial invoice identifier
• Use Voucher Ref. No. from Naturals Salon
• Use Narration and Particulars as supporting identifiers
• Extract useful references from transaction descriptions
• Automatically identify corresponding invoices
• Separate Fully Matched transactions
• Identify invoices with amount differences
• Identify transactions present only in Dynamics
• Identify transactions present only in Naturals Salon
• Review Remaining Amount and Open status for unresolved receivables
• Use TDS information while investigating settlement differences
• Manually match genuine transactions with inconsistent references
• Download the complete reconciliation working in Excel
• Upload revised ledgers and reconcile again
• Continue reconciling open transactions across future periods

---

Automate Microsoft Dynamics vs Naturals Salon customer reconciliation

If you supply Naturals Salon Private Limited and currently compare their ledger manually against your Microsoft Dynamics NAV or Business Central customer account, Cointab can automate much of the repetitive reconciliation work.

The process becomes:

Dynamics Customer Ledger → Naturals Salon Ledger → Automated Matching → Exception Review → Corrections → Updated Reconciliation

You can quickly identify:

• Invoices that agree
• Invoices with amount differences
• Invoices missing from either side
• Customer adjustments requiring review
• Open receivables requiring investigation
• Transactions where TDS may explain the settlement difference

Even if your Dynamics export contains dozens of accounting columns while the Naturals Salon statement contains only a few fields, both can be reconciled without manually rebuilding them into an identical Excel format.

The complete reconciliation can then be downloaded in Excel and used for internal review or customer follow-up.

If you currently reconcile your Naturals Salon customer account manually using Microsoft Dynamics and Excel, you can use Cointab to automate the process.

Try Cointab

For customized Dynamics exports, larger customer ledgers, or more complex accounts receivable reconciliation requirements:

Book a Demo