The following message may appear when importing an Open File Exchange (OFX) formatted statement for use in Bank Reconciliation:
No record has been imported
Solution or Workaround
This is usually caused when an investment-type OFX statement is imported into Bank Reconciliation. OFX statements are structured using Extensible Markup Language (XML) tags. Investment-type OFX statements use tags that are different from bank-type OFX statements. The following are two tags to take note of in a bank-type OFX statement.
Two Tags Associated With a Bank-Type OFX Statement
Description | Tags |
Account number | ACCTID 11010-000-0000 (checking account number) |
Type of Account | ACCTTYPE>CHECKING |
Sage Pro ERP Series searches for these tags to confirm the correct account number and type are being used before importing records from the OFX statement. These tags are not included in an investment-type OFX statement. The table below details the tag structure differences between the investment-type and bank-type OFX statements:
Tag differences between bank-type OFX and investment-type OFX statements
Investment | Bank |
INVSTMTMSGSRSV1 | BANKMSGSRSV1 |
INVSTMTTRNRS | STMTTRNRS |
INVACCTFROM | BANKACCTFROM |
INVTRANLIST | BANKTRANLIST |
BROKERID | Does not exist |
ACCTID – 33407679 (investment account number) |
Does not exist |
Does not exist | BANKID |
Does not exist | ACCTID – 11010-000-0000 (checking account number) |
Does not exist | CHECKING |
INVTRANLIST | BANKTRANLIST |
INVTRANLIST | BANKTRANLIST |
INVBANKTRAN | Does not exist |
All tags within and including INVPOSLIST | Does not exist. |
All tags within and including INVBAL | Does not exist |
Does not exist | All tags within and including LEDGERBAL |
If the tags from the first table are not found in the imported OFX statement, the import will halt and the message described above may appear.
Solution:
One solution to this issue is to modify the OFX statement to match the bank-type structure. Follow the steps below:
Note: Data edits should only be done by a Sage Certified Consultant or Business Partner. Create a full and verified backup before proceeding. This should first be attempted in a test installation and the results should be fully verified before implementing in a live system.
- Compare the investment OFX statement with a bank OFX statement. There is a sample bank statement (bankstatement.ofx) located within the External folder, inside the Sage Pro installation directory. The structure of the OFX files may be viewed using Microsoft Word, WordPad, Notepad or another text editor.
- Use the information provided in the second table above to modify the OFX tags listed in the left column to match the bank OFX tags listed in the right column.
- Remove the ACCTID tag containing the investment account number.
- Insert the following tags associated with the appropriate checking account.
- BankID
- ACCTID (checking account number set up in Sage Pro)
- ACCTTYPE – Checking
- LEDGERBAL – Insert these tag and anything that is nested within them. These tags usually precede the STMTRS tag.
- INVBAL – Insert these tags and anything that is nested within them. These tags usually precede the LEDGERBAL tag. Inserting these tags seems to have no affect when importing the OFX statement.
- INVPOSLIST – Insert these tags and anything that is nested within them. These tags usually precede the INVBAL tag. Inserting these tags seems to have no affect when importing the OFX statement.
© Copyright Sage Software