Skip to content
AX Achyliaxyra

Home Delivery

A close you can rehearse before you trust it.

Implementation is a sequence with owners, not a single "go-live" date written on a kickoff slide. Most UK engagements of this kind run eight to sixteen weeks from a complete source inventory to a cutover the controller has already watched succeed on a prior month.

A workshop in a bright meeting room with an abstract flow on the screen

The path

  1. Week 1–2

    Discovery and source inventory

    We list every feed that touches the close: banks, ledger, subledgers, payroll bureau, billing, treasury workbook, and the unofficial spreadsheet that actually explains the difference. Each source gets an owner, a frequency, a sample, a failure mode, and whether personal data is present. The close calendar is pinned to the wall, including the day management accounts are promised and the day the VAT working is frozen.

  2. Week 2–5

    Mapping workshops

    Finance and the system owner sit in the same conversation. Account crosswalks, tax codes, cost centres, sign conventions, and FX policy are written down. Disagreements are recorded as decisions, not left as comments in a cell. Maker-checker starts here, before a line of production posting exists.

  3. Week 4–8

    Golden files and a sandbox

    We build a test pack from real shapes and, where the client permits, masked samples. Each golden file has an expected journal, an expected exception list, and a checksum. A deliberate duplicate upload is part of the pack. So is a file that is empty, a file with a broken tax code, and a file aimed at a closed period.

  4. One full close

    Parallel run

    The integration produces the same month the team is already closing by hand. Nothing from the parallel path is allowed to be the only copy in the statutory book. Differences are classified: timing, mapping, source error, or a genuine catch such as a duplicate supplier payment. The parallel run is finished when the controller signs the difference log, not when the software stops throwing errors.

  5. Cutover

    A dated switch, with a way back

    Cutover has a runbook: who freezes manual journals, which opening balances are agreed, how a reversal would be posted if the first live day is wrong, and who may declare the old path retired. The old path is not deleted on day one. It is retired after an agreed number of clean closes.

  6. After

    Hypercare and the operating handbook

    For the first two live closes we stay on the calendar. The handbook names the daily tie-out, the person who clears each exception class, the on-call route, and how a map change is requested. When hypercare ends, the client owns the operation. A support retainer is optional and written separately. It is not assumed.

What you keep

These artefacts are deliverables, not internal notes we take away at the end of the month.

  • Source inventory

    Systems, owners, frequencies, sample files, personal-data flags, and known failure modes.

  • Interface specifications

    Field lists, idempotency keys, transport, schedule, and what "empty" means for each feed.

  • Mapping workbook

    Version history, authors, reviewers, effective dates, and the reason for each change.

  • Golden-file pack

    Inputs, expected journals, expected exceptions, and the duplicate-upload case.

  • Cutover runbook

    Freeze points, opening balances, reversal path, and the named person who may retire the old route.

  • Operating handbook

    Daily and monthly controls, exception RACI, retention, and how to ask for a map change.

Morning light across a quiet finance floor

Who needs to be in the room

A successful integration is not a technology project that visits finance at the end. We ask for a controller or financial controller with authority over the close, a systems owner who can grant read access without a month of tickets, and someone who actually clears bank reconciliations. Payroll is included only when payroll journals are in scope, and then the payroll lead joins the mapping, not merely the kickoff.

Achyliaxyra brings an integration architect, a finance-systems analyst who can read a journal, and a controls reviewer who is not the same person who wrote the map. The studio is small on purpose. You will not be handed between a sales team and a distant delivery factory.

Book a discovery conversation

Rules we do not relax to hit a date

No production posting from an unversioned map

If the reviewer has not signed the version, the job posts nothing to the statutory book. Sandbox remains available.

No cutover without a parallel month

A demo on last year's sample is not a parallel run. The parallel month is a month the team has already, or is currently, closing.

No silent widening of scope

A new entity, a new bank, or a new ledger is a change. It is estimated and written down. It is not absorbed into the same week because the file "looked similar".