If your company sells products to Yash Enterprises and maintains its customer account in Tally, you may periodically receive a ledger from Yash Enterprises for reconciliation.

Your Tally ledger represents the transactions recorded in your books.

Yash Enterprises maintains the same commercial relationship from the opposite side in its own Tally books.

Ideally, both ledgers should contain the same invoices, payments, credit notes, debit notes, and adjustments.

In practice, differences are common.

You may have raised an invoice that does not appear in the Yash Enterprises ledger.

Yash Enterprises may have recorded a payment or adjustment that is missing from your books.

The same invoice may be present in both ledgers but with a different amount.

A genuine transaction may also remain unmatched because the two Tally systems use different voucher numbers or narrations.

This creates a recurring customer reconciliation requirement:

Your Tally Customer Ledger ↔ Yash Enterprises Tally Ledger

Cointab can automate this reconciliation and show you:

• Fully Matched transactions
• Partially Matched transactions
• Transactions present in your Tally but missing from Yash Enterprises
• Transactions present in Yash Enterprises but missing from your Tally
• Manually Matched transactions
• Complete reconciliation working downloadable in Excel

Once both parties correct the required entries, you can upload the revised ledgers and run the reconciliation again.

The same process can then be repeated every month.

---

Why reconcile your ledger with Yash Enterprises?

If Yash Enterprises is your distributor or customer, your books may show an outstanding receivable against them.

Yash Enterprises, on the other hand, maintains your company as a supplier in its own accounting system.

Both ledgers should ultimately explain the same commercial activity.

For example, if you raise an invoice of:

₹2,50,000

on Yash Enterprises, their books should normally contain the corresponding purchase transaction for:

₹2,50,000

Similarly, if Yash Enterprises makes a payment of:

₹5,00,000

your customer ledger should contain the corresponding receipt.

Differences between the two ledgers can affect:

• Customer outstanding balance
• Accounts receivable
• Collection follow-up
• Credit limits
• Distributor relationship
• Customer balance confirmation
• Month-end closing
• Audit working
• Working capital reporting

The purpose of reconciliation is to identify exactly which transactions are causing the difference.

---

What does your Tally customer ledger look like?

Your Tally customer ledger may contain fields such as:

Useful transaction references may appear across several fields.

For example, an invoice number may be available in:

• Vch No.
• Narration
• Vch Type

A payment or adjustment may also contain additional reference information inside the narration.

This means reconciliation should not depend entirely on one exact field.

---

What does the Yash Enterprises Tally ledger look like?

The ledger received from Yash Enterprises may contain:

The structure is similar to a normal Tally ledger, but the entries are maintained independently by Yash Enterprises.

Their:

Vch No.

does not necessarily need to be the same as your:

Vch No.

The same transaction can therefore have different accounting references in both files.

---

Your customer ledger and their supplier ledger are opposite views of the same account

This is an important part of customer reconciliation.

In your books:

Yash Enterprises is a customer.

In the Yash Enterprises books:

Your company is a supplier.

The accounting entries are therefore viewed from opposite sides.

A sales invoice in your books corresponds to a purchase transaction in their books.

A receipt recorded by you corresponds to a payment recorded by them.

Cointab allows you to map the debit and credit columns from each ledger while setting up the reconciliation.

You do not need to manually restructure both files into identical Excel formats first.

---

How to reconcile your Tally ledger with Yash Enterprises in Cointab

The reconciliation can be performed using Cointab's standard:

Customer Reconciliation

workflow.

The process is:

Start Customer Reconciliation → Upload Your Tally Ledger → Upload Yash Enterprises Ledger → Configure Fields → Run Reconciliation

---

Step 1: Start a Customer Reconciliation

Create a new reconciliation in Cointab.

Choose:

Customer Reconciliation

For this reconciliation:

• Side 1 = Your Tally customer ledger for Yash Enterprises
• Side 2 = Ledger received from Yash Enterprises

---

Step 2: Upload your Tally customer ledger

Upload the ledger exported from your Tally account.

Your file may contain:

• Type
• Date
• Narration
• Vch Type
• Vch No.
• Debit
• Credit

Configure the relevant fields.

Select the date

Choose:

Date

Select identifiers

Useful identifier fields may include:

• Vch No.
• Narration
• Vch Type

These fields can contain invoice numbers, payment references, credit-note references, or other transaction identifiers.

Configure debit and credit

Select:

• Debit
• Credit

Cointab can now interpret the financial structure of your customer ledger.

---

Step 3: Upload the Yash Enterprises ledger

Upload the ledger shared by Yash Enterprises.

The file may contain:

• Date
• Particulars
• Vch Type
• Vch No.
• Debit
• Credit

Configure the corresponding fields.

Date

Select:

Date

Identifiers

Useful fields may include:

• Vch No.
• Particulars
• Vch Type

Amount columns

Configure:

• Debit
• Credit

The reconciliation is now ready to run.

---

Step 4: Run the customer reconciliation

Start the reconciliation.

Cointab analyzes both Tally ledgers and identifies useful transaction references from the configured fields.

The system then attempts to determine which entries in your books correspond to entries in the Yash Enterprises ledger.

For invoice-level matching, the main questions are:

1. Does the same invoice exist in both ledgers?
2. If the invoice exists in both ledgers, does the amount agree?

The output is separated into clear reconciliation categories.

---

Fully Matched invoices

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

For example:

Your Tally ledger

Invoice:

INV-1045

Amount:

₹1,80,000

Yash Enterprises ledger

Invoice:

INV-1045

Amount:

₹1,80,000

The invoice is present in both books and the amount agrees.

Cointab classifies it as:

Fully Matched

These transactions normally require no further action.

---

Partially Matched invoices

Sometimes the same invoice is present in both ledgers, but the amount is different.

For example:

Your ledger

Invoice:

INV-1045

Amount:

₹1,80,000

Yash Enterprises ledger

Invoice:

INV-1045

Amount:

₹1,75,000

The invoice number confirms that both records relate to the same commercial transaction.

However, there is a:

₹5,000

difference.

Cointab therefore classifies it as:

Partially Matched

You can then investigate the cause of the difference.

---

What can cause a partially matched invoice?

Possible reasons include:

• Invoice booked at an incorrect value
• Credit note missing
• Debit note missing
• Customer deduction
• Sales return
• Scheme adjustment
• Pricing difference
• Tax difference
• Manual accounting error
• Transaction split differently between the two books

The advantage of Partial Match is that you immediately know that the invoice itself has been identified.

You only need to investigate the amount difference.

---

Invoice present in your Tally but missing from Yash Enterprises

Suppose your Tally ledger contains:

Invoice: INV-2178

Amount: ₹3,25,000

but no corresponding transaction can be found in the Yash Enterprises ledger.

Cointab shows the transaction as:

Present in Your Ledger but not in Yash Enterprises

Possible explanations include:

• Yash Enterprises has not booked the invoice
• Invoice was received but accounting entry is pending
• Invoice was booked using another reference
• Invoice belongs to another period
• Invoice is under dispute
• Transaction was missed

You can share these transactions with the Yash Enterprises finance team for investigation.

---

Transaction present in Yash Enterprises but missing from your Tally

The opposite situation can also occur.

Suppose the Yash Enterprises ledger contains:

Reference: CN-821

Amount: ₹35,000

but the corresponding transaction does not appear in your customer ledger.

Cointab reports:

Present in Yash Enterprises but not in Your Ledger

This becomes an internal action item.

You can investigate whether:

• A payment is missing
• A receipt was posted incorrectly
• A credit note is missing
• An adjustment needs to be recorded
• The transaction exists using another reference
• Yash Enterprises has recorded an incorrect transaction

---

Identify customer payments missing from your books

A customer reconciliation is not limited to invoices.

Payments are equally important.

Suppose Yash Enterprises shows that it has made a payment of:

₹6,00,000

but the corresponding receipt is not identifiable in your Tally customer ledger.

Possible causes include:

• Payment received but not allocated
• Receipt booked under another customer
• Bank receipt posted using another reference
• Payment entry not yet recorded
• Timing difference

The reconciliation surfaces the transaction so you can investigate the receipt instead of simply seeing an unexplained difference in the closing balance.

---

One payment can settle several invoices

Distributor customers frequently make consolidated payments.

For example, Yash Enterprises may have five invoices outstanding:

Yash Enterprises may make one payment of:

₹5,00,000

instead of five separate payments.

Similarly:

• One invoice may be paid through multiple installments
• A payment may be net of credit notes
• A payment may contain customer deductions

Reconciliation therefore cannot always rely on exact one-payment-to-one-invoice matching.

Cointab can support more complex matching relationships where required.

---

Different Tally voucher numbers do not necessarily mean different transactions

Your Tally and Yash Enterprises' Tally are maintained independently.

The voucher numbers can therefore be different even for the same underlying invoice.

For example:

Your Tally

Vch No.:

SI/24-25/1458

Yash Enterprises

Vch No.:

PI/6582

A VLOOKUP on voucher number would not match these records.

However, other fields may contain the underlying invoice number.

For example:

Your Narration

Invoice 784512 - Yash Enterprises

Yash Enterprises Particulars

Purchase against Inv 784512

The common commercial reference is:

784512

Cointab can use multiple identifier fields when performing the reconciliation.

---

Extract invoice references from Narration and Particulars

Useful invoice information is often embedded inside Tally descriptions.

For example:

Your Narration

Sales Invoice 987521 YE Mumbai

Yash Enterprises Particulars

Purchase Inv No 987521

The invoice number:

987521

is present in both files, but it appears within different text.

A manual Excel reconciliation may require you to:

• Split text
• Create helper columns
• Search descriptions
• Clean references
• Build formulas

Cointab uses AI-assisted processing to extract useful identifiers from the selected ledger fields and use them for matching.

This can significantly reduce the preparation required before reconciliation.

---

Manual Match when you know two transactions are the same

Some transactions may still remain unmatched because their references are very different.

Suppose:

Your Tally

Narration:

YE Adjustment July

Amount:

₹28,500

Yash Enterprises

Particulars:

CN 7842

Amount:

₹28,500

You know from the supporting documents that both entries relate to the same adjustment.

Cointab provides a Manual Match option.

You can:

1. Open Manual Match.
2. Select the relevant transaction from your ledger.
3. Select the corresponding transaction from the Yash Enterprises ledger.
4. Review the selected entries.
5. Confirm the match.

The transaction is then recorded as manually reconciled.

---

Why Manual Match is useful in Tally reconciliation

Real accounting data is not always perfectly standardized.

Transactions may contain:

• Different voucher numbers
• Abbreviated narrations
• Manual postings
• Incorrect references
• Old accounting entries
• Rebooked transactions
• Adjustment vouchers

You may know that two transactions belong together even when the ledger data alone is not sufficient for an automatic match.

Manual Match allows you to use that accounting knowledge without editing the original Tally files simply to force the reconciliation to work.

---

Reconcile credit notes

Credit notes are common in distributor relationships.

They may arise because of:

• Product returns
• Damaged goods
• Rate differences
• Commercial schemes
• Discounts
• Promotional support
• Short supply
• Other adjustments

Suppose you issue a credit note of:

₹40,000

but Yash Enterprises has not recorded it.

Your ledgers will remain different even if all invoices and payments agree.

Similarly, Yash Enterprises may show an adjustment that has not yet been recorded in your books.

Transaction-level reconciliation helps identify these open items directly.

---

Reconcile sales returns

If Yash Enterprises returns products, several steps may occur:

1. Products are returned.
2. Return is acknowledged.
3. Credit note is issued.
4. Your customer ledger is adjusted.
5. Yash Enterprises records the corresponding entry.

If these steps are completed in different accounting periods, the two ledgers may temporarily disagree.

The reconciliation helps identify exactly which financial entry remains outstanding.

---

Reconcile customer deductions

Yash Enterprises may sometimes pay less than the invoice balance because of an adjustment.

For example:

Total invoices due

₹8,00,000

Payment received

₹7,70,000

Difference

₹30,000

The ₹30,000 could relate to:

• Sales return
• Rate difference
• Scheme
• Damage claim
• Discount
• Other deduction

Your finance team needs to determine whether the deduction has a valid corresponding credit or adjustment.

The customer reconciliation makes these differences easier to investigate.

---

Why closing balance comparison is not enough

Suppose your Tally shows:

Yash Enterprises outstanding: ₹24,80,000

The ledger shared by Yash Enterprises shows:

Outstanding: ₹23,60,000

Difference:

₹1,20,000

You know the ledgers differ.

But you still do not know why.

The ₹1,20,000 may consist of:

• One invoice missing at Yash Enterprises
• One customer payment missing in your books
• One credit note recorded only on one side
• One partially matched invoice
• Several old open items

Cointab breaks the balance difference into the underlying transaction-level exceptions.

---

Know which finance team needs to take action

Customer reconciliation becomes much more useful when every exception has a clear direction.

Present in your ledger but missing from Yash Enterprises

These items can be shared with Yash Enterprises.

They may need to:

• Book an invoice
• Record a credit note
• Correct a reference
• Confirm a disputed entry

Present in Yash Enterprises but missing from your ledger

These items can be shared with your internal finance team.

You may need to:

• Record a payment
• Allocate a receipt
• Book a credit note
• Correct the customer account
• Investigate an adjustment

The reconciliation output therefore becomes an action list rather than merely a balance comparison.

---

Download the complete customer reconciliation in Excel

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

The output can include:

• Fully Matched transactions
• Partially Matched transactions
• Unmatched transactions
• Manual Matches
• Relevant transaction details from both Tally ledgers

You can use the Excel file for:

• Internal accounts receivable review
• Customer follow-up
• Month-end working
• Balance confirmation
• Audit support
• Exception tracking

This gives you a prepared customer reconciliation working rather than having to maintain multiple manual Excel files.

---

Share missing entries internally

Transactions appearing in the Yash Enterprises ledger but not in your Tally can be shared with your accounting team.

For each exception, determine whether:

• Entry needs to be booked
• Payment needs to be allocated
• Credit note is missing
• Reference differs
• Transaction belongs to another period
• Yash Enterprises' entry is incorrect

Once your books are corrected, export the revised ledger.

---

Share Yash Enterprises-side differences with their team

Transactions appearing in your Tally but missing from the Yash Enterprises ledger can be shared with their finance team.

They can investigate whether:

• Invoice has been booked
• Different voucher number was used
• Entry is pending
• Credit note has been recorded
• Transaction is disputed
• Amount needs correction

This makes reconciliation between both finance teams more precise.

Instead of saying:

“Our balance differs by ₹1.2 lakh.”

you can say:

“These four specific transactions are causing the difference.”

---

Upload revised ledgers and run reconciliation again

After corrections are made, upload the latest ledgers again.

For example:

Updated Your Tally Ledger + Updated Yash Enterprises Ledger

Run the reconciliation again.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as missing transactions and amount differences are corrected.

The reconciliation therefore remains useful throughout the resolution process.

---

Example: invoice missing in Yash Enterprises Tally

Your ledger contains:

Invoice: INV-3284

Amount: ₹2,75,000

The invoice is not found in the Yash Enterprises ledger.

Cointab reports:

Present in Your Ledger but not in Yash Enterprises

You share the invoice details with their finance team.

They identify that the transaction was missed and book it in Tally.

The updated ledger is uploaded.

Both sides now show:

INV-3284

₹2,75,000

The transaction becomes:

Fully Matched

---

Example: payment is missing from your customer ledger

Yash Enterprises records:

Payment: ₹5,50,000

Your customer ledger has no corresponding receipt.

Cointab identifies:

Present in Yash Enterprises but not in Your Ledger

Your finance team checks the bank and discovers that the payment was received but incorrectly allocated.

The Tally entry is corrected.

After uploading the revised ledger, the payment can reconcile.

---

Example: same invoice but different amounts

Both ledgers contain:

Invoice: INV-4521

But:

Your Tally

₹1,65,000

Yash Enterprises

₹1,60,000

Cointab reports:

Partially Matched

You can immediately focus on the:

₹5,000

difference rather than searching for whether the invoice exists.

---

Example: voucher numbers differ

Your Tally shows:

Vch No.: SI/1735

Narration: Invoice 85621

Yash Enterprises shows:

Vch No.: PI/4872

Particulars: Purchase Inv 85621

The local voucher numbers differ.

The underlying invoice reference:

85621

connects the two transactions.

This is why multiple identifiers and ledger descriptions can be more useful than relying only on voucher numbers.

---

Repeat the Yash Enterprises reconciliation every month

Customer reconciliation should be a recurring process.

Every month there may be:

• New invoices
• New customer payments
• Credit notes
• Sales returns
• Deductions
• Adjustments
• Previously unresolved items

A typical monthly workflow can be:

1. Export your latest Yash Enterprises customer ledger from Tally.
2. Obtain the latest ledger from Yash Enterprises.
3. Upload your Tally ledger to Cointab.
4. Upload the Yash Enterprises ledger.
5. Run Customer Reconciliation.
6. Review Fully Matched transactions.
7. Investigate Partially Matched transactions.
8. Review transactions present only in your ledger.
9. Review transactions present only in Yash Enterprises.
10. Complete Manual Matches where required.
11. Download the reconciliation working.
12. Correct internal accounting entries.
13. Share customer-side differences with Yash Enterprises.
14. Upload revised ledgers when available.
15. Run the reconciliation again.

The same workflow can then continue into the next accounting period.

---

Open transactions can reconcile in future months

Not every unmatched transaction is necessarily an accounting error.

Sometimes the difference is only timing.

For example:

March

You raise an invoice on 31 March.

Your Tally ledger contains the invoice.

Yash Enterprises has not yet booked it.

The transaction remains unmatched.

April

Yash Enterprises records the invoice.

When the latest ledger is uploaded, Cointab can match the new transaction against the previously open item.

You do not need to manually rebuild the reconciliation history every month.

---

Customer reconciliation is especially useful for distributor accounts

Distributor relationships often contain more financial activity than a simple invoice-and-payment cycle.

You may need to reconcile:

• Sales invoices
• Payments
• Sales returns
• Credit notes
• Commercial schemes
• Discounts
• Customer deductions
• Rate differences
• Other adjustments

This makes distributor customer reconciliation particularly suitable for a structured reconciliation workflow.

---

How Cointab helps reconcile your Tally ledger with Yash Enterprises

Cointab's Customer Reconciliation workflow allows you to:

• Upload your Tally customer ledger
• Upload the Yash Enterprises Tally ledger
• Configure transaction dates
• Configure Debit and Credit fields
• Select multiple transaction identifiers
• Use Narration and Particulars as reference fields
• Extract useful invoice references from ledger descriptions
• Automatically identify matching transactions
• Separate Fully Matched invoices
• Identify Partially Matched transactions
• Find entries present only in your Tally
• Find entries present only in Yash Enterprises
• Manually match genuine transactions where references differ
• Download the entire reconciliation working in Excel
• Upload revised ledgers after corrections
• Continue reconciling open transactions in subsequent months

---

Automate your Tally vs Yash Enterprises customer reconciliation

If you currently receive a ledger from Yash Enterprises and compare it manually against your Tally customer ledger, Cointab can automate much of the reconciliation work.

The process becomes:

Upload Your Tally Ledger → Upload Yash Enterprises Ledger → Run Customer Reconciliation → Review Exceptions → Correct Ledgers → Reconcile Again

Invoices that agree are automatically separated.

Invoices with amount differences are shown as partially matched.

Transactions missing from either ledger are clearly identified.

Transactions with inconsistent references can still be reconciled using Manual Match.

You can then download the complete customer reconciliation working in Excel.

If you currently reconcile your Yash Enterprises customer account manually in Excel, you can use Cointab to automate the process.

Try Cointab

For larger ledgers, custom Tally formats, or more complex customer reconciliation requirements:

Book a Demo