If your company supplies products to Reliance Tira / Reliance Retail and maintains the customer account in Microsoft Dynamics NAV or Dynamics 365 Business Central, your finance team may periodically need to reconcile the Reliance customer ledger in Dynamics with the ledger received from Reliance Retail.

Your Microsoft Dynamics customer ledger records transactions from your accounting perspective.

Reliance Retail maintains the same commercial relationship from its own accounting perspective.

Both ledgers should ultimately contain the corresponding:

• Sales invoices
• Payments
• Credit notes
• Debit notes
• Adjustments
• Outstanding transactions

However, even when both files are well structured, the transactions may not line up automatically.

Your Microsoft Dynamics ledger may contain:

• Customer Code
• Customer Name
• Document Type
• Posting Date
• Document Date
• Document Number
• Reference
• Debit Amount
• Credit Amount
• Description
• Narration

The Reliance Tira / Reliance Retail ledger may contain:

• Posting Date
• Document Date
• Customer Name
• Types
• Doc Number
• Reference
• Header Text
• Text details
• Debit
• Credit

The reconciliation requirement is therefore:

Microsoft Dynamics NAV / Business Central Customer Ledger ↔ Reliance Tira / Reliance Retail Ledger

Cointab can automatically compare both datasets and classify transactions into:

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

The complete reconciliation can then be downloaded in Excel and used for internal accounting corrections and follow-up with Reliance Retail.

---

Why reconcile your Dynamics customer ledger with Reliance Tira?

If you supply Reliance Tira regularly, the customer account maintained in Microsoft Dynamics may contain transactions across several accounting periods.

These can include:

• New sales invoices
• Old unpaid invoices
• Customer receipts
• Credit notes
• Returns
• Commercial adjustments
• Previous-period open items

Microsoft Dynamics may show one customer balance.

Reliance Retail may show another.

For example:

Dynamics customer balance: ₹52,40,000

Reliance Retail balance: ₹51,85,000

Difference: ₹55,000

The closing-balance difference only tells you that the ledgers disagree.

It does not tell you whether the ₹55,000 is caused by:

• An invoice Reliance has not booked
• A credit note missing from Dynamics
• An invoice amount difference
• A customer payment posted differently
• Several older open transactions

The purpose of customer reconciliation is to identify the exact transactions behind the difference.

---

What does the Microsoft Dynamics customer ledger contain?

The Microsoft Dynamics NAV / Business Central ledger used for Reliance Tira reconciliation may contain fields such as:

For reconciliation, useful identifiers may appear across:

• Document Number
• Reference
• Description
• Narration

The best identifier can vary by transaction.

A Reliance invoice number may be stored in Reference for one entry and inside Narration for another.

---

What does the Reliance Tira / Reliance Retail ledger contain?

The ledger received from Reliance may contain:

This is structurally similar to the Microsoft Dynamics ledger.

But the values within those fields are generated independently.

For example:

Dynamics Document Number

does not necessarily equal:

Reliance Doc Number

Each accounting system generates its own internal document numbers.

The common commercial reference may instead be available through:

• Reference
• Description
• Narration
• Header Text
• Text details

---

Why Microsoft Dynamics Document Number may not match Reliance Doc Number

Consider one sales invoice.

Microsoft Dynamics

Document Number:

SI-009842

Reference:

INV-784521

Reliance Retail

Doc Number:

5100874521

Reference:

INV-784521

The Dynamics document number and Reliance document number are completely different.

That is normal.

They are internal accounting identifiers generated independently by the two systems.

The common commercial reference is:

INV-784521

A reconciliation based only on:

Dynamics Document Number ↔ Reliance Doc Number

would incorrectly classify the invoice as unmatched.

Cointab allows multiple identifiers to be selected so the underlying invoice can still be identified.

---

How to reconcile Microsoft Dynamics with Reliance Tira using Cointab

In Cointab, start a new reconciliation and select:

Customer Reconciliation

For this workflow:

• Side 1 = Microsoft Dynamics NAV / Business Central Reliance Tira customer ledger
• Side 2 = Reliance Tira / Reliance Retail ledger

The process is:

Upload Dynamics Ledger → Upload Reliance Ledger → Configure Fields → Run Reconciliation → Review Exceptions

---

Step 1: Upload the Microsoft Dynamics customer ledger

Export the Reliance Tira customer account from Dynamics NAV or Business Central.

Upload the file into Cointab.

Select the transaction date

Choose the relevant field such as:

• Posting Date
• Document Date

depending on your reconciliation process.

Select transaction identifiers

Useful Dynamics identifier fields may include:

• Document Number
• Reference
• Description
• Narration

Multiple identifier fields can be selected.

This allows Cointab to identify invoice and transaction references even when they are not stored consistently in one Dynamics column.

Configure debit and credit

Map:

• Debit Amount
• Credit Amount

Cointab can now interpret the financial values in your Dynamics customer ledger.

---

Step 2: Upload the Reliance Tira ledger

Upload the ledger received from Reliance Retail.

Select the date

Relevant fields can include:

• Posting Date
• Document Date

Select transaction identifiers

Useful Reliance fields may include:

• Doc Number
• Reference
• Header Text
• Text details

Configure debit and credit

Map:

• Debit (Rs.)
• Credit (Rs.)

The reconciliation is now ready to run.

---

Step 3: Run Customer Reconciliation

Start the reconciliation.

Cointab analyzes the identifiers and amounts across your Microsoft Dynamics ledger and the Reliance ledger.

For invoice-level reconciliation, the basic questions are:

1. Can the same invoice be identified in Dynamics and Reliance?
2. If the invoice exists on both sides, do the amounts agree?

The result is divided into clear reconciliation categories.

---

Fully Matched Reliance Tira invoices

An invoice is Fully Matched when:

• The underlying invoice can be identified in Microsoft Dynamics
• The corresponding invoice can be identified in Reliance
• There is no amount difference

For example:

Microsoft Dynamics

Reference:

INV-85214

Amount:

₹2,75,000

Reliance Retail

Reference:

INV-85214

Amount:

₹2,75,000

The transaction exists in both ledgers for the same value.

Cointab classifies it as:

Fully Matched

These transactions generally require no further reconciliation work.

---

Partially Matched Reliance invoices

An invoice may be clearly identifiable in both systems but contain different values.

For example:

Microsoft Dynamics

Reference:

INV-85214

Amount:

₹2,75,000

Reliance Retail

Reference:

INV-85214

Amount:

₹2,68,000

The invoice reference confirms that both entries represent the same commercial transaction.

However, the difference is:

₹7,000

Cointab therefore reports:

Partially Matched

The finance team can immediately investigate the ₹7,000 difference.

---

What can cause an amount difference?

A partially matched Reliance invoice may result from:

• Invoice booked at an incorrect value
• Credit note
• Debit note
• Customer deduction
• Product return
• Rate difference
• Commercial adjustment
• Tax-related difference
• Incorrect accounting entry
• Transaction split differently in both systems

Because Cointab has already identified the invoice, the finance team can focus directly on explaining the difference.

---

Invoice present in Microsoft Dynamics but missing from Reliance

Suppose your Dynamics customer ledger contains:

Reference: INV-96421

Amount: ₹3,40,000

but no corresponding Reliance transaction can be identified.

Cointab reports:

Present in Microsoft Dynamics but not in Reliance

Possible explanations include:

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

This exception can be shared directly with the Reliance finance team.

---

Transaction present in Reliance but missing from Microsoft Dynamics

The reverse situation can also occur.

Reliance may contain:

Reference: CN-78451

Amount: ₹42,000

while no corresponding transaction exists in your Dynamics customer ledger.

Cointab reports:

Present in Reliance but not in Microsoft Dynamics

Your finance team can investigate whether:

• Credit note needs to be booked
• Customer deduction is missing
• Receipt has not been allocated
• Transaction exists using another Dynamics reference
• Reliance's transaction requires clarification

This becomes an internal accounting action item.

---

Dynamics Reference can be more useful than Dynamics Document Number

For this reconciliation, the Dynamics Reference field can be more useful than the internal Document Number.

For example:

Microsoft Dynamics

Document Number:

SI-10742

Reference:

TIRA-INV-56218

Reliance Retail

Doc Number:

5100986421

Reference:

TIRA-INV-56218

The common commercial identifier is:

TIRA-INV-56218

The internal accounting numbers do not need to agree.

This is a common reason spreadsheet reconciliations based purely on document-number lookups produce unnecessary exceptions.

---

Reliance Header Text can contain invoice information

Reliance's:

Header Text

may also contain useful invoice or transaction references.

For example:

Dynamics

Reference:

INV-74218

Reliance

Reference:

Blank

Header Text:

Vendor Invoice INV-74218

The transaction still contains the invoice number.

A reconciliation that checks only the Reliance Reference column would miss it.

Cointab can use several configured identifier fields while searching for the underlying transaction.

---

Text details can provide another route to a match

Reliance also provides:

Text details

This field may contain:

• Invoice numbers
• Credit-note references
• Payment references
• Adjustment descriptions

For example:

Dynamics Narration

Reliance Tira invoice 85621

Reliance Text details

Against vendor invoice 85621

The useful common identifier is:

85621

even though the complete descriptions differ.

---

AI-assisted identifier extraction from Dynamics Narration and Reliance Text

Accounting references are frequently embedded inside descriptive text.

For example:

Microsoft Dynamics Narration

TIRA INV NO RT/24/98521 MUM

Reliance Text details

Vendor invoice 98521

A strict text-to-text comparison may not identify the relationship.

Cointab can use AI-assisted processing to extract useful identifiers from the selected Dynamics and Reliance fields.

This reduces the need to manually:

• Split text
• Build helper columns
• Remove prefixes
• Standardize references
• Create multiple lookup formulas

---

Document Type and Reliance Types help classify exceptions

Microsoft Dynamics contains:

Document Type

Reliance contains:

Types

These fields can provide useful information when reviewing transactions that did not reconcile automatically.

An unmatched transaction may represent:

• Invoice
• Payment
• Credit note
• Debit note
• Adjustment
• Another accounting entry

This helps the finance team understand what kind of corresponding transaction it should look for.

---

Debit and credit direction needs to be configured correctly

Your Microsoft Dynamics ledger contains:

• Debit Amount
• Credit Amount

The Reliance Retail ledger contains:

• Debit (Rs.)
• Credit (Rs.)

The same commercial transaction is being viewed from opposite accounting perspectives.

In Dynamics:

Reliance Tira is your customer.

In Reliance Retail's books:

Your company is their supplier.

The debit/credit treatment therefore needs to be configured appropriately during the reconciliation.

Cointab allows the relevant debit and credit columns to be selected on each side.

---

Reconcile customer credits and adjustments

Large retail relationships can generate many transactions in addition to sales invoices.

These may include:

• Product returns
• Rate differences
• Commercial deductions
• Promotional adjustments
• Credit notes
• Debit notes

Suppose Reliance records an adjustment of:

₹35,000

but Microsoft Dynamics does not contain the corresponding transaction.

Even if all major invoices agree, the customer balances will remain different by ₹35,000.

Cointab surfaces the adjustment as a specific reconciliation exception.

---

Reconcile customer payments using descriptions and references

Payment entries may not contain the original invoice number.

For example:

Microsoft Dynamics Narration

Reliance receipt UTR 874521963

Reliance Text details

Payment 874521963

The common payment reference can help identify the relationship.

This means reconciliation can use more than just invoice numbers.

Useful information may also be available in:

• Reference
• Narration
• Header Text
• Text details

---

One Reliance payment may settle several invoices

Reliance Retail may make consolidated payments.

For example:

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

could be settled through one payment of:

₹5,00,000

Your Microsoft Dynamics ledger may therefore contain a single customer receipt while several underlying invoices have been settled.

Similarly:

• One invoice may be settled through several payments
• Credits may be adjusted against invoice balances
• One payment may cover transactions from several dates

This means customer reconciliation cannot always be reduced to one-to-one amount matching.

---

Posting dates can differ between Dynamics and Reliance

Both files contain:

• Posting Date
• Document Date

But these dates may not always agree exactly.

For example:

Microsoft Dynamics

Document Date:

30 June

Posting Date:

30 June

Reliance Retail

Document Date:

30 June

Posting Date:

2 July

The transaction can still be the same invoice.

Reliance may simply have recorded it in a later accounting period.

The reconciliation can use references and amounts together rather than rejecting a valid transaction because the posting dates differ.

---

Similar ledger structures still need intelligent reconciliation

This is a distinctive feature of Microsoft Dynamics vs Reliance Tira reconciliation.

The two files already look quite similar.

Both contain:

• Posting dates
• Document dates
• Document numbers
• References
• Debit
• Credit
• Descriptions

The challenge is not converting one unusual file structure into another.

The challenge is that both companies have independently recorded the same commercial transactions.

As a result:

• Internal numbers differ
• Descriptions differ
• Posting dates differ
• References may appear in different fields

The reconciliation needs to identify the underlying transaction across these differences.

---

Why a VLOOKUP on document number may fail

A manual reconciliation may begin with:

Dynamics Document Number → Reliance Doc Number

For example:

Dynamics

SI-8452

Reliance

5100874521

No match.

But both transactions may contain:

INV-75214

in their Reference fields.

The invoice is not actually missing.

The lookup is simply using the wrong identifier.

Using several potential identifiers reduces these false exceptions.

---

Why a Reference-only lookup may also fail

Even the Reference field may not always be populated consistently.

For example:

Microsoft Dynamics

Reference:

INV-87521

Reliance

Reference:

Blank

Text details:

Invoice 87521

The transaction exists.

The useful invoice number is simply stored elsewhere in Reliance's ledger.

This is why fields such as:

• Reference
• Header Text
• Text details
• Description
• Narration

can all be valuable during reconciliation.

---

Manual Match for known Dynamics and Reliance transactions

Some transactions may still remain unmatched even after automated matching.

For example:

Microsoft Dynamics

Reference:

TIRA-ADJ-482

Amount:

₹28,500

Reliance Retail

Doc Number:

1900852147

Header Text:

Rate Adj Aug

Amount:

₹28,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 Reliance transaction.
3. Review both records.
4. Confirm the match.

The transaction is then included as a manually reconciled relationship.

---

Manual Match helps resolve older Dynamics customer-account items

Older customer ledgers may contain:

• Legacy references
• Manual postings
• Incorrect narrations
• Rebooked transactions
• Historical credits
• Old adjustments

Changing the source accounting data merely to make an Excel lookup work may not be appropriate.

Manual Match allows the finance team to use its knowledge of the underlying transaction while retaining the original Microsoft Dynamics and Reliance files.

---

Example: fully matched invoice with different internal document numbers

Microsoft Dynamics

Document Number:

SI-9652

Reference:

INV-65821

Debit Amount:

₹2,20,000

Reliance Retail

Doc Number:

5100968451

Reference:

INV-65821

Credit:

₹2,20,000

The internal accounting document numbers differ.

But the commercial invoice reference and financial value agree.

Cointab reports:

Fully Matched

---

Example: invoice reference agrees but amount differs

Microsoft Dynamics

Reference:

INV-78452

Amount:

₹3,10,000

Reliance Retail

Reference:

INV-78452

Amount:

₹3,04,000

The transaction is:

Partially Matched

Difference:

₹6,000

The finance team can investigate the ₹6,000 directly.

---

Example: invoice exists only in Microsoft Dynamics

Your Dynamics customer ledger contains:

Reference: INV-92154

Amount: ₹1,85,000

Reliance contains no corresponding transaction.

Cointab reports:

Present in Microsoft Dynamics but not in Reliance

You can share the invoice details with the Reliance finance team.

---

Example: Reliance credit is missing from Dynamics

Reliance contains:

Types: Credit

Reference: CN-75218

Amount: ₹45,000

Your Microsoft Dynamics ledger has no corresponding entry.

Cointab reports:

Present in Reliance but not in Microsoft Dynamics

Your finance team can investigate whether:

• Credit note needs to be booked
• Customer deduction is valid
• Transaction exists under another Dynamics reference
• Reliance's entry needs clarification

---

Example: invoice number appears inside Reliance Text details

Microsoft Dynamics

Reference:

INV-62418

Reliance

Reference:

Blank

Text details:

Against invoice 62418

The underlying invoice is still identifiable.

AI-assisted identifier extraction can help find the common reference without requiring another manually prepared Excel column.

---

Example: posting period creates a temporary mismatch

Microsoft Dynamics

Invoice:

INV-81425

Posting Date:

31 July

Reliance

The invoice does not appear in the July ledger.

Cointab reports:

Present in Microsoft Dynamics but not in Reliance

In August, Reliance posts the same invoice.

The updated Reliance ledger now contains:

INV-81425

Cointab can match the previously open Dynamics transaction against the new Reliance record.

This allows genuine timing differences to resolve in later periods.

---

Turn the reconciliation into two action lists

Once matching is complete, the exceptions naturally separate into two worklists.

Dynamics transactions missing from Reliance

These may require customer-side follow-up.

For example:

• Invoice not booked
• Different reference used
• Posting pending
• Invoice under review

Reliance transactions missing from Dynamics

These usually require internal investigation.

For example:

• Customer credit missing
• Payment not allocated
• Adjustment not booked
• Customer deduction requiring validation

This makes the reconciliation actionable instead of merely reporting a closing-balance difference.

---

Download the complete Dynamics vs Reliance Tira 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
• Reliance Retail source data

The working can be used for:

• Month-end customer reconciliation
• Accounts receivable review
• Internal accounting correction
• Reliance follow-up
• Customer balance confirmation
• Audit support
• Open-item tracking

---

Use transaction-level exceptions when following up with Reliance

Without a prepared reconciliation, communication may simply say:

"Our Reliance balance does not match yours."

That requires both finance teams to review the entire account again.

A transaction-level reconciliation allows you to say:

• Invoice INV-7845 is not present in your ledger.
• Invoice INV-8521 differs by ₹6,000.
• Credit CN-7521 appears in your ledger but not in our Dynamics account.
• Payment reference 874512963 is not allocated internally.

This provides a much clearer starting point for resolving the account.

---

Correct Microsoft Dynamics and Reliance records and reconcile again

Once exceptions have been investigated:

• Missing invoice may be posted by Reliance
• Credit may be recorded in Dynamics
• Receipt may be allocated
• Amount may be corrected
• Reference may be updated
• Old adjustment may be resolved

Upload the revised Microsoft Dynamics and Reliance files into Cointab.

Run the reconciliation again.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as the two ledgers become aligned.

---

Repeat Microsoft Dynamics vs Reliance Tira reconciliation every month

If you supply Reliance Tira regularly, the customer account continues to change.

Each month may introduce:

• New invoices
• New customer payments
• Credit notes
• Returns
• Adjustments
• Previously open transactions

A typical monthly process becomes:

1. Export the latest Reliance Tira customer ledger from Microsoft Dynamics NAV / Business Central.
2. Obtain the latest ledger from Reliance Retail.
3. Upload the Dynamics ledger into Cointab.
4. Select Posting Date or Document Date.
5. Configure Dynamics Document Number, Reference, Description, and Narration.
6. Map Dynamics Debit Amount and Credit Amount.
7. Upload the Reliance ledger.
8. Configure Reliance Doc Number, Reference, Header Text, and Text details.
9. Map Reliance Debit and Credit.
10. Run Customer Reconciliation.
11. Review Fully Matched invoices.
12. Investigate Partially Matched transactions.
13. Review transactions present only in Dynamics.
14. Review transactions present only in Reliance.
15. Complete Manual Matches where required.
16. Download the reconciliation working.
17. Correct internal Dynamics entries.
18. Share Reliance-side exceptions with their finance team.
19. Upload revised ledgers and reconcile again.

---

Why Microsoft Dynamics users can benefit from automated Reliance reconciliation

Microsoft Dynamics already provides structured customer-account data.

Reliance also provides a structured ledger.

The difficulty is that the two accounting systems have not been designed to use identical:

• Document numbers
• References
• Descriptions
• Posting dates
• Transaction narratives

A manual Excel process may therefore still require:

• Multiple lookups
• Reference cleaning
• Text searches
• Debit/credit normalization
• Exception tracking
• Manual comments

Cointab allows the existing Microsoft Dynamics and Reliance exports to be reconciled directly.

---

Move from Dynamics Excel exports to exception management

The manual workflow may look like:

Export Dynamics → Obtain Reliance Ledger → Build Lookups → Search References → Compare Debit/Credit → Find Missing Entries → Maintain Comments

Cointab changes this to:

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

The finance team can focus on the small number of transactions that genuinely require attention.

---

How Cointab helps reconcile Microsoft Dynamics with Reliance Tira

Cointab's Customer Reconciliation workflow allows you to:

• Upload your Microsoft Dynamics NAV / Business Central Reliance customer ledger
• Upload the Reliance Tira / Reliance Retail ledger
• Configure Posting Date or Document Date
• Map debit and credit columns independently
• Use Dynamics Reference as an invoice identifier
• Use Reliance Reference as a corresponding identifier
• Use Dynamics Description and Narration as supporting fields
• Use Reliance Header Text and Text details as supporting fields
• Extract useful invoice references from transaction descriptions
• Automatically identify matching transactions
• Separate Fully Matched invoices
• Identify Partially Matched transactions
• Identify transactions present only in Dynamics
• Identify transactions present only in Reliance
• Manually match genuine transactions where references differ
• Download the complete reconciliation working in Excel
• Upload revised files and reconcile again
• Continue reconciling previously open transactions in future periods

---

Automate Microsoft Dynamics vs Reliance Tira customer reconciliation

If you supply Reliance Tira / Reliance Retail 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 → Reliance Tira Ledger → Automated Matching → Exception Review → Corrections → Updated Reconciliation

You can quickly identify:

• Invoices that agree
• Invoices with amount differences
• Transactions missing from Reliance
• Reliance transactions missing from Dynamics
• Credits and adjustments requiring investigation
• Transactions where the invoice reference appears only inside descriptions or narration
• Previously open customer-account differences

The complete reconciliation can then be downloaded in Excel and used for internal review or follow-up with the Reliance Retail finance team.

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

Try Cointab

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

Book a Demo