Skip to content

UK finance teams

+44 7457 162137
Acinarypath

Data controls

A figure should have a path, an owner, and a last refresh.

Business intelligence fails in finance when the chart is trusted more than the ledger. Acinarypath treats lineage, reconciliation, and access as part of the product, not as a document written after go-live.

A controllership desk with out-of-focus screens, cream folders, glasses and a steel ruler

The source map comes first.

Before a visual design, we list every number the pack will show and the system it comes from. Typical sources in a UK finance team include the ERP or accounting ledger, payroll, billing, stock, bank feeds, and the planning workbooks that still hold assumptions. Each source gets an owner inside the client, a refresh pattern, and a note on what it is bad at.

Lineage

From the report line to the transformation to the source field. Written so a new FD can read it without us in the room. Abbreviations are expanded the first time.

Reconciliation

Bank, debtors, creditors, stock, and payroll-to-finance, where those balances matter to the pack. Open items have an age and a name, not a green tick with no working.

Change control

A definition changes only with a recorded reason, a date, and the person who accepted it. Prior periods are restated only when finance decides they should be, and the pack says so.

Access that matches the close.

Three roles cover most finance reporting. We do not invent a fourth because a software screen offered one.

Preparer

Refreshes sources, clears exceptions, and cannot publish the pack alone if your close requires a review.

Reviewer

Signs the commentary and the tie-out. The only role that marks a period as the version the meeting will use.

Reader

Sees the published pack and the slices agreed for their role. Cannot edit a driver or export a table they were never meant to hold.

Personal data inside commercial reports.

A sales line by customer, a payroll bridge, or a commission list can be personal data under UK GDPR even when the audience is internal. We design the cut of the data with that in mind: aggregated where a named individual is not required for the decision, access limited where it is, and retention agreed with you.

We do not connect personal bank accounts, medical files, or anything else that has no place in a management pack. If a source would pull more than the pack needs, we narrow the extract.

Our own handling of enquiry information is described in the privacy policy. Client reporting data is handled under the statement of work, not under the public website.

What “good” looks like at handover

  • A catalogue of definitions in plain English.
  • A source map with owners and refresh times.
  • Reconciliation checklist for the balances that matter.
  • A short runbook for the preparer on a normal close, and a page for the close that is not normal.
  • A list of what is still manual, and why that is acceptable for now.
See where this sits in the method