HomeCU Batch Guidelines


Contents


Interface Overview

To interface with HomeCU, a credit union needs programs to extract account balances and transactions for DDAs and loans.

The account balance files contain records for all HomeCU members, similar to a positive balance file. The transaction files are incremental and only include new transactions since the last extract and upload.

Most vendor extract programs for HomeCU need the following:

  1. A program that flags the members who sign-up for home banking.
  2. A method to set an initial password for those members.
  3. The program needs to keep track of the last history transaction sent to HomeCU for each member.
  4. If there is no last history record (i.e. a new sign-up), the program sends 90 days of history.
  5. A method to re-send all history for all members signed-up for home banking. This allows for support situations where it is simply easier to do a full refresh of the database. Do not re-send members passwords in this case.
  6. The program allows the credit union to create extract files and upload as often as desired. We strongly recommend designing a system capable of multiple uploads per day, rather than systems allowing only one upload per day.
  7. Optionally, a vendor’s interface should support the HomeCU transaction interface. Transactions generated via the Internet can be either e-mailed to the credit union or sent in a transaction file to be downloaded and processed on demand. Support for the transaction interface is the ability to process the transaction file generated by the HomeCU product. HomeCU has several formats for this transaction file, contact HomeCU for more information.

Terminology

The term "Vendor", refers to the vendor of the Credit Union's Internal System.

Required Files

The extract programs must create a minimum of four files. These four files are named with a credit union prefix assigned by HomeCU, followed by a two-character type, followed by a period and a three-digit extension. As an example, we’ll use a fictional client called "Big Sky Credit Union." HomeCU may assign that credit union an account code identified on our system as bscu. Vendors should allow up to 8 characters for the account code.

Our ficticious credit union’s files names are:

 

File

Name

Account Balance

bscudp.bal

Account Transactions

bscudp.his

Loan Balance

bsculn.bal

Loan Transaction

bsculn.his

HomeCU assigns the account code, which is up to eight characters in length. We recommend vendors make the account code a parameter in their extract software, making it changeable from credit union to credit union. (Typically, this is the only parameter to change when installing on a new credit union’s system.)

 

Optional Files

Header File

There is an optional header file that contains the batch number and prior batch number of the upload. This file is used by the HomeCU programs to notify the credit union that they may have sent a batch out of sequence. Although this file is optional, we strongly recommend vendors include it because it significantly decreases support for both DMS and the vendors.

Deleted Transactions

Optionally, HomeCU will process files with deleted transactions if they are included. The deleted transaction files’ structures are identical to normal transaction files, in that a deleted transaction record looks exactly like the original record to be removed. This allows for cases when history items have already been uploaded to HomeCU, but the transaction is subsequently reversed on the credit union’s system. These files are optional in that, they only need to be sent when needed.

Password File

The optional password file contains account additions and deletions for access to the home banking site. HomeCU recommends credit unions set up initial access to new members in this manner, that is, through a program on their system that flags members who want home banking access and sets their initial password. Because members can subsequently update their passwords on-line, changes through this file are not supported. This file only needs to be included when a new member is added.

The naming conventions for these additional files are as follows:

File

Name

Header File

bscu.hdr

Deleted

Account Transactions

bscudp.del

Deleted

Loan Transaction

bsculn.del

Password file

bscu.pwd

 

General File Structure

All of the files contain tab-delimited fields with new-line separated records. The individual fields need not be padded with leading or trailing spaces. These files are typically bundled into a single cpio, tar or zip file. The cpio or tar file is then compress’ed. The name of this resulting file is discussed below under Header File Format.

The resulting file requires accessibility by a PC with Internet connectivity. Most vendors with non-PC credit union systems already have methods of transferring their data to a credit union’s PC. Once the file is accessible either via a mapped drive or PC transfer, the file is uploaded to HomeCU through our secure Web interface.

Specific File Formats

Account Balance File Format

The Account Balance file is basically a positive-balance file containing deposit account information.
  • The combination of the first 3 fields of this file must be unique.
  • All members signed-up for home banking are included in this file each time it is created.

Account Balance

Field

Type

Comments

AccountNumber

 

Char(12)

 

This is the member’s account number.

AccountType

Char(10)

This is the account suffix or type. The combination of account number and AccountType must be unique.

CertificateNumber

Integer

This is the optional certificate number. Fill with zero if not applicable.

DepositType

Char(1)

This is a flag for checking accounts. Fill with ‘Y’ for checking, ‘N’ for savings, ‘C’ for certificates.

Description

Char(30)

Description of the AccountType. This can either be a system-wide generic description (e.g. savings, checking) or if the system permits, the member’s description of the account (e.g. "Joe’s Savings").

Amount

Money

The account’s current balance.

YTDInterest*

Money

YTD Interest

LastYTDInterest*

Money

Previous YTD Interest

Available

Money

Available Balance in the Account

MICR

Char(12)

MICR account number. Used for Credit Unions that have check imaging available. Currently used by Rocky Mountain Corporate

Account History File Format

The Account History file contains transactional information for each member signed-up for home banking.
  • This file is incremental, that is, it only contains new transactions since that last time this file was created.
  • The first 4 fields of this file must be unique.
  • The first 3 fields of this file are the same as in the Account Balance file.
  • When history is displayed for a member, the trace number is used to order the records.

Account History/Transactions

Field

Type

Comments

Account Number

 

Char(12)

 

This is the member’s account number.

AccountType

Char(10)

This is the account suffix or type. The combination of account number and account type must be unique.

Certificate Number

Integer

Optional certificate number. Fill with zero if not applicable.

TraceNumber

Char(16)

A persistent unique identifier for this transaction.

CheckNumber

Char(5)

The check number. Leave blank if not a checking account. This field may not contain leading spaces.

Date

Date

The date of the transaction. Must be a valid date. The format is yyyy/mm/dd.

Amount

Money

The amount of the transaction.

Description

Char(90)

The description of the transaction.

Balance

Money

The account balance after the transaction.

Loan Balance File Format

The Loan Balance file contains loan records for each member signed-up for home banking.
  • Records in this file are sent each time.
  • The first 2 fields of this file must be unique.
Loan Balance

Field

Type

Comments

AccountNumber

Char(12)

This is the member’s account number.

LoanNumber

Char(10)

This is the loan suffix or type. The combination of Account Number and loan number must be unique.

Current Balance

Money

The current balance of the loan as of the last payment.

LastPaymentDate

Date

Because this field is used for payoff calculation, this field is actually the last date interest was calculated. It may or may not be the true last payment date since certain loan adjustments, such as add-on debits could cause last payment date and interest calculation dates to be different. Use the original date of the loan if there is no last payment date or interest calculation date.

UnpaidInterest

Money

This field is used for payoff calculation. Include any unpaid interest at the time the last payment was applied. If the credit union charges late fees, these fees should be added to any unpaid interest. Zero if no last payment, unpaid interest or fees.

PaymentAmount

Money

The normal payment amount for this loan.

NextDueDate

Date

The date the next payment is due. If there is no next payment date and the loan is paid off, fill with the payoff date.

FrequencyPerYear

smallint

The number of payments per year.

Description

Char(30)

Description of this loan.

Type

Char(2)

Credit bureau type code.

InterestRate

Real

Annual interest rate of loan.

CreditLimit

Money

Credit Limit for open end Loan. Enter 0 for closed end.

OriginalAmount

Money

Original amount of loan (closed end). Enter 0 for open end.

OriginalDate

Date

Original date of loan.

Term

Integer

Term of the loan in months.

CDI

Char(1)

Credit disability insurance on this loan. (Y or N).

CLI

Char(1)

Credit life insurance on this loan. (Y or N).

YTDInterest*

Money

YTD Interest

LastYTDInterest*

Money

Previous YTD Interest

Loan Balance (Live Format)

The Loan Balance file contains loan records for each member signed-up for home banking.
  • Records in this file are sent each time.
  • The first 2 fields of this file must be unique.
Loan Balance (Live Format)

Field

Type

Comments

AccountNumber

Char(12)

This is the member’s account number.

LoanNumber

Char(10)

This is the loan suffix or type. The combination of Account Number and loan number must be unique.

Current Balance

Money

The current balance of the loan as of the last payment.

PayOff

Money

The amount to payoff this loan.

PaymentAmount

Money

The normal payment amount for this loan.

NextDueDate

Date

The date the next payment is due. If there is no next payment date and the loan is paid off, fill with the payoff date.

Description

Char(30)

Description of this loan.

InterestRate

Real

Annual interest rate of loan.

CreditLimit

Money

Credit Limit for open end Loan. Enter 0 for closed end.

YTDInterest*

Money

YTD Interest

LastYTDInterest*

Money

Previous YTD Interest

Miscellaneous Info

Varchar(255)

Credit Union-specific value needed for Loan Payment transactions. Available on an as-needed basis.

Loan History File Format

The Loan History file contains loan transaction information for each member signed-up for home banking.
  • This file is incremental, that is, it only contains new transactions since that last time this file was created.
  • The first 3 fields of this file must be unique.
  • The first 2 fields of this file are the same as in the Account Balance file.
  • When history is displayed for a member, the trace number is used to order the records.
Loan History

Field

Type

Comments

AccountNumber

 

Char(12)

 

This is the member’s account number.

LoanNumber

Char(10)

This is the loan suffix or type. The combination of Account Number and loan number must be unique.

TraceNumber

Char(16)

A persistent unique identifier for this transaction.

Date

Date

Date of transaction.

PrincipleAmount

Money

Amount of transaction applied towards principle.

InterestAmount

Money

Amount of transaction applied towards interest.

Description

Char(30)

Transaction description.

Balance

Money

Balance of loan after this transaction.

Password File Format

This file contains account numbers and passwords when members sign-up for home banking.
  • This file only contains a record for a member when they are initially flagged for home banking.

Password File

Field

Type

Comments

Action

 

Char(1)

 

Must contain either an ‘A’ for add, or a ‘D’ for delete.

AccountNumber

Char(12)

This is the member’s account number.

Password

Char(9)

This is the member’s password. It can contain any combination of letters and numbers.

 

Header File Format

This is simply a text file that contains identifying information for the upload. If this file is included, the HomeCU software checks the contents for two lines listed below. The export ID is simply a sequentially assigned number for each extract.
  • This file is used to determine if the credit union may have missed an upload.
  • This file is used to check if the credit union may have sent an old upload by mistake.

Header File

Prev Export ID: 268
Curr Export ID: 269

The Contents of this file consist of the above 2 lines. The HomeCU software only looks for the lines that begin with "Prev Export ID:" or "Curr Export ID:" followed by a number. Because anything else in this file is ignored, vendors may put additional information in this file, such as, number of members sent, date ranges, etc.


When all the required files are bundled together, we recommend that the resulting file name contain the export ID. Under UNIX like systems, the files are typically cpio'd, then compress'd, then the resulting file is named 269.daz. Under DOS systems, the files are zipped and the resulting file is named 269.zip. This naming method allows the credit union to easily send an old export.

 

Transaction File Format

This file contains transactions performed by members within HomeCU. If a credit union chooses to receive transactions via this method, the HomeCU software creates this file on-demand from within the administration area of the HomeCU web-site. A credit union can then download this file and process it on their core system.
  • The file consists of 3 types of records:
    • A single header record.
    • Multiple transaction detail records.
    • A single trailer record.
  • Currently there are several different formats for the detail records of this file to accomodate various vendor's systems. The format listed below is the preferred format for this file. Contact DMS for information on other formats.

Transaction File Header Record

Field

Type

Comments

Record ID

Char(2)

Value is "AA" for the Header Record.

File ID

Char(10)

Value is "DMS HomeCU"

Batch ID

Char(5)

Numeric Batch Number (e.g. 00001, 00002, 00003, etc.)

Creation Date

Char(24)

e.g. Thu Jun 1 13:48:49 2000

CU Account Code

Char(8)

e.g bscu

 

 

Transaction Detail Record
AccountNumberThe Member Number
TransactionDateThe date the transaction was generated.
TransactionCode
Transaction Codes
ATAccount Transfer
LPLoan Payment
LALoan Addon
CWCheck Withdrawal
CPCredit Card Payment
MDMessage Delete
MAMember Activation
ESElectronic Statement Activation
Reference1 For transfers between accounts, Reference1 is the account suffix or loan number for the "from" side. For a "Message Delete" (MD) transaction, this is the Message I.D.
For "Member Activation" (MA) transactions, this is the first field required by the credit union to authenticate the member (e.g. Social Security Number).
Reference2For transfers between accounts, Reference2 is the account suffix or loan number for the "to" side. For CW, CP, MD and ES this field will be blank.
For MA transactions, this field will be the second field required by the credit union to authenticate the member (e.g. Birth Date).
Reference3This field will hold the email address (if any) provided by the member at the time the transaction was recorded.
AmountAmount of the Transaction or Withdrawal. For MD transactions, this field will be zero or blank.

 

Transaction File Trailer Record

Field

Type

Comments

Record ID

Char(2)

Value "ZZ", constant.

 

All contents copyright © 2000 Database Management Services Inc. Important Notices.