Problem
Accepted work still needs a controlled payment handoff.
Once a quote is accepted, the next steps often move through email, invoices, payment checks, and delivery notes. Without one review queue, the owner has to remember what has been invoiced, what is paid, and what can safely start.
- Which accepted scopes still need invoice review?
- Which invoices were sent but not confirmed?
- Which payments are received but not handed to delivery?
- Which jobs are waiting for customer inputs?
- Which jobs are complete and need a close reason?
Minimum queue
Track state before adding automation.
A first version should make the owner review obvious and should avoid storing sensitive payment data.
- Accepted scope: short label and owner-approved deliverable.
- Invoice status: draft, reviewed, sent, revised, void.
- Payment status: waiting, received, partial, disputed, refunded.
- Payment instruction review: owner approved, not approved, needs correction.
- Delivery start: blocked, ready, started, delivered, closed.
- Evidence link: public transaction ID, receipt reference, or owner-approved record location.
- Close reason: delivered, cancelled, unpaid, refunded, duplicate, no response.
Payment boundary
Owner-controlled payment instructions only.
The workflow can organize invoice review and status tracking. It should not create wallet addresses, store private keys, store wallet seeds, manage exchange accounts, provide investment advice, custody funds, issue payment instructions without owner approval, or move money.