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

The two files can look very different.

Your Microsoft Dynamics export may be relatively compact:

• Posting Date
• Document No.
• Description
• Narration
• Customer Order No.
• Debit Amount
• Credit Amount
• Balance

Blinkit's ledger may contain a much richer set of accounting information:

• Assignment
• Document Number
• Document Type
• Document Date
• Amount in Local Currency
• Reference
• Reference Key 1
• Reference Key 2
• Reference Key 3
• Text
• Document Header Text
• Business Place
• Clearing Document
• Clearing Date
• Payment Block
• UTR No.
• Withholding Tax Amount
• Net Due Date
• GSTIN Number

The reconciliation requirement is therefore:

Microsoft Dynamics NAV / Business Central Customer Ledger ↔ Blinkit Ledger

Cointab can compare both datasets and help identify:

• Transactions that agree
• Transactions with amount differences
• Invoices present in Dynamics but not found in Blinkit
• Blinkit transactions missing from Dynamics
• References stored in different fields
• Transactions requiring manual matching

The resulting reconciliation can then be downloaded in Excel and used to investigate the remaining customer-account differences.

---

Why Blinkit customer reconciliation can be difficult

A simple customer reconciliation assumes that both companies store the same invoice number in the same type of field.

In practice, that may not happen.

Your Microsoft Dynamics ledger may have a useful reference in:

Customer Order No.

or inside:

Description

or:

Narration

Blinkit may store the corresponding transaction reference in:

• Assignment
• Reference
• Reference Key 1
• Reference Key 2
• Reference Key 3
• Text
• Document Header Text

Blinkit also generates its own internal:

Document Number

which does not necessarily have any relationship with your Microsoft Dynamics Document No..

This means a simple:

Dynamics Document No. = Blinkit Document Number

lookup may generate a large number of false exceptions.

The reconciliation needs to identify the underlying commercial transaction, even when each accounting system stores it differently.

---

What does your Microsoft Dynamics customer ledger contain?

For this reconciliation, your Dynamics export may contain:

Compared with some larger Business Central exports, this is a relatively focused customer-ledger file.

That can actually make the reconciliation easier.

The key is determining which of:

• Customer Order No.
• Document No.
• Description
• Narration

contains the reference that also appears somewhere in Blinkit's ledger.

---

What does the Blinkit ledger contain?

Blinkit's ledger may contain:

The distinctive feature of this file is the number of possible reference fields available.

An invoice reference may not necessarily be stored in Reference.

It could appear in:

• Assignment
• Reference Key 1
• Reference Key 2
• Reference Key 3
• Text
• Document Header Text

This makes multi-field identification especially useful.

---

Customer Order No. can be an important bridge to Blinkit

Your Microsoft Dynamics file includes:

Customer Order No.

For customer reconciliation, this can provide a valuable commercial reference.

Suppose your Dynamics transaction contains:

Customer Order No.:

BLK-PO-784521

Blinkit may contain the same reference under:

Assignment:

BLK-PO-784521

or perhaps:

Reference Key 1:

BLK-PO-784521

The column names do not need to match.

The important thing is that both records contain the same underlying business identifier.

Cointab allows the relevant identifier fields to be configured independently on each side.

---

One Dynamics reference may appear in any of Blinkit's Reference Key fields

Blinkit provides:

• Reference
• Reference Key 1
• Reference Key 2
• Reference Key 3

This is particularly useful when the customer-side accounting system uses several reference fields for different purposes.

For example:

Microsoft Dynamics

Customer Order No.:

ORD-85214

Blinkit

Reference:

5100784521

Reference Key 1:

ORD-85214

Reference Key 2:

INV-62415

Reference Key 3:

Bangalore

The useful match for your customer order is:

ORD-85214

even though Blinkit's primary Reference field contains something completely different.

A one-column Excel lookup may miss the transaction.

A reconciliation using multiple reference fields has a much better chance of identifying it correctly.

---

How to reconcile Microsoft Dynamics with Blinkit using Cointab

Start a new reconciliation in Cointab and select:

Customer Reconciliation

For this workflow:

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

The process is:

Upload Dynamics Ledger → Upload Blinkit Ledger → Configure References and Amounts → Run Reconciliation → Review Exceptions

---

Step 1: Upload the Microsoft Dynamics ledger

Upload the Blinkit customer ledger exported from Microsoft Dynamics.

Select the date

Choose:

Posting Date

as the relevant transaction date where appropriate.

Select identifiers

Useful identifier fields can include:

• Customer Order No.
• Document No.
• Description
• Narration

Selecting multiple fields can help when an invoice, order, payment, or adjustment reference appears in different places.

Configure debit and credit

Map:

• Debit Amount
• Credit Amount

The Balance field can remain available as useful customer-account context.

---

Step 2: Upload the Blinkit ledger

Upload the ledger received from Blinkit.

Select the date

Possible date fields include:

• Posting Date
• Document Date

Select identifiers

Useful identifier fields may include:

• Assignment
• Reference
• Reference Key 1
• Reference Key 2
• Reference Key 3
• Document Number
• Text
• Document Header Text
• UTR No.

Not every field needs to be selected.

The appropriate configuration depends on where the common invoice, order, and payment references appear.

Configure the amount

Use:

Amount in local currency

as the relevant transaction amount where appropriate.

Cointab can then compare the two datasets.

---

Fully Matched Blinkit transactions

Suppose your Dynamics ledger contains:

Customer Order No.: ORD-78421

Amount: ₹2,40,000

Blinkit's ledger contains:

Reference Key 1: ORD-78421

Amount in local currency: ₹2,40,000

The transaction can be identified on both sides and the value agrees.

Cointab reports:

Fully Matched

The finance team generally does not need to investigate this transaction further at the original-transaction level.

---

Partially Matched Blinkit transactions

Suppose:

Microsoft Dynamics

Customer Order No.:

ORD-96521

Amount:

₹3,20,000

Blinkit

Reference Key 1:

ORD-96521

Amount:

₹3,12,000

The common reference establishes that both records represent the same underlying transaction.

However, there is an:

₹8,000

difference.

Cointab reports:

Partially Matched

The finance team can now investigate the ₹8,000 discrepancy directly.

---

What can cause an amount difference?

Possible reasons include:

• Invoice booked at a different value
• Product return
• Credit adjustment
• Debit adjustment
• Commercial deduction
• Rate difference
• Withholding
• Incorrect accounting entry
• Transaction split differently
• Another customer-side adjustment

The important point is that the underlying transaction has already been found.

Your team can focus on explaining the difference rather than manually searching the complete Blinkit ledger.

---

Transaction in Dynamics but not found in Blinkit

Suppose Dynamics contains:

Customer Order No.: ORD-87542

Amount: ₹2,75,000

but Cointab cannot identify a corresponding Blinkit record through:

• Assignment
• Reference
• Reference Keys
• Text
• Other selected fields

The transaction is reported as:

Present in Microsoft Dynamics but not in Blinkit

Possible explanations include:

• Blinkit has not recorded the transaction yet
• Different reference was used
• Customer processing is pending
• Transaction belongs to another period
• Invoice requires further review

This gives your finance team a specific item to follow up with Blinkit.

---

Transaction in Blinkit but not found in Dynamics

The opposite situation may also occur.

Blinkit may contain:

Reference: CN-78452

Amount: ₹35,000

while your Microsoft Dynamics ledger contains no corresponding entry.

Cointab reports:

Present in Blinkit but not in Microsoft Dynamics

Your finance team can investigate whether:

• Credit note needs to be recorded
• Customer deduction is missing
• Adjustment exists under another reference
• Receipt is not correctly allocated
• Blinkit's transaction needs clarification

This creates a clear internal action item.

---

Do not match Microsoft Dynamics Document No. directly to Blinkit Document Number

Both datasets contain a document-number field.

But they are generated independently.

For example:

Microsoft Dynamics

Document No.:

SI-008521

Customer Order No.:

BLK-78415

Blinkit

Document Number:

5100862451

Reference Key 2:

BLK-78415

The Dynamics document number:

SI-008521

and Blinkit document number:

5100862451

do not need to match.

The commercial relationship is established through:

BLK-78415

A document-number-only reconciliation could therefore produce a false mismatch.

---

Assignment can contain the most useful Blinkit reference

One useful Blinkit field is:

Assignment

Depending on how the transaction is posted, it may contain an invoice, order, or another external business reference.

For example:

Dynamics

Narration:

Blinkit Invoice INV-62418

Blinkit

Assignment:

INV-62418

The matching reference is clear even if Blinkit's:

• Document Number
• Reference
• Posting Date

are all different from the Dynamics record.

---

Reference Keys provide additional matching possibilities

The availability of:

• Reference Key 1
• Reference Key 2
• Reference Key 3

makes this reconciliation different from many simpler customer ledgers.

Suppose:

Dynamics

Description:

Blinkit Inv BL/24/84521

Blinkit

Reference:

Blank

Reference Key 1:

84521

Reference Key 2:

BL

Reference Key 3:

2024

A useful transaction identifier still exists even though it is not in the obvious Reference column.

Cointab can use the relevant reference fields configured during reconciliation.

---

Description and Text may contain the same reference in different formats

Your Microsoft Dynamics ledger provides:

• Description
• Narration

Blinkit provides:

• Text
• Document Header Text

These fields can contain useful references that are embedded inside longer descriptions.

For example:

Dynamics Narration

Blinkit sales invoice BLK/24/86521

Blinkit Text

Against invoice 86521

The underlying identifier is:

86521

A strict full-text lookup would not match the two rows.

---

AI-assisted identifier extraction can help with embedded references

In manual Excel reconciliation, embedded references often require:

• Text cleanup
• LEFT / RIGHT / MID formulas
• FIND formulas
• Helper columns
• Manual searches

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

This can help connect:

Dynamics Description / Narration

with:

Blinkit Text / Header Text / Reference Keys

even where their surrounding descriptions are different.

---

Blinkit Clearing Document tells you whether the item has been cleared

Blinkit's ledger contains:

Clearing Document

This provides useful information after the original transaction has been identified.

Suppose:

Blinkit

Reference Key:

INV-78421

Amount:

₹3,00,000

Clearing Document:

2000874521

Clearing Date:

16 August

This indicates that Blinkit has cleared the transaction in its accounting records.

If your Microsoft Dynamics customer ledger still indicates that the corresponding balance remains outstanding, the finance team can investigate:

• Customer receipt
• Payment allocation
• Missing accounting entry
• Incorrect customer posting
• Adjustment not reflected internally

The problem may therefore be settlement, rather than invoice recognition.

---

Clearing Date provides another useful timeline

Blinkit also provides:

Clearing date

This can help establish when a customer-side transaction was settled.

For example:

Your Dynamics ledger

Posting Date:

28 July

Blinkit

Document Date:

28 July

Clearing Date:

19 August

This may represent a completely normal lifecycle:

Invoice posted → Remains open → Payment received → Invoice cleared

The clearing date provides useful context around when the item stopped being outstanding in Blinkit's records.

---

Payment Block can explain why an invoice has not been settled

One of the most distinctive fields in the Blinkit ledger is:

Payment Block

This can provide valuable information when an invoice exists in both systems but has not yet been paid or cleared.

Consider:

Dynamics

Customer Order No.:

ORD-65218

Transaction remains outstanding.

Blinkit

Corresponding transaction exists.

Payment Block:

Active

No Clearing Document.

The issue is no longer:

"Has Blinkit booked our transaction?"

The transaction is already present.

Instead, the reconciliation can help identify that the item may require investigation around its payment processing status.

The finance team can follow up on the specific blocked transaction rather than sending a generic outstanding statement.

---

Payment Block and missing invoice are very different exceptions

Consider two outstanding Dynamics transactions.

Transaction A

No corresponding Blinkit transaction can be identified.

Transaction B

Blinkit transaction exists, but Payment Block is populated and the item is uncleared.

Both appear outstanding internally.

But the next action is different.

For Transaction A:

Investigate invoice recognition.

For Transaction B:

Investigate why the recognized transaction remains blocked or uncleared.

This is why bringing Blinkit's accounting fields into the customer reconciliation can make the output significantly more actionable.

---

UTR No. can help trace a customer payment

Blinkit's ledger contains:

UTR No

This can be extremely useful when the customer has already made payment.

Your Microsoft Dynamics:

Narration

or:

Description

may contain the corresponding bank/payment reference.

For example:

Blinkit

UTR No.:

HDFC874521963

Dynamics

Narration:

Blinkit receipt HDFC874521963

The common UTR can connect the customer-side clearing/payment information with the receipt recorded in your own books.

---

When Blinkit shows a UTR but your customer balance is still open

Suppose Blinkit contains:

UTR No.: ICICI98521463

Clearing Document: populated

Clearing Date: populated

But your Microsoft Dynamics ledger still contributes the transaction to the outstanding customer balance.

This tells your finance team where to look:

• Was the money received in the bank?
• Was the customer receipt posted?
• Was it posted against the correct Blinkit account?
• Was the receipt applied to the appropriate invoice?
• Was another reference used?

The reconciliation can therefore help locate unallocated or incorrectly applied customer receipts.

---

Withholding tax can explain why settlement differs from the invoice amount

Blinkit's file also contains:

Withholding tax amnt

Suppose:

Original transaction

₹1,00,000

Cash received

₹98,000

Blinkit withholding

₹2,000

A simple comparison of invoice amount against customer receipt would appear to show a ₹2,000 short payment.

The withholding information provides additional context.

Your finance team can then verify whether the corresponding withholding treatment has been accounted for correctly in Microsoft Dynamics.

---

Do not treat every lower payment as an amount mismatch

When reviewing customer settlement, a lower amount can have several explanations.

For example:

• Withholding tax
• Credit note
• Commercial adjustment
• Product return
• Customer deduction
• Genuine short payment

The objective of reconciliation is first to identify the related transactions and then determine why the financial position differs.

This avoids treating every difference as an accounting error.

---

Net Due Date helps distinguish reconciliation from collections

Blinkit's ledger also contains:

Net due date

This becomes useful after the transaction itself has been reconciled.

Consider two fully matched transactions.

Invoice A

Net Due Date: Next week
No Clearing Document

Invoice B

Net Due Date: 45 days ago
No Clearing Document

Both invoices may reconcile correctly.

But Invoice B may require collection follow-up.

This separates two finance processes.

Reconciliation

Do both parties agree on the transaction?

Collections

Has an agreed transaction been paid when due?

---

Payment Block adds another dimension to ageing

An overdue transaction can have very different meanings depending on Blinkit's accounting status.

For example:

These situations should not all receive the same follow-up.

A reconciliation enriched with Blinkit's payment and clearing fields can help prioritize the next action.

---

Business Place can help distinguish transactions across Blinkit operations

Blinkit provides:

Business Place

This may provide additional context where transactions relate to different business or accounting locations.

Suppose several transactions have:

• Similar dates
• Similar amounts
• Similar descriptions

but correspond to different business places.

The Business Place can help the finance team distinguish the relevant entries during exception investigation.

It does not necessarily need to drive the primary match, but it can provide useful supporting information.

---

GSTIN Number can help validate the correct transaction population

Blinkit also provides:

GSTIN Number

This can be useful where transactions span different GST registrations or locations.

For companies supplying large customers across multiple states or registrations, an invoice may need to be associated with the correct customer GSTIN.

If a reconciliation exception appears unusual, GSTIN can provide another way to check whether:

• Correct customer entity is being reconciled
• Correct location is involved
• Transaction belongs to another registration

Again, this is typically supporting context rather than the primary invoice identifier.

---

Special G/L Indicator can provide accounting context

Blinkit's ledger includes:

Special G/L ind.

This field may help identify transactions that are treated differently from standard accounting items.

It does not normally need to drive the transaction match.

However, when a row behaves differently from a normal invoice or payment, the field can provide useful accounting context during investigation.

---

Document Type helps separate invoices, credits and other entries

Blinkit also provides:

Document Type

When an unmatched Blinkit transaction appears, the finance team should first understand what kind of accounting entry it represents.

It could be:

• Invoice
• Credit
• Payment
• Adjustment
• Another financial document

This is important because a Blinkit-only amount should not automatically be interpreted as a missing invoice in Microsoft Dynamics.

The expected corresponding transaction depends on the document type.

---

Debit and credit need to be interpreted from opposite accounting perspectives

Your Dynamics ledger contains:

• Debit Amount
• Credit Amount

Blinkit provides:

Amount in local currency

as its transaction value.

Remember that the commercial relationship is recorded from opposite perspectives.

In your Microsoft Dynamics system:

Blinkit is your customer.

In Blinkit's accounting system:

Your company is the supplier/vendor.

The financial direction therefore needs to be configured appropriately when comparing both datasets.

---

Balance helps quantify the Microsoft Dynamics receivable position

Your Dynamics export includes:

Balance

This provides useful account-level context.

For example:

Dynamics Blinkit balance: ₹42,50,000

But the objective of reconciliation is not simply to find whether Blinkit's ledger also totals ₹42,50,000.

If the balances differ, you need the transaction-level explanation.

A difference of ₹1,00,000 could consist of:

• One invoice missing from Blinkit
• One blocked invoice
• One payment already cleared by Blinkit but not reflected internally
• One withholding adjustment
• Several smaller exceptions

Cointab breaks the balance difference into these underlying transactions.

---

Example: Customer Order No. matches Blinkit Assignment

Microsoft Dynamics

Customer Order No.:

ORD-78521

Debit Amount:

₹2,80,000

Blinkit

Assignment:

ORD-78521

Amount:

₹2,80,000

The transaction and amount agree.

Cointab reports:

Fully Matched

---

Example: the common reference is hidden in Reference Key 2

Dynamics

Narration:

Blinkit Invoice BLK-96421

Blinkit

Reference:

Blank

Reference Key 1:

510085421

Reference Key 2:

BLK-96421

Reference Key 3:

Mumbai

The useful common identifier is in:

Reference Key 2

rather than the main Reference column.

Cointab can use the selected reference fields to identify the transaction.

---

Example: invoice exists but amount differs

Microsoft Dynamics

Customer Order No.:

ORD-65218

Amount:

₹3,50,000

Blinkit

Assignment:

ORD-65218

Amount in local currency:

₹3,42,000

Cointab reports:

Partially Matched

Difference:

₹8,000

The finance team can investigate the specific value difference.

---

Example: Blinkit transaction is payment-blocked

Dynamics

Transaction:

INV-78421

Still contributes to the outstanding customer balance.

Blinkit

Reference:

INV-78421

Payment Block:

Populated

Clearing Document:

Blank

The invoice is present in both datasets.

The issue is therefore not whether Blinkit has recognized it.

The finance team can focus its follow-up on the payment-block status.

---

Example: Blinkit has cleared the transaction but Dynamics still shows it outstanding

Blinkit

Reference:

INV-85241

Clearing Document:

2000874512

Clearing Date:

18 August

UTR No.:

HDFC78521469

Microsoft Dynamics

The corresponding transaction remains part of the customer balance.

The next investigation should focus on:

• Bank receipt
• Dynamics customer receipt
• Payment application
• Customer allocation

rather than invoice recognition.

---

Example: withholding explains a settlement difference

Invoice value

₹2,00,000

Blinkit withholding tax

₹4,000

Net payment

₹1,96,000

If the Microsoft Dynamics receivable still contains the ₹4,000 difference, the finance team can investigate the corresponding withholding accounting rather than treating it immediately as a Blinkit short payment.

---

Example: Blinkit entry exists but is missing from Dynamics

Blinkit contains:

Document Type: Credit

Reference: CN-8542

Amount: ₹36,000

No corresponding Microsoft Dynamics transaction can be identified.

Cointab reports:

Present in Blinkit but not in Microsoft Dynamics

Your team can investigate whether:

• Credit note needs to be recorded
• Customer deduction is valid
• Transaction exists under another reference
• Blinkit's entry requires clarification

---

Manual Match for references that cannot be connected automatically

Some genuine transactions may remain unmatched.

For example:

Dynamics

Narration:

Blinkit commercial adjustment Aug

Credit Amount:

₹28,500

Blinkit

Document Number:

1900874521

Header Text:

Rate Adjustment

Amount:

₹28,500

Your finance team knows from supporting documentation that both entries represent the same transaction.

Cointab provides:

Manual Match

You can:

1. Select the Microsoft Dynamics transaction.
2. Select the corresponding Blinkit transaction.
3. Review both records.
4. Confirm the relationship.

The transaction is then recorded as manually reconciled.

---

A useful way to classify Blinkit reconciliation exceptions

Instead of looking at one large unmatched list, Blinkit exceptions can be understood by their likely stage.

Reference problem

The transaction exists, but your reference is stored in a different Blinkit field.

Review:

• Assignment
• Reference
• Reference Keys
• Text
• Header Text

Recognition problem

The transaction exists in Dynamics but cannot be found in Blinkit.

Follow up on whether it has been recorded.

Amount problem

The transaction exists on both sides but the financial values differ.

Investigate deductions, credits or other adjustments.

Payment-processing problem

The transaction exists but Blinkit shows:

Payment Block

Investigate the reason for the block.

Settlement problem

Blinkit shows:

• Clearing Document
• Clearing Date
• UTR

but the corresponding Dynamics position still appears outstanding.

Investigate receipt posting and application.

Withholding problem

The apparent balance difference may be explained by:

Withholding tax amnt

rather than an unpaid customer amount.

This classification makes the reconciliation much easier to act on.

---

Create separate internal and Blinkit follow-up lists

Once the reconciliation is complete, exceptions can also be routed based on which finance team needs to act.

Follow up with Blinkit

Examples:

• Dynamics invoice not found in Blinkit
• Invoice amount differs
• Payment Block requires clarification
• Customer-side accounting reference is unclear
• Overdue item remains uncleared

Investigate internally

Examples:

• Blinkit transaction missing from Dynamics
• Blinkit shows clearing but Dynamics remains outstanding
• UTR exists but receipt is not allocated
• Credit is missing internally
• Withholding entry needs to be accounted for

This converts reconciliation into a practical resolution workflow.

---

Download the complete Microsoft Dynamics vs Blinkit reconciliation in Excel

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

The Excel output can contain:

• Fully Matched transactions
• Partially Matched transactions
• Unmatched transactions
• Manual Matches
• Microsoft Dynamics transaction details
• Blinkit transaction details

Useful Blinkit fields can remain available for investigation, including:

• Assignment
• Reference
• Reference Key 1
• Reference Key 2
• Reference Key 3
• Clearing Document
• Clearing Date
• Payment Block
• UTR No.
• Withholding tax amount
• Net Due Date
• Business Place

This makes the output useful not just as reconciliation evidence but also as an accounts-receivable action list.

---

Use transaction-level details when following up with Blinkit

Instead of sending:

"Our Blinkit balance does not match yours."

your finance team can communicate precise exceptions.

For example:

• Invoice INV-7842 does not appear in the Blinkit ledger.
• Transaction ORD-6521 differs by ₹8,000.
• Invoice INV-8421 is present but shows a Payment Block.
• Invoice INV-9251 was cleared under UTR 78521469 but remains open in our books.
• Credit CN-8542 appears in Blinkit but is not recorded internally.

This is much easier for both finance teams to investigate.

---

Correct the underlying records and reconcile again

Once differences have been reviewed:

• Blinkit may book a missing invoice
• Payment block may be resolved
• Customer receipt may be recorded internally
• Receipt may be applied against the correct transaction
• Credit may be booked
• Withholding may be accounted for
• Amount may be corrected

Upload the latest ledgers into Cointab and run the reconciliation again.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as the underlying accounting position becomes aligned.

---

Repeat Microsoft Dynamics vs Blinkit reconciliation every month

If you supply Blinkit regularly, the customer account changes continuously.

Each month can introduce:

• New invoices
• New customer orders
• New payments
• New clearing documents
• Withholding entries
• Credits
• Previously outstanding items

A recurring monthly workflow can be:

1. Export the latest Blinkit customer ledger from Microsoft Dynamics NAV / Business Central.
2. Obtain the latest Blinkit ledger.
3. Upload the Dynamics file into Cointab.
4. Configure Posting Date.
5. Select Customer Order No., Document No., Description, and Narration as relevant identifiers.
6. Map Debit Amount and Credit Amount.
7. Upload the Blinkit file.
8. Configure Assignment, Reference, Reference Keys, Text, and other useful identifiers.
9. Configure Amount in Local Currency.
10. Run Customer Reconciliation.
11. Review Fully Matched transactions.
12. Investigate Partially Matched transactions.
13. Review Dynamics transactions missing from Blinkit.
14. Review Blinkit transactions missing from Dynamics.
15. Check Payment Block for recognized but unsettled items.
16. Review Clearing Document, Clearing Date, and UTR where Blinkit shows settlement.
17. Investigate withholding-related differences.
18. Complete Manual Matches where required.
19. Download the reconciliation working.
20. Correct internal accounting entries.
21. Share Blinkit-side exceptions with their finance team.
22. Upload revised files and reconcile again.

---

Previously unmatched Blinkit transactions can reconcile later

Timing differences are normal.

For example:

July

Microsoft Dynamics contains a transaction raised at the end of the month.

Blinkit's July ledger does not yet contain it.

Cointab reports:

Present in Microsoft Dynamics but not in Blinkit

August

Blinkit's latest ledger now contains the corresponding reference in:

• Assignment
• Reference
• Reference Key

Cointab can match the previously open transaction.

Later, Blinkit may add:

• Clearing Document
• Clearing Date
• UTR

as the transaction progresses through payment.

This allows the reconciliation to continue across accounting periods rather than forcing every timing difference to be resolved within one month's file.

---

Why this reconciliation is different from a standard invoice lookup

The distinctive challenge in Microsoft Dynamics vs Blinkit reconciliation is not simply comparing:

Invoice Number ↔ Invoice Number

Your compact Dynamics ledger may contain the commercial reference in:

• Customer Order No.
• Description
• Narration

Blinkit may contain it in:

• Assignment
• Reference
• Reference Key 1
• Reference Key 2
• Reference Key 3
• Text
• Document Header Text

After the transaction is found, Blinkit's:

• Payment Block
• Clearing Document
• Clearing Date
• UTR
• Withholding Tax

can help explain why the corresponding receivable remains unresolved.

The result is therefore both a transaction matching exercise and an open-receivable investigation workflow.

---

Move from manual Blinkit Excel reconciliation to exception management

A manual Microsoft Dynamics vs Blinkit reconciliation may require the finance team to:

• Export the Dynamics customer ledger
• Obtain the Blinkit ledger
• Search Customer Order Numbers
• Check Assignment
• Check several Reference Key fields
• Search descriptions and narrations
• Compare debit and credit values
• Review clearing documents
• Check UTRs
• Check payment blocks
• Investigate withholding
• Maintain an Excel exception tracker

Cointab changes this process to:

Upload Dynamics → Upload Blinkit → Run Reconciliation → Review Exceptions → Resolve

Instead of manually searching every Blinkit reference field for every invoice, the finance team can focus on the transactions that genuinely require attention.

---

How Cointab helps reconcile Microsoft Dynamics with Blinkit

Cointab's Customer Reconciliation workflow can help you:

• Upload your Microsoft Dynamics NAV / Business Central customer ledger
• Upload the Blinkit ledger
• Reconcile files with very different structures
• Use Dynamics Customer Order No. as a commercial reference
• Use Blinkit Assignment and Reference fields
• Use Reference Key 1, Reference Key 2, and Reference Key 3 where relevant
• Use Dynamics Description and Narration as supporting identifiers
• Use Blinkit Text and Document Header Text as supporting identifiers
• Extract useful references from transaction descriptions
• Automatically identify corresponding transactions
• Separate Fully Matched transactions
• Identify transactions with amount differences
• Identify Dynamics transactions missing from Blinkit
• Identify Blinkit transactions missing from Dynamics
• Review Payment Block for unsettled items
• Review Clearing Document and Clearing Date
• Use UTR references to investigate customer receipts
• Investigate withholding-related differences
• Manually match genuine transactions with inconsistent references
• Download the complete reconciliation working in Excel
• Upload corrected files and reconcile again
• Continue resolving open transactions across future periods

---

Automate Microsoft Dynamics vs Blinkit customer reconciliation

If your company supplies Blinkit and currently reconciles 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 → Blinkit Ledger → Multi-Reference Matching → Payment & Clearing Review → Exception Resolution

You can identify:

• Transactions that agree
• Transactions with amount differences
• Invoices missing from Blinkit
• Blinkit transactions missing from Dynamics
• References stored in Assignment or Reference Key fields
• Transactions with a Payment Block
• Items Blinkit has already cleared
• UTRs requiring internal receipt investigation
• Withholding-related differences
• Older unresolved customer-account transactions

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

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

Try Cointab

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

Book a Demo