Skip to content
AX Achyliaxyra

Home Engagement records

Three records, with the names taken out.

These are anonymised accounts of completed UK engagements, published with permission. Trading names, people, and exact account numbers are withheld. Figures are from the engagement record, rounded so a reader cannot reconstruct a private close. They are not a promise that the next client will see the same movement.

A reconciliation review at a desk, with figures deliberately out of focus

Record 01

Coastal components group

South West England · manufacturing and stores · three UK entities

A single analyst working late with harbour lights outside

The group closed three entities on Sage 50, with stock movements coming from a bespoke system that pre-dated the finance team now running it. Four GBP current accounts were reconciled in workbooks that only two people could update. The published management pack regularly waited until the twelfth working day, and the wait was mostly explanation, not bookkeeping.

Discovery found that supplier payments were exported from the bank twice in some months, once from the portal CSV and once from a saved copy with a slightly different filename. Nothing in the workbook treated those as the same payment. In the first parallel month the idempotency rule flagged 37 candidate duplicates. Eleven were true duplicates that had been posted, or were about to be. The rest were legitimate split remittances that shared a fragment of a reference, which is why the key included amount and value date rather than reference alone.

The stock system remained the operational record. A nightly read-only extract produced a movement journal only when the control total matched the stock valuation change within a stated tolerance. When it did not, the batch held. The team stopped "plugging stock" on the morning of the pack.

By the third live close, the management pack left on the sixth working day. The two-person workbook was retired after that close, not before. The group still uses Sage 50. Achyliaxyra did not replace it.

Entities
3 UK companies
Close
12 working days to 6
True duplicate payments caught in parallel
11 of 37 candidates

Record 02

Clinic partnership

Community healthcare · nine Xero organisations · monthly management charges

An open-plan office in soft morning light

Each clinic kept its own Xero organisation, which was the right operational choice and a poor group one. A single workbook pulled trial balances through a chain of links. Management charges between clinics were typed into both sides when someone remembered. Most months, an unexplained plug in the tens of thousands of pounds was labelled "timing" and carried forward.

The canonical event made the management charge a paired posting: origin clinic, destination clinic, amount, narrative, and the agreement reference. A group run refused to finish while any pair was open. Intercompany was no longer a formula at the bottom of a tab. It was a list of named residuals.

By month three of live running, the unexplained plug was gone. What remained was a residual list under two thousand pounds, each line owned by a clinic manager, most of them genuine timing differences on card settlements. The workbook still exists, but it is a presentation of the group file, not the place the numbers are born.

Personal data in patient systems was out of scope and stayed out. The integration saw clinic-level journals and settlement totals, not clinical records.

Books
9 Xero organisations
What changed
Plug replaced by a residual list
Residual by month three
Under £2,000, named

Record 03

Freight forwarder

UK books · GBP, EUR, and USD settlements · job-level operations system

Ordered network connections suggesting a controlled interface

The forwarder posted job revenue from an operations system into NetSuite and took bank statements as CAMT.053 from two banks. Treasury revalued open foreign-currency positions at month end. When a statement file was fetched again after a timeout, the integration they had inherited created a second set of cash lines and a second set of FX translations. The cashbook tie-out then consumed a day that should have been spent on jobs.

The idempotency key for a bank entry was set to bank account, statement id, entry reference, value date, currency, and signed amount. FX revaluation was modelled as its own event, keyed by entity, account, currency, rate date, and rate type, so a repeated valuation replaced evidence rather than stacking journals. A deliberate replay of a 2,400-line statement, run in the parallel month and again after cutover, created no new journals. The run log showed the replay and the original posting ids.

Job-level operational detail stayed in the operations system. Finance received the journal and a tie to the job control total. We did not rebuild a second operations database in order to explain revenue.

Currencies
GBP, EUR, USD
Replay test
2,400 lines, 0 new journals
Ledger
NetSuite, unchanged as system of record

What we will not publish

We do not name clients who have not agreed, we do not show statement extracts, and we do not imply that a software vendor endorsed the work. If you are evaluating Achyliaxyra, we can arrange a conversation with a referee where permission already exists. That conversation is private and is not a performance of these pages.

If your shape is different

A single-entity professional firm, a charity with fund codes, or a group mid-migration between ledgers is still the same discipline: inventory, map, golden file, parallel month, cutover. The calendar changes. The refusal to double-post does not.

Describe your close