ICE Mortgage Technology loan data into Power BI, done for you
Encompass by ICE Mortgage Technology has no Power BI connector, so this is a plumbing job before it is a reporting job: the extraction route your licence actually covers, the field IDs mapped, the milestone timestamps turned into cycle time, and a refresh cadence that survives a busy lock desk.
Representative dashboard — sample data
Before anything else
Encompass is the mortgage loan origination system from ICE Mortgage Technology, sold as Ellie Mae Encompass until Intercontinental Exchange acquired Ellie Mae. It is where applications are taken, services ordered, conditions cleared, locks recorded and loans funded — and because encompass is also an ordinary English word, half the advice a lender finds when searching for reporting help is about something else entirely. This page is about the LOS.
The reason an Encompass Power BI dashboard is a project rather than an afternoon is that none of the interesting data is one click away. Encompass stores a loan as several thousand numbered fields, only a subset of which an administrator has published to the reporting database; milestones and loan-team members are one-to-many against a loan rather than columns on it; and how you get any of it out depends on which data-access product your contract includes. Get those three things right and the visuals take a fraction of the time.
What we build from Encompass
Buy a block of prepaid Flex hours and, if you're unhappy within the first 4 hours, we refund you in full — no questions asked. Hours are deducted only for work you've reviewed and approved, there's no project minimum, and your banked hours never expire.
What the build covers
Every one of them is made before a chart exists, and every one is where a lender's own attempt usually stalls.
Data Connect, Developer Connect, the reporting database or a scheduled export — which of these you have depends on your ICE agreement, not on what a vendor page implies. We establish it in scoping, before anything is designed around it.
Every metric traces back to specific Encompass field IDs, including the custom fields your admin team added. We document that mapping so a number on a page can always be defended back to a field on a loan.
Milestone completion dates are rows against a loan, not columns. Pivoted into a proper fact table they become stage-by-stage turn times instead of a single application-to-close number nobody can act on.
Funded units this month divided by applications this month is not pull-through. We follow an application cohort forward to its outcome, which is the only version of the number a secondary desk will accept.
Row-level security scoped to originator, branch, region or channel from the loan team assignments — so a loan officer opens the report and sees their own pipeline, and onboarding one is a data change, not a rebuild.
A hosted warehouse, an API pull and an overnight export do not support the same cadence. We match the schedule to what the source can actually deliver, then fix refresh failures out of your banked hours.
Through whichever data-access route your lender licenses, because there is no direct connector. Encompass does not appear on Microsoft's published list of Power Query and Power BI connectors (opens in new tab), so nobody is clicking Get Data and choosing Encompass. What exists instead is a set of documented paths, and which of them is open to you is a contract question before it is a technical one.
That contractual framing matters in lending more than in most sectors, because analytics-grade data access is frequently a licensed product rather than an included feature. We confirm the route, the licensing and any ICE-side charge in the scope estimate before a query is written — the same discipline applied on our Power BI dashboard for mortgage lenders page, which covers the wider lender KPI set once the data is flowing.
| Route | What it is | What it suits — and what to check |
|---|---|---|
| Data Connect — hosted | ICE's analytics product in its hosted form: your loan data lands in a dedicated Snowflake instance you query directly | The cleanest path for a lender with no warehouse of its own — Power BI has a first-party Snowflake connector (opens in new tab) supporting import and DirectQuery. Confirm entitlement, credentials and how much history is included |
| Data Connect — direct write | The same product writing loan data straight into your own reporting warehouse instead of a hosted one | The right choice when the lender already runs a warehouse and wants Encompass beside the GL and payroll. Confirm which schema ICE writes into and who owns the target |
| Developer Connect REST APIs | ICE's API platform (opens in new tab) over OAuth 2.0, covering loans, pipeline queries, schemas and loan-team resources | Built for loan-level and transactional integration rather than bulk analytics. Excellent for targeted feeds; confirm client credentials, rate limits and who administers the API user |
| Encompass reporting database | The relational database Encompass populates with the fields an administrator has explicitly added, plus its external replication into a lender-owned SQL Server | The long-standing route for lenders already writing their own reports. Confirm which fields are actually published, and who can run the Admin Tools update |
| Scheduled exports into SQL Server | Encompass report output landed on a schedule into a database or file share you control | Common, and workable as a bridge while a durable route is licensed. Watch for silent truncation and for history that only starts the day the export did |
| A warehouse you already own | Encompass data already landed into your SQL Server, Fabric or Snowflake environment by an existing pipeline | Model from that copy — it refreshes faster and joins far more easily to the general ledger, payroll and the pricing engine. See our SQL Server Power BI dashboard service |
ICE ships quick-start templates for Power BI, Tableau and Qlik alongside Data Connect, and they are a reasonable way to see the shape of the data. They are not a substitute for a model built around how your shop defines a unit, a cohort and a channel — which is where every argument about the numbers actually happens.
Because the reporting database holds only what an administrator published to it. Encompass identifies loan data by numbered field IDs, and a field can be populated on every loan in the shop yet remain invisible downstream until someone opens Admin Tools, adds it from the relevant tab, updates the database and repopulates it. This is the single most common reason a promised metric stalls.
It is worth knowing before you scope anything, because the fix is an internal change on your side rather than a development task on ours, and it can take a maintenance window. The same is true of the custom fields nearly every lender has created — a channel flag, a referral source, a committed-investor code — which carry no meaning outside your shop and must be mapped by someone who knows why they were added.
| Encompass structure | How it behaves | Role in the model |
|---|---|---|
| Loan-level fields | Numbered field IDs on the loan — amount, rate, product, purpose, occupancy, action taken | The loan fact table plus the product, purpose and channel dimensions hung off it |
| Custom fields | Lender-defined fields carrying local meaning that no outside documentation explains | Mapped explicitly in scoping, then modelled as attributes or flags with the definition written down |
| Milestones | Multiple rows per loan — one per milestone, with completion date and the associate who finished it | A milestone fact that yields stage-level turn times, not one flattened cycle-time column |
| Loan team members | Multiple rows per loan for originator, processor, underwriter, closer and their assignment history | The originator and staff dimensions, and the key row-level security filters on |
| Conditions | Prior-to-approval, prior-to-doc and post-closing conditions, each with its own status history | A condition fact behind aging, clearing rates and where files genuinely sit |
| Locks and lock requests | Lock, extension and re-lock records that change the economics of a loan mid-flight | Lock fact for locked-pipeline exposure and expiration windows |
| Borrower pairs | One or more borrower pairs per loan file, only one of which is usually the reporting subject | Resolved to a single reporting grain so a two-pair file cannot double-count |
| Branch and channel structure | The organizational hierarchy production is credited and costed against | The dimension every total has to reconcile to before finance will trust it |
All of it is conformed into a star schema before a measure is written, following the model design Microsoft recommends for star schemas in Power BI (opens in new tab). The craft underneath is the same one described on our Power BI data modeling and DAX page.
By treating each milestone completion as a timestamped event and measuring the gaps between them. Encompass ships thirteen predefined milestones out of the box, and administrators rename them, add their own, and apply different milestone templates by loan type or channel — so the first job is agreeing which of your milestones marks the start and end of each segment you care about.
| Milestone group | Default milestones | What the segment tells you |
|---|---|---|
| Intake | Started, Qualification | How long a lead sits before it becomes a real application — and the cohort every pull-through measure counts from |
| Processing | Processing, Submittal | Where the file waits on documents and where processor capacity is genuinely constrained |
| Underwriting | Cond. Approval, Resubmittal, Approval | Underwriting turn time and the resubmittal loop — the segment most lenders under-measure |
| Closing | Doc Preparation, Docs Signing, Funding | Whether the closing calendar is realistic and how often locks are pressured by doc timing |
| Post-close | Post Closing, Shipping, Completion | Delivery and purchase timing, and how long capital stays tied up after funding |
With that in place, the measures a production meeting argues about become explicit DAX rather than a spreadsheet convention: locked and in-process pipeline as at any selected date; pull-through following an application cohort to its outcome instead of dividing two unrelated months; fallout and withdrawal split by reason where the reason is captured; turn time by segment, by branch and by underwriter; and loan officer production by units, volume and pull-through rather than volume alone. Each definition is documented, because the point of the model is that two reports cannot quietly disagree.
The wider lender metric set — cost to originate, net marketing income, branch profitability and the general-ledger reconciliation behind them — belongs on our mortgage lender dashboard page, and finance-side budget and forecast work on Power BI dashboards for finance teams. This page is deliberately the technical half: getting Encompass data out, mapped and modelled correctly.
As often as the route can genuinely support, which is usually less often than a sales manager would like. A lock desk wants intraday numbers; an overnight export cannot supply them at any price. Matching the promise to the plumbing at scoping time prevents the most common failure mode, which is a dashboard everyone stops trusting because it is quietly a day behind.
| Route | Practical cadence | What it needs |
|---|---|---|
| Hosted Snowflake instance | Several times a day, or DirectQuery for a live pipeline page | Cloud-to-cloud, so no gateway — but DirectQuery needs the model tuned for it |
| Direct write to your warehouse | Scheduled to follow ICE's write, typically several times a day | A gateway only if the target is on-premises |
| Developer Connect APIs | Incremental pulls of changed loans, hourly to daily depending on volume | Token handling, paging and a landing store — not a direct query from a report |
| Reporting database on SQL Server | Nightly, with intraday runs where the server can take it | An on-premises data gateway (opens in new tab), plus a window that avoids the nightly batch |
| Scheduled export | Whatever the export runs at, and no faster | Failure alerting, because a missing file is silent otherwise |
Lenders with several years of loan history get incremental refresh (opens in new tab) configured, so each run processes a recent window instead of reloading every loan the shop has ever closed. Where a gateway is involved, our guide to Power BI gateway setup covers the configuration, and we monitor and fix refresh failures out of your banked hours rather than leaving them with whoever in operations happened to build the report.
Whoever your loan team assignments say should. Visibility is enforced in the model with row-level security (opens in new tab), driven from a mapping table of Power BI users to originator IDs, branches, regions and channels — so a loan officer sees their pipeline, a branch manager sees the branch, and the executive team sees everything, all from one report.
That matters more here than in most verticals, because loan-level files carry borrower data and originator compensation detail that should not travel by email attachment. Our guide to setting up row-level security covers the configuration in detail. We test the roles against real accounts before go-live and document who can see what — a useful artifact the first time an auditor asks how originator-level data is controlled.
Prepaid Flex hours that never expire: Starter is 20 hours at $125/hr ($2,500), Growth is 40 hours at $115/hr ($4,600), and Power is 80 hours at $100/hr ($8,000), with senior hourly work from $100/hour on the largest block. A first build covering pipeline, milestone turn times, pull-through and loan officer production from a single Encompass instance usually fits inside a Starter block. Adding the general ledger for branch profitability, commission detail, or a second LOS inherited with a branch acquisition generally moves a lender to Growth, because agreeing the rules takes discussion as well as development.
Most tasks ship within 3–5 business days of scope approval. You get a written scope and hours estimate before anything starts, and hours are deducted only for work you approve. Our guide to Power BI dashboard development cost covers what moves the number, custom dashboard development explains how a build is run end to end, and how prepaid Flex hours work sets out the model in full.
Independent mortgage banks, bank lending divisions and credit union mortgage desks running Encompass with enough history to trend and no in-house data engineer — typically the point where someone exports an Encompass pipeline report to Excel every Monday and nobody entirely trusts the result. Production managers, secondary marketing leads, COOs and CFOs are the people who usually get in touch, often after a leadership meeting where two reports disagreed about the same month.
Shops originating anywhere from a few hundred to several thousand loans a year are the sweet spot: large enough that branch and originator reporting is a real monthly job, small enough that a dedicated analyst is hard to justify in a soft quarter. Credit unions running a mortgage desk alongside consumer lending usually want this page for the LOS plumbing and Power BI dashboards for credit unions for member, share and branch reporting. We are an independent US-based Power BI consultancy with no ICE Mortgage Technology partnership to claim — we build on the documented access your lender already licenses, and everything we produce is published into your own Power BI workspace. Contact is form-only — send your request and we'll reply with a scope estimate.
business days, typical
hours, never expire
own everything
A first Encompass build usually fits inside one Flex block, and hours deduct only for work you approve. See Flex pricing →
How it works
We establish which route your ICE agreement actually covers, audit which fields are published to the reporting database, work out which custom fields and milestone names your shop has made load-bearing, agree the pull-through and turn-time definitions with your leadership, and reply with a written scope and hours estimate before any work begins.
A senior US-based engineer pulls loans, borrowers, milestones, conditions, locks and loan team members, documents the field-ID mapping behind every metric, conforms it all into a star schema with a date table and the branch and channel hierarchy, then writes the DAX — validating totals against the Encompass reports your team already trusts.
Published to your workspace with a refresh cadence the source can actually sustain, row-level security so each originator and branch sees only its slice, and documentation you keep. We maintain it from your banked hours.
Representative perspective
Once turn time was split by milestone instead of measured application to close, it was obvious the delay was the resubmittal loop and not processing, which is where we had been adding people.Production manager, independent mortgage bank
Representative perspective
Two of the fields our whole channel analysis depended on had never been added to the reporting database. Finding that out in week one rather than week six was worth the engagement on its own.COO, bank lending division
Tell us which ICE data access your shop has, how you define pull-through, and the views your production and secondary teams actually ask for. We'll confirm the route, scope the task, and tell you the hours before anything starts — no project minimums, no obligation.
FAQ
Encompass by ICE Mortgage Technology — the mortgage loan origination system sold as Ellie Mae Encompass before ICE acquired Ellie Mae. It is the system your team takes applications, orders services, clears conditions and funds loans in. If you are searching for a dashboard that covers something else the word encompass describes, this is not that page.
No. Encompass does not appear in Microsoft's published list of Power Query and Power BI connectors, so there is no Get Data option for it. Power BI reads whatever destination your Encompass data lands in — a Snowflake instance, your own SQL Server or warehouse, or tables loaded from the Developer Connect APIs.
Data Connect is the bulk analytics route: ICE either writes your loan data into your own reporting warehouse or hosts it in a dedicated Snowflake instance you query. Developer Connect is the REST API platform, authenticated with OAuth 2.0, built for loan-level and pipeline calls. Reporting wants the first; transactional integrations want the second.
Because the Encompass reporting database holds only the fields an administrator has added to it. A field can be populated on the loan and still be absent downstream until someone opens Admin Tools, adds it, and repopulates the database. We audit that field set against the metrics you asked for before quoting any build.
Yes. Row-level security maps each Power BI user to an originator ID, branch, region or channel taken from the loan team assignments, and every visual filters to that scope automatically. Managers see their branch and executives see the consolidated book from the same report, so nobody maintains a separate file per branch.
For the lender-wide metric set rather than the source-system plumbing, Power BI dashboards for mortgage lenders is the page to read next — it owns cost to originate, net marketing income and branch profitability. Credit unions running a mortgage desk alongside member and share reporting should see Power BI dashboards for credit unions, and finance teams focused on budget versus actual and the board pack should start with Power BI dashboards for finance teams. If your Encompass data already lands in a database you control, SQL Server dashboards covers building straight on it. The supporting mechanics have their own guides: gateway setup for on-premises sources, row-level security setup for originator and branch visibility, and dashboard development cost for what moves a quote. Every task is scoped before work begins from your prepaid block of senior-led hours — no project minimums, no change-order surprises, and hours are deducted only for work you approve.
Book a free demo
Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.
The fastest way to reach us is the form — tell us the task and we'll reply within one business day.