Overview

StoneRiver is a line of business accounting software. BriteCore produces return premium, claim payment, and commission payment files to import to StoneRiver.

StoneRiver accepts files with the record types shown in the table below, which BriteCore supports.

Code Name Description Uses
T TransactionRecord The primary record that every exported transaction requires Return premiums;
Claim payments;
Commission payments
D DistributionRecord This record stores vendor and accounting information such as FEIN and account numbers Claim payments;
Commission payments
A PayeeAddressRecord This record stores address information that is printed on the check Return premiums;
Claim payments
F CheckDescriptionRecord These are "free-form" description records that add additional printable information to a check Claim payments



Vendor Contact

Contact StoneRiver.


Getting Started

  1. Contact StoneRiver
  2. Complete paperwork
  3. Work with StoneRiver to install and train your staff on StoneRiver processes

BriteCore Setup

  1. Complete the StoneRiver installation above
  2. Complete the BriteCore vendor setup in Settings > Vendors > StoneRiver. Each account number should be 24 digits long
    • Expense Account Numbers
    • LAE Expense Account Numbers
    • Payable Account Numbers

BriteCore Processing

Folder Creation

If a qualifying return premium, claim payment, or commission payment exists, a folder will be created in Reports > Attachments for the month, e.g., StoneRiver March 2016.

Return Premiums and Claim Payments

With each overnight process, BriteCore will check for qualifying return premium and claim payment transactions. If a transaction exists, a dated file will be created in the month's folder:

  • REFYYYYMMDD.txt for return premiums
  • CLMYYYYMMDD.txt for claim payments

Dates matter. The date of the file will be today. You will be reviewing transactions that were generated during yesterday's business or, in the case of return premiums, policies that canceled overnight and generated a return premium.

Commissions

At the end of each month, BriteCore will generate a commission file. The commission export files are attached to the month in which they are run. For example, December commissions would appear in the January folder as the commissions are processed on the first of each month:

  • COMYYYYMMDD.txt for commission payments

To import commission files to StoneRiver,

  1. Click on an individual file
  2. Save the file to your computer
  3. Upload the file to StoneRiver

How-Tos

Generate a File (IWS Only)

Shell tools > vendors > StoneRiver


FAQ

Does the check number export back to BriteCore?
Not presently. The integration works one way. You can record the check number by inputting into the individual policy’s Notes section, if desired.

When does a transaction appear in a file?

  • REFYYYYMMDD.txt for return premiums
    • Payment must not be selected as "ignored" (database)
    • Payment must not have been canceled
    • Payment must not have been transferred
    • Payment amount must be greater than $0
    • Return premium's date must either be today or in the past
    • Future return premium amounts are not selected
    • Payment must not have been previously exported
  • CLMYYYYMMDD.txt for claim payments
    • Payment must have a positive amount
    • Payment must have payees associated with it
    • Payment must not have been previously exported
    • The claim corresponding to the payment must have associated perils
  • COMYYYYMMDD.txt for commission payments
    • Payment amount must be greater than $0
    • Payment must not be an electronic payment
    • Payment must not have been previously exported

Why isn't the COM (commission) file displaying?
The StoneRiver COM report depends upon the completion of commission's processing. If the process started late or ran into an error, the COM report will not appear until the processing is complete. If you do not receive your COM file by 10 a.m., please submit an OOPS! ticket.


More Information

Record Layout

T Record
('RecordID', 1, COBOL_str(1)),
('RecordGroupCode', 4, COBOL_num(4)),
('VendorID', 10, COBOL_str(10)),
('CheckType', 1, COBOL_str(1)),
('RemitToVendorId', 10, COBOL_str(10)),
('TransactionType', 1, COBOL_str(1)),
('SelectionGroup', 3, COBOL_str(3)),
('PrintingGroupCode', 3, COBOL_str(3)),
('UserDefinedField', 24, COBOL_str(24)),
('InvoiceNumber', 12, COBOL_str(12)),
('AppliesToInvoiceNumber', 12, COBOL_str(12)),
('InvoiceDate', 8, COBOL_num(8)),
('InvoiceAmount', 11, COBOL_num_trailing(11,2)),
('NonDiscountAmount', 11, COBOL_num_trailing(11,2)),
('TermsCode', 3, COBOL_str(3)),
('DueDate', 8, COBOL_num(8)),
('DiscountDate', 8, COBOL_num(8)),
('DiscountPercent', 4, COBOL_num(4,2)),
('DiscountAmount', 11, COBOL_num_trailing(11,2)),
('JobCode', 6, COBOL_str(6)),
('Sundry', 30, COBOL_str(30)),
('VoucherReference', 30, COBOL_str(30)),
('PrePaymentBankCode', 3, COBOL_str(3)),
('PrePaymentCheckNumber', 10, COBOL_num(10)),
('PrePaymentCheckDate', 8, COBOL_num(8)),
('UseTaxVendorId', 10, COBOL_str(10)),
('UseTaxDueDate', 8, COBOL_num(8)),
('UseTaxPercent', 4, COBOL_num(4,2)),
('UseTaxAdjustment', 11, COBOL_num_trailing(11,2)),
('UseTaxAmount', 11, COBOL_num_trailing(11,2)),
('UCPPropertyID', 5, COBOL_str(5)),
('OptionalVoucherDate', 8, COBOL_str(8)), # is a num in spec, use str because it's
"optional"
('Filler', 111, COBOL_str(111)),

A Record
('RecordID', 1, COBOL_str(1)),
('RecordGroupCode', 4, COBOL_num(4)),
('VendorID', 10, COBOL_str(10)),
('InvoiceNumber', 12, COBOL_str(12)),
('Name', 50, COBOL_str(50)),
('Address1', 50, COBOL_str(50)),
('Address2', 50, COBOL_str(50)),
('Address3', 50, COBOL_str(50)),
('Address4', 50, COBOL_str(50)),
('ABA Number', 9, COBOL_str(9)),
('BankAccountNumber', 17, COBOL_str(17)),
('BankAccountType', 1, COBOL_str(1)),
('EFTStartDate', 8, COBOL_num(8)),
('Filler', 88, COBOL_str(88)),

F Record
('RecordID', 1, COBOL_str(1)),
('RecordGroupCode', 4, COBOL_num(4)),
('VendorID', 10, COBOL_str(10)),
('InvoiceNumber', 12, COBOL_str(12)),
('SequenceNumber', 3, COBOL_num(3)),
('Description1', 66, COBOL_str(66)),
('Amount1', 11, COBOL_num_trailing(11,2)),
('Filler', 1, COBOL_str(1)),
('Description2', 66, COBOL_str(66)),
('Amount2', 11, COBOL_num_trailing(11,2)),
('Filler', 1, COBOL_str(1)),
('Description3', 66, COBOL_str(66)),
('Amount3', 11, COBOL_num_trailing(11,2)),
('Filler', 1, COBOL_str(1)),
('Description4', 66, COBOL_str(66)),
('Amount4', 11, COBOL_num_trailing(11,2)),
('Filler', 1, COBOL_str(1)),
('Filler', 58, COBOL_str(58)),

D Record
('RecordID', 1, COBOL_str(1)),
('RecordGroupCode', 4, COBOL_num(4)),
('VendorID', 10, COBOL_str(10)),
('InvoiceNumber', 12, COBOL_str(12)),
('SequenceNumber', 3, COBOL_num(3)),
('DistributionType1', 1, COBOL_str(1)),
('AccountNumber1', 24, COBOL_str(24)),
('Source1', 6, COBOL_str(6)),
('AllocationCode1', 6, COBOL_str(6)),
('Suspense1', 15, COBOL_str(15)),
('DistributionAmount1', 11, COBOL_num_trailing(11, 2)),
('TaxAmount1', 11, COBOL_num_trailing(11, 2)),
('Description1', 30, COBOL_str(30)),
('Filler1', 1, COBOL_str(1)),
('DistributionType2', 1, COBOL_str(1)),
('AccountNumber2', 24, COBOL_str(24)),
('Source2', 6, COBOL_str(6)),
('AllocationCode2', 6, COBOL_str(6)),
('Suspense2', 15, COBOL_str(15)),
('DistributionAmount2', 11, COBOL_num_trailing(11, 2)),
('TaxAmount2', 11, COBOL_num_trailing(11, 2)),
('Description2', 30, COBOL_str(30)),
('Filler2', 1, COBOL_str(1)),
('DistributionType3', 1, COBOL_str(1)),
('AccountNumber3', 24, COBOL_str(24)),
('Source3', 6, COBOL_str(6)),
('AllocationCode3', 6, COBOL_str(6)),
('Suspense3', 15, COBOL_str(15)),
('DistributionAmount3', 11, COBOL_num_trailing(11, 2)),
('TaxAmount3', 11, COBOL_num_trailing(11, 2)),
('Description3', 30, COBOL_str(30)),
('Filler3', 1, COBOL_str(1)),
('Filler', 55, COBOL_str(55)),

Notes on Claim Transactions

Claim transactions are separated into three distinct types. Two are sometimes referred to as LAE payments, with the last being a normal claim payment to an insured. LAE transactions correspond to contacts with either a FEIN or the following roles in BriteCore: Attorney, Claims Adjuster, Contractor, Inspector, Loss Payee, or Vendor. Each of the three types of claims export contain different types of records. Depending on what information is available in BriteCore, the StoneRiver vendor export will generate the following:

  • LAE with FEIN Creates a TransactionRecord along with a DistributionRecord. An example would be a claims adjuster. Having an FEIN attached to the contact allows us to use a DistributionRecord to link up with the database in the client's PTE
  • LAE without FEIN (LAE role) Creates a TransactionRecord along with a PayeeAddressRecord. An example is an attorney with no FEIN. Since the contact is missing the FEIN we just export the address record explicitly
  • Normal Payment Creates a TransactionRecord, four CheckDescriptionRecords and a PayeeAddressRecord. We write everything explicitly since this is a normal check

The display on check data stored along with a transaction in BriteCore (claim_transactions.checkDisplay) is used to include invoice tracking in the voucher field on TransactionRecords. Since the LAE transaction exports don't include CheckDescriptionRecords, the voucher reference gets printed on Eastern Mutual's checks. The client will have to make sure to enter their manual tracking information when the transaction is created in BriteCore.


Feedback

Report unclear or missing documentation.