Professional Documents
Culture Documents
End of Year Procedure FATCA Bangalore
End of Year Procedure FATCA Bangalore
Table of Contents
Table of Contents...........................................................................................................................................2
Document History ..........................................................................................................................................4
Introduction ....................................................................................................................................................5
Overview of FATCA Year End Processing ....................................................................................................5
Balance aggregation ................................................................................................................................. 5
FATCA TAX BASE formation .................................................................................................................... 5
FATCA.AGGREGATION.PARAMETER ........................................................................................................5
RELATION.LEVEL ................................................................................................................................ 6
RELATION.CODE ................................................................................................................................. 6
EXCLD.FOR.ACCT.AGG ...................................................................................................................... 6
SAM.FIELD ........................................................................................................................................... 7
SAM.OPERAND .................................................................................................................................... 7
SAM.VALUE.......................................................................................................................................... 7
ENT.CUST.FIELD ................................................................................................................................. 7
ENT.CUST.OPERAND .......................................................................................................................... 7
ENT.CUST.VALUE................................................................................................................................ 7
ACCT.AGGR.RTN................................................................................................................................. 7
ROLE.TYPE .......................................................................................................................................... 7
FATCA.REPORTING.PARAMETER .............................................................................................................7
REP.EXTRACT.DATE .......................................................................................................................... 8
REPORTABLE.STATUS ...................................................................................................................... 8
OWN.REP.STATUS .............................................................................................................................. 9
STATUS.TYPE ...................................................................................................................................... 9
FATCA.STATUS ................................................................................................................................... 9
DEFAULT.ADDRESS ........................................................................................................................... 9
ADDRESS.RECORD ............................................................................................................................ 9
REL.IDENTIFIER................................................................................................................................. 10
REL.CODE .......................................................................................................................................... 10
OWNER.ADDRESS ............................................................................................................................ 10
OWNER.ADD.RECORD ..................................................................................................................... 10
COUNTRY.SUB.ENTITY .................................................................................................................... 10
FCY.ACC.REPORT ............................................................................................................................. 10
RECAL.REPORT ................................................................................................................................ 10
NPFFI.REPORT .................................................................................................................................. 11
MIN.BAL.CHECK ................................................................................................................................ 11
AGG.BAL.CHECK .............................................................................................................................. 11
UPDATE.INC.BASE ............................................................................................................................ 11
AGGRALL – Aggregation to be done for both custody and depository by adding the reporting
balance per tax base record ........................................................................................................................11
NEW.ACCOUNT.ONLY ...................................................................................................................... 11
NEW.ACCOUNT.ENT ......................................................................................................................... 11
NEW.ACC.EXIST ................................................................................................................................ 12
XML.DIR .............................................................................................................................................. 12
PAYMENT.TYPE ................................................................................................................................. 12
TXN.CODE .......................................................................................................................................... 13
CLOSED.ACCTS.BAL ........................................................................................................................ 13
REP.PMT.INCOME.ONLY .................................................................................................................. 13
Report Generation .......................................................................................................................................15
FATCA.XML.REQUEST .......................................................................................................................... 15
YEAR ................................................................................................................................................... 17
ACTION ............................................................................................................................................... 17
REPORT.TYPE ................................................................................................................................... 17
POOL.STATUS.TYPE ......................................................................................................................... 18
POOL.INDICIA .................................................................................................................................... 18
POOL.REPORT.DATE ........................................................................................................................ 18
Report Generating Service ..........................................................................................................................18
Conclusion ...................................................................................................................................................18
Document History
Comments:
NA
Introduction
The financial institutions have an obligation to obtain and exchange information with respect to reportable
accounts. Detailed explanation on parameterization of reporting requirements applicable to US accounts
and procedure for report generation is explained in this document.
Balance aggregation
▪ Balance aggregation is collection of all reportable balances.
▪ Aggregation process is controlled by the parameter
FATCA.AGGREGATION.PARAMETER
▪ Aggregate balances were built using the batches FATCA.BUILD.AGGR.BAL and stored
in the file FATCA.AGGREGATE.BALANCES
FATCA.AGGREGATION.PARAMETER
Figure 1: FATCA.AGGREGATION.PARAMETER
RELATION.LEVEL
▪ This field specifies from where joint customers/accounts to be identified from.
▪ Allowed values are CUSTOMER or ACCOUNT.
- CUSTOMER denotes to include balances of all accounts of that joint customer.
- ACCOUNT denotes only the accounts are jointly held are considered in balance
aggregation.
RELATION.CODE
▪ Relation codes, that needs to be considered for balance aggregation can be defined in
this field
▪ Valid input is from RELATION
- Example: RELATION.CODE = 9
- Any customer with relation code ‘9’ to an eligible FATCA client will be reported as
joint holder of that FATCA client.
EXCLD.FOR.ACCT.AGG
▪ Bank can define any CATEGORY here; all accounts with this category will be excluded
from balance aggregation.
The fields SAM.FIELD, SAM.OPERAND & SAM.VALUE are associated multi-value fields used to define a
condition, any portfolio satisfying these conditions are exempted from aggregation process. When more
than one condition is defined, each set will be considered with OR condition.
SAM.FIELD
▪ Any valid field from SEC.ACC.MASTER
SAM.OPERAND
▪ Input an operand EQ or NE
SAM.VALUE
▪ Input the value to be compared with field defined in SAM.FIELD using SAM.OPERAND,
resultant records will be exempted.
ENT.CUST.FIELD
▪ Input a field from CUSTOMER table to identify a customer as legal entity.
ENT.CUST.OPERAND
▪ Input EQ or NE
ENT.CUST.VALUE
▪ Input the value to be compared with field defined in ENT.CUST.FIELD using
ENT.CUST.OPERAND to identify as legal entity.
ACCT.AGGR.RTN
▪ In case bank maintains any depository/custodian balances externally and wishes to add
them along with balances extracted by aggregation process, and then they may do it
using a local routine, which takes two input arguments, 1 is Customer number and 2 is
FATCA.AGGREGATE.BALANCE record. Output argument is
FATCA.AGGREGATE.BALANCE record with additional balances. The local routine
should be attached to this field.
ROLE.TYPE
▪ Currently not functional, this is for future use.
FATCA.REPORTING.PARAMETER
This is a high-level parameter table, which provides some flexibility to setup the system to generate FATCA
regulatory reports.
This parameter table can be used to setup values like report extract date, the statuses/account
classifications to be included in the report, the relations of customer to be used for balance aggregation,
minimum or aggregate balance check, the directory into which the generated XML is to be placed and many
more.
Below is a brief description of important fields in FATCA.REPORTING.PARAMETER, which can help you
to setup the table suitably.
Figure 2: FATCA.REPORTING.PARAMETER
REP.EXTRACT.DATE
▪ It is standard date/frequency field to denote the date on which the base data for reporting
will be extracted and consolidated in the FATCA TAX BASE file.
▪ The COB will run on this date to update the base file with the ‘base’ data for all clients.
▪ It is recommended that this date is always set to 31st December of the year.
▪ If the date happens to be a holiday, the extraction will be on the previous working day.
The account balances will always be updated on the last working day of the calendar
year.
▪ It will be recycled to the next date when the base update for a year is done.
REPORTABLE.STATUS
▪ FATCA.TAX.BASE records will be built only for these status.
▪ Allowed input is from FATCA.TAX.STATUS.
▪ The statuses to be reported are
- Specified US person, Passive NFFEs with US substantial owners, Owner
documented FFIs, etc.
- i.e. FATCA.STATUS for a client in FCSI can be any status as per the documents
received or manually set. FATCA.STATUS can be ACTIVE.NFFE,
PASSIVE.NFFE, US.ACCOUNT, NON.US.ACCOUNT, etc...
OWN.REP.STATUS
▪ A FATCA client can have owners like JOINT, SUBSTANTIAL or BENEFICIAL owner. As
there is a FATCA.STATUS for a FATCA client, each owner also holds his own status.
▪ When owner details needs to be reported based on statuses, such statues can be
defined here.
▪ JOINT/BENEFICIAL/SUBSTATIAL owner status can be found in JO.BO.STATUS field in
FCSI.
▪ As per Form 8966 reporting, this will be required for OD FFIs and Passive NFFEs with
identified US owners.
STATUS.TYPE
▪ As you may know, FATCA.TAX.STATUS is flexible in T24. Therefore, Banks can define a
status with a name of their convenience through the table FATCA.STATUS.
▪ While reporting, system looks for clients with standard statues like
RECALCITRANT/NONPARTICIPATING/ DORMANT
/INACTIVE/PASSIVE_NFFE/OD_FFI/SPEC_US_PERSON.
▪ In order to map the actual status type used in the system against each standard type,
field STATUS.TYPE and FATCA.STATUS are used in conjunction, where STATUS.TYPE
holds standard type and FATCA.STATUS holds actual type used.
FATCA.STATUS
▪ As explained in above field. STATUS.TYPE and FATCA.STATUS works in conjunction,
please refer explanation for field STATUS.TYPE for more clarity.
▪ It takes any valid ID from FATCA.TAX.STATUS.
DEFAULT.ADDRESS
▪ The field is used to specify the application from which the client’s address needs to be
picked up for
▪ Reporting. It can either be ‘CUSTOMER’ or ‘DE ADDRESS’.
ADDRESS.RECORD
▪ When DEFAULT.ADDRESS is specified as DE.ADDRESS, then this field is used to
identify the record ID from where the address of the customer will be picked up for
reporting.
▪ For example, if the ADDRESS.RECORD is set as PRINT.1, for customer ID (100807) in
Company 1 (US0010001), the system will read the DE ADDRESS record US0010001.C-
100807.PRINT.1 and get the address
OWNER.TYPE
▪ Input any owner such as JOINT/ BENEFICIAL/SUBSTANTIAL.
REL.IDENTIFIER
▪ This field holds the application name from which joint customer/owners of a FATCA client
can be identified from, either CUSTOMER or FCSI is allowed.
▪ In T24 joint customers may be defined in FCSI record or CUSTOMER record, so enter
FCSI or CUSTOMER in this field according to the practice.
▪ If left blank, the related customers will be from Customer or Account as defined in FATCA
AGGREGATION PARAMETER based on Relation level.
Note: For beneficial and substantial ownership, the relationships will be only from FCSI. So, if the
OWNER TYPE is Beneficial or substantial, only FCSI is allowed.
REL.CODE
▪ If REL.IDENTIFIER is left blank, this field can be used to specify the relation codes for
identifying the joint owners.
▪ This will only be used for defining relation codes for joint owners if the relationships are
not defined in FATCA CUSTOMER SUPPLEMENTARY INFO or in FATCA
AGGREGATION PARAMETER
OWNER.ADDRESS
▪ It is used to identify the application from which owner’s address is to be taken for
reporting.
Note: Beneficial and Substantial owners will be only from FATCA CUSTOMER
SUPPLEMENTARY INFO and for JOINT owner it can be from CUSTOMER or
DE.ADDRESS as defined in this field.
OWNER.ADD.RECORD
▪ This is same as ADDRESS.RECORD field but this one acts for owners
▪ If the OWNER ADDRESS is set to DE.ADDRESS (for joint owners), the field is used to
identify the record from where the address of the customer will be picked up and updated
in FATCA TAX BASE.
COUNTRY.SUB.ENTITY
▪ This field must hold a valid field name from the application entered in
DEFAULT.ADDRESS.
▪ Country Sub entity is generally a state or province as part of client address, so enter an
appropriate field from default address application.
FCY.ACC.REPORT
▪ Account balances can either be in reported in account currency itself or USD.
▪ When non US accounts’ are to be reported in its own currency then specify it as ACCOUNT
▪ Alternatively, if they are to be reported in USD, this field has to be set as USD. By default,
all accounts will be reported in USD.
▪ For portfolios, reporting currency will be USD by default.
RECAL.REPORT
▪ This field should be set to YES when POOL report is required. When it is set to YES,
FATCA.POOL.BALANCE table will be updated with aggregate balance of
Recalcitrant/Dormant accounts facilitating generation of POOL report.
Figure 3: FATCA.REPORTING.PARAMETER
NPFFI.REPORT
▪ When Non-Participating Foreign Financial Institution (NPFFI) payments are to be reported
in POOL report, then set this field to YES.
MIN.BAL.CHECK
▪ When depository accounts with balance below $50000 is not to be reported, then you can
set this field to YES.
AGG.BAL.CHECK
▪ If this field is set to YES, the minimum balance check (based on MIN BAL CHECK field)
will be based on aggregate balances (total of custody and depository accounts). The
depository accounts will be reported only if the aggregate balance is above $50000.
▪ If this field is left blank, then the minimum balance check will be based on individual account
balances.
UPDATE.INC.BASE
▪ Account balances can be aggregated in different ways. Allowed values and its explanation
is as below
AGGRALL – Aggregation to be done for both custody and depository by adding the
reporting balance per tax base record
AGGRCUSDEP – aggregation by custody and depository done separately and reported
AGGRCUST – aggregation by custody and depository not aggregated it is reported
individually
Blank – Non aggregation, all accounts reported individually.
NEW.ACCOUNT.ONLY
▪ If this is set to YES, individual accounts opened after 1st July 2014 will be reported provided
the field NEW.ACC.EXIST is left blank. Default is NO.
NEW.ACCOUNT.ENT
▪ This is same as NEW.ACCOUNT.ONLY but entities. Default is NO.
NEW.ACC.EXIST
▪ If this is set to YES, new accounts for an existing client who already has accounts will be
treated as pre-existing.
XML.DIR
▪ The directory into which the generated XML should be updated is specified here.
Figure 4: FATCA.REPORTING.PARAMETER
PAYMENT.TYPE
▪ As per FATCA design, it is possible to identify and report balances of specific TXN.CODE
under required PAYMENT.TYPE.
▪ Such transactions considered may be custody or depository with interest or dividend or
gross proceeds/redemption or other incomes.
▪ It can take values like DEP.INTEREST or CUS.DIVIDEND or CUS.INTEREST or
CUS.GROSSPROCEEDS/REDEMPTION or CUS.OTHER.INCOME.
TXN.CODE
▪ It is used to define the transaction code of the income to be reported.
▪ As explained in above field. PAYMENT.TYPE and TXN.CODE works in conjunction, please
refer explanation for field PAYMENT.TYPE for more clarity.
▪ It takes any valid ID from TRANSACTION table.
CLOSED.ACCTS.BAL
▪ As per FATCA design, any FATCA client may be marked as INACTIVE. For such
INACTIVE Customers the balances can be reported as of closure date or as of previous
month end of closure date.
▪ It can take two values CLOSE.DAY & MONTH.END. Option CLOSE.DAY is to report as of
closure date and option MONTH.END is to report as of previous month end of closure date.
▪ Closure date of the account/client is entered in the field STATUS.CHANGE.DATE in FCSI
record.
▪ When nothing is selected then the Close Day will be considered as default.
REP.PMT.INCOME.ONLY
▪ Whenever the Payment related information alone has to be reported for specific
FATCA.STATUS then this field can be used.
▪ Example: For Non-Participating Financial Institutions bank may choose to report only
payment information while its account balance to be updated as 0.00, then this field can be
used by specifying the relevant FATCA.STATUS.
▪ It can take any valid ID from FATCA.TAX.STATUS table.
▪ BNK/FATCA.BUILD.AGGR.BAL
- Jobs running under this batch collects, collates and forms the final file
FATCA.AGGREGATE.BALANCES for each customer.
- This runs daily.
▪ BNK/FATCA.TAX.UPDATE
- Jobs running this batch produce the files FATCA.TAX.BASE,
FATCA.POOL.BALANCES and FATCA.AGGR.TAX.BASE
- FATCA.TAX.BASE holds information by customer including addresses, balances,
etc.
- FATCA.AGGR.TAX.BASE holds information by reportable status.
- FATCA.POOL.BALANCES holds information for each type of pool report.
Figure 5: BATCH-BNK/FATCA.BUILD.AGGR.BAL
Figure 6: BATCH-BNK/FATCA.TAX.UPDATE
Report Generation
After setting up above defined FATCA.REPORTING.PARAMETER table, in COB the system builds all
necessary data for report generation into base files FATCA.TAX.BASE & FATCA.AGGR.TAX.BASE.
FATCA.XML.REQUEST
Figure 7:FATCA.XML.REQUEST-AGGR
Figure 8:FATCA.XML.REQUEST-AGGR-SPEC.US.PERSON
4. POOL: To generate a Pool report create a record with ID – POOL and enter Account Holder Type
in filed POOL.STATUS.TYPE.
Figure 9:FATCA.XML.REQUEST-POOL
5. POOL-(Message Reference): This is same as POOL report using which you can re-generate a
report after making necessary corrections in FATCA.POOL.BALANCE, where Message Reference
is reference of already generate XML report, same can be found in MSG.REF.IF field of
FATCA.POOL.BALANCE
6. A-(Message Reference): This is same as AGGR but facilitates report re-generation when
correction is done to an existing FATCA.AGGR.TAX.BASE, where Message Reference is
reference of already generated XML report, same can be found in MSG.REF.ID field of
FATCA.AGGR.TAX.BASE
YEAR
▪ The field identifies the year to which XML report is being generated.
ACTION
▪ This fields will accept values like NEW, CORRECTION, VOID & AMEND.
▪ The default value will be NEW means the message is being generated for the first time.
▪ When a XML that has been generated needs to be corrected then Corrected Data is used
for records being re-transmitted after the IRS has notified the sender of a problem with the
file or underlying data. Corrected Data should ONLY be used when responding to an IRS
request to correct the data. (not used for Decryption, XML or other file-level errors).
▪ Void Data is used to erase previously-filed records when data needs to be re-transmitted.
▪ Amended Data is used to amend a record(s) previously transmitted to, received and
processed by the IRS, but is later found to contain erroneous information.
REPORT.TYPE
▪ It is a system updated field, based on ACTION following will be populated in it.
- FATCA1 = New Data
- FATCA2 = Corrected Data
- FATCA3 = Void Data
- FATCA4 = Amended Data
With use of POOL.STATUS.TYPE and POOL.INDICIA you can generate these reports.
POOL.STATUS.TYPE
▪ Mention the status RECALCITRANT / DORMANT / NON-PARTICIPATING) for which the
pool report is needed.
▪ If the field is left blank, all types of POOL reports will be generated as per the availability.
POOL.INDICIA
▪ This field indicates whether pool report is to be generated for clients with indicia or
without indicia.
▪ To generate FATCA201 or FATCA202, set POOL.STATUS.TYPE as RECALCILTRANT
and POOL.INDICIA as YES or NO correspondingly.
▪ If the field is left blank, two reports will be generated for specified POOL.STATUS.TYPE,
one with INDICIA and another without INDICIA
POOL.REPORT.DATE
▪ The field identifies the date on which the pool report is extracted.
▪ It is input able only for POOL report, if left blank REP.EXTRACT.DATE of
FATCA.REPORTING.PARAMETER is defaulted.
Conclusion