Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt

Infor LN & Baan Tips & Tricks for FINANCE: Use of Electronic Bank Statements

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

  1. Convert Electronic Bank Statements (tfcmg5202m000)
    Convert the received bank file to a format that LN can process. LN stores the converted bank statement files in the directory specified in the Path For EBS Archive field of the Bank Relations (tfcmg0510m000) session. In the Pathname EBS File field, you must add the file name. To add the current date to the file name, append a tilde (~) to the file name.

  2. Validate Bank Statements (tfcmg5202m000 / tfcmg5510m000 / tfcmg5511m000)
    Validate the converted electronic bank statement.

  3. Match Bank Statements (tfcmg5210m000)
    Automatically match as many of the imported statements (status Validated) as possible with open items. LN can match the statements with sales invoices, purchase invoices, and anticipated payment documents.

    Matching Options:

    • Match - Surplus on Aging / Unallocated (Default value)
    • Match - Surplus on Unallocated
    • Match - Surplus to be allocated Manually
    • Allow Underpayments
    • Use Payment Difference Tolerance
       
  4. Matching Results (tfcmg2500m100)
    Review the results of the matching process.

    To handle an unmatched amount, you can:

    • Manually add an unallocated payment or receipt line.
    • Reconcile the surplus with remaining open entries of the business partner.
       
  5. Post Bank Statements (tfcmg5210m100)
    Post the bank transactions to the General Ledger.

    Update the business partner’s bank account number and other details in the Bank Account by Pay-by Business Partner (tccom4115s000) session, based on the details read from the bank statement file.
     

Previous Article Harnessing the Power of AI to Help Manufacturers Sell More at the Right Time
Next Article Eliminating ERP Customizations: Key Considerations and Modern Solutions
Print
626 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Previously, users were unable to delete items in IDF Enterprise Items when they have inventory balances or the item is connected to ancillary records, such as sales history records. This feature added in LX 8.4 provides the ability to delete an item when sales history records are found but all sales history activity is zero.

When the user attempts to delete an item in IDF Enterprise Items that is tied to a sales history record, the panel displays a message that the item cannot be deleted. The user can then run the Delete Validation Report to determine which records are tied to this item that prevents the validation. If the item no longer has manufacturing activity but had old sales history, the item can be deleted.

First5455565759616263Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories