Start a conversation

Oracle APEX · Fusion integration · data migration

The finance systems specialists

Oracle APEX applications, Fusion Cloud integrations and data migration for NHS and public-sector finance teams — designed, built and reconciled by the people you actually speak to.

What we build Talk to us
FDX · document intake source: mailbox · illustrative data Posted
capture extract validate route
supplierMERIDIAN MEDICAL SUPPLIESmatched
po4500018221matched
net£1,284.50validated
vat£256.90confirmed
one register row no duplicates field-level audit trail

Services

What we do

Oracle APEX application development

Bespoke finance and back-office applications on Oracle APEX — workbenches, registers and workflow layers that pick up where your ERP's standard screens stop.

Oracle Fusion Cloud integration

REST APIs and interfaces into Fusion General Ledger, Payables, Receivables and Procurement — with OAuth, idempotency, retries and error recovery designed in.

Data migration, between any two systems

We profile, cleanse, extract, transform and load finance data between any legacy and target system — from ledger databases to departmental systems and spreadsheet estates — with reconciliation and validation at every step.

FDX

Finance Document Exchange

Invoices arrive however they arrive — mailbox, scan, supplier feed, spreadsheet. FDX captures each one, extracts and validates it against live ERP reference data, and routes it to your ledger with a single register row per invoice: no duplicates, a field-level audit trail, and assignment and chase workflows for the invoices that need a person. Currently in validation, with thousands of real documents processed.

Built and running

Working software, built for finance teams

Solutions from live programmes, ready to adapt — and offerings we can build for you.

GL journal import platform

Governed journal capture, validation and posting to Fusion General Ledger — behind hard test gates, with every batch balanced and traceable.

Budget statements

Budget against actuals and forecast outturn by cost centre, with per-user access control — the statement pack budget holders actually open.

Supplier, customer and catalogue onboarding

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

Payment and document interfaces

Controlled payment-file egress, invoice holds, scanned-document channels and departmental system feeds — the unglamorous interfaces that keep a finance office moving.

Approvals · Scheme of delegation

Invoice approvals on your scheme of delegation

Approvals routed by your delegation register, synced from Fusion reference data — first responder wins or serial chains, tracked from AP and procurement through to the final approver, then loaded into Fusion already approved. No BPM rules to manage.

Migration

From legacy finance systems, without losing the numbers

  1. 01

    Profile and cleanse

    We start in the legacy ledger as it really is: volumes and code structures profiled, legacy codes mapped to the new chart of accounts, suppliers and customers de-duplicated, balances proved against transactions — so quality issues surface before they cost you a cutover.

  2. 02

    Extract and transform

    ETL from ledger tables, departmental systems and spreadsheet estates into validated, target-shaped staging, with mappings agreed and documented as we go.

  3. 03

    Load, reconcile and validate

    Governed loads with error recovery, then reconciliation until source and target agree — to the penny.

  4. 04

    Cutover and knowledge transfer

    Rehearsed cutover, hypercare through your first closes, and handover written for the team who stay.

We work with NHS trusts, public-sector organisations — and finance teams in any organisation that needs this work done properly.

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