Post invoice, collect receivable, and handle return or credit note

In the runtime, a draft invoice is not yet customer exposure. The operator has to use Post while the invoice is still draft or unposted. That action is what turns the billing document into live receivable value the business should now expect to collect.

Teach learners to separate document preparation from document posting. Until the invoice is posted, Receivables should not be treated as the source of truth for what the customer owes.

Evidence should come from the customer record, quote or order state, approval trail, fulfillment posture, billing document, receipt, or credit workflow. For Posting is the point where billing becomes real exposure, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

Receivables shows the posted invoice exposure, due dates, outstanding amount, and whether an item is open, partial, paid, or overdue. That makes it the review surface for collections posture, not the action surface for fixing everything retroactively.

Receipts are where cash is captured, but the runtime makes one crucial rule explicit: the operator must apply the receipt to an invoice ID and an applied amount. Without that step, money was received but the intended receivable was not actually reduced in a controlled way.

For Cash collection is more than recording a receipt, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Receivable Follow-ups exist because overdue exposure is not solved by awareness alone. The operator records when the next reminder, call, email, visit, or escalation should happen, assigns it, and then marks the follow-up completed or deferred as work progresses.

That means collections discipline is visible in the system. A follow-up left pending forever is not harmless admin debt; it is proof the collection loop is still open.

Use this section to confirm the learner understands more than the page label. They should connect Follow-up is controlled collections work to the business state, owner, and consequence behind it.

When shipped or invoiced value must be corrected, the runtime keeps the reversal path deliberate: create the sales return, approve the return, create the credit note from that approved return, post the credit note, and only then create and post a refund if money must be paid back.

That chain matters because customer service, commercial explanation, and accounting correction all need the same traceability. If teams skip approval or jump straight to refund behavior, the system loses why the value changed and who authorized it.

Use this section to confirm the learner understands more than the page label. They should connect The reversal chain should stay explicit to the business state, owner, and consequence behind it.

A healthy outcome is not just “invoice sent.” It is a posted invoice with visible AR, receipts applied against the right invoice and amount, follow-ups closed or deferred intentionally, and disputed value resolved through posted credits and posted refunds when required.

That is the point where revenue operations can say the commercial promise was not only shipped, but also billed, collected, and corrected under control when reality changed.

For What good looks like after billing and correction work, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Run the lesson as a quote-to-cash operating rehearsal. Start with the practical task: understand when shipment or order activity is ready to become a posted invoice. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from the customer record, quote or order state, approval trail, fulfillment posture, billing document, receipt, or credit workflow. The practice should end with the learner connecting the action back to the lesson summary: teach the live post-fulfillment job: post the invoice, turn it into visible receivable exposure, apply and post receipts, manage collection follow-up, and resolve disputed value through returns, credit notes, and refunds.

Close the exercise by asking the learner to restate the objective in operational terms: understand when shipment or order activity is ready to become a posted invoice. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let revenue work move forward only because the next button is available. The learner should check commercial terms, customer context, fulfillment readiness, and finance impact first. In this lesson, watch for that risk while learners work on this objective: understand when shipment or order activity is ready to become a posted invoice.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain why posting the invoice is the point where billing becomes real receivable exposure and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain why posting the invoice is the point where billing becomes real receivable exposure, keep the lesson in practice mode before marking it complete.