Back  Top

Outline of Bank account control module

Outline of Bank account control module

[Bank account control module] under [Finance Subsystem] is a module used to exchange data with financial institutions.
Payment/Receipt data is received from financial institutions and is imported into A.S.I.A. to perform matching settlement (identification and summarization) against Collection plan data.  Also T/F request files are created from an A.S.I.A. Payment plan for financial institutions.  Settlement of created T/F data is handled within [Bank account control module].

Further, maintenance of JBA codes used by A.S.I.A. is performed including registration and update.

Linkage and processing of operations of menu items are as follows.

[Payment/Receipt data matching  → Settle (receipt/claims) processing]

[Payment/Receipt data matching] imports Payment/Receipt files concerning own bank account distributed by financial institutions, and performs identification of ID codes and pattern matching of each Customer/Bank account (identification and summarization).  It is also possible to enter Payment/Receipt data directly without importing any file.  Matching settlement of Claims collection plan data is carried out based on receipt data which have been taken in by file import or have entered directly.

Menu

Process

Payment/Receipt data matching

This process reads Payment/Receipt files (Received files) from banks and performs identification of ID codes and matching between T/F applicant names and bank accounts of correspondents (identification and summarization).

Settle (receipt/claims)

This process performs matching between data imported by [Payment/Receipt data matching] and Claims/Collection plan data.
If amount of actual receipt and Collection plan amt do not match, it is possible to add data for different expiration date or different settle method as settle data and to forcibly settle differences as commissions, miscellaneous gains, or miscellaneous losses using adjustment entry.  Also, settlement of claims is carried out at this time.

Example of journalizing: Bank deposit/Account receivable

[Auto-transfer request processing  → Settle debts/Auto-journal processing]

Data for which settle method is entered with "Auto-transfer" is extracted from payment plan data which is entered from [Debts entry], [Purchase entry], [Repayment commit entry], [Lease payment commit entry], or [Create expenses management data], and T/F request file (JBA format) is created.  At this time, T/F commission can be subtracted and paid by correspondent.  After it is reported by financial institution that actual T/F payment has been correctly processed, settle (commit) of target data is processed.  Auto-journal process is carried out at the same time.

Menu

Process

Create auto-transfer data

According to payment plan data such as Debts/Payment plan, this menu creates auto-transfer data to be provided to a bank that will perform auto T/F.

Settle auto-transfer data

After auto-transfer is executed by the bank, settlement of debts/payment plan data of T/F object is processed based on auto-transfer request data.  Also, auto-journal process is performed at the same time.

Example of journalizing: Account payable/Bank deposit

Menu structure

Forms that can be output

[Bank account control module] can output the following forms:

Forms

Comment

Payment/Receipt list

This form is used to output checklist of payment/receipt data.

Auto-transfer data list

This form is used to output checklist of auto-transfer data.
It can also create lists of settlement data and payment plan/collection plan data.

Difference receipt/collection plan list

This form is for summary of matching target data.  Simulation prior to execution of settlement can be performed.

Refer to here for Output of Forms.

 

Back  Top

Copyright © 2019 Business Engineering Corp.