web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Matched documents appe...
Microsoft Dynamics AX (Archived)

Matched documents appearing in Open documents in Advance bank reconciliation

(0) ShareShare
ReportReport
Posted on by Community Member

Scenario is using advance bank reconciliation.

User has matched statement lines against open bank documents, saved and closed.

Subsequently when re-open recon session, the statement/bank document lines were found again to be in the "Open documents" section again. When attempt to match again the error message was "The bank document or statement line is already matched".

I need to mention that the bank recon session is done in multiple user setting.

Thanks

Daniel

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Ludwig Reinhard Profile Picture
    Ludwig Reinhard Microsoft Employee on at
    RE: Matched documents appearing in Open documents in Advance bank reconciliation

    Hi Daniel,

    Have you checked LCS for an available hotfix? Recently several hot fixes have been issued for the auto bank reconciliation feature.

    Ludwig

  • Community Member Profile Picture
    Community Member on at
    RE: Matched documents appearing in Open documents in Advance bank reconciliation

    Thanks Ludwig. Will run thru it.

    Regards

    Daniel

  • Community Member Profile Picture
    Community Member on at
    RE: Matched documents appearing in Open documents in Advance bank reconciliation

    Hi Daniel,

    did you find an answer to this as I am having the same issue >

    Mark

  • Verified answer
    Community Member Profile Picture
    Community Member on at
    RE: Matched documents appearing in Open documents in Advance bank reconciliation

    Hi all

    A final update on this:

    Findings for this issue, is somehow the field BankReconciliationHeader , in BankReconciliationMatching table was pointing to the wrong journal batch header recID.

    Once this was corrected at backend, issue resolved.

    Error was able to be simulated when this field was pointed to wrong journal batch.

    Symptoms are: Lines appear in unmatched section, and when tried to post match,  message is statement lines has been reconciled and not able to post

    When BankReconciliationHeader field corrected to correct batch, Lines reverted to appear matched section.

  • Community Member Profile Picture
    Community Member on at
    RE: Matched documents appearing in Open documents in Advance bank reconciliation

    Hi Mark

    Please see my update below . This workaround worked in my case. Hope it does for yours.

  • Rafael Araujo Profile Picture
    Rafael Araujo 183 on at
    RE: Matched documents appearing in Open documents in Advance bank reconciliation

    Hi Daniel,

    I'm getting the same error message. How do you fix it?

    Thanks!

  • Suggested answer
    Community Member Profile Picture
    Community Member on at
    RE: Matched documents appearing in Open documents in Advance bank reconciliation

    Issue :

    We get error while matching the statement and document on Bank Reconciliations

    AX->Cash and Bank management -> Journals -> Bank Reconciliation ->Select the journal and check Lines

    Now in the unmatched section, select 1 line on both sides -> statement and Bank document, we will get the error

    Analyse :

    We will run below query to check all the records from Bank Document which is having different BankAccountId from the journal Bank AccountId.
    Generally Documents AccountId will be ok and we can match which documents have been wrongly assigned to different Journal AccountId with this query.
    To check Document details
    (select * from BANKDOCUMENTTABLEView where BANKDOCUMENTTABLEView.ISRECONCILED = 0 )

    This will fetch us the Reconciliation Id with which its getting conflicted to.

    select BANKRECONCILIATIONHEADER.ACCOUNTID as HeaderAccountId,BANKDOCUMENTTABLEView.ACCOUNTID as BankDocumentAccountId,
BANKRECONCILIATIONHEADER.RECONCILIATIONID,BANKRECONCILIATIONHEADER.ISRECONCILED,
BANKRECONCILIATIONHEADER.DESCRIPTION,
BankReconciliationMatching,
BANKRECONCILIATIONHEADER,* 
	
	from BankReconciliationMatchingItem
	
	join BankReconciliationMatching
	            on BankReconciliationMatchingItem.BankReconciliationMatching = BankReconciliationMatching.RecId
	            and BankReconciliationMatching.Cancelled        = 0
	join BANKRECONCILIATIONHEADER
		on	BANKRECONCILIATIONHEADER.RECID =  BankReconciliationMatching.BANKRECONCILIATIONHEADER
	
	join BANKDOCUMENTTABLEView
		on BANKDOCUMENTTABLEView.RECID = BankReconciliationMatchingItem.BankDocumentTable
		and BANKRECONCILIATIONHEADER.ACCOUNTID != BANKDOCUMENTTABLEView.ACCOUNTID
		and BANKDOCUMENTTABLEView.ISRECONCILED = 0

    Now we have all the transactions that are in conflicts, we need to change the correct header on the matching table to fix the issue

    Fix :

    • First of all remember the transaction refrence id and amount where you got the error, this will be used later

    • Generally for most of the transactions in the unmatch for a particular statementID will have same Matching record

    • you need to update the header on matching table to correct Header (Which is the recid of the Journal)

      Update BANKRECONCILIATIONMATCHING
      set BANKRECONCILIATIONHEADER = (recid of actual/correct journal)
      where recid in (BankReconciliationMatching Recid's from above query)

    • Once the Header is updated, you need to open the Reconciliation Form Again.

    • The transactions will be appearing on the Matched section

    • Search for the transaction , select it and in the document colum , select all transactions,

    • Click on Unmatch. This will move all the transactions from both statement and document will move back to Unmatched section.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 3

#3
Scott_itD Profile Picture

Scott_itD 2 Community Manager

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans