.svg)
Data Integration
Secure, structured, and designed to work with your firm’s existing financial systems.
Oddr integrates with your firm’s Financial Management System — whether that is Aderant or Elite 3E, on-premises or Cloud — using a proven, secure data flow that keeps your IT team in control. Data moves from your FMS systems into the Oddr Secure Cloud through encrypted channels and standardized REST APIs, with validation, monitoring, and error handling built into every step.
.png)
How Data Flows into Oddr
Data flows into the Oddr platform through a unidirectional pipeline — meaning data only moves from your source systems to Oddr, not the other way around. This design minimizes risk and simplifies security review.
The integration uses a firm-managed middleware tool (such as Intapp Integration Builder (IB) or Intapp Integration Service (IIS)) to extract data from source systems, transform it to meet the Oddr platform’s requirements, and push it securely to the Oddr Cloud via REST APIs over HTTPS.
Your firm’s IT team manages the integration tool and the credentials it uses, giving you full control over what data is extracted and when.
Source Systems
Risk assessments are performed annually and whenever significant changes in security posture occur. Risks are identified, evaluated for likelihood and impact, and treated with appropriate controls. A risk register and treatment plan are maintained and tracked to completion.
PDF invoice and statement files are picked from relevant network file shares as part of the integration process.
Oddr replaces legacy collections tools as part of its platform offering. A one-time data migration extracts relevant historical data from systems such as ARCS, Star Collect, Elite 3E Collections, or Aderant Collections.
Supplementary data such as eBilling invoice status can be pulled from third-party eBilling platforms like EBillingHub or BillBlast when needed.
Integration Modes
Oddr supports three integration modes to keep your data current:
.svg){kind=icon}
Extracts and loads all historical data from the FMS and legacy collections software into Oddr. The historical scope is determined collaboratively with your firm during implementation.
Gathers all changes made throughout the day and loads them into Oddr as a daily delta, ensuring the platform reflects the latest state of your financial data by the following morning.
.svg){kind=icon}
Operates on database triggers within your FMS. Whenever relevant data is created or updated, the integration tool automatically extracts and loads it into Oddr — providing near-real-time accuracy for time-sensitive operations.
Security of the Data Pipeline
Every step of the data pipeline is secured:
All data transfer between the firm’s network and the Oddr Cloud is encrypted using TLS.
Authentication credentials used by the integration tool are stored securely within the firm’s own infrastructure.
The Oddr REST APIs require authentication for every request, ensuring only authorized integration processes can deliver data.
Data transfer is strictly unidirectional — Oddr does not reach back into the firm’s network or source systems.
Validation & Error Handling
Oddr applies multiple layers of data validation to ensure only properly formatted, business-rule-compliant data is loaded into the platform:
Client, matter, and user records are validated against specified business rules.
Invoice documents are loaded only within the stipulated time period or where a balance remains pending.
Notes and attachments are loaded based on agreed timeframes.
Email addresses and phone numbers are verified for correct format before loading.
Non-data-related errors in the Daily Sync and Real-Time Sync are logged to an internal error logging database within the firm’s on-premise environment. A regular polling process picks up these errors and reports them to Oddr for resolution.
Monitoring & Alerting
The integration pipeline includes monitoring at every stage:
Alerts are configured within the integration tool to notify both the Oddr implementation team and the firm’s IT team via email if a rule encounters an error, fails for technical reasons, or runs longer than expected.
All actions from the integration processes are logged to a logging folder on the firm’s internal file share for debugging and audit purposes.
Logs are maintained as text files and are accessible to the firm’s IT team at all times.