If your company supplies products to Apollo Pharmaproducts Pvt Ltd and maintains the customer account in Microsoft Dynamics NAV or Dynamics 365 Business Central, your finance team may periodically need to compare your customer ledger with the ledger received from Apollo.

Both datasets represent the same commercial relationship, but they can look completely different.

Your Microsoft Dynamics customer ledger may contain detailed information relating to:

• Customer invoices
• Original and remaining amounts
• Payment application
• TDS
• Due dates
• Open-item status
• Branches
• Profit centres
• GST
• Product categories
• Customer references

Apollo's ledger may instead provide a more transaction-oriented view containing:

• Invoice No
• Invoice Date
• Voucher
• Document Num
• Location
• Channel
• Debit
• Credit
• Net Amount
• Payment Reference / Narration
• External doc no
• Posting Profile

The reconciliation requirement is:

Your Microsoft Dynamics Customer Ledger ↔ Apollo Pharmaproducts Customer Ledger

Cointab can compare both files and automatically categorize the transactions into:

• Fully Matched
• Partially Matched
• Present in your Dynamics ledger but not found in Apollo
• Present in Apollo but not found in your Dynamics ledger
• Manually Matched

This provides a transaction-level explanation of the customer balance instead of leaving the finance team to manually compare two large ledger exports in Excel.

---

Why reconcile your Apollo Pharmaproducts customer account?

When you supply a large customer regularly, the outstanding balance can contain transactions from several periods.

The customer account may include:

• New invoices
• Older unpaid invoices
• Customer payments
• Credit notes
• Debit adjustments
• TDS entries
• Returns
• Commercial deductions
• Previously disputed items

Your books may show one receivable balance.

Apollo's books may show another.

The important question is not merely:

"Why are our balances different?"

You need to identify the exact transactions behind that difference.

For example:

• Which invoice is missing?
• Which invoice exists on both sides but at a different value?
• Has Apollo recorded a payment that is not applied in your books?
• Is the transaction recorded under a different external document number?
• Does a transaction relate to a particular location or channel?
• Has an adjustment been posted using another voucher?
• Is an old invoice still open internally even though the customer has settled it?

Customer reconciliation converts these questions into a structured exception list.

---

What does your Microsoft Dynamics customer ledger contain?

Microsoft Dynamics NAV / Business Central customer-ledger exports can be extremely detailed.

Relevant fields may include:

Your actual Dynamics export may contain many more columns relating to:

• GST
• State
• Location
• Cost centres
• Brand
• Product category
• HSN / SAC
• TDS certificate tracking
• Payment tolerances
• Customer groups

You do not need to use every field for reconciliation.

A smaller set of dates, identifiers, and amount columns can drive the match while the remaining information stays available for investigation.

---

What does the Apollo Pharmaproducts ledger contain?

The Apollo-side ledger may contain:

This creates several possible ways of linking Apollo's records back to your Dynamics ledger.

A transaction may be identifiable through:

• Invoice No
• External doc no
• Payment Reference / Narration
• Description
• Voucher
• Document Num

The best identifier may differ by transaction type.

---

Apollo reconciliation is not just an invoice-number comparison

The obvious first step is to match:

Dynamics invoice reference ↔ Apollo Invoice No

But the customer ledger contains more information than that.

Suppose an invoice is not found using the Invoice No field.

The same transaction may still be identifiable through:

• External doc no
• Payment Reference / Narration
• Description
• Document Num

Similarly, payment-related entries may not have an invoice number at all.

This means the reconciliation should consider several reference fields instead of relying on one exact VLOOKUP.

---

How to reconcile Dynamics with Apollo Pharmaproducts in Cointab

Start a new reconciliation in Cointab and choose:

Customer Reconciliation

For this workflow:

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

The process becomes:

Upload Dynamics Ledger → Upload Apollo Ledger → Configure Relevant Fields → Run Reconciliation → Review Exceptions

---

Step 1: Upload your Dynamics customer ledger

Export the Apollo Pharmaproducts customer account from Microsoft Dynamics.

Upload the file to Cointab.

Because your file may contain dozens of fields, select only those relevant to matching.

Select the transaction date

Possible fields include:

• Posting Date
• Document Date

Use the date that best represents your reconciliation process.

Select transaction identifiers

Useful fields may include:

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

These fields can contain the invoice, payment, credit-note, or transaction references required for matching.

Select the amount

Configure the relevant financial field such as:

• Original Amount
• Amount
• Amount (LCY)

depending on how your ledger is exported.

---

Step 2: Upload the Apollo customer ledger

Upload the ledger received from Apollo Pharmaproducts.

Select the transaction date

Potential fields include:

• Trans Date
• Invoice Date

Select identifiers

Useful identifiers may include:

• Invoice No
• External doc no
• Payment Reference / Narration
• Document Num
• Voucher
• Description

Select amounts

Apollo provides:

• Debit
• Credit
• Net Amount

These fields can be configured based on the required reconciliation structure.

Once both files are mapped, the reconciliation can begin.

---

Step 3: Run Customer Reconciliation

Start the reconciliation.

Cointab analyzes the configured identifiers and financial values in both ledgers.

For invoice transactions, the first objective is to establish:

1. Does the same invoice exist in both ledgers?
2. If it exists, do the amounts agree?

The results are categorized automatically.

---

Fully Matched Apollo invoices

An invoice is Fully Matched when the same transaction can be identified in both systems and the financial values agree.

For example:

Microsoft Dynamics

External Document No.:

INV-72415

Original Amount:

₹2,40,000

Apollo Pharmaproducts

Invoice No:

INV-72415

Net Amount:

₹2,40,000

The invoice exists in both ledgers and there is no amount difference.

Cointab classifies the transaction as:

Fully Matched

These transactions generally require no further invoice-level investigation.

---

Partially Matched invoices

An invoice may exist in both ledgers while the amounts disagree.

For example:

Dynamics

External Document No.:

INV-72415

Amount:

₹2,40,000

Apollo

Invoice No:

INV-72415

Net Amount:

₹2,35,000

The invoice number establishes the relationship.

However, the values differ by:

₹5,000

Cointab therefore classifies the transaction as:

Partially Matched

The finance team can now investigate the ₹5,000 difference rather than searching through both ledgers to determine whether the invoice exists.

---

What may cause an amount difference?

A partially matched Apollo invoice may require investigation for reasons such as:

• Incorrect invoice amount
• Credit note
• Debit note
• Customer deduction
• TDS
• Sales return
• Pricing adjustment
• Commercial claim
• Incorrect posting
• Transaction split across multiple rows

The invoice relationship is already established.

The remaining work is to explain the financial difference.

---

Invoice present in Dynamics but not found in Apollo

Suppose your Dynamics ledger contains:

External Document No.: INV-83521

Amount: ₹3,15,000

but Cointab cannot identify a corresponding Apollo transaction.

The invoice is shown as:

Present in Your Ledger but not in Apollo

Possible explanations include:

• Apollo has not booked the invoice
• Invoice is pending processing
• Apollo used another reference
• Transaction belongs to another period
• Invoice is under review
• Invoice was missed by the customer

You can share this specific list of invoices with Apollo's finance team.

---

Transaction present in Apollo but missing from Dynamics

The opposite situation can also occur.

Apollo may contain:

External doc no: CN-8452

Net Amount: ₹35,000

while no corresponding record exists in your Dynamics customer ledger.

Cointab reports:

Present in Apollo but not in Your Ledger

Your finance team can investigate whether:

• Credit note is missing
• Customer deduction has not been booked
• Payment adjustment is unallocated
• Transaction exists under another Dynamics reference
• Apollo's accounting entry needs clarification

This becomes an internal action item.

---

Invoice No can provide the primary transaction link

The Apollo ledger contains:

Invoice No

This can often provide the clearest connection with your invoice.

For example:

Dynamics

External Document No.:

APL/25/78451

Apollo

Invoice No:

APL/25/78451

This common commercial identifier is more useful than comparing internal document numbers created independently by each accounting system.

---

External document numbers provide a second matching route

Apollo also provides:

External doc no

Your Dynamics data contains:

External Document No.

Depending on how the ledgers are maintained, these can provide another strong relationship.

For example:

Dynamics

External Document No.:

INV-98521

Apollo

External doc no:

INV-98521

Even if Apollo's internal:

• Voucher
• Document Num

are completely different from your Dynamics Document No., the external reference can connect the two transactions.

---

Internal vouchers do not need to match

Consider:

Microsoft Dynamics

Document No.:

SI-0097845

Apollo

Voucher:

AR-458721

Document Num:

1900785421

These internal identifiers may have no relationship.

That is normal.

Both organizations generate their own accounting references.

The reconciliation should instead search for common commercial information such as:

• Invoice No
• External Document No.
• Amount
• Transaction date
• Supporting descriptions

---

Location can help investigate similar transactions

Apollo's file includes:

Location

This can provide valuable context when multiple transactions look similar.

For example, you may have two invoices with:

• Similar dates
• Similar amounts
• Similar descriptions

but relating to different Apollo locations.

Location helps distinguish those records during exception review.

This can be especially useful where supplies are made across several:

• Warehouses
• Distribution points
• Business locations
• Operating units

---

Channel provides another dimension for investigation

The Apollo ledger also contains:

Channel

This can help explain how a transaction has been classified on the customer side.

For businesses supplying through different commercial arrangements, a transaction may belong to a particular:

• Sales channel
• Distribution channel
• Business stream
• Customer program

Channel may not necessarily be required for the primary invoice match.

But it can be valuable when reviewing an unmatched or differently classified transaction.

---

Location and Channel can help segment a large customer account

Suppose the total Apollo account contains thousands of transactions.

An unmatched population can be easier to investigate when it can also be understood by:

Location + Channel

For example:

• 12 unmatched invoices in Location A
• 2 unmatched invoices in Location B
• 8 amount differences in a particular Channel

This can help reveal whether a reconciliation issue is concentrated in a specific part of the customer relationship.

---

Posting Profile can help explain accounting treatment

Apollo's file includes:

Posting Profile

This is another useful investigation field.

Different transaction types may be posted through different accounting profiles.

For example, an unmatched item may relate to:

• Standard receivable
• Payment
• Adjustment
• Another accounting classification

Posting Profile may not be the first field used to identify an invoice.

However, it can help the finance team understand why a transaction is behaving differently from a normal sales entry.

---

Journal Description helps identify non-invoice transactions

Apollo also provides:

Journal Description

An unmatched entry may not necessarily be another customer invoice.

It could represent:

• Payment
• Journal adjustment
• Credit
• Transfer
• Another accounting transaction

The Journal Description can help the finance team understand the nature of the exception before deciding what action to take.

---

Payment Reference / Narration can help reconcile customer receipts

One of the most useful fields in the Apollo dataset is:

Payment Reference / Narration

Payments often use references that are completely different from invoice numbers.

For example:

Apollo

Payment Reference:

UTR HDFC874521963

Dynamics

Narration:

Receipt HDFC874521963 Apollo

The common bank or payment reference can connect the transactions even if:

• Voucher numbers differ
• Posting dates differ
• No invoice number exists on the payment line

This makes customer reconciliation useful for payment matching as well as invoice matching.

---

Customer payment reconciliation is different from invoice reconciliation

A customer account has two separate questions.

Invoice reconciliation

Does Apollo recognize the invoice that you raised?

Receipt reconciliation

Does the payment recorded by Apollo correspond to the receipt and application in your Dynamics ledger?

An invoice can be Fully Matched while its payment is still unresolved.

Keeping these stages separate helps finance teams identify the real cause of the outstanding balance.

---

One Apollo payment may cover multiple invoices

Large customers may make consolidated payments.

For example, Apollo could have four invoices:

• INV-101 — ₹1,00,000
• INV-102 — ₹1,50,000
• INV-103 — ₹75,000
• INV-104 — ₹1,25,000

and make one payment of:

₹4,50,000

Your Dynamics ledger may therefore contain one customer receipt while Apollo has four underlying invoice records.

This creates a:

many invoices → one payment

relationship.

Similarly, one invoice may be paid in multiple installments.

This is why a complete customer reconciliation cannot rely purely on one-to-one amount matching.

---

Net Amount can simplify Apollo-side comparison

Apollo provides:

Net Amount

alongside:

• Debit
• Credit

This can be particularly useful for reconciliation because it gives a normalized transaction value.

Instead of manually building an Excel formula to convert debit and credit into one comparable amount, the finance team may be able to use the available net value directly where appropriate.

The correct configuration depends on the transaction structure used in the file.

---

Debit and credit direction still provides useful context

Although Net Amount is convenient, the underlying:

• Debit
• Credit

columns remain useful.

They can help determine whether the transaction represents:

• Invoice
• Payment
• Credit
• Adjustment

When reviewing an exception, the direction of the accounting entry can provide important context.

---

AI-assisted identifier extraction from descriptions

Accounting references may not always be stored cleanly.

For example:

Dynamics Narration

Apollo invoice AP/784521 Bangalore

Apollo Description

Purchase Inv 784521

The underlying identifier is:

784521

A strict spreadsheet lookup may fail because the text strings are different.

Cointab can use AI-assisted processing to identify useful transaction references from configured ledger fields and use them while matching.

This reduces the need to manually create:

• Helper columns
• Text-extraction formulas
• Cleaned reference fields
• Multiple Excel lookups

---

Payment narration can contain useful references too

The same applies to payments.

For example:

Dynamics

Narration:

Receipt Apollo UTR 98214567

Apollo

Payment Reference / Narration:

Payment 98214567

The common reference is embedded inside larger text.

AI-assisted identifier extraction can help identify such relationships during reconciliation.

---

Manual Match when the finance team knows the relationship

Some transactions may still remain unmatched even though the finance team knows they belong together.

For example:

Dynamics

Narration:

Apollo Adjustment August

Amount:

₹42,000

Apollo

Journal Description:

Rate Adjustment

Voucher:

ADJ-78521

Net Amount:

₹42,000

The source references are not the same.

However, the finance team may have supporting documents proving that both records represent the same transaction.

Cointab's Manual Match option allows the user to:

1. Select the Dynamics transaction.
2. Select the corresponding Apollo transaction.
3. Review both entries.
4. Confirm the match.

The relationship is then included in the reconciliation.

---

Use Remaining Amount to understand unresolved receivables

Your Dynamics ledger provides:

• Remaining Amount
• Remaining Amt. (LCY)

These fields can be especially useful after the original invoice has been matched.

Suppose:

Original Amount

₹5,00,000

Remaining Amount

₹80,000

The invoice itself may be Fully Matched with Apollo.

But ₹80,000 remains open in your books.

The next investigation may involve:

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

This separates the invoice-recognition problem from the outstanding-receivable problem.

---

Open status can tell you whether the transaction still requires settlement

Microsoft Dynamics provides an:

Open

indicator.

An invoice can therefore have two different statuses.

Reconciliation status

Fully Matched

Both parties agree on the invoice.

Dynamics status

Open

The transaction has not yet been completely settled.

This distinction is useful.

A Fully Matched invoice does not automatically mean the customer has paid it.

---

Due Date helps separate reconciliation issues from collection issues

Your Dynamics ledger also contains:

Due Date

Suppose an invoice is Fully Matched.

If its due date is still in the future, there may be no action required.

If it became due 60 days ago and remains open, the issue may now be collection rather than reconciliation.

This gives the finance team three useful questions:

1. Does the invoice exist in both ledgers?
2. Do both sides agree on its value?
3. Is the agreed invoice still outstanding?

---

TDS can explain differences between invoice and settlement

Your Dynamics file contains detailed TDS information.

Relevant fields may include:

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

Suppose the invoice is:

₹2,00,000

but the actual customer receipt is:

₹1,96,000

A ₹4,000 difference may be explained by TDS rather than a short payment.

Once the invoice itself is reconciled, the finance team can use the TDS information in Dynamics to understand the settlement.

---

Customer deductions need separate investigation

Not every difference between an invoice and a receipt is TDS.

Other possibilities include:

• Rate difference
• Product return
• Commercial deduction
• Promotional adjustment
• Debit note
• Short payment

A customer reconciliation makes it easier to distinguish these situations because the underlying transactions are visible separately.

---

Example: invoice agrees completely

Dynamics

External Document No.:

INV-98541

Original Amount:

₹1,90,000

Apollo

Invoice No:

INV-98541

Net Amount:

₹1,90,000

Cointab reports:

Fully Matched

No invoice-level discrepancy exists.

---

Example: Apollo has the invoice at a different amount

Dynamics

Invoice:

INV-64218

Amount:

₹3,75,000

Apollo

Invoice:

INV-64218

Net Amount:

₹3,68,000

The invoice is:

Partially Matched

Difference:

₹7,000

Your finance team can immediately investigate the ₹7,000 rather than comparing the entire customer ledger.

---

Example: invoice exists only in your Dynamics ledger

Your Dynamics account contains:

Invoice: INV-78251

Amount: ₹2,30,000

Apollo has no corresponding invoice or external reference.

Cointab reports:

Present in Your Ledger but not in Apollo

You can provide Apollo with:

• Invoice No.
• Invoice Date
• Amount
• Relevant supporting details

for investigation.

---

Example: Apollo has a transaction missing from your books

Apollo contains:

Document Num: 190078452

External doc no: CN-5842

Net Amount: ₹30,000

Your Dynamics customer ledger has no corresponding credit.

The transaction appears as:

Present in Apollo but not in Your Ledger

Your finance team can investigate whether:

• A credit note needs to be booked
• Apollo has taken a deduction
• The transaction exists under another reference
• The customer entry requires clarification

---

Example: payment references connect transactions

Apollo shows:

Payment Reference / Narration:

UTR 8745123698

Your Dynamics ledger contains:

Narration:

Receipt Apollo UTR 8745123698

The matching payment reference can connect the two records even if their voucher numbers and posting dates are different.

---

Example: Location helps distinguish two similar invoices

Suppose Apollo has two transactions with:

• Same amount
• Same invoice date
• Similar descriptions

but:

Transaction A

Location: Mumbai

Transaction B

Location: Bangalore

Location provides additional context to prevent the wrong transaction from being linked during investigation.

---

Example: Channel reveals where an issue is concentrated

Suppose most Apollo transactions reconcile automatically, but several unmatched invoices belong to one specific Channel.

That may indicate a process issue affecting only that segment.

For example:

• Invoice references generated differently
• Separate internal processing workflow
• Adjustment mechanism differs
• Another operational team is involved

The reconciliation output therefore can reveal patterns beyond individual transaction differences.

---

From a large customer ledger to a manageable exception list

A Microsoft Dynamics ledger can contain dozens of columns.

The Apollo ledger adds further dimensions such as:

• Location
• Channel
• Posting Profile
• Journal Description

But the finance team does not need to manually review all those fields for every transaction.

Cointab can first reduce the population into:

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

Then the additional fields are used only when investigating the exceptions.

This changes the reconciliation from a data-comparison exercise into an exception-management process.

---

Know which party needs to take action

The unmatched population naturally creates two different worklists.

Present in Dynamics but not in Apollo

These may require customer-side follow-up.

For example:

• Invoice not booked
• Different reference used
• Entry still pending
• Invoice under review

Present in Apollo but not in Dynamics

These typically require internal investigation first.

For example:

• Customer credit missing
• Receipt not allocated
• Adjustment not booked
• Transaction recorded under another reference
• Customer deduction needs validation

This makes the reconciliation immediately actionable.

---

Download the complete Apollo Pharmaproducts 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
• Dynamics transaction details
• Apollo transaction details

Fields such as:

• Invoice No
• Location
• Channel
• Payment Reference
• Net Amount
• External Document No.
• Remaining Amount
• Due Date

can provide valuable context during exception review.

---

Use transaction-level differences for customer communication

Instead of telling Apollo:

"Our balance does not match your balance."

you can work from a precise reconciliation.

For example:

• Invoice INV-5842 is not available in your ledger.
• Invoice INV-6421 differs by ₹7,000.
• Credit CN-7521 exists in your books but not ours.
• Payment reference UTR 8745123698 remains unapplied internally.

This makes reconciliation discussions significantly easier for both finance teams.

---

Correct the respective ledgers and reconcile again

Once exceptions have been reviewed:

• Your Dynamics ledger may be corrected
• Apollo may post a missing invoice
• Credit may be recorded
• Receipt may be allocated
• Amount may be corrected
• Reference may be updated

Upload the revised datasets to Cointab.

Run the reconciliation again.

Transactions can move from:

Unmatched → Fully Matched

or:

Partially Matched → Fully Matched

as the underlying differences are resolved.

---

Repeat the Apollo customer reconciliation every month

If you transact with Apollo regularly, customer reconciliation becomes a recurring process.

Each new period may contain:

• New invoices
• Customer payments
• Credits
• TDS entries
• Customer adjustments
• Older unresolved items

A typical process can become:

1. Export the latest Apollo customer ledger from Dynamics NAV / Business Central.
2. Obtain the latest Apollo ledger.
3. Upload your Dynamics file to Cointab.
4. Select the relevant date, identifiers, and amount fields.
5. Upload the Apollo ledger.
6. Select Invoice No, External doc no, Payment Reference, and financial fields.
7. Run Customer Reconciliation.
8. Review Fully Matched transactions.
9. Investigate Partially Matched invoices.
10. Review Dynamics-only items.
11. Review Apollo-only items.
12. Use Location and Channel information when investigating exceptions.
13. Review payment references for receipt differences.
14. Complete Manual Matches where required.
15. Download the reconciliation working.
16. Correct your internal entries.
17. Share customer-side exceptions with Apollo.
18. Upload revised ledgers and reconcile again.

---

Previously unmatched invoices can reconcile in later periods

An unmatched transaction does not always indicate an error.

Sometimes it is a timing difference.

For example:

July

You raise an invoice in Dynamics.

Apollo has not yet posted it.

The transaction appears as:

Present in Your Ledger but not in Apollo

August

Apollo's latest ledger contains the invoice.

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

The same principle applies to:

• Payments
• Credits
• Adjustments

This allows reconciliation to continue naturally across accounting periods.

---

Why this reconciliation is useful for multi-location customer accounts

A large customer relationship can become more complicated when transactions span several:

• Locations
• Channels
• Accounting profiles
• Invoice types

A simple closing-balance comparison cannot show whether the difference is concentrated in one part of the account.

Apollo's Location and Channel fields provide additional information that can help the finance team understand where reconciliation exceptions originate.

This makes the workflow particularly useful when a customer account contains large transaction volumes.

---

How Cointab helps reconcile Dynamics with Apollo Pharmaproducts

Cointab's Customer Reconciliation workflow allows you to:

• Upload your Microsoft Dynamics NAV / Business Central customer ledger
• Upload the Apollo Pharmaproducts ledger
• Reconcile files with completely different structures
• Select only the ERP fields required for matching
• Use External Document No. and Invoice No as commercial identifiers
• Use payment references for customer receipt matching
• Use descriptions and narrations as supporting identifiers
• Extract useful references from transaction text
• Automatically identify corresponding invoices
• Separate Fully Matched transactions
• Identify invoices with amount differences
• Identify entries present only in Dynamics
• Identify entries present only in Apollo
• Use Location and Channel during exception analysis
• Review Remaining Amount and Due Date for open receivables
• Use TDS information while investigating settlement differences
• Manually match genuine transactions with different references
• Download the complete reconciliation working in Excel
• Upload revised ledgers and reconcile again
• Continue reconciling open items across subsequent periods

---

Automate Microsoft Dynamics vs Apollo Pharmaproducts customer reconciliation

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

The process becomes:

Dynamics Customer Ledger → Apollo Ledger → Automated Matching → Exception Review → Corrections → Updated Reconciliation

You can quickly identify:

• Invoices that agree
• Invoices with amount differences
• Transactions missing from either ledger
• Customer payments that need allocation
• Credits and adjustments requiring review
• Exceptions associated with specific locations or channels
• Older open receivables

The complete reconciliation can then be downloaded in Excel and used for internal review or customer follow-up.

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

Try Cointab

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

Book a Demo