Integration with eCollect (ecollections.com)

Modified on Fri, Jul 17 at 10:19 AM

Concepts2Code and eCollect can facilitate real-time data exchange. This must be configured on both ends, but once connected, the portal email and texting services can read directly out of eCollect in real time.


Data Fields

The following fields are mapped from eCollect to the portal. Other fields may be made available in the future:


Concepts2Code FieldeCollect Field
UniqueIDAccountID
PrimaryFirstNameNameFirst
PrimaryLastNameNameLast
PrimaryAccountName
NameFull
AddressAddressLine1 + AddressLine2
CityCity
StateState
ZipZip
DOBDateOfBirth
ClientName(not set)
OrigionalCreditorIssuer
AssignedBalanceOrigionalBalance
CurrentBalanceCurrentBalance
AssignedDateDateAccountOpened
EmailEmail
DeskUniqueIDDesk
OrigionalAccountNumberIssuerAccountID
InternalStatusProcessStatus
AccountConsumerToAccessIsActive
CanMakePaymentIsActive
AcceptCheckingPaymentfalse
AcceptRecurringCheckingPaymentfalse
SettlmentACHAllowedfalse
AcceptCreditCardPaymentIsActive
AcceptDebitCardPaymentIsActive
AcceptRecurringCreditCardPaymentIsActive
AcceptRecurringDebitCardPaymentIsActive
SettlementCreditCardAllowedIsActive
SettlementDebitCardAllowedIsActive
*PhoneNumberPhoneNumber
*NameMiddleNameMiddle
*NameSufficNameSuffic
*DriverLicense
DriverLicense
*AmountFinancedAmountFinanced
*PrincipleDuePrincipleDue
*FeesDueFeesDue
*AmountPaidOnAccount
AmountPaidOnAccount
*DateOfLastPayment*DateOfLastPayment
*eCollect.phone.1.phonePhoneNumber
*eCollect.phone.1.PhoneTypePhoneType
*eCollect.phone.1.IsGoodNumberIsGoodNumber
*eCollect.phone.1.IsPrimaryNumber
IsPrimaryNumber
Note about Phone NumbersAll phone numbers are imported on each account. The 4 fields above are added to the custom fields for each phone number. By default the field marked ass PhoneType 'cell' will be set to the cell phone number used for texting. If you choose to use the PrimaryNumber as the texting number that can be configured during onboarding.



Payment Processing / Post Dates

eCollect currently support a read-only integration with the portal, which means that the portal can pull data out in real-time, but it does not send data back. To get data back into eCollect, the portal provides standard CSV data files which you may process to get data back into eCollect. Payments taken on the portal for future dates will be processed by the portal. When daily post dates are run, you will receive an email with the approvals and/or declines. Additionally nightly CSV files are available for import that include daily activity for payments, emails, text messages, logins, etc.











Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article