Invoicing is an important control point, but wholesale reality does not always stop changing when an invoice is created. A final weight may be confirmed late, a short-supplied line may need correcting, a substitution may have been recorded incorrectly or a delivery charge may need adjustment. If the operational order becomes impossible to correct, staff are forced to carry the truth somewhere else.
The answer is not unrestricted editing. The answer is a controlled correction path that keeps the operational order and the accounting record understandable. Staff should be able to identify what changed, decide whether the connected invoice must be updated and preserve a clear link between the two systems.
Why hard locks create shadow records
A hard lock can feel safe because it prevents accidental changes. The problem appears when the locked values are known to be wrong. Teams then create an adjustment in a spreadsheet, message finance, add a private note or edit the accounting invoice without bringing the order record back into line.
At that point there are two versions of the commercial event. Customer service may look at the order, finance may look at the invoice and operations may rely on a delivery record. Each version can be reasonable on its own while the business as a whole loses a dependable answer.
Separate permission from possibility
An order can remain technically editable without giving every user unrestricted authority. Good control asks who may change an invoiced order, which fields may change, what status should be visible and whether the connected accounting record requires an explicit update.
This is a permission design question. A routine order-desk user may be allowed to correct quantities before invoicing, while an invoiced-order change may require an owner or finance-capable role. The system should make the higher-impact action clear rather than pretending the scenario cannot happen.
Keep Porosi and Xero ownership clear
Porosi owns the operational order lifecycle. Xero owns the accounting invoice and ledger context. A connected workflow should preserve that boundary while giving staff an intentional way to bring the records back into agreement.
In the Porosi Xero management workflow, an authorised user can amend the relevant order and then update the linked Xero invoice from the changed record. The action is explicit because a financial document is being affected. The order does not silently pretend nothing changed, and the accounting handoff does not need to be rebuilt from scratch.
Control principle: an invoiced order should not be casually mutable, but a known error should have a supported and traceable correction route.
Define what happens in each correction scenario
- Quantity correction: confirm whether the delivered and invoiced quantity should both change.
- Price correction: establish who approved the commercial change and whether tax or totals are affected.
- Removed line: decide whether the invoice should be updated or a separate credit process is required.
- Added charge: record the operational reason and confirm the accounting treatment.
- Paid invoice: treat the case differently from an unpaid invoice because downstream reconciliation may already exist.
The correct route can depend on invoice state, accounting policy and how the customer has been informed. Software should expose those decisions rather than hide them behind a universal “edit” button.
Test the correction route before rollout
Integration testing often proves that a clean order can create an invoice. That is necessary but incomplete. A production-ready test also changes a line after invoicing, attempts a change with the wrong permission, handles a missing link, retries a failed accounting update and confirms what staff see in both systems.
- Create and review a representative order.
- Create the connected invoice.
- Change one controlled value in the order.
- Confirm that the system identifies the accounting impact.
- Update the linked invoice through the approved action.
- Verify the final values and operational history.
Do not confuse correction with cancellation
Changing an invoiced order, cancelling an order and issuing a credit are different commercial events. The workflow should not use one as a shortcut for another. A correction brings an inaccurate record to the intended position. A cancellation ends the order. A credit records a financial reversal or reduction under the relevant accounting process.
During discovery, map these events with the finance team and define which actions Porosi should support directly, which actions remain in Xero and which require a linked handoff. The integrations overview explains this system-ownership approach in more detail.
A better definition of invoice control
Strong control does not mean freezing a mistake forever. It means limiting authority, making impact visible, recording the reason and keeping connected records aligned through an explicit route. That gives operations enough flexibility to reflect reality and gives finance enough structure to trust the result.
Bring one of your real correction scenarios to a Porosi workflow demo. It is a better integration test than a perfect order that never changes.