Skip to content
AX Achyliaxyra

Home Architecture

A financial event, stated once, posted once.

Architecture at Achyliaxyra is not a diagram that lives in a slide. It is the contract between a source system and a journal: which fields exist, which are allowed to change, and what happens when the same file arrives again on a Tuesday.

Professionals standing at a glass wall of geometric integration diagrams

The canonical financial event

Every source is translated into the same record before anyone talks about posting. The list below is the working set we start from. A client may add dimensions. We do not drop fields to make a demo look tidy.

Field What it holds
Entity code The UK company, branch, or clinic the entry belongs to. Group reporting never guesses this from a filename.
Book Statutory, management, or tax. A management elimination does not silently land in the statutory book.
Account The target chart-of-accounts code after the versioned crosswalk, not the source system's private code.
Cost centre Department, vessel, contract, clinic, or other dimension the close actually uses.
Tax code The VAT or other tax treatment the source asserts. Missing codes are held, not defaulted to a convenient rate.
Currency The transaction currency as the source stated it.
Amount Signed amount in transaction currency. Sign convention is documented per source and tested with golden files.
Base currency Usually GBP for a UK statutory book. Stated explicitly so a EUR entity is not assumed.
Base amount Amount translated at the agreed rate. The translation is stored, not recomputed differently on each replay.
Rate and rate type The numeric rate, the rate date, and whether it is spot, month-average, or a contract rate the treasury team supplied.
Value date The economic date: when the cash moved or the invoice fell due, according to the source.
Booking date The date the source recorded the item. Late-arriving lines stay visible as late, rather than being backdated in silence.
Document id Invoice, payment, payroll run, or statement entry id in the originating system.
Idempotency key A stable key built from fields that do not change when a file is exported again. A replay finds the original posting instead of creating another.
Source system The platform and the interface name, so lineage does not stop at "the bank file".
Posting status Accepted, held, rejected, or reversed, with the reason code and the person or rule that set it.
Narrative The text destined for the journal line, trimmed to what the target ledger will accept, with the original kept alongside.

How sources actually arrive

We integrate the channel the organisation already has a right to use. Achyliaxyra does not open bank accounts, does not enrol as an AIS provider, and does not ask staff to email spreadsheets of live payroll to a personal inbox.

  • API. Ledger, billing, or an existing Open Banking provider the client has contracted. Calls are idempotent where the vendor allows it, and every response used for posting is retained with its timestamp.
  • File drop. SFTP or a client-controlled bucket. CAMT.053, MT940, bureau payroll journals, and the CSV a bank portal still insists on. Each file is checksummed before parse.
  • Database extract. A read-only query or a change feed, agreed with the system owner, with a watermark. We do not take write access to an operational database in order to "just fix" a mapping.
  • Controlled workbook. Some treasury positions still live in a workbook. We accept that, version the file, and refuse to post from an unnamed copy on a desktop.
Close view of neatly dressed fibre connections

Interfaces are named, owned, and monitored. A silent empty file is an incident, not a quiet month.

Mapping is a controlled document

A crosswalk from source account to target account is not a tab anyone may overwrite on the morning of the close. Each version has an author, a reviewer, an effective datetime, and a reason.

Postings record the map version they used. If a code is remapped in March, January can still be reproduced. Reversals point at the original idempotency key rather than a fresh invention.

Exceptions we refuse to swallow

  • CASHBank line with no cashbook match inside the agreed tolerance and date window.
  • DUPPayment reference already posted, including references that differ only by spaces or a leading zero where the bank is known to do that.
  • FXRate date outside policy, missing rate, or a base amount that does not tie to rate times amount within a stated penny tolerance.
  • PERTarget period closed. The line is held for a dated journal, not forced into the next open period without a person.
  • TAXVAT code absent or not in the allowed set for that entity.
  • ICIntercompany pair that does not balance across entities in the same run.
  • CTLSubledger total that does not equal the proposed control-account movement.
  • PAYPayroll journal hash or control total different from the bureau file.

Replay is a feature, not an accident

Banks reissue statements. APIs time out and get retried. A nervous operator uploads Thursday's file twice. The idempotency key is how the second arrival finds the first posting.

For a bank entry we typically compose the key from account identifier, statement id, entry reference, value date, currency, and signed amount. If a source cannot offer a stable reference, we say so in the interface specification and agree a narrower key with the controller, in writing, before go-live. We do not invent uniqueness with a fresh UUID on every parse.

What the parallel run proves
Evening treasury desk with abstract charts and harbour lights

Questions controllers ask first

Do you replace our ledger?

No. The ledger you close remains the system of record. We deliver journals, exceptions, and evidence into the way that ledger already accepts work: its API or the import format your team is willing to own.

Can you connect anything with a logo?

We connect systems the client is licensed to extract from, and targets that expose a documented posting path. A logo on this website would not make us a partner of that vendor, so we do not display borrowed marks.

Where do historic months go?

Opening position is agreed. We do not silently rebuild three years of journals unless that migration is in the statement of work, with a reconciliation to the signed accounts or management pack for each period in scope.

What if two entities share a bank account?

The cash line is captured once. Allocation rules, if any, are explicit and reviewed. Unallocated cash remains unallocated. It is not sprayed across entities to make a dashboard look finished.

If this is the shape of the problem you have, tell us which systems are in the room.