What payments covers
Payments is the heart of servicing: collecting ACH or card payments, posting them to the right contracts, and handling the ones that fail. Ask Lendscape which payment methods and processors are supported, and which are pre-built versus custom.
A worked example
Say 3% of your 2,000 monthly payments fail — 60 failed payments. Each failure needs a retry, a customer contact, and a note on the account. At 15 minutes each, that is 15 hours of monthly labor if the system does not automate the retry and the notice.
Expected output in the demo: a failed payment that retries on a schedule, notifies the customer, and lands in a work queue if it fails again — with no manual tracking.
Demo checks
- Post an ACH payment and show the accounting entries.
- Show a failed payment retry flow end to end.
- Reverse a payment and show the correction entries.
- Show a partial payment and how it applies.
The exception to check
Ask how the platform handles a payment that arrives with no contract reference — a check with a vague memo, or an ACH from a new bank account. Unapplied cash handling is where servicing teams lose hours every week.
Also ask which payment processors have pre-built connections today. An API-led platform can connect to many processors, but each connection still needs to be built, tested, and owned by someone.
Payments capability checks
- Supported payment methods and processors are listed.
- Failed payment retry flow is demonstrated.
- Reversal creates correct accounting entries.
- Unapplied cash queue is demonstrated.
- Customer notification on failure is automatic.
Sources
- Lendscape — Equipment finance software checked 2026-11-05
- Lendscape — JDR Solutions technology partnership (news) checked 2026-11-05
Based on public product documentation. We have not tested a private account. Landscaping Equipment Financing LLC is an independent commercial equipment finance broker, not a lender, and not affiliated with any software vendor listed here.