Contents

• Review Transaction Import Errors from Sola
• Cardknox Rebrand to Sola FAQ

Review Transaction Import Errors from Sola

Note: The information in this section pertains only to Sola.

When the Merchant Download Automation job runs, it analyzes payments in the recently settled Sola batch for any missing customer information. If missing customer information is found, the job is aborted, and a Transaction Import Errors (TIE) record is created. The job cannot proceed until all the Transaction Import Errors are resolved.

Best Practice for Reviewing Issues

Recommended: Check for Bank Deposits and Journal Entries every day (if you received payments on the previous day).

If you do not locate any records, check any of these resources for additional information:

• Review the Exception: Merchant Download or Automated Job Results
• Navigate to the Automated Job Results tab and find more information on the Merchant Download list view
• Check Sola to see if there is a batch of payments processed for the previous day. If there is a batch, review the Transaction Import Errors page

Important: When the Merchant Download job runs, it searches up to 99 previous days to complete missing details once TIEs and/or errors have been addressed. Because of this, you should not manually create missing records as it can result in duplicates.

Review and Address Transaction Import Errors

Access the Transaction Import Errors page by clicking the Related tab on the Payment Processor page or navigating directly to the tab using the App Launcher. Error messages on the Transaction Import Errors page might be related to one of the following:

1. The Customer 19 field was not added to the Payment Site Page Layout in Sola. For more information, refer to the Complete Sola and PaymentSITE Configurations section of the Sola Onboarding Process article.
2. Sometimes the Merchant Download Automation job does not identify the related Customer Account name in Accounting Seed. This can be because the payment was not initiated through Accounting Seed or was not associated with a valid Billing record (for example, it was made through a standalone payment link, directly in Sola, or the original Billing was deleted), which prevents it from syncing with Salesforce.

Note: To correct this, add the Billing number and Customer Account name. If you add only the Customer Account then rerun the Merchant Download job, a Cash Receipt is created but not applied since no billing is specified to apply it to. Include the Billing number so the Cash Receipt is both created and applied to the Cash Receipt for the specific Billing when the job runs. Click the drop-down arrow to the right of a row and select Edit. In the Edit dialog box, add the information, then Save.

TIE Notes

• If there are TIE records, ensure they are updated with the Billing/Customer
• Errored/Declined Sola Transaction: If a transaction has a TIE but was for an Errored/Declined Sola Transaction, it must still be assigned to either a Customer or Billing. The Payment Activity record cannot be updated until the TIE is resolved. AR Automation recognizes the transaction was errored/declined and does not create the CRs and/or include them the JEs and BDs
• TIEs should not be deleted because they return until resolved

Re-run the Merchant Download Job

When all error messages are cleared from the Transaction Import Errors page on the Related tab, the Run Merchant Download button is available on the Payment Processor page. Run this job to re-start the transaction import process, or, if you have this job scheduled to run at night, it runs as part of the normal process.

Once the job runs successfully, the Last Sync field on the Payment Processor page is updated to reflect the last date and start time of the Merchant Download Automation job.

Cardknox Rebrand to Sola FAQ

Since Cardknox has become Sola, you may have questions.

What has changed?

The only change you should see is in the portal, which consists primarily of rebranding (updated colors and logo). The portal layout and functionality are similar to the previous view.

What affect does this have on our PaymentSite URLs?

There is no change to the unique Billing URLs or the PaymentSite URLs. The URLs redirect automatically.

Will the redirect end at some point and cause our links to no longer work?

No. The URLs should continue to redirect.

The email mentioned white listing the new domain. Is there anything I need to do to ensure our Automated Job and Automation is not interrupted?

No changes are required within Salesforce/Accounting Seed.

Are there any changes that we should make?

Update the URL to log into your Cardknox portal. This might require steps to add MFA (multi-factor authentication) for Sola. Use the updated information going forward.