Stellvia is planned to keep the customer's instruction, proof, sign-off, required documents and submission route together, then prepare one traceable handoff for invoicing and accounting.
Keep the completed service and its original record visible.
02
Gather what the customer expects
Bring the instruction or PO, proof and required documents together.
03
Check what is missing
Compare the job with this customer's current requirements.
04
Ask the right person
Send the missing sign-off or information request to its owner.
05
Prepare the handoff
Give invoicing and accounting one traceable buyer-ready record.
The detailed job record
Ten states keep each source and decision distinct.
01
Instruction
The source that authorises the service or commercial request.
02
Contract or PO
The terms, buyer reference and requirements that apply.
03
Service
The delivered outcome, period, milestone and responsible owner.
04
Evidence
The source that shows what happened, retained with provenance.
05
Approval
The attributable buyer or commercial decision and its state.
06
Required form
The verified buyer format, version, reference and supporting set.
07
Submission
The authorised route, event, acknowledgement and follow-up owner.
08
Invoice
Why preparation or issue is supported—and what remains separate.
09
Accounting
A traceable handoff into the ledger and adviser workflow.
10
Payment
Reported, verified and matched payment states remain distinct.
One decision, clearly isolated
One buyer-specific approval still needs a person before submission.
When a customer acceptance reference is uncertain, Stellvia is designed to preserve the completed work and proof, prepare the missing-information request and surface the relationship decision to commercial operations.
05 / 10 · needs a decision
Authorised acceptance has not been linked
Work
Service visit completed
Proof
Signed delivery note retained
Owner
Commercial operations
Next action
Request the attributable approval through the agreed route
Rejoin
Authorised reviewer confirms the linked reference
Illustrative document context, not an actual Stellvia record.
AI prepares. People keep authority.
The routine context arrives before the decision does.
The planned mechanism gathers the source, prepares structured facts, proposes the work relationship, checks the evidence requirement and names the missing item. A delivery note can prove that work happened; it does not automatically prove acceptance. The authorised person makes that decision, and the history remains attached for the buyer-ready handoff.
This route describes representative planned operation. It does not claim that every buyer format is configured, that a native integration is live, or that payment, accounting, tax, compliance or product availability is guaranteed.
Find the first missing item before it delays invoicing.