If your company supplies products to Nature's Basket, your finance team may periodically need to reconcile the customer balance maintained in your accounting system with the ledger shared by Nature's Basket.

Your books may be maintained in Tally.

Nature's Basket may provide a much more detailed customer ledger containing document numbers, references, posting dates, clearing information, business-place information, and other accounting fields.

Both files ultimately represent the same commercial relationship.

But their structures can look completely different.

Your Tally ledger may show:

• Sales invoices
• Customer receipts
• Credit notes
• Debit notes
• Adjustments

Nature's Basket may represent the same activity using:

• Document numbers
• Reference fields
• Posting dates
• Clearing documents
• Clearing dates
• Local-currency amounts
• Withholding-related information

This makes a simple row-by-row Excel comparison difficult.

The reconciliation requirement is:

Your Tally Customer Ledger ↔ Nature's Basket Customer Ledger

Cointab can automate this comparison and classify the transactions into:

• Fully Matched
• Partially Matched
• Present in your Tally but not found in Nature's Basket
• Present in Nature's Basket but not found in your Tally
• Manually Matched

Once the exceptions have been investigated and the respective ledgers corrected, revised files can be uploaded and the reconciliation run again.

The same workflow can then be reused every month.

---

Why reconcile your Nature's Basket customer account?

If you sell to a large retail customer such as Nature's Basket, the outstanding balance in your books may consist of many individual transactions.

These may include:

• Product invoices
• Customer payments
• Credit notes
• Returns
• Commercial deductions
• Adjustments
• Older outstanding transactions

Your Tally ledger tells you what your company believes is outstanding.

The Nature's Basket ledger tells you what their accounting system reflects.

If the balances differ, the finance team needs to understand exactly why.

For example:

• Have they missed one of your invoices?
• Have they recorded a payment that you have not allocated?
• Has an invoice been booked at a different amount?
• Has a credit note been recorded on only one side?
• Is a transaction already cleared in their system but still open in yours?
• Is the difference related to a deduction or withholding treatment?

A proper customer reconciliation converts the closing-balance difference into individual actionable transactions.

---

What does your Tally customer ledger look like?

Your Tally export may contain fields such as:

This is a useful structure for reconciliation because several fields may contain information that identifies the underlying customer transaction.

Useful identifiers can include:

• Document No
• Reference
• Particulars
• Narration

The Net field can also provide a normalized financial value where appropriate.

---

What does the Nature's Basket ledger look like?

The Nature's Basket file can be significantly more detailed.

A typical format may contain:

This file contains several fields that can help identify and explain transactions.

Unlike a simple customer ledger, it also provides information about whether an item has already been cleared in Nature's Basket's books.

That makes the reconciliation useful not only for matching invoices, but also for understanding the status of outstanding transactions.

---

Why these two files cannot be matched using identical columns

Your Tally export and the Nature's Basket ledger do not have the same structure.

For example, your invoice number may appear in:

Document No

while Nature's Basket may record the same invoice in:

Reference

or:

Reference key 1

or:

Reference key 2

or:

Reference key 3

The Nature's Basket internal:

Document Number

may be completely different from your own invoice number.

Similarly, your Tally transaction may contain separate:

• Debit
• Credit
• Net

values.

Nature's Basket may instead provide a signed:

Amount in local currency

The reconciliation therefore needs to understand the commercial transaction, not simply compare identically named spreadsheet columns.

---

How to reconcile your Tally ledger with Nature's Basket using Cointab

Cointab provides a standard:

Customer Reconciliation

workflow.

The overall process is:

Create Customer Reconciliation → Upload Your Tally Ledger → Upload Nature's Basket Ledger → Configure Fields → Run Reconciliation

You do not need to manually rebuild the Nature's Basket file into your Tally structure first.

---

Step 1: Start a Customer Reconciliation

In Cointab, start a new reconciliation and select:

Customer Reconciliation

For this workflow:

• Internal ledger = Your Tally customer ledger for Nature's Basket
• Customer ledger = Ledger received from Nature's Basket

---

Step 2: Upload your Tally customer ledger

Upload the Tally export.

Your file may include:

• Type
• Date
• DR/CR
• Particulars
• Vch Type
• Document No
• Reference
• Narration
• Debit
• Credit
• Net

Configure the fields Cointab should use.

Select the date

Choose:

Date

Select transaction identifiers

Useful identifiers may include:

• Document No
• Reference
• Particulars
• Narration

Multiple fields can be selected because the invoice or transaction reference may not always appear in exactly one place.

Configure the amounts

Depending on the file structure, use the relevant:

• Debit
• Credit

columns and the available net amount as appropriate.

Cointab can then interpret the financial values represented in your customer ledger.

---

Step 3: Upload the Nature's Basket ledger

Upload the customer ledger shared by Nature's Basket.

This file contains a different set of accounting fields.

Select the transaction date

Relevant dates can include:

• Document Date
• Posting Date

The appropriate field can be selected based on how you perform the reconciliation.

Select transaction identifiers

Useful fields may include:

• Reference
• Reference key 1
• Reference key 2
• Reference key 3
• Document Number
• Text

These fields provide several possible ways of identifying the invoice or adjustment represented by a transaction.

Configure the amount

The Nature's Basket file contains:

Amount in local currency

This represents the financial value that needs to be compared against the corresponding entry in your customer ledger.

---

Step 4: Run the reconciliation

Once both files have been configured, start the reconciliation.

Cointab analyzes the transaction identifiers and financial values across both datasets.

For invoice-level reconciliation, the system primarily needs to establish:

1. Can the same invoice or commercial transaction be identified on both sides?
2. If the transaction exists in both ledgers, do the financial values agree?

The resulting transactions are classified into clear reconciliation categories.

---

Fully Matched Nature's Basket invoices

An invoice can be classified as Fully Matched when:

• The corresponding invoice is identifiable in both ledgers.
• The amounts agree.

For example:

Your Tally ledger

Document No:

INV-5274

Amount:

₹2,45,000

Nature's Basket ledger

Reference:

INV-5274

Amount in local currency:

₹2,45,000

The transaction exists in both systems at the same value.

Cointab therefore classifies it as:

Fully Matched

These invoices normally require no further reconciliation action.

---

Partially Matched invoices

An invoice may be clearly identifiable in both ledgers while the amounts differ.

For example:

Your Tally

Invoice:

INV-5274

Amount:

₹2,45,000

Nature's Basket

Reference:

INV-5274

Amount:

₹2,40,000

The common invoice reference tells the system that both records represent the same underlying transaction.

However, there is a:

₹5,000

difference.

The invoice is therefore classified as:

Partially Matched

Your finance team can now investigate the amount difference rather than searching for whether the invoice exists.

---

Why might the amount differ?

A partial match can occur for several reasons.

For example:

• Invoice was booked at a different value
• Credit note exists on only one side
• Customer deduction has been recorded
• Return has been accounted for differently
• Commercial adjustment is pending
• Tax treatment differs
• Withholding-related treatment affects the balance
• Incorrect entry has been posted
• Transaction has been split across multiple records

The reconciliation identifies the transaction relationship first so the finance team can focus on explaining the actual amount difference.

---

Invoice present in your Tally but missing from Nature's Basket

Suppose your books contain:

Invoice: INV-6841

Amount: ₹3,60,000

but Cointab cannot identify the corresponding transaction in the Nature's Basket ledger.

The transaction appears as:

Present in Your Tally but not in Nature's Basket

Possible reasons include:

• Nature's Basket has not yet booked the invoice
• Invoice is pending processing
• Invoice was recorded using another reference
• Invoice belongs to another posting period
• Invoice is under dispute
• Transaction was missed

This exception can be shared with the Nature's Basket finance or accounts team for review.

---

Transaction present in Nature's Basket but missing from your Tally

The opposite situation can also occur.

Nature's Basket may have an accounting transaction that cannot be identified in your Tally ledger.

For example:

Nature's Basket

Reference:

CN-45127

Amount:

₹42,000

Your Tally

No corresponding record identified.

Cointab reports:

Present in Nature's Basket but not in Your Tally

Your finance team can investigate whether:

• Credit note is missing
• Customer payment has not been allocated
• Adjustment has not been recorded
• Transaction was posted against another customer
• Reference differs
• Nature's Basket has recorded an incorrect transaction

This creates a clear internal action list.

---

Nature's Basket may use several reference fields for the same transaction

One of the most useful characteristics of the Nature's Basket ledger is the presence of several reference fields:

• Reference
• Reference key 1
• Reference key 2
• Reference key 3

A commercial transaction may be identifiable through any one of these.

For example, your invoice may be:

NB-784521

Nature's Basket could store this in:

Reference key 1

while its own internal accounting document appears as:

Document Number: 1900457821

A lookup based only on Document Number would fail because the internal Nature's Basket document number is not your invoice number.

Cointab allows several identifier fields to be selected during configuration.

This helps the reconciliation search for the underlying external reference instead of relying exclusively on the customer's internal ERP document number.

---

Internal document numbers do not need to match your invoice numbers

Large customers frequently generate their own accounting document numbers.

For example:

Your Tally

Document No:

INV-8915

Nature's Basket

Document Number:

1900876542

These numbers may have no visible relationship.

However, Nature's Basket may store:

INV-8915

inside:

• Reference
• Reference key 1
• Reference key 2
• Reference key 3
• Text

This is why customer reconciliation should use multiple possible reference fields.

The objective is not to make both accounting systems use the same document number.

The objective is to identify which records represent the same business transaction.

---

AI-assisted extraction from transaction references

Accounting references are not always stored in a clean format.

For example, your Tally may contain:

NB Invoice INV-8915

while Nature's Basket shows:

Pur Inv 8915 / Store 102

The same underlying identifier may be embedded in different descriptions.

A spreadsheet-led process can require:

• Text cleaning
• Helper columns
• Manual searches
• Multiple lookup formulas
• Reference normalization

Cointab can use AI-assisted processing to identify useful transaction references from the configured fields.

This reduces the amount of manual data preparation required before matching.

---

Use Nature's Basket clearing information during investigation

A distinctive feature of the Nature's Basket ledger is the availability of:

• Clearing Document
• Clearing date

This can provide valuable context when investigating a customer reconciliation difference.

A transaction may already be cleared in Nature's Basket's books even though your ledger still shows it as outstanding.

For example:

Nature's Basket

Invoice:

INV-5621

Clearing Document:

2000784512

Clearing Date:

15 July

Your Tally

Invoice still appears open.

This tells your finance team that the transaction may need further investigation.

Possible causes could include:

• Payment received but not allocated
• Credit note not linked correctly
• Receipt posted under another reference
• Clearing happened through an adjustment
• Customer-side allocation differs from your books

The clearing fields can therefore help explain why the two outstanding balances differ.

---

What does a clearing document mean for reconciliation?

A clearing document indicates that Nature's Basket has used another accounting transaction to settle or clear an open item.

Depending on the transaction, this could relate to:

• Payment
• Credit adjustment
• Offset
• Other accounting settlement

The existence of a clearing document does not automatically tell you that your books are correct.

But it gives the finance team an important investigation clue.

Instead of simply seeing:

Invoice unmatched

you can also see:

Nature's Basket has already cleared this invoice internally.

That can significantly narrow the follow-up required.

---

Use the clearing date to understand timing differences

The Nature's Basket ledger also provides:

Clearing date

This is useful where the two ledgers differ because transactions were settled in different accounting periods.

For example:

Your ledger

Receipt posted:

2 August

Nature's Basket

Invoice cleared:

31 July

The underlying transaction may still be valid even though the accounting dates are different.

Reconciliation therefore should not assume that every relevant date must be identical across both systems.

---

Document Date and Posting Date can also differ

Nature's Basket provides both:

• Document Date
• Posting Date

These may not always be the same.

For example:

Document Date: 29 June

Posting Date: 2 July

Your Tally may have:

Date: 29 June

A strict date-to-date lookup could incorrectly reject the transaction because the posting date differs.

Cointab allows the relevant transaction date and identifiers to be configured so the reconciliation can focus on the actual commercial relationship.

---

Business Place can provide additional reconciliation context

The Nature's Basket ledger contains:

Business Place

For suppliers servicing multiple locations, this can provide useful information when investigating differences.

For example, an invoice may relate to:

• Different store
• Different distribution location
• Different business unit
• Different operational location

If two transactions have similar values but relate to different business places, the location information can help distinguish them.

This is especially useful when the same customer relationship generates large volumes of similar invoices.

---

Company Code can matter when the customer has multiple accounting entities

The Nature's Basket file also contains:

Company Code

This can help distinguish accounting activity where a customer operates through multiple organizational structures or accounting entities.

A finance team reviewing unmatched items can therefore use more than only:

• Invoice number
• Amount

Additional context such as:

• Company Code
• Business Place
• Document Type
• Posting Date

can help determine whether two records really correspond.

---

Document Type can help explain the nature of an unmatched transaction

The Nature's Basket ledger contains:

Document Type

This can help distinguish different accounting entries.

For example, an unmatched record may not necessarily represent another sales invoice.

It may instead represent:

• Payment-related posting
• Credit adjustment
• Debit adjustment
• Other accounting transaction

When reviewing exceptions, document type provides useful context about what action may be required.

---

Reconciling customer payments

Customer reconciliation is not limited to invoice matching.

Payments are equally important.

Suppose Nature's Basket has cleared several invoices through a payment.

Your Tally should contain the corresponding customer receipt.

If the receipt is missing or allocated differently, the balances will continue to differ even though the invoices themselves were correctly recorded.

Cointab can help isolate transactions where:

• Nature's Basket shows settlement
• Your books still show the invoice outstanding
• Payment reference differs
• Receipt has not been allocated correctly

---

One Nature's Basket payment may clear multiple invoices

Large retail customers may make consolidated payments.

For example, Nature's Basket may settle:

• Invoice A – ₹1,20,000
• Invoice B – ₹2,40,000
• Invoice C – ₹80,000
• Invoice D – ₹1,60,000

through one payment of:

₹6,00,000

The Nature's Basket ledger may show clearing information against the individual documents while your Tally contains one customer receipt.

The financial relationship is therefore not always one invoice to one payment.

Cointab can support more complex matching relationships where required.

---

Withholding-related information can help explain differences

The Nature's Basket ledger includes:

Withhldg tax base amount

This provides additional context where withholding treatment is relevant to the customer transaction.

A customer may record withholding-related information that is not represented in exactly the same way in your ledger.

As a result, the gross invoice value and the eventual amount received or cleared may not always have a simple one-to-one relationship.

When investigating such differences, finance teams may need to consider:

• Invoice value
• Amount received
• Credit or adjustment
• Withholding-related accounting
• Final cleared amount

The reconciliation provides the transaction-level records needed to investigate the difference.

---

Why matching only bank receipts to invoices may be insufficient

Suppose you raise an invoice of:

₹5,00,000

The customer later clears it through a combination of:

• Payment
• Adjustment
• Withholding-related treatment

The bank receipt alone may not equal the original invoice amount.

If the finance team attempts to reconcile only:

Invoice Amount ↔ Bank Receipt

the transaction may appear unresolved.

A customer-ledger reconciliation provides the additional accounting context required to understand how Nature's Basket has treated the transaction.

---

Manual Match for transactions with different references

Some transactions may remain unmatched even though your finance team knows they represent the same commercial activity.

For example:

Your Tally

Reference:

NB/ADJ/JUL/42

Amount:

₹55,000

Nature's Basket

Document Number:

1900872145

Reference key 2:

ADJ42

Amount:

₹55,000

If the automatic reconciliation cannot confidently determine the relationship, you can use:

Manual Match

The workflow allows you to:

1. Select the transaction from your Tally ledger.
2. Select the corresponding Nature's Basket transaction.
3. Review both records.
4. Confirm the match.

The reconciliation then records the transaction as manually reconciled.

---

Manual Match is useful for old open items

Older customer accounts often contain transactions with inconsistent or incomplete references.

Examples include:

• Old invoices
• Manual journals
• Rebooked transactions
• Legacy credit notes
• Payment adjustments
• Incorrectly entered references

Your finance team may understand the relationship based on supporting documents even though no perfect identifier exists in the files.

Manual Match allows the reconciliation to reflect this business judgment without requiring you to alter the original accounting data.

---

Why a simple closing-balance comparison is not enough

Suppose your Tally shows:

Nature's Basket Receivable: ₹41,80,000

The Nature's Basket ledger implies:

Outstanding Balance: ₹39,95,000

Difference:

**₹1,85,000`

Knowing that the balances differ is only the beginning.

The difference may consist of:

• One invoice missing from Nature's Basket
• One cleared transaction still open in your Tally
• One credit note missing internally
• One invoice with a value difference
• Several old timing differences

A transaction-level reconciliation breaks the ₹1,85,000 into the individual records that explain it.

---

Separate customer-side and internal action items

Once the reconciliation has been completed, the unmatched transactions naturally create two different worklists.

Present in your Tally but missing from Nature's Basket

These transactions may require follow-up with the Nature's Basket finance team.

Possible actions include:

• Confirm invoice booking
• Check reference used
• Check document status
• Investigate dispute
• Confirm whether entry belongs to another period

Present in Nature's Basket but missing from your Tally

These transactions usually require an internal review first.

Possible actions include:

• Record a customer receipt
• Book a credit note
• Correct allocation
• Investigate adjustment
• Check another customer account
• Verify whether the Nature's Basket transaction is correct

This makes the reconciliation directly actionable.

---

Use clearing information to prioritize exceptions

Not every unmatched transaction requires the same type of investigation.

For example, compare two Nature's Basket transactions.

Transaction A

No Clearing Document

Transaction B

Clearing Document available
Clearing Date available

Transaction A may still be genuinely outstanding.

Transaction B has already been settled in the customer's books and may deserve immediate investigation if your books still show it as open.

The extra ledger fields therefore provide useful context beyond a simple match/unmatch status.

---

Download the complete Nature's Basket reconciliation in Excel

Once the reconciliation has been reviewed, download the complete working from Cointab.

The Excel output provides a structured record of the reconciliation across:

• Fully Matched transactions
• Partially Matched transactions
• Unmatched transactions
• Manual Matches
• Relevant source-ledger information

The file can be used for:

• Accounts receivable review
• Customer follow-up
• Balance confirmation
• Month-end closing
• Internal finance discussions
• Audit working
• Exception tracking

This gives you a prepared customer reconciliation working rather than a manually maintained lookup workbook.

---

Share missing invoices with Nature's Basket

Suppose Cointab identifies invoices that exist in your Tally but cannot be found in Nature's Basket's ledger.

You can provide their finance team with a focused list containing information such as:

• Invoice number
• Invoice date
• Amount
• Relevant reference

Nature's Basket can then determine whether:

• Invoice has not been booked
• Different reference was used
• Invoice is under review
• Entry belongs to another accounting period
• Transaction has been recorded elsewhere

This is far more actionable than simply telling the customer:

“Our balances do not match.”

---

Investigate cleared items that still appear open in your books

The reverse situation can be equally important.

If Nature's Basket shows a:

• Clearing Document
• Clearing Date

but your corresponding invoice remains open, investigate the internal receipt or adjustment.

The underlying issue may be:

• Payment not allocated
• Receipt posted to another ledger
• Reference mismatch
• Credit adjustment not linked
• Accounting entry missing

This can help clean up old customer outstanding balances.

---

Example: invoice exists in Tally but not in Nature's Basket

Your Tally contains:

Invoice: INV-7245

Amount: ₹3,15,000

The Nature's Basket file contains no corresponding reference.

Cointab reports:

Present in Your Tally but not in Nature's Basket

You share the invoice information with their finance team.

They confirm the invoice was not posted and update their books.

When the revised ledger is uploaded, Cointab can compare the new transaction with your existing invoice.

If the values agree, it becomes:

Fully Matched

---

Example: same invoice, different amount

Suppose both files contain:

Invoice: INV-8421

But:

Your Tally

₹2,80,000

Nature's Basket

₹2,72,500

Cointab classifies the invoice as:

Partially Matched

Your finance team can investigate the:

₹7,500

difference.

The cause may relate to an adjustment, credit, deduction, or incorrect accounting entry.

---

Example: Nature's Basket shows the invoice as cleared

Your Tally contains:

Invoice: INV-9321

Amount: ₹4,50,000

The invoice still appears outstanding internally.

Nature's Basket shows the same invoice together with:

Clearing Document: 2000784521

Clearing Date: 12 August

This provides a strong clue that the customer has already settled or adjusted the item.

Your finance team can now investigate:

• Customer receipt
• Bank collection
• Credit adjustment
• Allocation

instead of treating the invoice simply as an unexplained customer balance.

---

Example: Nature's Basket internal document number differs from your invoice

Your Tally shows:

Document No: INV-10482

Nature's Basket shows:

Document Number: 1900965841

At first glance, these do not match.

However, Nature's Basket also contains:

Reference key 1: INV-10482

The common external reference allows the two transactions to be connected.

This is why reconciliation across several reference fields is important for large-customer ledger matching.

---

Example: customer-side transaction missing from your Tally

Suppose Nature's Basket records:

Reference: CN-5872

Amount: ₹62,000

Your Tally has no corresponding entry.

Cointab reports:

Present in Nature's Basket but not in Your Tally

Your finance team investigates and determines that a corresponding credit adjustment needs to be recorded.

Once the entry is added and the updated Tally ledger uploaded, the transaction can reconcile.

---

Upload corrected ledgers and run the reconciliation again

Customer reconciliation is an iterative process.

Once exceptions have been identified:

• You may correct your Tally
• Nature's Basket may update its ledger
• Payments may be allocated
• Credit notes may be recorded
• Missing invoices may be booked

Upload the latest files again.

Cointab reruns the reconciliation and updates the results.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as the underlying accounting differences are resolved.

---

Repeat the Nature's Basket reconciliation every month

Large customer accounts continuously generate new transactions.

Every month can introduce:

• New sales invoices
• New payments
• Credit notes
• Deductions
• Returns
• Adjustments
• Previously open items

The reconciliation can therefore become a recurring monthly process.

A typical workflow is:

1. Export your latest Nature's Basket customer ledger from Tally.
2. Obtain the latest ledger from Nature's Basket.
3. Upload your Tally ledger into Cointab.
4. Configure the relevant dates, identifiers, and amount fields.
5. Upload the Nature's Basket ledger.
6. Configure reference fields and transaction amounts.
7. Run Customer Reconciliation.
8. Review Fully Matched transactions.
9. Investigate Partially Matched items.
10. Review entries present only in your books.
11. Review entries present only in Nature's Basket.
12. Use clearing information while investigating exceptions.
13. Complete Manual Matches where required.
14. Download the reconciliation working.
15. Correct internal entries.
16. Share customer-side differences with Nature's Basket.
17. Upload revised files where required.

The same reconciliation can then continue into the next month.

---

Previously open invoices can match in a later period

Timing differences are common when reconciling large retail customers.

For example:

June

You raise an invoice on 30 June.

The invoice appears in your Tally ledger.

Nature's Basket has not yet posted it.

The transaction appears unmatched.

July

Nature's Basket records the invoice.

The next ledger now contains the corresponding reference.

Cointab can reconcile the newly available entry against the previously open transaction.

This allows genuine timing differences to resolve naturally over subsequent periods.

---

Customer reconciliation for brands selling through modern retail

Supplying large retail chains introduces different finance requirements compared with direct-to-consumer sales.

On your own website, you may reconcile:

Orders → Payment Gateway → Bank

For a modern-retail customer such as Nature's Basket, the requirement is different:

Sales Invoices → Customer Ledger → Collections and Adjustments

The finance team needs visibility into:

• What was invoiced
• What the customer booked
• What the customer has cleared
• What remains outstanding
• What deductions or adjustments exist
• Which party needs to correct an entry

A structured customer reconciliation is therefore particularly valuable for brands expanding into organized retail.

---

Move from spreadsheet comparisons to exception management

A manual Nature's Basket reconciliation could require the finance team to:

• Export Tally
• Obtain the customer ledger
• Understand multiple reference keys
• Normalize signed amounts
• Search invoice numbers
• Compare document dates
• Compare posting dates
• Review clearing documents
• Check amount differences
• Maintain old open items
• Build Excel formulas
• Add manual comments

This work can repeat every month.

Cointab changes the process to:

Upload Your Tally → Upload Nature's Basket Ledger → Run Reconciliation → Review Exceptions → Resolve Differences

The finance team can spend less time constructing the reconciliation and more time resolving the customer-account issues.

---

How Cointab helps reconcile Tally with Nature's Basket

Cointab's Customer Reconciliation workflow allows you to:

• Upload your Tally customer ledger
• Upload the Nature's Basket ledger
• Configure different transaction-date fields
• Use multiple customer reference fields
• Match against Reference and Reference key fields
• Use Document Number and Text as supporting identifiers
• Interpret different financial amount structures
• Extract useful invoice references from transaction descriptions
• Automatically identify corresponding transactions
• Separate Fully Matched invoices
• Identify Partially Matched invoices
• Identify transactions present only in your books
• Identify transactions present only in Nature's Basket
• Use clearing information while investigating outstanding items
• Manually match genuine transactions with inconsistent references
• Download the complete reconciliation working in Excel
• Upload corrected ledgers and rerun the reconciliation
• Carry unresolved transactions into future periods

---

Automate your Tally vs Nature's Basket customer reconciliation

If you supply Nature's Basket and currently compare their customer ledger manually against your Tally account, Cointab can automate much of the repetitive reconciliation work.

The process becomes:

Your Tally Customer Ledger → Nature's Basket Ledger → Automated Matching → Exception Review → Accounting Corrections → Updated Reconciliation

Invoices that agree are automatically separated.

Invoices with value differences appear as partially matched.

Transactions existing on only one side are clearly identified.

Reference keys, document information, and clearing details provide additional context while investigating exceptions.

Transactions that genuinely belong together but use different references can still be resolved through Manual Match.

Once the reconciliation is complete, the entire working can be downloaded in Excel.

If you currently reconcile your Nature's Basket customer account manually using Tally and Excel, you can use Cointab to automate the process.

Try Cointab

For larger customer ledgers, custom ERP formats, or more complex modern-trade reconciliation requirements:

Book a Demo