Reconciliation

at the end of each day, the partner is responsible for updating cross river on any external activity that needs to be posted to the customer’s account, and for ensuring that all cross river account balances match the partner's ledger this update takes place through reconciliation the table below describes each step of this process reconciliation step description detail daily activity reconciliation cross river generates a reconcliation file and supplies it to the partner to be used for reconciliation the contents will ensure that all messages were received and all transactions were posted correctly reconciliation /#reconciliation file record that will include every transaction message received that day daily account balance sync after reconciling the daily operations, the partner will post net balance updates to any cross river accounts that had any activity on that day to ensure the balances match the partner's ledger if an account has not had any external activity, it is not necessary to post any update transactions use this api to move funds between cross river accounts cut off time cross river requires partners to post net external activity into cross river accounts and ensure that all accounts have been updated before midnight u s eastern time (et) the transaction cut off time is 8 00 pm et, to allow enough time for the end of day synchronization process to conclude before midnight any external activity that takes place between 8 00 pm and 11 59 pm et should be posted the following day reconciliation file record cross river provides a daily transaction detail file for the purposes of partner reconciliation this comma separated ( csv) file will have all the transaction messages for a given day of operation, including those that were sent to the partner via the authorization stream and any others that may have been posted by the card networks after close of operation format messagetypeidentifier \[“authorizationrequest”,”authorizationadvice”, “authorizationincremental”, “financialadvice”, “financialrequest”, “authorizationreversal”, “clearingreversal”, “fee”] id guid relatedtransactionid guid of related transaction id amount number in cents transactiontype \[“debit”,”credit”, "balanceinquiry"] cardid guid for cos card accountnumber string, nullable cardacceptoridentificationcode string merchantnamelocation string merchantcategorycode string devicetype string ismulticlearing bool isfinalmulticlearing bool ischargeback bool response \[“approve”, “deny”] reason \[“approve”, “accountrestricted”, “insufficientfunds”, “inactivecard”, “suspectedfraud”, “duplicatetransmission”,"timeout", "systemerror"] lastmodifiedat mmddyyyy hh\ mm\ ss sample csv header messagetypeidentifier,id,relatedtransactionid,amount,transactiontype,cardid,accountnumber,cardacceptoridentificationcode,merchantnamelocation,merchantcategorycode,devicetype,ismulticlearing,isfinalmulticlearing,ischargeback,response,reason,lastmodifiedat sample csv record authorizationrequest, dcaa6541 657f 4c59 abbb b163005b6d8d, fd09a580 bf59 4d0f a0c2 b2100027a6df,300,debit,dbd4f4eb 1975 4119 bb44 b1d80110ddef,2429153915,111111111111111,usps po 54137206 224 2nd cheney wausa,1111,pos terminal,false,false,false,approve,approve,10202024 22 24 31