Start a conversation

Oracle APEX · Fusion integrations · REST APIs

Clean month-ends are an engineering outcome.

We build Oracle APEX applications and REST integrations alongside Oracle Fusion Cloud ERP — and carry finance teams through the migration that gets them there.

See what we build Talk to us
era_gl · journal import period 03 · illustrative data Posted
5110-2210Agency staffing — June128,400.00
5230-1000Drugs and pharmacy supply96,213.07
7010-3300Estates planned maintenance188,234.25
2100-0000Accruals control(412,847.32)
Debits £412,847.32 Credits £412,847.32 Balanced

What we do

Three disciplines, one team

APEX engineering

Bespoke workbenches and extensions built on Oracle APEX, embedded where Fusion's standard screens stop. Fast to ship, governed properly.

Integrations and REST APIs

Fusion REST and FBDI orchestration with OAuth, idempotency, retries and error recovery designed in — not bolted on after the first failure.

ERP migration and data

Legacy ERP to Fusion: profiling, extraction, transformation and reconciled loads, with consultancy through cutover and beyond.

Solutions

Working software, not slideware

Solutions from live programmes, ready to adapt — they should give you an idea of what we can build for you.

Documents · AP

FDX mailbox integration

Financial documents arrive by mailbox, are parsed, validated and posted into Fusion automatically — with every step auditable.

APEX · Workflow

Invoice approval workbench

Accounts payable and receivable capture, validation and approval routing in one APEX workbench on top of Fusion.

General ledger

GL journal import platform

Governed journal capture, validation and posting to Fusion general ledger, with hard test gates and a full audit trail.

Procurement · AR

Supplier and catalogue onboarding

Bulk capture and load pipelines for suppliers, customers and catalogues — including NHS catalogue formats.

Platform capability

ERP migration

From legacy ERP to Fusion, without losing the numbers

  1. 01

    Assess and profile

    Understand the legacy estate first: data quality, volumes, mappings and the risks worth respecting.

  2. 02

    Extract and transform

    ETL from SQL Server, Access, Excel and legacy ERP databases into validated, Fusion-shaped staging.

  3. 03

    Load and reconcile

    FBDI and REST loads with error recovery, then reconciliation until the numbers agree — to the penny.

  4. 04

    Run and hand over

    Hypercare through the first closes, then documentation and handover written for the team who stay.

01

Engineering over configuration

Version control, code review and repeatable builds — the disciplines of software delivery applied to finance systems.

02

Test gates before go-lives

Nothing ships on optimism. End-to-end suites must pass green before a phase moves, and the results are on the record.

03

Documentation that survives handover

Every build leaves behind runbooks and design notes written for the team who inherit the system, not the team who built it.

Start a conversation

Tell us about your Fusion programme, your APEX idea or the legacy system you need to leave behind.

Email us