NS doesnt feel like helping today!
# general
i
NS doesnt feel like helping today!
k
This is because you haven't configured the accounts properly.
Set up the banking info on the chart of accounts
i
I managed to make the BAI2 import work, but MT940 still returns the same error
k
MT940?
i
Yes, the file format SWIFT MT940
I'm still having problems with the BAI2 because HSBC adds two extra codes under record 03 that messes up with the calculation NS does
k
I see. I don't think SWIFT MT940 is a supported file type
i
And I tried removing them (codes 102 and 402), but didn't work so far. It works if I manually edit the BAI2 file
k
I suggest reading this document from the User Guides page: https://docs.oracle.com/cloud/latest/netsuitecs_gs/NSBNK/NSBNK.pdf
i
Thank you!
k
Page 45 is where it talks about the format types supported
i
I've tried to follow instructions, but unfortunately MT940 didn't work yet
k
It won't...
i
Which is a shame because it brings complete info from Bank Statements
Why so?
It is a supported file format under the standard parser
k
Copy code
■ BAI2 (Bank Administrative Institute Version 2) TXT with UTF-8 encoding – common format developed
by Bank Administrative Institute for exchanging data. This data describes account activities, including
securities transactions and lockbox deposits. NetSuite supports BAI2 Prior-Day Reporting for Bank
Reconciliation. The statement can contain multiple bank accounts.
Note: If you are using default parsers, NetSuite supports the BAI2 format with UTF-8
encoding for the following banks: TD, Wells Fargo, US Bank, JP Morgan Chase, and Bank of
America Merrill Lynch. If you are using Parser Plug-ins, NetSuite supports any format.
■ CAMT.053.001.06 XML with UTF-8 encoding – file format in compliance with ISO 20022 and used by
SWIFT. This statement file can contain end-of-day bank transactions for multiple bank accounts.
■ CSV with UTF-8 encoding – files with the .csv extension. This statement file must also adhere to the
provided CSV template and constraints. See Preparing CSV Files for Import.
■ OFX (Open Financial Exchange) – file format sponsored by Intuit, Microsoft, and Fiserv (CheckFree). It
is commonly used with Microsoft Money. When importing, select the method of character encoding
associated with the file. If you are not sure which encoding the file has, check with your financial
institution.
■ QFX (Quicken Financial Exchange) – file format developed by Intuit and is used with their Quicken
software. It is a variant of the OFX file format. When importing, select the method of character
encoding associated with the file. If you are not sure which encoding the file has, check with your
financial institution.
i
I don't see MT940 on this list, but it is on the Banking.pdf file Standard parser – Available through the Bank Statement Parsers SuiteApp, which includes OFX or QFX, BAI2, and MT940 file format. After you save the format profile, configuration settings for the BAI2 or MT940 parser are populated in the Parser Configuration subtab
k
Read a bit more - I see your MT940 in the parser section
I haven't worked with that, so can't provide any guidance there.
i
Oh thank you
Re BAI2, I've managed to import it successfully, but had to do manual edits to the file
k
which is inadvised and beats the point of BAI2
i
Exactly
The problem is that the file contains 102 and 402 codes that are messing up with NS sum of all transactions
I've added them to the account mapping as exclusions but didnt work
k
You are in over my head if you are editing the parser.
i
Alright - thank you for the support!