Integrations
Plug into the systems credit originators actually run on.
dPlat integrates with the enterprise platforms, billing engines, customer-service environments, and recovery workflows your portfolio already moves through. Over 60 production integrations across 16 platform types, with twenty years of integration patterns behind them.
Connected to the systems you already run
The footprint
What dPlat connects to today.
60+
Production integrations
16
Platform types
500+
Agency and legal partners integrated
Since 2003
In continuous production
The concentration sits in the systems large credit originators actually use to bill, service, and manage customer accounts. SAP and Oracle utility environments alone account for 34 active integrations. Add proprietary servicing platforms and dPlat already covers most of the footprint an enterprise originator needs.
Past the enterprise systems, dPlat is integrated on the back end with 500+ collection agencies, law firms, and recovery vendors. Placement files, status updates, payments, and reconciliation move between dPlat and your network directly, with no vendor portal in between.
For your engineering team, that means most of the integration work has already been done. The patterns, the field mappings, the reconciliation logic, and the exception handling are built, tested, and deployed against production volumes.
Enterprise and ERP
Enterprise and ERP integrations.
The largest concentration of dPlat deployments lives inside enterprise resource planning environments. Utility billing engines and ERP-class platforms run on these systems, and dPlat is already inside them at production scale.
| Platform | Category |
|---|---|
| SAPEnterprise ERP | Enterprise ERP |
| Oracle CC&BUtility CIS | Utility CIS |
| Oracle Utilities C2MUtility CIS | Utility CIS |
| CR SoftwareCollections | Collections |
| ArtivaCollections | Collections |
The bulk of these run inside large utility and telecom operations where SAP and Oracle handle billing, service requests, and customer-master data. dPlat reads placement files, applies your business rules, and pushes account status, payments, and reconciliation results back to those systems on schedule.
Customer servicing and billing
Customer service and billing platforms.
Traditional servicing and billing ecosystems used across utilities, telecom, and consumer financial services. These integrations pull placement and update files on a defined cadence, with field mapping customized for each source.
| Platform | Category |
|---|---|
| ICOMSCable/Telecom CIS | Cable/Telecom CIS |
| CSGTelecom billing | Telecom billing |
| CSSCustomer servicing | Customer servicing |
| PCCCustomer servicing | Customer servicing |
| CRSCustomer servicing | Customer servicing |
| CIS+Utility CIS | Utility CIS |
| CACSCollections | Collections |
| DPIServicing | Servicing |
Proprietary servicing platforms
Proprietary and custom systems.
Ten active dPlat integrations sit against proprietary or heavily customized client servicing platforms. These deployments take longer to scope than ERP-class integrations but run on the same architectural patterns: defined data exchange, mapped business rules, scheduled reconciliation, and bidirectional status updates.
Client systems in this category include proprietary servicing platforms operated by Fortune 100 financial institutions, large investor-grade utilities, education-services networks, and consumer-products manufacturers.
| Platform | Category |
|---|---|
| Proprietary servicing platformsCustom | Custom |
Recovery and workflow
Recovery and workflow platforms.
Operational workflow and recovery management integrations. The dPlat-to-dPlat pattern is notable: a client running dPlat at their corporate placement layer with a recovery vendor also running dPlat at their operational layer, both instances exchanging placement, status, and reconciliation data.
| Platform | Category |
|---|---|
| PegaWorkflow/BPM | Workflow/BPM |
| dPlat-to-dPlatRecovery | Recovery |
How dPlat integrates
Integration patterns.
dPlat supports the integration approaches enterprise IT teams already use. The choice is yours; the platform doesn't dictate it.
- API integrations for real-time data exchange
- SFTP for scheduled, secured file movement
- Direct file exchange where security policy requires it
- Custom field mapping per source system
- Bidirectional updates: dPlat ingests placement files and returns account status, payments, and reconciliation results
Why integration history matters
What 60+ integrations tells you about scope and risk.
Most recovery software vendors have integrated with a handful of source systems. dPlat has done it more than 60 times across 16 platform types. That's a credibility check enterprise buyers can verify directly during evaluation.
It also reduces real implementation risk. The integration patterns aren't being designed for the first time. That puts the timeline pressure on the parts of the project that always take real time: your team's availability, security review, and the source-system owner. Systems like SAP and Oracle CC&B have known data shapes that dPlat's existing mappings already account for. Exception handling, reconciliation breaks, and corner cases have surfaced and been solved against real production volumes.
The implementation runway shortens. The unknowns shrink. The team you put on the project actually finishes it.
At scale, in production
In production, at scale, since 2003.
100M+
Active accounts under management
Across client portfolios
$1B+
Transactional dollars managed annually
Processed through the platform on behalf of clients
20+ yrs
In continuous production
Building recovery software since 2003
See dPlat connected to your stack.
A 30-minute walkthrough against your portfolio, your source systems, and your vendor mix. The people running the demo are the people who configure the platform.
Bring your source systems and vendor list. We'll map the connections live.