Cash and banks
CAMT.053, MT940, and the CSV exports your banks already issue. Where a client has an existing Open Banking provider, we take the feed they already trust. We are not an account information service provider.
Plymouth studio · United Kingdom
Achyliaxyra integrates the financial data UK organisations already hold. Bank statements, general ledgers, subledgers, payroll journals, and treasury positions are joined into a controlled posting model, with a trail from the source document to the journal line.
Working sessions run from the studio at 9 Highfield Cl, Plymouth PL3 6HW, UK, and on the client's own systems.
14 days
Typical discovery. We inventory sources, owners, file shapes, and the close calendar before any mapping is treated as final.
GBP base
Multi-currency events keep transaction amount, rate, rate date, and base amount. Replay does not invent a second translation.
UK tenancy
Processing sits in the client's UK cloud tenancy or a network they control. We do not require a standing copy of the production ledger.
Named exceptions
Unmatched cash, missing tax codes, closed periods, and duplicate payment references land in a queue a person can clear.
01 — What we join
CAMT.053, MT940, and the CSV exports your banks already issue. Where a client has an existing Open Banking provider, we take the feed they already trust. We are not an account information service provider.
Sales, purchase, and stock subledgers tied back to control accounts. Journals aimed at the system of record the finance team already closes: commonly Xero, Sage, Business Central, NetSuite, or SAP Business One.
A hashed payroll journal, cost-centre splits, and a control total that must match the payroll bureau file before anything is allowed to post. People data stays in the payroll system.
Value date against booking date, rate source, and revaluation lines that can be replayed without doubling. Intercompany balances are named, not plugged.
02 — How a figure moves
The source file or API payload is stored as it arrived, with a checksum. We do not "tidy" a statement before anyone has seen the original.
Entity, book, account, cost centre, tax code, currency, amounts, dates, document id, and an idempotency key. The same shape, whichever system spoke first.
Chart-of-accounts crosswalks are versioned. A change is maker-checker. Yesterday's posting can still be explained with yesterday's map.
Accepted lines post. Held lines wait in an exception queue with a reason a controller recognises: closed period, missing VAT code, unbalanced intercompany, duplicate reference.
03 — Three practices
The canonical event, source patterns, mapping layers, currencies, and the idempotency rules that make a replay safe.
Read the model
Discovery, golden files, a parallel run against a real close, cutover, and hypercare. The artefacts stay with you.
See the path
Who can change a map, where data sits, how long it is kept, and how UK GDPR applies to an integration engagement.
Review the controls04 — What we will not pretend
Achyliaxyra is a specialist studio. We design and implement the pipes and the controls. We do not prepare statutory accounts, file VAT returns, give investment advice, or move client money. We are not authorised by the Financial Conduct Authority.
If a number needs an accounting judgement, that judgement stays with your finance lead or your adviser. Our job is to make the path of the number visible, repeatable, and hard to double-post.
About the studio
The useful first conversation is specific. Which entities, which banks, which ledger, where the month currently slips, and who is allowed to change a mapping. Write to [email protected] or call +44 7390556970. The studio is at 9 Highfield Cl, Plymouth PL3 6HW, UK.