Home Controls
Lineage you can show, access you can name.
Financial data integration fails in two quiet ways: a number that cannot be traced, and a change that nobody remembers authorising. The control design is part of the integration, not a policy PDF added after go-live.
Regulatory position, stated plainly
Achyliaxyra provides professional services that design and implement financial data integration. We are not authorised or regulated by the Financial Conduct Authority. We do not accept deposits, issue electronic money, execute payments, arrange investments, or give regulated advice. We do not submit returns to HMRC on a client's behalf unless a separate written engagement says so, and even then the statutory responsibility remains with the client.
Where a client is itself regulated, our work is built to sit inside that client's control environment. We do not claim ISO 27001 certification or Cyber Essentials on this website. If you need suppliers to hold a named certification, say so at discovery and we will confirm the current position in writing before any data is shared.
Lineage
Every accepted journal line can be walked backwards: target document, canonical event, map version, source record, source file or API response, checksum, and the time it was captured. Held and rejected lines are kept with their reason codes. Reversals reference the original idempotency key.
Lineage is readable by a controller without asking an engineer to query a console. The operating handbook includes the exact screen or report. If the only explanation of a balance is "the pipeline did it", the design is not finished.
Access and segregation
- Production credentials live in the client's secret store. They are not pasted into chat, email, or a shared desktop note.
- The person who edits a mapping version is not the person who approves it for production.
- Read access to samples is named, time-bounded, and logged. Broad "everyone in the project" groups are not used for payroll or bank files.
- Achyliaxyra staff do not receive write access to the statutory ledger as a convenience. Posting runs as a service account the client owns.
- Leavers, both sides, are removed on the day the engagement owner confirms they have left the work.
Reconciliation controls we expect to see running
| Control | Cadence | What "pass" means |
|---|---|---|
| Bank to cashbook | Each business day the feed runs | Statement total equals posted cash plus named open exceptions. No balancing figure without an owner. |
| Subledger to control account | Each posting run | The movement proposed for the control account equals the subledger extract. A mismatch holds the batch. |
| Payroll journal | Each pay run in scope | Hash and control totals match the bureau file. Gross-to-net is not rebuilt by us from employee records. |
| Intercompany | Each group run | Pairs balance in the agreed currency. Residuals are listed by entity, not netted into a suspense account by default. |
| FX translation | Each multi-currency run | Base amount ties to the stored rate within the penny tolerance. Revaluations are their own events and can be reversed as a set. |
| Map changes | Whenever a version changes | Author and reviewer are different people. Effective time is in the future or explicitly backdated with a reason. |
| Replay | Tested before go-live and after material change | A second delivery of the same source creates no new journals and is visible in the run log. |
Where the data sits
The preferred pattern is simple: processing runs in the client's own UK tenancy, commonly in London or UK South regions of the cloud they already pay for, or on a network they control. Achyliaxyra does not require a permanent replica of the production ledger on studio laptops.
Samples used in design are minimised, masked where the test does not depend on the real value, and destroyed at the end of the retention period written in the statement of work. Live bank files and payroll files are not sent to personal email. The studio address, 9 Highfield Cl, Plymouth PL3 6HW, UK, is where we meet. It is not a data centre, and it is not a place to drop unmarked USB drives.
This website is a separate, public system. Enquiry details submitted through the contact page are sent by email to [email protected]. They are not mixed with client ledger data.
UK GDPR in the engagement
Much of a ledger is not personal data. Some of it is: supplier sole traders, employee cost allocations, beneficiary names on bank lines, and email addresses of the people who run the close. We agree the role before any transfer. In the usual pattern the client is the controller of finance data and Achyliaxyra is a processor under a data processing schedule. For enquiry emails about this website, Achyliaxyra is the controller. That split is written in the privacy policy and, for client data, in the processing terms of the statement of work.
We do not use client finance data to train public models, to build a pooled benchmark, or to demonstrate the studio to another prospect. References are anonymised and only published with permission, as on the engagement records page.
Retention, in outline
- Enquiry correspondence. Kept long enough to answer and to hold a record of what was proposed, then deleted on the schedule in the privacy policy unless a contract follows.
- Working samples. Kept for the engagement and the agreed defect window, then deleted from studio-held copies. The client's own tenancy follows the client's retention policy.
- Map versions and run logs. Kept for the period the client needs in order to explain a prior close. Seven years is a common request for UK statutory support. It is the client's setting, not a default we impose in their tenancy.
- Credentials. Not retained at the studio beyond the access window. When the window ends, access is revoked and the revocation is noted.