If your company supplies products to Lifestyle International Pvt. Ltd. and maintains the customer account in Microsoft Dynamics NAV or Dynamics 365 Business Central, your finance team may periodically need to reconcile your Lifestyle receivable ledger with the statement received from their finance team.

Your Microsoft Dynamics ledger may contain a very detailed customer-account history.

Lifestyle's ledger can be much more concise.

Your Dynamics export may include information such as:

• Posting Date
• Document Date
• Document Type
• Document No.
• External Document No.
• Original Amount
• Remaining Amount
• Due Date
• Open status
• TDS information
• Customer application references
• Narration
• Description

The Lifestyle ledger may instead contain fields such as:

• GL Date
• Voucher No.
• Invoice Type
• Pay Group
• Inv Check Num
• Inv Check Date
• Currency
• INR Amount
• Description

Although the files look very different, both ultimately represent transactions belonging to the same customer relationship.

The reconciliation requirement is:

Microsoft Dynamics NAV / Business Central Customer Ledger ↔ Lifestyle International Ledger

Cointab can compare both datasets and automatically classify transactions into:

• Fully Matched
• Partially Matched
• Present in Microsoft Dynamics but not found in Lifestyle
• Present in Lifestyle but not found in Microsoft Dynamics
• Manually Matched

The resulting customer reconciliation can then be downloaded in Excel, shared internally or with Lifestyle, corrected, and rerun using updated ledgers.

---

Why reconcile your Lifestyle International customer account?

If you regularly supply Lifestyle International, your Microsoft Dynamics customer account may contain transactions across several accounting periods.

These can include:

• New sales invoices
• Customer receipts
• Credit notes
• Returns
• TDS-related entries
• Adjustments
• Previously unpaid invoices
• Older reconciliation differences

Lifestyle maintains the same commercial relationship from its own accounting perspective.

Your receivable balance and Lifestyle's payable records should ultimately agree.

If they do not, the finance team needs to understand exactly which transactions are responsible.

For example:

• Has Lifestyle booked every invoice you raised?
• Is the invoice amount the same in both systems?
• Has Lifestyle recorded a payment that is not applied in Dynamics?
• Does their voucher number differ from your Dynamics document number?
• Is an invoice associated with a payment/check reference you do not recognize?
• Is a customer-side credit or adjustment missing internally?

A transaction-level reconciliation answers these questions much more effectively than comparing only the closing balances.

---

What does your Microsoft Dynamics customer ledger contain?

Microsoft Dynamics NAV / Business Central can provide a highly detailed customer-ledger export.

For Lifestyle reconciliation, some of the most useful fields may include:

Your actual Dynamics file may contain many more fields relating to:

• GST
• Product categories
• Branches
• Cost centres
• Profit centres
• Location
• State
• TDS certificates
• Customer applications

You do not need to reconcile every one of these columns.

Cointab allows you to choose the fields that matter for matching while retaining the remaining data for investigation.

---

What does the Lifestyle International ledger contain?

The Lifestyle ledger may have a much simpler structure:

This creates an interesting reconciliation situation.

Your Microsoft Dynamics file may contain dozens of columns.

Lifestyle may provide fewer than ten.

But both files can still be reconciled because the objective is not to make the spreadsheets look identical.

The objective is to find the same underlying commercial transactions.

---

Lifestyle reconciliation is a reference-and-amount matching problem

For this reconciliation, the most useful relationship may often be between:

Dynamics invoice or external reference ↔ Lifestyle invoice/check reference

For example:

Microsoft Dynamics

External Document No.:

INV-784521

Amount:

₹2,40,000

Lifestyle

Inv Check Num:

INV-784521

INR Amount:

₹2,40,000

The internal accounting structures are different.

But the same commercial invoice can still be identified.

This is the core purpose of the reconciliation.

---

Lifestyle Voucher No. does not need to match your Dynamics Document No.

One of the easiest mistakes in a manual Excel reconciliation is to assume:

Dynamics Document No. = Lifestyle Voucher No.

These are internal accounting identifiers generated independently by each organization.

For example:

Microsoft Dynamics

Document No.:

SI-0098521

External Document No.:

INV-68215

Lifestyle

Voucher No.:

2400068741

Inv Check Num:

INV-68215

The internal numbers:

SI-0098521

and:

2400068741

have no relationship.

The common commercial reference is:

INV-68215

A reconciliation based purely on internal document numbers would incorrectly classify this invoice as unmatched.

---

How to reconcile Microsoft Dynamics with Lifestyle International using Cointab

Start a new reconciliation in Cointab and choose:

Customer Reconciliation

For this workflow:

• Side 1 = Your Microsoft Dynamics NAV / Business Central Lifestyle customer ledger
• Side 2 = Lifestyle International ledger

The process becomes:

Upload Dynamics Ledger → Upload Lifestyle Ledger → Configure Dates, References and Amounts → Run Reconciliation → Review Exceptions

---

Step 1: Upload the Microsoft Dynamics customer ledger

Export the Lifestyle customer account from Microsoft Dynamics NAV / Business Central.

Upload the file into Cointab.

Select the date

Depending on your accounting process, choose a relevant field such as:

• Posting Date
• Document Date

Select transaction identifiers

Useful fields may include:

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

You can configure more than one identifier field.

This is useful because invoice or payment information may be recorded differently across various Dynamics transactions.

Configure the amount

Select the relevant financial value, such as:

• Original Amount
• Amount
• Amount (LCY)

The Lifestyle side can then be compared against the appropriate Dynamics amount.

---

Step 2: Upload the Lifestyle International ledger

Upload the Lifestyle file.

Select the transaction date

A useful field may be:

GL Date

or, depending on the transaction:

Inv Check Date

Select transaction identifiers

Useful Lifestyle identifiers may include:

• Inv Check Num
• Voucher No.
• Description

Configure the amount

Select:

INR Amount

for INR-denominated transaction comparison.

The file also contains:

Currency

which provides additional context where transactions involve different currencies.

---

Step 3: Run Customer Reconciliation

Start the reconciliation.

Cointab analyzes the selected identifiers and financial values across both ledgers.

At invoice level, the process asks:

1. Can the same invoice be identified in Dynamics and Lifestyle?
2. If it exists in both datasets, do the values agree?

Transactions can then be separated into:

• Fully Matched
• Partially Matched
• Dynamics-only
• Lifestyle-only
• Manual Matches

---

Fully Matched Lifestyle invoices

An invoice is Fully Matched when it can be identified in both ledgers and there is no amount difference.

For example:

Microsoft Dynamics

External Document No.:

INV-74215

Original Amount:

₹1,85,000

Lifestyle

Inv Check Num:

INV-74215

INR Amount:

₹1,85,000

Both records represent the same invoice and the financial values agree.

Cointab reports:

Fully Matched

The finance team normally does not need to investigate this invoice further as part of invoice reconciliation.

---

Partially Matched Lifestyle invoices

The same invoice may exist in both datasets while the recorded values differ.

For example:

Dynamics

External Document No.:

INV-74215

Amount:

₹1,85,000

Lifestyle

Inv Check Num:

INV-74215

INR Amount:

₹1,80,000

The common invoice reference establishes the relationship.

However, there is a:

₹5,000

difference.

Cointab therefore classifies the transaction as:

Partially Matched

The finance team can focus directly on the ₹5,000 difference.

---

What can cause an amount difference?

Possible causes include:

• Invoice booked at an incorrect amount
• Customer deduction
• Credit note
• Debit adjustment
• Product return
• Pricing difference
• TDS-related accounting
• Commercial adjustment
• Incorrect posting
• Transaction split across several records

Because Cointab has already identified the invoice, the finance team does not need to spend time determining whether the transaction exists.

The investigation can start with the amount difference itself.

---

Invoice present in Microsoft Dynamics but missing from Lifestyle

Suppose your Dynamics customer ledger contains:

External Document No.: INV-86215

Amount: ₹3,10,000

but no matching Lifestyle record can be found.

Cointab reports:

Present in Microsoft Dynamics but not in Lifestyle

Possible explanations include:

• Lifestyle has not yet booked the invoice
• Invoice processing is pending
• Lifestyle recorded another reference
• Transaction belongs to another accounting period
• Invoice is under review
• Invoice was missed

This creates a specific customer-side reconciliation exception.

---

Transaction present in Lifestyle but missing from Microsoft Dynamics

The reverse situation can also occur.

Lifestyle may contain:

Inv Check Num: CN-7842

INR Amount: ₹32,000

while no corresponding Dynamics entry can be identified.

Cointab reports:

Present in Lifestyle but not in Microsoft Dynamics

Your finance team can investigate whether:

• Credit note is missing
• Customer adjustment has not been recorded
• Receipt is unallocated
• Transaction exists under another Dynamics reference
• Lifestyle's entry needs clarification

This becomes an internal accounting action item.

---

Inv Check Num can be an important Lifestyle reference

One of the distinctive fields in the Lifestyle ledger is:

Inv Check Num

Depending on the transaction, this can provide a useful link back to the commercial invoice or payment-related record.

For reconciliation, this field may be compared against references such as:

• Dynamics External Document No.
• Dynamics Document No.
• Reference embedded in Narration
• Reference embedded in Description

The exact relationship can vary across transaction types.

---

Inv Check Date provides useful timing context

Lifestyle also provides:

Inv Check Date

This can help when the invoice or payment reference is correct but the accounting dates differ.

For example:

Dynamics

Document Date:

29 July

Posting Date:

30 July

Lifestyle

GL Date:

2 August

Inv Check Date:

29 July

The two systems may still be referring to the same transaction.

The different GL posting date can simply reflect the customer's processing timeline.

A reconciliation should therefore not require every date to match exactly.

---

GL Date and Dynamics Posting Date may legitimately differ

Suppose you post an invoice in Dynamics on:

31 March

Lifestyle records it in its GL on:

2 April

A simple reconciliation based on exact posting dates could treat the transaction as different.

But if:

• Invoice reference agrees
• Amount agrees
• Supporting description agrees

the transaction may still represent a valid match.

Cointab allows identifiers and financial values to drive the relationship instead of relying entirely on identical dates.

---

Pay Group provides additional context

Lifestyle's ledger includes:

Pay Group

This may provide useful context about how the transaction is grouped or processed for payment.

It may not be the primary invoice-matching field.

However, once an exception has been identified, Pay Group can help distinguish transactions handled through different payment classifications or customer processes.

This is particularly useful when several invoices have similar:

• Dates
• Values
• Descriptions

but belong to different payment groups.

---

Invoice Type helps identify what kind of transaction is being reviewed

Lifestyle also provides:

Invoice Type

When a transaction remains unmatched, this field can help the finance team determine its nature.

The row may relate to:

• Standard invoice
• Credit
• Adjustment
• Another invoice classification

This matters because not every Lifestyle-only transaction should automatically be treated as a missing sales invoice.

Understanding its type helps determine what corresponding Dynamics entry should exist.

---

Currency and INR Amount simplify local-currency reconciliation

The Lifestyle ledger contains both:

• Currency
• INR Amount

Your Microsoft Dynamics ledger similarly contains local-currency information through fields such as:

• Amount (LCY)
• Remaining Amt. (LCY)
• Currency Code

This provides a useful basis for comparing transactions in a common currency.

For example, if the Lifestyle transaction is reported in INR and your Dynamics ledger contains the equivalent local-currency amount, the financial values can be compared consistently.

Currency also provides another safeguard against matching unrelated transactions that happen to have the same numerical amount.

---

Do not rely only on amount matching

Suppose the Lifestyle ledger contains five invoices for:

₹1,00,000

and your Dynamics ledger contains several transactions for the same value.

Amount alone is not enough to determine the correct match.

Useful additional information can include:

• External Document No.
• Inv Check Num
• GL Date
• Document Date
• Invoice Type
• Description
• Narration
• Currency

Cointab can use combinations of identifiers and conditions to avoid creating false matches between unrelated transactions.

---

Lifestyle Description can provide another route to the invoice reference

The Lifestyle ledger also includes:

Description

This may contain additional information about:

• Invoice
• Payment
• Credit
• Adjustment

For example:

Lifestyle

Inv Check Num:

Blank

Description:

Against invoice 85214

Dynamics

External Document No.:

INV-85214

The commercial reference is still available even though it is embedded in descriptive text.

---

AI-assisted identifier extraction from Dynamics Narration and Lifestyle Description

Accounting teams do not always enter references in standardized formats.

For example:

Microsoft Dynamics Narration

Lifestyle INV LS/24/86521

Lifestyle Description

Invoice 86521

The relevant common identifier is:

86521

A manual spreadsheet reconciliation may require:

• Text cleaning
• Helper columns
• FIND formulas
• MID formulas
• Manual searches

Cointab can use AI-assisted processing to extract useful transaction identifiers from selected text fields and use them during reconciliation.

---

Reconcile payments separately from invoices

Customer reconciliation involves more than invoice recognition.

An invoice may be fully matched but still remain outstanding.

The finance team also needs to understand whether Lifestyle's payment-related transaction has been recorded and applied correctly in Dynamics.

This creates two related questions:

Invoice reconciliation

Does Lifestyle recognize the same invoice for the same value?

Settlement reconciliation

Has the corresponding customer payment or adjustment been correctly reflected in Dynamics?

Keeping these separate helps explain customer outstanding balances more accurately.

---

One Lifestyle payment may settle multiple invoices

Large customers frequently make consolidated payments.

Suppose Lifestyle has the following invoices:

• Invoice A — ₹1,00,000
• Invoice B — ₹1,20,000
• Invoice C — ₹80,000
• Invoice D — ₹2,00,000

Lifestyle may make a single payment of:

₹5,00,000

Your Dynamics customer ledger may therefore contain:

One customer receipt

while several invoice records become settled.

Similarly:

• One invoice may be paid through several transactions
• Credits may be adjusted against invoices
• Payment may be net of TDS or another adjustment

This means customer reconciliation cannot always depend on a one-invoice-to-one-payment relationship.

---

Remaining Amount in Dynamics helps identify settlement issues

Your Microsoft Dynamics ledger contains:

Remaining Amount

and:

Remaining Amt. (LCY)

These fields become useful after an invoice has been matched.

For example:

Dynamics

Original Amount:

₹4,00,000

Remaining Amount:

₹75,000

Lifestyle

Invoice value:

₹4,00,000

The invoice itself may be:

Fully Matched

But ₹75,000 remains open internally.

The finance team can now investigate:

• Partial payment
• Credit adjustment
• TDS
• Customer deduction
• Incorrect application

The original invoice match and the remaining receivable are therefore separate issues.

---

Open status tells you whether Dynamics still considers the item unsettled

Dynamics contains an:

Open

field.

This makes it possible for a transaction to be:

Fully Matched in reconciliation

but:

Open in Microsoft Dynamics

That is not necessarily contradictory.

It simply means:

• Both parties agree that the invoice exists
• The invoice has not yet been fully settled in your books

This distinction is important when reviewing accounts receivable.

---

Due Date helps distinguish customer reconciliation from collections

Dynamics also contains:

Due Date

Suppose an invoice is Fully Matched with Lifestyle.

If its due date is next month, it may simply be a normal open receivable.

If it has been overdue for 60 days, it may require collection follow-up.

Reconciliation therefore answers:

Do our books agree?

Collections answers:

Has Lifestyle paid the agreed invoice when due?

The two processes should not be confused.

---

TDS can explain why payment is lower than the invoice

Your Microsoft Dynamics ledger contains detailed TDS-related information.

For example:

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

Suppose:

Invoice

₹1,00,000

Customer payment

₹98,000

TDS

₹2,000

The ₹2,000 difference may be legitimate withholding rather than a short payment.

Once the Lifestyle invoice has been matched, the Dynamics TDS information can help your finance team explain the remaining settlement difference.

---

Customer deduction and TDS are not the same

A lower receipt can be caused by several different things.

For example:

• TDS
• Credit note
• Product return
• Rate difference
• Commercial deduction
• Unexplained short payment

A reconciliation should therefore not simply assume:

Invoice Amount - Receipt = Error

The finance team needs to identify the transaction relationship first and then understand the components of the settlement.

---

Manual Match for Lifestyle transactions with different references

Some genuine transactions may remain unmatched because the references are too different for a confident automatic match.

For example:

Microsoft Dynamics

Narration:

Lifestyle Commercial Adj Aug

Amount:

₹45,000

Lifestyle

Voucher No.:

2400874521

Description:

Rate Adjustment

INR Amount:

₹45,000

Your finance team may know from supporting documents that both entries represent the same transaction.

Cointab provides a:

Manual Match

option.

You can:

1. Select the Dynamics transaction.
2. Select the corresponding Lifestyle transaction.
3. Review the records.
4. Confirm the match.

The relationship is then recorded in the reconciliation.

---

Manual Match helps resolve historical open items

Older customer accounts frequently contain:

• Manual journal entries
• Old credit notes
• Incomplete references
• Legacy invoice formats
• Rebooked transactions
• Payment adjustments

These transactions may be difficult to reconcile automatically.

Manual Match allows the finance team to resolve the genuine relationship without modifying the original Microsoft Dynamics or Lifestyle source files.

---

Example: fully matched Lifestyle invoice

Microsoft Dynamics

External Document No.:

INV-98521

Original Amount:

₹2,15,000

Lifestyle

Inv Check Num:

INV-98521

INR Amount:

₹2,15,000

The invoice reference and amount agree.

Cointab reports:

Fully Matched

---

Example: invoice reference matches but the amount is different

Microsoft Dynamics

External Document No.:

INV-62418

Amount:

₹3,20,000

Lifestyle

Inv Check Num:

INV-62418

INR Amount:

₹3,12,500

The transaction is:

Partially Matched

Difference:

₹7,500

The finance team can investigate the specific amount discrepancy.

---

Example: Dynamics invoice is missing from Lifestyle

Your Microsoft Dynamics ledger contains:

External Document No.: INV-75214

Amount: ₹1,90,000

Lifestyle contains no identifiable corresponding transaction.

Cointab reports:

Present in Microsoft Dynamics but not in Lifestyle

You can provide Lifestyle's finance team with:

• Invoice reference
• Invoice date
• Amount
• Supporting details

for investigation.

---

Example: Lifestyle transaction is missing from Dynamics

Lifestyle contains:

Inv Check Num: CN-8452

Invoice Type: Credit

INR Amount: ₹38,000

Your Dynamics customer ledger contains no corresponding credit.

Cointab reports:

Present in Lifestyle but not in Microsoft Dynamics

Your internal team can investigate whether:

• Credit note needs to be booked
• Customer deduction is valid
• Entry exists under another reference
• Lifestyle's transaction requires clarification

---

Example: Lifestyle voucher differs but invoice reference agrees

Microsoft Dynamics

Document No.:

SI-0087452

External Document No.:

INV-58214

Lifestyle

Voucher No.:

2400078451

Inv Check Num:

INV-58214

The voucher numbers are different.

That is expected.

The common invoice reference allows the transaction to reconcile.

---

Example: dates differ but the transaction is valid

Microsoft Dynamics

Document Date:

30 June

Posting Date:

30 June

External Document No.:

INV-78214

Lifestyle

Inv Check Date:

30 June

GL Date:

3 July

Inv Check Num:

INV-78214

The posting dates differ, but the invoice reference, original date, and amount can still establish that these records represent the same transaction.

---

Example: invoice reference is embedded inside Lifestyle Description

Your Dynamics ledger contains:

External Document No.:

INV-96521

Lifestyle contains:

Inv Check Num: blank

Description:

Against invoice 96521

The identifier still exists in the customer data.

AI-assisted extraction can help identify this reference and use it during reconciliation.

---

Create separate internal and Lifestyle action lists

Once the automatic matching is complete, unmatched items can be split based on which side contains the transaction.

Present in Dynamics but not Lifestyle

These may require Lifestyle-side follow-up.

Examples:

• Invoice not booked
• Different customer reference
• Processing pending
• Invoice under review

Present in Lifestyle but not Dynamics

These usually require internal investigation first.

Examples:

• Credit missing
• Customer adjustment not booked
• Receipt not applied
• Transaction entered under another reference

This makes the reconciliation immediately actionable.

---

Download the complete Lifestyle International reconciliation in Excel

Once the reconciliation is reviewed, download the complete working from Cointab.

The Excel output can contain:

• Fully Matched transactions
• Partially Matched transactions
• Unmatched transactions
• Manual Matches
• Microsoft Dynamics source data
• Lifestyle source data

Fields such as:

• External Document No.
• Inv Check Num
• Voucher No.
• Invoice Type
• Pay Group
• GL Date
• INR Amount
• Remaining Amount
• Due Date

can provide useful context when investigating individual exceptions.

The output can be used for:

• Month-end customer reconciliation
• Accounts receivable review
• Lifestyle follow-up
• Balance confirmation
• Internal accounting corrections
• Audit working
• Open-item tracking

---

Use specific exceptions when communicating with Lifestyle

Without a transaction-level working, reconciliation communication may simply say:

"Our balance does not agree with yours."

That forces both finance teams to start reviewing the entire account.

A prepared reconciliation allows much more specific communication:

• Invoice INV-5821 does not appear in your ledger.
• Invoice INV-6418 differs by ₹7,500.
• Credit CN-8452 appears in your ledger but not ours.
• These three historic transactions remain unmatched.

This gives Lifestyle's finance team an exact list to investigate.

---

Correct the ledgers and reconcile again

Once exceptions are investigated:

• Lifestyle may record a missing invoice
• You may record a missing credit
• Customer payment may be applied
• Amount may be corrected
• Reference may be updated
• Old adjustment may be resolved

Upload the revised Microsoft Dynamics and Lifestyle ledgers into Cointab.

Run the reconciliation again.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as the underlying books become aligned.

---

Repeat Microsoft Dynamics vs Lifestyle reconciliation every month

If you supply Lifestyle International regularly, the customer account keeps changing.

Each accounting period can introduce:

• New invoices
• Customer payments
• Credits
• Returns
• TDS
• Adjustments
• Previously open transactions

The reconciliation can therefore become a reusable monthly process.

A typical workflow is:

1. Export the latest Lifestyle customer ledger from Microsoft Dynamics NAV / Business Central.
2. Obtain the latest Lifestyle International ledger.
3. Upload your Dynamics file into Cointab.
4. Configure Posting Date or Document Date.
5. Select External Document No., Document No., Narration, and other useful identifiers.
6. Configure the relevant Dynamics amount.
7. Upload the Lifestyle ledger.
8. Configure GL Date or Inv Check Date.
9. Select Inv Check Num, Voucher No., and Description as relevant identifiers.
10. Configure INR Amount.
11. Run Customer Reconciliation.
12. Review Fully Matched invoices.
13. Investigate Partially Matched transactions.
14. Review Dynamics-only transactions.
15. Review Lifestyle-only transactions.
16. Complete Manual Matches where required.
17. Download the reconciliation working.
18. Correct internal Dynamics entries.
19. Share customer-side exceptions with Lifestyle.
20. Upload revised ledgers and reconcile again.

---

Previously unmatched Lifestyle invoices can reconcile later

Not every unmatched invoice represents an error.

Some are timing differences.

For example:

July

You record an invoice in Microsoft Dynamics.

Lifestyle has not yet processed it.

The transaction appears:

Present in Microsoft Dynamics but not in Lifestyle

August

Lifestyle's latest ledger now contains the invoice under Inv Check Num.

Cointab can reconcile the new Lifestyle record against the previously open Dynamics transaction.

The same can happen with:

• Customer credits
• Payments
• Adjustments

This allows the reconciliation to continue naturally across periods.

---

Reconcile a detailed Microsoft Dynamics ledger against a concise Lifestyle ledger

One of the defining characteristics of this reconciliation is the difference in file complexity.

Your Microsoft Dynamics customer ledger may contain dozens of accounting, TDS, GST, product, customer, and settlement fields.

Lifestyle may send a file containing only:

GL Date → Voucher → Invoice Type → Pay Group → Invoice/Check Reference → Currency → Amount → Description

You do not need to manually transform both files into identical spreadsheets.

Cointab lets you select the relevant fields in each dataset and reconcile the underlying transactions directly.

The detailed Dynamics data remains available whenever an exception requires deeper investigation.

---

Move from ERP exports and manual lookups to exception management

A manual Lifestyle reconciliation may require the finance team to:

• Export Microsoft Dynamics
• Obtain the Lifestyle ledger
• Reduce the Dynamics file to relevant columns
• Compare voucher numbers
• Search invoice references
• Normalize amounts
• Review descriptions
• Compare dates
• Carry older open items forward
• Maintain reconciliation comments

Cointab changes the process to:

Upload Microsoft Dynamics → Upload Lifestyle → Run Reconciliation → Review Exceptions → Resolve Differences

The finance team can focus on the relatively small number of transactions that genuinely need investigation.

---

How Cointab helps reconcile Microsoft Dynamics with Lifestyle International

Cointab's Customer Reconciliation workflow allows you to:

• Upload your Microsoft Dynamics NAV / Business Central customer ledger
• Upload the Lifestyle International ledger
• Reconcile files with very different levels of detail
• Select only the Dynamics fields needed for matching
• Use External Document No. as a commercial invoice reference
• Use Lifestyle Inv Check Num as a corresponding identifier
• Use Voucher No. and Description as supporting references
• Map different transaction dates
• Compare local-currency transaction values
• Extract useful identifiers from Dynamics Narration and Lifestyle Description
• Automatically identify matching invoices
• Separate Fully Matched transactions
• Identify invoices with amount differences
• Identify Dynamics-only transactions
• Identify Lifestyle-only transactions
• Use Remaining Amount and Open status to investigate unresolved receivables
• Use TDS data when investigating payment differences
• Manually match genuine transactions with different references
• Download the complete reconciliation working in Excel
• Upload corrected ledgers and reconcile again
• Continue resolving open items across subsequent periods

---

Automate Microsoft Dynamics vs Lifestyle International customer reconciliation

If you supply Lifestyle International Pvt. Ltd. and currently reconcile their ledger manually against your Microsoft Dynamics NAV or Dynamics 365 Business Central customer account, Cointab can automate much of the repetitive reconciliation work.

The workflow becomes:

Microsoft Dynamics Customer Ledger → Lifestyle International Ledger → Automated Matching → Exception Review → Corrections → Updated Reconciliation

You can quickly identify:

• Invoices that agree
• Invoices with amount differences
• Invoices missing from Lifestyle
• Lifestyle transactions missing from Dynamics
• Customer credits and adjustments requiring investigation
• Transactions where Lifestyle uses a different voucher or invoice/check reference
• Older unresolved customer-account items

Even when your Microsoft Dynamics export contains dozens of fields and Lifestyle provides a much simpler ledger, Cointab can reconcile the two without requiring you to manually rebuild them into an identical Excel format.

The complete working can then be downloaded in Excel and used for internal review or follow-up with Lifestyle's finance team.

If your company uses Microsoft Dynamics NAV / Business Central and currently reconciles its Lifestyle International customer account manually in Excel, you can use Cointab to automate the process.

Try Cointab

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

Book a Demo