Three Habits QuantX Ops Refuses to Let You Form

A well-designed system is partly defined by what it declines to do. Three of QuantX Ops's refusals are worth stating plainly, because each one occasionally annoys somebody — and each one exists for a reason that annoys somebody far more when it is absent.

1 · You cannot edit an issued invoice

Once an invoice is issued it has been sent to a customer, recorded as a sale, and created a tax liability. Editing it would change all three silently, and the copy in the customer's hand would no longer match yours.

The correction is a credit or debit note — a document of its own, referencing the original. Slower by a minute, and the only version that survives an audit.

2 · You cannot mark work billed without an invoice

It used to be possible to tick a milestone as invoiced. It was a reasonable-looking button that recorded revenue with no tax, no document and nothing accounts knew about. A company could bill for months and discover at return time that none of it carried GST.

Now the billing schedule is a schedule: what to bill and when. Raising the tax invoice is what recognises revenue. The two cannot drift because only one of them posts.

3 · You cannot delete a posted journal

A correction is a reversal — a mirror entry that cancels the original, tagged as one. The original stays visible. A ledger you can delete from is not a ledger; it is a spreadsheet of balances with extra steps.

What QuantX Ops does not refuse

Worth saying, because the list above could give the wrong impression: QuantX Ops lets you bill past the customer's order. It warns, in amber, with the figures — and then lets you proceed.

That is the line we try to hold. Refuse where proceeding would be genuinely unsafe or irreversible; warn everywhere else. A control that blocks legitimate work does not prevent the work, it just moves it somewhere nobody can see it.