Connecting Oracle Fusion to Housing, CRM and Banking Systems Through Your Integration Hub
A new finance system is only as good as its connections. This is how we link Oracle Fusion to the housing management system, CRM, repairs, payroll and banks through the integration hub you already run, so information moves once and every run is monitored.
Housing providers are increasingly building an integration hub before, or alongside, their finance replacement.
The aim is sound: one place where data moves between systems, a single customer view in CRM, no duplicate keying. A finance replacement should strengthen that strategy rather than bypass it with a new set of point-to-point links.
Think of Oracle as the finance core and your hub as the connector between it and everything else.
Who keeps what
Good integration starts with a clear line between systems:
Oracle Fusion holds
Accounting, dimensions, budgets, payables, receivables, fixed assets, cash and financial reporting.
Your systems keep
Resident-level rent, arrears and statements, customer cases and contact data, repairs and works detail, payroll and HR records.
With that line drawn, each interface carries only what the other side needs, usually summarised financial postings into the ledger and reference data or status back out.
The interfaces a housing provider typically needs
- Housing management system (for example Aareon QL): rent, arrears and adjustment postings into the ledger.
- CRM (for example Salesforce): customer account data and arrears or escalation information, through the hub.
- Repairs and asset systems: job costs, works orders and capitalisation of components.
- Payroll and HR: payroll journals and expenses into the ledger.
- Banks: payment files including BACS, bank statements and daily reconciliation.
- Document management: invoice images and audit evidence linked to transactions.
- Data warehouse and BI (for example SQL Server and Power BI): scheduled finance extracts for organisation-wide reporting.
Oracle Fusion exposes REST APIs and supported bulk file interfaces for all of these. They can be orchestrated through an existing hub such as MuleSoft, or through Oracle integration services where that is agreed. No new compulsory middleware is needed.
Built to be run, not just built
An interface that works on go-live day but fails silently in month three is worse than no interface at all. Every integration we deliver has:
- A documented data contract: fields, formats, frequency, direction and owner.
- Logging and alerts on every run, so failures are seen the same day.
- Error queues with retry and replay, so a rejected batch can be fixed and re-sent without manual rekeying.
- Reconciliation back to the source system, so finance can prove the ledger matches.
When a source system is later replaced, the interface is designed so it can be re-pointed rather than rebuilt.
Working with your platform team
Where a housing provider already runs a hub, its platform team owns the platform. The split of work is agreed in discovery: who administers the platform, who builds which flows, and how runtime and deployment access work. Whatever that split, delivery of the integrations remains our obligation.
The housing management, CRM and banking suppliers each need to provide specifications, access and test slots. Those dates go on the programme plan as early starts in the first weeks, because they are the most common source of delay in any finance implementation.
Keep CRM off the critical path
CRM integration often belongs to a wider customer programme with its own timetable. We run it as its own workstream so that finance go-live does not wait for it. The finance interfaces that matter on day one, housing management postings and banking, are prioritised; the CRM link follows when the wider programme is ready.
Banking tested end to end
Payment runs are where integration failures hurt most. Bank connections and BACS files are tested end to end with the bank before go-live, including the certification path the bank requires. Test stubs keep system testing moving if a partner is not ready, but a stub never replaces live acceptance.
Our article on cutover and hypercare for housing finance covers how payment runs and bank reconciliation are watched in the first weeks after go-live.