BC DIRECT DELIVERYPrice at acceptance
Keep the supplier-approved wholesale price evidence with the date the order was accepted.
B.C. DIRECT DELIVERY MONTH-END
Close the month from the orders that actually happened.
Month-end should be a review of the operating record, not an archaeological dig through inboxes and spreadsheets. Build the reporting pack from the approved transactions, then leave submission and remittance with the authorized operator.
THE REPORT IS THE LAST STEP, NOT THE FIRST
A trustworthy month-end starts when the retailer order is accepted.
The registered wholesale price, order date, fulfilled quantity, delivery result, return, and credit cannot be reconstructed reliably if each fact lives in a different file with a different identifier.
BC Direct Delivery keeps those facts tied to canonical order lines. Month-end then becomes an exception review: missing references, unresolved variances, mismatched quantities, or unapproved adjustments are visible before an authorized person prepares the official file.
THE CONTROLLED HANDOFF
What the operating record does, step by step.
- 01
Freeze the review period
Select the reporting month and identify orders accepted, delivered, returned, or credited during the period.
- 02
Reconcile order and delivery
Compare approved quantities with fulfillment, receipt, and any recorded discrepancy outcome.
- 03
Review commercial evidence
Confirm the recorded wholesale price snapshot, invoice obligation, external settlement reference, and approved credit.
- 04
Clear the exception queue
Assign unresolved records to an owner instead of hiding them inside a total.
- 05
Prepare the operator pack
Export the reviewed operational evidence for the authorized supplier team to validate and submit through the required BCLDB process.
MONTH-END CONTROL LIST
Every number should lead back to a transaction and a decision.
The useful unit is not a spreadsheet cell. It is the supplier-retailer-SKU transaction with enough evidence for an operator to explain the amount.
Net movement
Review what was ordered, delivered, returned, replaced, or credited without erasing the original quantities.
Open obligations
Separate operational completion from external payment status so an unpaid invoice is not mistaken for an unfulfilled order.
EXCEPTION-FIRST REVIEW
Do not make a person reread every clean order.
A controlled close highlights what is incomplete, contradictory, duplicated, or missing approval. Clean records remain available, but operator time is directed toward the few records that can change the result.
Missing source
The record exists, but the invoice, receipt, return evidence, or external reference has not been attached.
Quantity variance
Approved, shipped, received, returned, and credited quantities do not reconcile.
Approval variance
A material adjustment exists without the role, timestamp, reason, and decision required by the pilot procedure.
OPERATING BOUNDARY
This is operational preparation, not automatic filing.
The workspace does not claim to calculate or submit every regulatory, tax, fee, deposit, or remittance obligation. BCLDB instructions, the supplier agreement, current law, and the supplier's authorized finance and compliance owners remain authoritative.
- Review before export
- No silent adjustments
- Submission stays with the authorized operator
PLAIN ANSWERS
Questions operators ask before a pilot.
Does the product submit the BCLDB report for us?
No. The current product organizes and reviews the operational evidence. The authorized supplier operator remains responsible for validating and submitting the required information.
Can historical records be reviewed?
Yes, if the supplier can provide approved business records with enough identifiers to match orders, SKUs, deliveries, invoices, returns, and credits.
What happens when a record does not reconcile?
It remains in an exception queue with its source evidence and assigned decision. The system should not invent a balancing adjustment.
PROVE THE WEDGE BEFORE THE MIGRATION
Put one month of Direct Delivery on one record.
The founding audit covers a bounded supplier workflow, approved business records, explicit unsupported connections, and a written proceed, narrow, or stop recommendation.