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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Invalid sign for amoun...
Microsoft Dynamics AX (Archived)

Invalid sign for amount during bank statement import

(0) ShareShare
ReportReport
Posted on by BrandonSA 1,673

Hi everyone

When I import a bank statement (BAI file), there is a certain line with a certain transaction type/code, say x, which when imported should be a credit, but it is a debit instead. Where does Ax determine whether a certain transaction code will be imported with a debit or credit value?

Thanks!

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hi BrandonSA,

    Did you find the root cause of this? We are also facing the same issue.

    We have transaction type code 951 in the import file which is showing as 'Debit' after importing into D365. This is actually a Credit amount in Bank statement. When we manually modify this code to 501 in the import file then it gets imported as 'Credit'. So I am not sure why we have got such setup in D365 for these 2 codes that is behaving in opposite manner.

  • Community Member Profile Picture
    Community Member on at

    Does anyone know where D365FO BankStatementLineEntity is determining whether the amount will go as debit or credit based on the transaction code present in the import file?

  • Community Member Profile Picture
    Community Member on at

    Finally I have raised the MS Support ticket. Let's see what's the outcome.

  • Verified answer
    BrandonSA Profile Picture
    BrandonSA 1,673 on at

    Hi everyone

    I saw replies to this thread recently - a topic I posted over a year ago! :)

    The problem was that the corresponding bank used a file format incompatible with what D365FO uses.

    This problem needs to be resolved by changing the XSLT files.

    There is more detail here:

    docs.microsoft.com/.../import-bank-statement-file-failed-incorrect-results

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
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans