BEAM Software has an integration with the Payment Portal. Users of this system can expect the following benefits:
BEAM is a direct partner of Concepts2Code and Integration is seamless.
Data is read from BEAM in real-time. Consumers can see up-to-the-minute information on their account.
Data from the payment portal is made available within the portal and CSV files that the agency can access.
Payment data must be manually imported into BEAM.
Credit Card Post Dates taken on the Payment Portal will be processed using your existing gateway. Payments taken on the portal will be managed on the portal.
ACH Post Dates taken on the Payment Portal need to be processed through BEAM. You can import these payments using one of the CSV files.
Automatic C2c Portal Posting Agent
Over 200 Custom fields are available for email and texting templates.
Generate Targeted Campaigns in BEAM's Debt Commander
Create customized debt recovery campaigns using hundreds of customizable criteria. Easily filter accounts by:
• Active status with no current payment plan/promise
• Balance thresholds
• Client characteristics
• [Other key filters]
Export your refined account lists directly to Concepts2Code to launch mass email campaigns or other communication strategies.
Learn more: Create campaigns from account lists
Cell Phone Numbers in BEAM
To allow cell phone number to be picked up in BEAM, you must have then configured as cell phones. The following configuration should be made to any number that you wish to use for texting:
The number description must be "Mobile"
The Status must be saved as "Hot"
This will update the number to "Active"
The number must be set to "Allow SMS". (if you do not use the "Allow SMS" features, please let us know, we can set your system to ignore this requirement.)
If the cell phone numbers are not appearing, ensure that the data is configured correctly in BEAM.
If you have multiple phone numbers that meet these requirements, only the first number will be used.
BEAM Field Mappings
The following table shows how fields in BEAM are mapped to the system. (not all fields are currently listed)
BEAM Field Name | C2C | Notes |
IssuerName | OriginalCreditor | |
PortfolioOwner | ClientName | |
Not Used | Client ID | |
SSN_SIN | SSN | |
AccountID | Reference Number | |
Account Table | [*account.PortfolioOwner] | Any field in the account table will be available by its own name |
Debtor Table | [*debtor.FirstName] | Any field in the debtor table will be available by its own name |
Debtor Address Table | [*debtorAddress.Other.Address1] | Any field in the debtor table will be available by its own name |
Hot Address | [*hotAddress.Address1] | Only one address can be considered the "Hot Address". It is accessible through field such as: [*hotAddress.Address1] |
DomainName | If the domain is "Closed" they cannot access the account. If it is anything else but "Closed" they can access their account. | |
Beam Custom Properties | [*beam.custom.property.1] | Beam Account Custom Properties are pulled from Beam Software and listed in Consumer Replacement fields as *beam.custom.property.1-100. Custom Property labels on Beam Software account pages can be edited and changed, therefore, each custom property is added to the Consumer Replacement Fields as a generic numeric value to ensure data is consistently transferred. |
Post Dates | Post Dates are read from the BEAM Promise Screen. | Post dates will show up for any Active Promise in which the ACH or Credit Card options are checked in BEAM |
Settlements | A settlement will be Offered to a consumer when there is a Promise in BEAM. | To determine this, the system will examine all payments in the promise screen. If all of them are "Promised" and there is a value in the Settlement Balance field. Then a settlement of that amount will be offered to the consumer. The amount of the Settlement will be the Settlement Balance. The max number of payments will be the number of rows in the promise screen and the max settlement date will be the latest date in the Settlement rows. The consumer will have the ability to modify the dates and amounts as long as they conform the the values specified, so the payments may not exactly match what is in the promise screen, but the end result will be a settlement of the agreed amount. |
"Domain" in BEAM | AllowConsumerToAccess | The "Domain" in BEAM is used to determine if a account is accessible in web portal. If the "Domain" is "closed" the account will not be accessible in the portal. Accounts with any other domain will be able to access the portal. |
AllowConsumerToAccess | if the "Domain Name" is "Closed" this is set to false, otherwise it is set to true. | |
CanMakePayment | if the "Domain Name" is "Closed" this is set to false, otherwise it is set to true. | |
AcceptCheckingPayment | false by default. This can be overriden at the BEAM level, so please verify your settings during onboarding. If it is true at the BEAM level, the consumer also must have the "Domain Name" not equal to "Closed" | |
AcceptCreditCardPayment | if the "Domain Name" is "Closed" this is set to false, otherwise it is set to True. | |
AcceptDebitCardPayment | if the "Domain Name" is "Closed" this is set to false, otherwise it is set to True. | |
AcceptRecurringCheckingPayment | False by default. Some older systems may have this configured to be true by default.We recommend using Custom Mappings on this field to ensure you have full control over it. | |
AcceptRecurringDebitCard | False by default. Some older systems may have this configured to be true by default.We recommend using Custom Mappings on this field to ensure you have full control over it. | |
AcceptRecurringCreditCard | False by default. Some older systems may have this configured to be true by default.We recommend using Custom Mappings on this field to ensure you have full control over it. | |
Domain Name | *beam.domainname |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article