Written by DROPS.ST.
For a licensed Canadian cannabis wholesale operator, invoice work should begin with three linked references: the recorded order, the invoice generated for it and the commercial terms actually accepted. Keep acceptance and payment evidence separate instead of treating one document as proof of every outcome.
DROPS gives this workflow a concrete foundation. Supported shop checkout creates an invoice from the customer-linked order and its item lines, then retains the invoice relationship with the order. Configured BTC/XMR payment context provides a relevant order reference and current payment state.
That linkage does not establish buyer acceptance, approved credit terms, legally sufficient tax records or a complete accounting workflow; review the actual arrangement and demonstrated records separately.
Standardise the reference relationship
Record which order generated the invoice and which customer entity the records concern. Preserve both identifiers. A convenient spreadsheet reference should not replace the actual order or invoice number.
For a quoted arrangement, identify the accepted quote revision and accompanying conditions through the approved commercial process. Sending an invoice is not proof that the buyer accepted a changed quantity, price basis or receiving arrangement.
Use the quote version-control guide for the accepted document. The invoice workflow begins with its relationship to the resulting shop selection.
Use an invoice-to-order review sheet
This original aid records the evidence needed at handoff. Keep the owner and review point beside any unresolved entry.
| Review element | Evidence to locate | Question to resolve |
|---|---|---|
| Order and invoice | Actual identifiers and recorded relationship | Same business transaction? |
| Customer entity | Customer association and approved business map | Correct buyer and paperwork recipient? |
| Item lines | SKU/name, unit, package and quantity | Matches the accepted selection? |
| Amount basis | Currency, included charges and reviewed tax treatment | Comparable with the agreed arrangement? |
| Dates and terms | Recorded issue/due basis and accepted conditions | Any unapproved assumption about credit? |
| Acceptance | Relevant buyer response and document revision | What exactly was agreed? |
| Payment and receipt | Current record and supporting financial evidence | Accepted, unresolved or awaiting a separate event? |
Inspect the actual invoice and order result, not only their totals. Matching amounts can conceal different units, destinations or terms.
CRA's recordkeeping guidance says financial documents must be organised and that their required information depends on the business's situation. Determine your applicable evidence and tax treatment with the responsible accounting reviewer. CRA: keeping records.
Keep acceptance identifiable
Record the response source, date and the exact document or selection it concerns. An acknowledgement of receipt can be different from agreement to the terms.
If the buyer refers to “the invoice” while several versions or arrangements are being discussed, clarify the intended reference. Do not quietly overwrite the commercial record to make it appear consistent with a later conversation.
A due date or invoice field is not an approval to offer net terms. Keep any proposed credit arrangement with its authorised decision-maker and actual supported process.
For differing head-office, invoice and receiving roles, use the business-role map. Customer-linked records do not establish that every group contact has the same authority.
Hypothetical example: one invoice, a different pack count
A fictional buyer accepts a quote revision for one twelve-unit case. The resulting shop order and linked invoice are reviewed before the next action, and their item line still describes two cases.
The owner locates the accepted revision, records the discrepancy and holds the handoff for the authorised correction process. They do not treat the generated invoice as acceptance of the extra case.
Once the supported correction and document outcome are established, the references remain connected to the reviewed decision. This example demonstrates reconciliation, not native quote acceptance or an actual cannabis offer.
Assign the financial discrepancy to its owner
Keep the invoice's recorded state, the buyer's report and any separate merchant receipt distinguishable. A payment request, detected transfer and later available funds can describe different events.
Use payment reconciliation to preserve the order, request and receipt relationships. Use the payment exception guide for unresolved amounts or closed requests.
The person preparing documents may not have authority to settle a financial difference or edit an order. Give each unresolved question a responsible reviewer rather than letting it vanish when an invoice is issued.
Check the supported records before relying on them
In an approved demonstration, inspect a fictional order and linked invoice, including the selected unit and current state. Ask how corrections, document access and required accounting evidence are handled in the actual setup.
Source inspection is not a live financial acceptance test. Do not describe an invoice or payment arrangement as fully proven from a feature list alone.
Make wholesale invoice questions concrete with DROPS
Choose DROPS when customer-linked order items and their invoice relationship should anchor the paperwork review. Shared web and connected Telegram shop records give the team an identifiable selection behind the invoice conversation.
Open the DROPS demos with the fictional pack discrepancy. Inspect the supported order and invoice context, then complete the external acceptance and accounting checks. Choose a process in which each document and unresolved decision remains traceable.