Access, audit and security

Named users, and only what they need

Everyone gets their own login. Not a shared password on a terminal — every receipt, batch and delivery carries the person who recorded it, which is also what makes the quality records worth anything.

Access is controlled in two layers. Which screens a person lands on, and — separately and more importantly — which documents they may open, create or submit. A picker sees picking, not the ledger, and cannot reach it by typing an address either.

Sign-off where you want it

Any document can be put behind an approval route: who may move it, at what value, and what happens next. Batch release, credit and purchase approval all use the same mechanism, so there is one thing to understand rather than several.

Every write is on the record

A full request log

Every write to Intacct is recorded with the function called, the document behind it, the entity, the duration, the key Intacct returned and the complete request and response. Credentials are stripped before storage, and no role can edit an entry — including an administrator.

Record history

Every record keeps its own history: what changed, who changed it and when. Nothing is edited quietly.

A retry cannot double-post stock

Every post carries an identifier derived from the document itself, marked unique. A request that times out after Intacct committed it is rejected as a replay rather than moving stock twice.

Multi-leg movements are all or nothing

A production run is two postings and a transfer is two legs. They go inside a single Intacct transaction, so stock can never leave one place and fail to arrive in another.

A cancellation reverses in Intacct

Undoing a posted movement writes a reversing pair into Intacct, dated to the original posting date so the two net to zero in the period they happened in. If that period is closed, Intacct refuses — which is the correct answer, not an obstacle.

What lives where

Intacct is the golden source, and that is a design rule rather than a preference. Anything Intacct can hold is held there — items, customers, suppliers, warehouses, bins, units, orders, costs. Fuse reads them and never writes them back, so there is no second copy for anyone to edit.

Fuse keeps only what Intacct has nowhere to put: the operational record of how the work was done. Who picked which lot, what the inspection measured and on which instrument, what the shop floor scanned, what a works order actually consumed — plus the log of every message sent to Intacct and what came back.

If Fuse were switched off tomorrow, your financial record would be complete and correct in Intacct. What you would lose is the operational detail behind it, not the books.

What an ISO 9001 assessor asks for

Where the quality module is switched on, these are produced as a by-product of doing the work rather than written up afterwards:

8.4 — Purchasing

Supplier goods inspected before they are accepted.

8.5.1 — Production control

In-process check on the batch being made.

8.5.2 — Identification and traceability

Lot traceable through receipt, production and delivery.

8.6 — Release

Nothing released without a passing inspection and a named releaser.

8.7 — Nonconforming output

A failed batch refused, and the decision about it recorded.

7.1.5.2 — Measurement traceability

A calibrated instrument behind every reading, enforced.

7.5 — Documented information

The records retained, printable and traceable to the batch.

Certification is awarded to your organisation, against your processes and your people as well as your system. Fuse provides the evidence; you run the system.