Tsd-brd-043 Facturacion Cargos Debito A Cuenta V0.6.es - en

PRODUCT - Model Bank Country Specific
Development & Client Development

TECHNICAL SPECIFICATION DOCUMENT
Banco Machala
BRD-043 DEBIT CHARGES BILLING ACCOUNT
Information In This document is subject to change without notice.
No part of este documento May be reproduced or transmitted in any form or by any Means, for any purpose, without the express written permission of TEMENOS
HEADQUARTERS SA.
© 2018 Temenos Headquarters SA - all rights reserved.

Technical Specification
Document History
Author / Changed
Version Date Status Change Description
By
0.1 23 July 2019 Gopal Initial version draft Copy
0.2 02 Aug 2019 Praveen P Review Review comments

comments
0.3 05 Aug 2019 Gopal rEVIEWED Comments Addressed.
0.4 07 Aug 2019 Praveen P Review no Comments
0.5 08/29/2019 Gopal PAYMENT.ORDER related

Amend Adjustments are done. Latest FSD
attached.
0.6 10/10/2019 Gerardo L Amend
Sign Off History
Version Date Temenos Authorization Client Authorization
V3.2 / Nov-18 Quality Assurance Internal Use

Click here to view history template
2
Table of Contents
one. Management Summary ......................................................................................... 4

2. Functional Overview ............................................................................................. 5
3. Operational Overview.......................................................................................... 13
Four. reusable Components ......................................................................................... 13
5. New / Amended Files........................................................................................... 13
6. New Tables ........................................................................................................... 19
7. Subroutines .......................................................................................................... 23
8. Appendix .............................................................................................................. 32
9. Accounting ........................................................................................................... 32
10. Limits .................................................................................................................... 32
eleven. COB Processing .................................................................................................. 33
12. assumptions ........................................................................................................ 33
13. Dependencies / Exclusions ................................................................................ 33
14. Testing Notes ....................................................................................................... 33
fifteen. Packaging / Installation....................................................................................... 33
16. Data Migration ...................................................................................................... 34

3
1. Management Summary
1.1 background
This document aims to propose a solution to that from the T24 Core Banking of the following
tasks are performed:
- Allow set Charges Financial Services, which they are charged by debit to the account,
to be considered in the billing process.
- Allow set the period for which all charges will be billed debit account.
- Total fees charged for all debit account within the parameterised period to generate the
items in the bill, subtotals and total.
- Send the invoice information to external billing system Bank through IRD-014 interface.
- To run the service request only within the first 24 hours after the default date, validating
that double billing charges have already been invoiced is not generated.
1.2 modification Overview

To Achieve new configurations Including esta functionality versions, parametrisations,
routines and inquiries will be done in T24.
1.3 Reference Documents
Reference Document Description / Path Author, Company
FSD Carlos De Leon, Aspire Commented [PP1]: Please attach the latest version of
Systems the FSD.
FSD-BRD-043 Commented [GA2R1]: Updated
FACTURACION CARGOS DEBITO A CUENTA v1.1.docx
TO THE
1.3.1 Reference Number of the Requirement (ODR) Which is dependent

on This Requirement
BRD-043
1.4 Glossary (Optional)

This section Provides glossary & descriptions are used in That este documento.
Glossary description

4
2. Functional Overview
2.1 Existing Functionality
2.1.1 ACCT.ENT.LWORK.DAY
Concat table containing all accounting entries of the previous business day for each
Arrangement.
Example:
2.1.2 STMT.ENTRY
This table shows all accounting entries generated in the system and serves as the basis for
generating statements are saved.
This is the internal table containing details of all entries in client accounts and internal. Entries
in this table are generated for each process online and batch involving debit or accreditation of
accounts. This table is used by any process you need details of entries in accounts, such
statements.

5
2.1.3 BATCH
This the BATCH table routines that run during the closing day are configured. FREQUENCY
field in the frequency of execution of the service is configured. The values that accepts this field
are "D" for everyday, "M" monthly and "Y" annually.
2.1.4 TSA.SERVICE
This application is used to run a service in T24. will use this table to run the service manually
for this development.
2.1.5 PAYMENT.ORDER
PAYMENT.ORDER is the application with Which it is possible to relate to Obtain the payment
information product. Application used to carry out transfers Between accounts.

6
2.2 New Functionality

2.2.1 Parameterization Charges Financial Services
1. The income of the Financial Services Charges that apply for processing debit account
billing charges will be made through version:
ECMB.ACCT.FIN.SERVICES.CHG, INPUT.
In this version, the user will enter the application in T24 where you have set office, and
underneath, in sub-values fields, enter charges that apply to the application billing
process.
According to the charges that the Bank will handle, T24 applications that must be
entered in this release are:
- FT.COMMISSION.TYPE
- CHEQUE.CHARGE
- AA.PROPERTY
The routine ECMB.V.FIN.SERVICE.CHG validate that the charges are valid for the
application under which records are being registered.
2.2.2 Charges Daily Record
1. Multithread ECMB.B.ACCT.REGISTER.CHARGES routine that will run daily during the

Closing day at the stage where the date APPLICATION already changed the next day
will be created, and will be responsible for registering and keeping going debits made

7
to the account fee concept of Financial Services at a local table name type
ECMB.ACCT.REGISTER.CHARGES LIVE.
The process is as follows:
 The routine must identify all active accounts in the Accounts table that do not
have any of the following statuses:
 UNAUTH
 CANCELED
 CLOSE
 matured
 For each of the registers perform the following process:
 It will take account ID and enter the core ACCT.ENT.LWORK.TODAY table

containing the accounting entries of the previous business day for each
account this being a multivalued data.
 For each accounting entry, the routine takes the ID, and entering the
STMT.ENTRY table to extract the transaction detail taking the following
values:
o To identify the module where the transaction is generated the
value of the field is taken SYSTEM.ID
o And the ID of the transaction with the value of
TRANS.REFERENCE field.
 The routine will identify whether any charge will be charged on the
transaction. The process for identifying and obtaining information charge
varies according to different applications:
o ARRANGEMENT ARCHITECTURE:With the

TRANS.REFERENCE the routine will enter the AA.BILL.DETAILS
table. In the PROPERTY field will be recorded property related to
the transaction, which the system will validate if it corresponds to
a charge for financial services.
o TELLER: With the TRANS.REFERENCE the routine will enter the
TELLER table and field CHARGE.CODE code you will be
registered by FT.COMMISSION.TYPE.
o CHECK: The routine should take TRANS.REFERENCE ID which
is composed of three parts: <CHEQUE.TYPE> <ID ACCOUNT>
<consecutive number> .And check whether the CHEQUE.TYPE is
registered in the CHEQUE.CHARGE table. If it is, intone means
that if you have configured charges for that type of check.
o PAYMENTS PLATFORM:With TRANS.REFERENCE, the routine
will enter the tablePOR.TRANSACTION, and field
SendersReferenceIncoming be registered the ID of the payment
order. With this ID, it will enter the PAYMENT.ORDER table. This
table will be verified whether there is any charge in the
CHARGE.TYPE field. The charges in this field are
FT.COMMISSIONT.TYPE records.
o AC.CHARGE.REQUEST: With TRANS.REFERENCE, the routine
will enter the AC.CHARGE.REQUEST table and get the type of
charge and the amount of CHARGE.CODE fields and
CHARGE.AMOUNT
 After identifying the code office, the routine must validate that the code is
registered in the table ECMB.FINANCIAL.SERVICES.CHG parameters.

8
o If the code is not within the table, then the process stops and starts
again with the following accounting entry or account.
o But if you are in the table, then it means that it is a position that
should be considered to generate bill and the process continues.
 The routine will identify the type of associated tax charge. The way to
identify module varies according to where the transaction is generated:
o ARRANGEMENT ARCHITECTURE: Tax be in the

AA.BILL.DETAILS table in PROPERTY field, and is characterized
in that the property name will be registered as the name of charge
plus TAX termination.
Example:
o TELLER:Like the office, the tax will also be registered with

CHARGE.CODE field. But in this case, the code is a code of TAX
table. The amount of tax on the CHRG.AMOUNT.LOCAL field with
the description of the tax.
Example:

9
o CHECK:To associate a tax office in checks, must have a record of

FT.COMMISSION.TYPE in the field of CHEQUE.CHARGE
CHARGE.CODE table. In this case, the routine code would take
charge and get the code FT.COMMISSION.TYPE the tax field
TAX.CODE
o PAYMENTS PLATFORM: The charge code will be in the field of
PAYENT.ORDER CHARGE.TYPE table. The code will be entered
to FT.CMMISSION.TYPE and field TAX.CODE will the tax code if
you have. With this, you can get the information from the TAX tax
table.
o AC.CHARGE.REQUEST: The tax code can be found in the
TAX.CODE field and the amount of TAX.AMT field.
 If there is an associated tax information tax table by the TAX code is

obtained. If the transaction is not carried out a debit for income tax, the
system will classify it as Cargo VAT 0%, which is registered in the TAX
table with a code 99. This registration must be obtained information for
charges no associated tax.
 The routine will save the information office in the local table that will have
an ID ECMB.ACCT.REGISTER.CHARGES composed of three parts:
<account number> <code Cargo> <YYYYMM>.
The information stored this table is as follows:
A multivalued group consisting of fields:
- Reference Transaction
- Transaction date
- Charge Amount
- Position Description
- Tax code
- Description Tax
- Tax rate
- Amount of tax

10
* If during the period parameterised a charge to the account of the

same type, this will be stored in the same record within another block
as multivalued fields for this new transaction will open.
Example:
TABLE FIELDS VALUE

Table D 00009822.CHE.201907
Reference Transaction CHE9287373
Transaction date 20190703
Charge Amount 6.9
CHQ. RETURNED CHECKS
Position Description
EXTERIOR
Tax code
eleven
Description Tax Agregado1 tax Value
Tax rate 12%
Amount of tax 0.5
Status INVOICED
Status field will be taken to indicate whether the record has already been billed.
These fields will be filled when communication with the IRD-014 is established
- Flag to indicate whether the record has been billed
 ECMB.ACCT.REGISTER.CHARGES records table They cleaned every

month. This will be done by BATCH BNK /
ECMB.CLEAR.ACCT.REGISTER.CHARGES with the following
parameters in the field FRECUENCY:
* Where M10 means it will run on the 10th of each month.
2.2.3 Invoice generation and shipping information to the external system
a service called BNK // ECMB.FIN.SERVICES.CHG.BILL, which will be executed by a user

operating COB before the last business day of the month will be created.
This service routine run multithread ECMB.B.GEN.BILL.INF, which will total fees charged by
debit to the account, segregating by type of charge to generate the invoice detail with subtotals
and totals.
The process of this routine is described below:

11
 The routine search the ECMB.ACCT.REGISTER.CHARGES table whose ID <account

number> <code Cargo> <YYYYMM> and each account will do the following:
 You enter each record in the table that begins with your account number and that
is not with checked status.
 Each record is a type of charge. For each type of charge, the system must total
the amounts collected, separated by type of tax charged.
 Once having totalized segregated charges of charge and tax, the system will
generate the invoice detail.
The details include the following information:

- Account number.
- Cargo code.
- Position Description
- Amount of debits made by each type of charge.
- Total price. It corresponds to the total amount debited by type of charge.
 Generate subtotals of the bill: For subtotals, the routine will identify the type of tax
claimed for each position, and add the total amounts of those charges. The result will
be saved as "Subtotal Percentage of tax-" such as:
 Subtotal 0%. (If no tax charges)

 Subtotal 12%
Once having the value of subtotals, the routine must calculate Total income tax. This is
the sum of all debits tax in respect of fees charged to the customer. Continuing the
above example:
 Total VAT 12% (the tax rate is VAT)
Note: For the subtotal of the charges do not charge tax, this information does not
apply.
Finally, the system must calculate the total value of the invoice, which corresponds to
the sum of the subtotal and total tax. In other words: Subtotal Subtotal 0% + 12% +
12% Total VAT.
 Customer information: The routine should obtain the following information from the
customer assigned as head of the Arrangement:
 Type ID
 ID number
 Customer name
 Main address
 Phone
 Email
 Opening agency code
This information will be available in CUSTOMER
 Descrit0a call interface in the IRD-014:After obtaining all the necessary information,
the routine should call the IRD-014 and assess the response of the issuance of the
invoice and does the following:
 If the answer is successful, update the status in the table
ECMB.ACCT.REGISTER.CHARGES CHECKED.
 If the answer is not successful status is not updated.
.

12
3. Operational Overview
4. reusable Components
4.1 reusability Pack
4.1.1 Reusable - (Yes / No)
Do not.
4.1.2 Reason
Developed with a specific set of requirements in mind.
4.2 Reusable Components Table

NA.
5. New / Amended Files

5.1 LOCAL.TABLE
NA
5.2 LOCAL.REF.TABLE
NA
5.3 Inquiry
5.3.1 ECMB.ENQ.FIN.SERVICES.CHG
PAGE.SIZE 4,99
FILE.NAME ECMB.ACCT.REGISTER.CHARGES
SELECTION.FLDS STATUS
SEL.LABEL Status
OPEREND EQ
+1 SELECTION.FLDS VALUE.DATE
SEL.LABEL Date
FIELD.NAME @ID
OPERATION @ID
COLUMN one
FIELD.LBL Bill

13
FIELD.NAME- CLIENT NAME
OPERATION CLIENT NAME
COLUMN 10
FIELD.LBL Name
+1 FIELD.NAME TRANS.REFERENCE
OPERATION TRANS.REFERENCE
COLUMN twenty
FIELD.LBL Transaction ID
+1 FIELD.NAME VALUE.DATE
OPERATION VALUE.DATE
COLUMN 30
FIELD.LBL Transaction date
+1 FIELD.NAME CHG.AMOUNT
OPERATION CHG.AMOUNT
COLUMN 40
FIELD.LBL charge amount
+1 FIELD.NAME CHG.DESCRIPTION
OPERATION CHG.DESCRIPTION
COLUMN fifty
FIELD.LBL description Cargo
+1 FIELD.NAME TAX.DESCRIPTION
OPERATION TAX.DESCRIPTION
COLUMN 70
FIELD.LBL Tax description
+1 FIELD.NAME TAX.RATE
OPERATION TAX.RATE
COLUMN 90
FIELD.LBL rate
+1 FIELD.NAME TAX.AMOUNT

14
OPERATION TAX.AMOUNT
COLUMN 100
FIELD.LBL Tax amount
+1 FIELD.NAME STATUS
OPERATION STATUS
COLUMN 110
FIELD.LBL Status
5.4 HelpText Menu

5.4.1 ECMB.DROP3
Field Name Field Value
Application.1 ECMB.BRD043
Description.1 BRD-043 DEBIT CHARGES BILLING ACCOUNT
5.4.2 ECMB.BRD043
Application.1 ECMB.ACCT.FIN.SERVICES.CHG, INPUT
Description.1 Parameterize Charges for Financial Services
Application.2 TSA.SERVICE, FIN.SERVICE.CHG
Description.2 Run Billing Charges Debit Account
5.5 HelpText MainMenu

5.5.1 one
Application.1 ECMB.DROP3
Description.1 Drop3
5.6 Version
5.6.1 ECMB.ACCT.FIN.SERVICES.CHG, INPUT
Do
Countryside Description EN / ES mandated Field Type default
not.

15
one APPLICATION Name Application T24

2 CHARGE Name Position
3 OVERRIDE override
4 RECORD.STATUS record Status
5 CURR.NO Curr Number
6 INPUTTER Inputter
7 date.time Date Time
8 authoriser authoriser
CHECK.REC.RTN
INPUT ROUTINE
ROUTINE VALIDATION APPLICATION> ECMB.V.FIN.SERVICE.CHG
AUTH ROUTINE
ASSOC.VERSION
NEXT.VERSION
NO.OF.AUTH 0
5.6.2 TSA.SERVICE, FIN.SERVICE.CHG

Do
Countryside Description EN / ES mandated Field Type default
not.
one DESCRIPTION Name Application T24

2 SERVICE.CONTROL Name Position
3 OVERRIDE override
4 RECORD.STATUS record Status
5 CURR.NO Curr Number
6 INPUTTER Inputter
7 date.time Date Time
8 authoriser authoriser
CHECK.REC.RTN
INPUT ROUTINE
SERVICE.CONTROL>
ROUTINE VALIDATION
ECMB.V.GEN.BILL.PROCESS
AUTH ROUTINE
ASSOC.VERSION
NEXT.VERSION
NO.OF.AUTH 0

16
5.7 BATCH
5.7.1 BNK / REGISTER.SERVICES
Index Field Name Observations
BATCH.STAGE A020
BATCH.ENVIRONMENT F
JOB.NAME ECMB.B.ACCT.REGISTER.CHARGES
VERIFICATION
FREQUENCY D
5.7.2 BNK / ECMB.FIN.SERVICES.CHG.BILL
BATCH.STAGE
BATCH.ENVIRONMENT F
JOB.NAME ECMB.B.GEN.BILL.INF
VERIFICATION
FREQUENCY D
5.7.3 BNK / ECMB.CLEAR.CHARGES.REGISTER
BATCH.STAGE O100
BATCH.ENVIRONMENT F
JOB.NAME ECMB.B.REMOVE.CHARGES.REGISTER
VERIFICATION
FREQUENCY D
5.8 EB.API
5.8.1 ECMB.V.FIN.SERVICE.CHG
Index Field Name Field Value
@ID ECMB.V.FIN.SERVICE.CHG
PROTECTION.LEVEL FULL

17
SOURCE.TYPE BASIC
5.8.2 ECMB.V.GEN.BILL.PROCESS
@ID ECMB.V.GEN.BILL.PROCESS
PROTECTION.LEVEL FULL
SOURCE.TYPE BASIC
5.9 PGM.FILE
5.9.1 ECMB.B.REMOVE.CHARGES.REGISTER
@ID ECMB.B.REMOVE.CHARGES.REGISTER
TYPE B
PRODUCT EB
BATCH.JOB @ BATCH.JOB.CONTROL
5.9.2 ECMB.B.ACCT.REGISTER.CHARGES
@ID ECMB.B.ACCT.REGISTER.CHARGES
TYPE B
PRODUCT EB
5.9.3 ECMB.B.GEN.BILL.INF
@ID ECMB.B.GEN.BILL.INF
TYPE B
PRODUCT EB

18
5.10 Data Records
S.No Table Name record ID detail
one EB.ERROR EB- GB: More Than 24 Days

ECMB.SERVICE.NOT.ALLOWED Have Passed Since the
default Date
ES: It's been more than 24
hours from the date
Predefined
2 EB.ERROR EB-ECMB.NOT.VALID.CHARGE GB: Invalid Charge

EN: The charge is invalid
3 EB.ERROR EB.ECMB.INVALID.ID GB: Invalid ID

ES: Not valid ID
5.11 Communications (Optional)

NA.
6. New Tables
6.1 ECMB.ACCT.FIN.SERVICES.CHG
6.1.1 Table Properties
Do Property Definition
not.
one Yam ECMB.ACCT.FIN.SERVICES.CHG
2 Product EB
3 File Type H
4 Classification CUS
5 prefix EC.AC
6.1.2 Table Layout

Do Field Name Field IN2 & description
not. Length Edit
(Field
Property)
one @ID 6 SYSTEM ID
2 XX <APPLICATION 30 TO Application
Checkfile:
STANDARD.SELECTION

19
3 XX> CHARGE 30 TO ID cargo
4 DELETE.TABLE 4 N Duration
4 RESERVED.5 noinput
Add Audit fields. Using Either the V = Z + 9 option or the Table.setAuditPosition option.
6.1.3 Field Checks

S.No Name of the field Check's to be done
6.1.4 Cross Validation Checks

NA
6.1.5 Other Processing

Check function:
a) BEFORE.AUTH.WRITE:
NA.
b) AFTER.AUTH.WRITE:
NA.
6.1.6 INSERT Files

Use the EB.DEV.HELPER utility to create the insert file for the above template.
6.2 ECMB.ACCT.REGISTER.CHARGES
not.
one Yam ECMB.ACCT.REGISTER.CHARGES
2 Product EB
3 File Type H

20
5 prefix EC.AC
6.2.2 Table Layout

Do Field Name Field IN2 & Edit description
not. Length (Field
Property)
one @ID 17 TO The ID will consist of

<account number>
<Code Title> <Tax>
<YYYYMM>
2 16 TO Application
XX <TRANS.REFERENCE Checkfile:
STANDARD.SELECTION
3 XX.XX.VALUE.DATE 8 DATE ID cargo
4 XX.XX.CHG.AMOUNT 25 AMT Fee amount
60 TO
5
XX.XX.CHG.DESCRIPTION Position Description
6 XX.XX.TAX.DESCRIPTION 60 TO Description of Tax
7 XX.XX.TAX.RATE 6 AMT Tax rate
8 12 AMT It will be deducted by

XX> TAX.AMOUNT
way of tax charge
9 STATUS 10 TO State
6.2.3 Field Checks


NA

Check function:
c) BEFORE.AUTH.WRITE:
NA.
d) AFTER.AUTH.WRITE:
NA

21
6.2.6 INSERT Files

6.3 ECMB.EXTERNAL.BILL.STATUS
not.
one Yam ECMB.EXTERNAL.BILL.STATUS
2 Product EB
3 File Type H
5 prefix EC.AC
6.3.2 Table Layout

Do Field Name Field IN2 & Edit (Field description
not. Length Property)
one @ID 17 TO There are only two

records in this table:
BAGGAGE and
NO.FACTURADO
9 10 TO Text to describe the

DESCRIPTION
status of the bill.
6.3.3 Field Checks


NA

Check function:
e) BEFORE.AUTH.WRITE:
NA.
f) AFTER.AUTH.WRITE:
NA
6.3.6 INSERT Files


22
7. Subroutines
7.1 ECMB.I.FIN.SERVICE.CHG
Property Specification
Type Input routine
Attached To ECMB.ACCT.FIN.SERVICES.CHG, INPUT
As Attached Input routine
Dependency NA
This routine validate Input That Correspond to the charges Entered
description
Their respective application
Arguments - IN NA
Arguments - OUT NA
Prelim Conditions NA
subroutine Flow a. Insert the I_ Necessary files.

b. Get the values from APPLICATION and CHARGE fields and
store the values into Y.APPLICATION and Y.CHARGE.
c. Use LOOP and REMOVE and get the values below
Y.APP = Y.APPLICATION <POS>
Y.CHG = Y.CHARGE <POS>
BEGIN CASE
CASE Y.APP EQ "FT.COMMISION.TYPE"
GOSUB FT.COMM.PROCESS
CASE Y.APP EQ "CHEQUE.CHARGE"
GOSUB CHQ.PROCESS
CASE Y.APP EQ "AA.PROPERTY"
GOSUB AA.PROCESS
END CASE
FT.COMM.PROCESS:
Read the table FT.COMMISION.PROCESS With the id Y.CHG and if
the record exists Then continue, if not THEN RAISE the error "EB-
ECMB.NOT.VALID.CHARGE" Using STORE.END.ERROR
CHQ.PROCESS:
Read the table CHEQUE.CHARGE With the id Y.CHG and if the record
exists Then continue, if not THEN RAISE the error "EB-
AA.PROCESS:
Read the table AA.PROPERY With the id Y.CHG and if the record
exists Then continue, if not THEN RAISE the error "EB-
End

23
7.2 ECMB.B.REMOVE.CHARGES.REGISTER.LOAD
Type batch Routine
Attached To BNK / ECMB.CLEAR.CHARGES.REGISTER
As Attached batch Routine
Dependency NA
description Open the tables used in the main routine.
Arguments - IN NA
Arguments - OUT NA
subroutine Flow a. Insert the Necessary I_Files

b. Open the Necessary tables used in the main process
c. End.
Special Instructions
7.3 ECMB.B.REMOVE.CHARGES.REGISTER.SELECT
Type batch Routine
Dependency NA
description Gets the list generated in the query id
Arguments - IN NA
Arguments - OUT SEL.LIST

b. Read the ECMB.ACCT.FIN.SERVICES.CHG table and get the
value of the DELETE.TABLE field and save the value in
Y.DEL.FREQ
c. Using CDT, Get the date Which is older Y.DEL.FREQ months
from date and assign the TODAY value into Y.FIN.DATA
d. Select the records from table
ECMB.ACCT.REGISTER.CHARGES by @ID like ... EQ

24
BAGGAGE STATUS Y.FIN.DAY and store the values into the

SEL.LIST.
e. End.
7.4 ECMB.B.REMOVE.CHARGES.REGISTER
Type batch Routine
Dependency NA
description Delete records from the table ECMB.ACCT.REGISTER.CHARGES
Arguments - IN Y.SEL.ID
Arguments - OUT NA

b. Using F.DELETE delete the records With the FN.
ECMB.ACCT.REGISTER.CHARGES, Y.SEL.ID.
c. End.
7.5 ECMB.B.ACCT.REGISTER.CHARGES.LOAD
Type batch Routine
Attached To BNK / REGISTER.SERVICES
Dependency NA
Arguments - IN NA
Arguments - OUT NA

25
subroutine Flow - Insert the I_ Necessary files.

- Open the Necessary tables used in the main process
- End
7.6 ECMB.B.ACCT.REGISTER.CHARGES.SELECT
Type batch Routine
Dependency NA
Arguments - IN NA

- Select the table with PRODUCT.LINE AA.ARRANGEMENT
equal to "Accounts" and ARR.STATUS NOT equals with
"UNAUTH" "CANCELED" "CLOSE" "Matured" and store the id
in SEL.LIST
- End
7.7 ECMB.B.ACCT.REGISTER.CHARGES
Type batch Routine
Dependency NA
description Register charges debited to the account during the day
Arguments - IN SEL.ID
Arguments - OUT NA

26

- Read the AA.ARRAGEMENT table with SEL.ID and and get
the LINKED.APPL and LINKED.APPL.ID and store it as Y.APP,
Y.ACCOUNT
- IF LINKED.APPL EQ "ACCOUNT" then store the value into the
Variable Y.ACC
- Read the .ACCT.ENT.LWORK.DAY With the id Y.ACC and get
the latest id and Read the STMT.ENTRY table and get the
SYSTEM.ID, TRANS.REFERENCE and store it into
Y.SYSTEM.ID and Y. TRANS.REF
BEGIN CASE
CASE Y.SYSTEM.ID equal to "CQ" then
GOSUB CQ.PROCESS
CASE Y.SYSTEM.ID equal to "AAAA" then
GOSUB AAAA.PROCESS
CASE Y.SYSTEM.ID equal to "TT" then
GOSUB TT.PROCESS
CASE Y.SYSTEM.ID equal to "PP" then
GOSUB PP.PROCESS
CASE Y.SYSTEM.ID equal to "AC" then
GOSUB AC.PROCESS
END CASE
CQ.PROCESS:
- Using FIELD function, Get the first part and store it into
Y.CHQ.TYPE from the Y.TRANS.REF.
- Read the CHEQUE.CHARGE table with the id Y.CHQ.TYPE, if
the record exists, CHARGE.CODE get the field value and store
it into Y.CHARGE.CODE
- Check Y.CHARGE.CODE Not equals to IF EMPTY, then a
Read the the table ECMB.ACCT.FIN.SERVICES.CHG With the
id and if the Y.CHARGE.CODE is available in CHARGE, Then
keep the information and CONTINUE.
- If not Read The Tax table with the id 99 and get the field values
RATE and store the value into Y.TAX.AMOUNT. If
Y.TAX.CODE not equal to empty, then a use TAX.CODE and
TAX.AMOUNT and assign the value 99 Y.TAX.CODE.
- Using f.write Update the table
ECMB.ACCT.REGISTER.CHARGES With the information from
the stored in the variables below Y.CHARGE.CODE,
Y.CHARGE.AMOUNT, Y.TAX.CODE and Y.TAX.AMOUNT into
the fields CHARGE.CODE, CHARGE.AMOUNT, TAX.CODE,
TAX.AMOUNT and TRANS.REFERENCE ..
AAAA.PROCESS:
- Read the table AA.BILL.DETAILS With the id Y.TRANS.REF
and get the value property, OS.TOTAL.AMOUNT and store it
into Y.PROPERTY, Y.OS.TOTAL.AMOUNT
- Read the table ECMB.ACCT.FIN.SERVICES.CHG With the id
SYSTEM and check Whether the Y.PROPERTY is exists, then
a keep the information and CONTINUE,
- Using FIELD function, extract the value from Y.PROPERTY by
"-" Check the value of Y.PROPERTY second part Equals to
TAX, TAX if then Read the table with value Y.PROPERTY and
get the value RATE into Y.TAX. AMOUNT.
- If not Read The Tax table with the id 99 and get the field values
RATE and store the value into Y.TAX.AMOUNT. If

27
Y.TAX.CODE not equal to empty, then a use TAX.CODE and

TAX.AMOUNT and assign the value 99 Y.TAX.CODE.
TAX.AMOUNT and TRANS.REFERENCE.
TT.PROCESS:
- Read the table TELLER With Y.TRANS.REF and get the field
value CHARGE.CODE and store the value into
Y.CHARGE.CODE
- If Y.CHARGE.CODE is empty, then a CONTINUE
If Y.CHARGE.CODE is not empty, then a
Read the Parameter table ECMB.ACCT.FIN.SERVICES.CHG
With the id SYSTEM and and check the field value
Y.CHARGE.CODE With CHARGE, if it is equal, then a keep
the information and CONTINUE
- Also available Check Whether another code, Verify the value
with the table for the second TAX code. If the record not exists
then assign the value 99 to Y.TAX and Read the table and get
Y.TAX With TAX RATE and ASSIGN into the Y.TAX.AMOUNT.
PP.PROCESS:
- Read the table PP.ORDER.ENTRY With the id Y.TRANS.REF
and Get the value of the field CREDIT.CHARGE.COMPONENT
and store it into Y.CHARGE.CODE.
- Read the Parameter table ECMB.ACCT.FIN.SERVICES.CHG
the information and CONTINUE. Get the amount from
STMT.ENTRY and store it into the Variable
Y.CHARGE.AMOUNT.
- Check Whether Y.TAX.CODE Charge With details available, if
not then a Read the TAX table with the id 99 and get the field
values RATE and store the value into Y.TAX.AMOUNT and
assign the value 99 Y.TAX.CODE.
AC.PROCESS:
- Read the table AC.CHARGE.REQUEST With the id
Y.TRANS.REF and Get the value of the field CHARGE.CODE
and CHARGE.AMOUNT, TAX.CODE, TAX.AMOUNT store it
into the Variable Y.CHARGE.CODE, Y .CHARGE.AMOUNT,
Y.TAX.CODE, Y.TAX.AMOUNT.
- Read the Parameter table ECMB.ACCT.FIN.SERVICES.CHG

28

the information and CONTINUE.
- Check Whether Y.TAX.CODE equal to empty TAX Then Read
the table with the id 99 and get the field values RATE and store
the value into Y.TAX.AMOUNT. If Y.TAX.CODE not equal to
empty, then a use TAX.CODE and TAX.AMOUNT from
AC.CHARGE.REQUEST.
End
7.8 ECMB.B.GEN.BILL.INF.LOAD
Type batch Routine
Attached To BNK / ECMB.FIN.SERVICES.CHG.BILL
Dependency NA
Arguments - IN NA
Arguments - OUT NA

b. Open the Necessary tables used in the main process
c. End.
7.9 ECMB.B.GEN.BILL.INF.SELECT
Type batch Routine

29
Dependency NA
Arguments - IN NA

b. Select all records from the table
ECMB.ACCT.REGISTER.CHARGES With STATUS not equal
to BAGGAGE and store all the ids into SEL.LIST
c. End.
7.10 ECMB.B.GEN.BILL.INF
Type batch Routine
Dependency NA
description Generate billing information and send it to the external system
Arguments - IN NA
Arguments - OUT NA

b. Using FIELD function get the second part the value from
Y.SEL.ID and store it into Y.CHARGE.CODE
c. Read the table ECMB.ACCT.REGISTER.CHARGES With
Y.SEL.ID and get the id field values CHG.AMOUNT,
TAX.AMOUNT and store the values into Y.CHG.AMOUNT,
Y.TAX.AMOUNT
d. If Y.CHARGE.CODE equal to 99 then a

Assign the value Y.CHG.AMOUNT into Y.SUBTOTAL
END ELSE
Assign the value Sum of Y.CHG.AMOUNT and Y.TOTAL.IVA
END
e. The total amount will be Calculated Y.TOTAL = Y.SUB.TOTAL
+ Y.TOTAL.IVA.

30
f. Using FIELD function get the first part the value from @ID and
store it into Y.ACCOUNT
g. Read the ACCOUNT table and get the CUSTOMER,
ARRANGMENT.ID and store into Y.CUSTOMER, Y.ARR.ID
h. Read the CUSTOMER table with the id Y.CUSTOMER and get
the field values LEGAL.DOC.NAME and COMPANY.BOOK
and store the value into the variable-Y.LEGAL.DOC.NAME,
Y.COM.BOOK, Also use MULTI.GET .LOC.REF to Obtain the
position of the reference Local field and use the position to get
the value from the field LT.NOMBERE.COMPLETO and store it
in to Y.NOMBRE
i. Read the ECMB.CUSTOMER.DATA table with the id
Y.CUSTOMER and get the field values ADDRESS,
TELEPHONE, EMAIL and store the values into Y.ADDRESS,
Y.TELEPHONE, Y.EMAIL.
j. Need to send the below details to IRD-014 interface using the
routine ECMB.INT.FACTURA.,
Y.ARR.ID,
Y.CHARGE.CODE,
Y.SUBTOTAL
Y.VAT,
Y.TOTAL.VALUE,
Y.LEGAL.DOC.NAME,
Y.NOMBRE,
Y.ADDRESS,
Y.TELEPHONE,
Y.EMAIL,
Y.COM.BOOK,
k. If the interface Responds successfully, the STATUS field will be

updated as BILLED in the table
ECMB.ACCT.REGISTER.CHARGES
l. End.
Special Instructions We assume the routine ECMB.INT.FACTURA to send the Already

developed details to IRD-014 interface.
7.11 ECMB.V.GEN.BILL.PROCESS
Type Validation Routine
Attached To TSA.SERVICE, FIN.SERVICES.CHG.BILL
As Attached Validation Routine
Dependency NA
description Validates that the process of generating the invoice can not run 24
hours after the default date
Arguments - IN NA
Arguments - OUT NA

31
subroutine Flow a. Get the field value STARTED R.NEW from the value and store
into Y.DATE.TIME and use the FIELD function to extract first
part value by "." And store it into Y.DATE
b. Use FIELD function and arrange the values in date
YYYYMMDD structure and store into Y.FIN.DATE and get the
value and store into Y.TODAY TODAY
c. If EQ Y.TODAY Then Y.FIN.DATE
Raise the error "EB-ECMB.SERVICE.NOT.ALLOWED"
End
7.12 ECMB.ACCT.REGISTER.CHARGES.ID
Type Routine ID
Attached To
As Attached Routine ID
Dependency NA
description To validate the ID of the template
Arguments - IN NA
Arguments - OUT NA

b. Open the Necessary files.
c. Get the ID from ID.NEW and store the value into Y.ID
d. Using the extract by FILED function. "" Whether the ID has 3
parts or not. If the ID do not have 3 parts, kindly throw the bug
using STORE.END.ERROR With EB.ECMB.INVALID.ID.
e. End
8. Appendix
NA
9. Accounting
NA
10. Limits
NA

32
11. COB Processing

NA
12. assumptions
NA
13. Dependencies / Exclusions

NA
14. Testing Notes
FSD-BRD-043
FACTURACION CARGOS DEBITO A CUENTA v0.4_TestCase.xlsx
15. Packaging / Installation

Application Data Record
VERSION ECMB.ACCT.FIN.SERVICES.CHG, INPUT
VERSION TSA.SERVICE, FIN.SERVICE.CHG
INQUIRY ECMB.ENQ.FIN.SERVICES.CHG
HELPTEXT.MENU ECMB.DROP2
HELPTEXT.MENU ECMB.BRD043
HELPTEXT.MAINMENU one
BATCH BNK / REGISTER.SERVICES
BATCH BNK / ECMB.FIN.SERVICES.CHG.BILL
BATCH BNK / ECMB.CLEAR.CHARGES.REGISTER
EB.API ECMB.V.FIN.SERVICE.CHG
EB.API ECMB.V.GEN.BILL.PROCESS
PGM.FILE ECMB.B.ACCT.REGISTER.CHARGES
PGM.FILE ECMB.B.GEN.BILL.INF
PGM.FILE ECMB.B.REMOVE.CHARGES.REGISTER
EB.ERROR EB-ECMB.SERVICE.NOT.ALLOWED
EB.ERROR EB-ECMB.NOT.VALID.CHARGE

33
STANDARD.SELECTION ECMB.ACCT.FIN.SERVICES.CHG
PGM.FILE ECMB.ACCT.FIN.SERVICES.CHG
FILE.CONTROL ECMB.ACCT.FIN.SERVICES.CHG
STANDARD.SELECTION ECMB.ACCT.REGISTER.CHARGES
PGM.FILE ECMB.ACCT.REGISTER.CHARGES
FILE.CONTROL ECMB.ACCT.REGISTER.CHARGES
Type Yam
routine ECMB.V.FIN.SERVICE.CHG
routine ECMB.B.REMOVE.CHARGES.REGISTER
routine ECMB.B.ACCT.REGISTER.CHARGES
routine ECMB.B.GEN.BILL.INF
routine ECMB.V.GEN.BILL.PROCESS
routine ECMB.ACCT.REGISTER.CHARGES.ID
16. Data Migration

NA

34

Tsd-brd-043 Facturacion Cargos Debito A Cuenta V0.6.es - en

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Tsd-brd-043 Facturacion Cargos Debito A Cuenta V0.6.es - en

Caricato da

Copyright:

Formati disponibili

PRODUCT - Model Bank Country Specific

Development & Client Development

Information In This document is subject to change without notice.

© 2018 Temenos Headquarters SA - all rights reserved.

0.1 23 July 2019 Gopal Initial version draft Copy

0.2 02 Aug 2019 Praveen P Review Review comments

0.3 05 Aug 2019 Gopal rEVIEWED Comments Addressed.

0.4 07 Aug 2019 Praveen P Review no Comments

0.5 08/29/2019 Gopal PAYMENT.ORDER related

0.6 10/10/2019 Gerardo L Amend

Sign Off History

Version Date Temenos Authorization Client Authorization

V3.2 / Nov-18 Quality Assurance Internal Use

one. Management Summary ......................................................................................... 4

V3.2 / Nov-18 Quality Assurance Internal Use

1.2 modification Overview

1.3 Reference Documents

Reference Document Description / Path Author, Company

1.3.1 Reference Number of the Requirement (ODR) Which is dependent

1.4 Glossary (Optional)

V3.2 / Nov-18 Quality Assurance Internal Use

V3.2 / Nov-18 Quality Assurance Internal Use

V3.2 / Nov-18 Quality Assurance Internal Use

2.2 New Functionality

2.2.2 Charges Daily Record

1. Multithread ECMB.B.ACCT.REGISTER.CHARGES routine that will run daily during the

V3.2 / Nov-18 Quality Assurance Internal Use

The process is as follows:

 For each of the registers perform the following process:

 It will take account ID and enter the core ACCT.ENT.LWORK.TODAY table

o ARRANGEMENT ARCHITECTURE:With the

V3.2 / Nov-18 Quality Assurance Internal Use

o ARRANGEMENT ARCHITECTURE: Tax be in the

o TELLER:Like the office, the tax will also be registered with

V3.2 / Nov-18 Quality Assurance Internal Use

o CHECK:To associate a tax office in checks, must have a record of

 If there is an associated tax information tax table by the TAX code is

The information stored this table is as follows:

A multivalued group consisting of fields:

V3.2 / Nov-18 Quality Assurance Internal Use

* If during the period parameterised a charge to the account of the

TABLE FIELDS VALUE

- Flag to indicate whether the record has been billed

 ECMB.ACCT.REGISTER.CHARGES records table They cleaned every

* Where M10 means it will run on the 10th of each month.

2.2.3 Invoice generation and shipping information to the external system

a service called BNK // ECMB.FIN.SERVICES.CHG.BILL, which will be executed by a user

V3.2 / Nov-18 Quality Assurance Internal Use

 The routine search the ECMB.ACCT.REGISTER.CHARGES table whose ID <account

The details include the following information:

 Subtotal 0%. (If no tax charges)

V3.2 / Nov-18 Quality Assurance Internal Use

4.2 Reusable Components Table

5. New / Amended Files

V3.2 / Nov-18 Quality Assurance Internal Use

FIELD.NAME- CLIENT NAME

OPERATION CLIENT NAME

FIELD.LBL Transaction date

FIELD.LBL charge amount

FIELD.LBL description Cargo

FIELD.LBL Tax description

V3.2 / Nov-18 Quality Assurance Internal Use

FIELD.LBL Tax amount