Issuing a native invoice creates the accounting document under the current Books permissions. It does not mark the invoice sent or paid. The issuance panel explicitly separates those later events so you can verify each result from its own history.
After issuance, prepare and review the current document PDF before using Email invoice. Delivery history then records the email provider's response. A queued email is still a pending delivery state, not proof that the customer received the invoice.
Payment matching records a confirmed existing bank movement against the invoice. It does not collect money from the customer. Review the recorded payment and remaining balance separately from whether an email was sent.
When updating a teammate, state the stage precisely: issued, email queued or delivered according to the history, and payment recorded where supported. Avoid a single 'done' label that hides an outstanding delivery or settlement step. If a stage fails, resolve that workflow rather than creating another invoice for the same obligation.
Was this article helpful?
Tell us whether this answered the question you came with.