Year‑End Stock Reconciliation Checklist for Wholesalers & Pharmacies in Africa

Preparing the store and warehouse for count

A clean, organized space is the foundation of any reliable year‑end stock reconciliation checklist Africa. Start by assigning a count‑lead for each location — usually the store manager or a senior warehouse clerk — and give them a printed “Count‑Day Pack” that includes:

• Floor‑plan with aisle numbers and bin locations
• Current system stock‑on‑hand report (exported from the ERP the night before)
• Blank variance sheets (one per SKU) for manual notes
• Sealable count tags or barcode stickers for each pallet/bin
• Pen, highlighter, and a clipboard for each counting team

Schedule the count during the slowest trading window — early morning for pharmacies, late afternoon for wholesalers — and communicate the cut‑off time to purchasing and sales so no new receipts or dispatches occur after the freeze. Lock the receiving dock, pause POS transactions, and post a visible “Count in Progress” sign at every entry point. If you run multiple warehouses, stagger the counts by 30‑minute intervals to keep the count‑lead reachable by phone or radio.

Conducting the physical count with mobile scanners

Equip each two‑person team with a rugged mobile scanner (or a smartphone running the ERP’s count app). The workflow is deliberately simple:

1. Scan the location barcode on the bin or pallet tag.
2. Scan each SKU barcode; the app auto‑fills the expected quantity from the frozen ledger.
3. Enter the actual counted quantity. If the count differs, the app flags the line in red and prompts a “reason code” (damage, expiry, mis‑pick, theft, data‑entry error).
4. Press “Confirm”. The record is written locally and synced when the device reconnects to Wi‑Fi.

For pharmacies, add a mandatory “expiry‑check” step: any batch within 90 days of expiry must be photographed and the batch number recorded. Wholesalers handling bulk packs should count by case and then break down to units only when a variance appears. Keep a master “Count‑Control Sheet” at the count‑lead’s desk — tick off each location as it finishes to avoid double‑counts or missed aisles.

Importing count results into the ERP

Once every device has synced, run the ERP’s “Import Physical Count” routine. The import does three things automatically:

• Creates a Count Batch record with timestamp, user, and location.
• Compares counted qty vs. system qty and writes a variance line for every SKU.
• Locks the counted locations so no further stock movements can be posted until the batch is closed.

Before you hit “Post”, run the built‑in validation report: it lists any SKUs with a variance > 5 % or > 10 units (whichever is higher). Export this list to Excel — it becomes the working document for the variance investigation step. Keep the original frozen ledger snapshot archived; auditors will ask for the “pre‑count” baseline.

Investigating and approving variances

Variance investigation is where most teams lose time. Use a structured, repeatable process:

1. Group variances by reason code (damage, expiry, mis‑pick, theft, data‑entry). The mobile app already captured the code; if a line is blank, the count‑lead assigns one now.
2. Cross‑check documentation: pull the last three GRVs, the last two sales invoices, and any transfer notes for the SKU. A quick VLOOKUP in the exported sheet usually reveals a missing receipt or a double‑posted sale.
3. Physical verification: for any variance > 20 units or > 10 % of line value, send a second team to recount the exact bin. Photograph the bin, the count tag, and the product label.
4. Approval matrix:
   • ≤ 5 % variance → Count‑lead signs off.
   • 5‑15 % → Finance controller signs off.
   • > 15 % or any theft flag → Managing director sign‑off + incident report.
5. Document the decision in the ERP’s “Variance Log” (date, reviewer, action: adjust, write‑off, investigate further). Attach the photos and the cross‑check spreadsheet as supporting docs — this satisfies most audit trails without re‑working the whole sheet.

Posting adjustments and updating cost of goods

With approved variances in hand, post the adjustments in a single “Stock Adjustment Journal”. The ERP should let you:

• Select the Count Batch as the source, so every line inherits the reason code and auditor‑ready attachment.
• Choose the adjustment account: “Inventory Shrinkage”, “Damaged Goods”, “Expired Stock Write‑Off”, or “Theft Loss” — each maps to a distinct GL account for clear P&L visibility.
• Auto‑recalculate weighted‑average cost (or FIFO/LIFO per your policy) for the affected SKUs. The journal posts the quantity change and the cost impact in one atomic transaction.

Run the “COGS Impact Report” immediately after posting. It shows the net effect on cost of goods sold for the period — essential for the finance team’s final profit‑and‑loss close. If you operate multiple warehouses, the journal automatically splits the adjustment by warehouse, preserving the multi‑location ledger integrity.

Generating the final stock valuation report

The last deliverable is a printable, audit‑ready Stock Valuation Report. Configure the report to include:

• Valuation date (the count freeze date)
• Warehouse / store breakdown
• SKU, description, unit of measure, counted qty, system qty, variance qty, unit cost, total value
• Summary totals per warehouse and grand total
• Variance reason‑code summary (counts and values)
• Sign‑off block: Count‑lead, Finance Controller, Managing Director — each with name, signature, date

Export to PDF and store in the ERP’s document vault with a naming convention like YYYYMMDD_StockValuation_WarehouseA.pdf. Attach the same PDF to the year‑end audit pack. Because the report pulls directly from the posted adjustment journal, there is no manual re‑keying — auditors can trace every number back to the original count batch.

Quick‑print checklist for the team

Print the following one‑page checklist and hand it to every count‑lead. Tick each box as you go; the completed sheet becomes part of the audit evidence.

• [ ] Count‑Day Pack distributed (floor‑plan, frozen report, variance sheets, tags, pens)
• [ ] Receiving dock locked, POS frozen, “Count in Progress” signs posted
• [ ] Mobile scanners charged, app logged in, Wi‑Fi tested
• [ ] Two‑person teams assigned per aisle/bin
• [ ] Expiry‑check step completed for pharmacy batches
• [ ] All locations ticked on Count‑Control Sheet
• [ ] Devices synced, Count Batch created in ERP
• [ ] Validation report run, variance > 5 % / > 10 units exported
• [ ] Variances grouped, cross‑checked, re‑counted where required
• [ ] Approval matrix applied, Variance Log completed with attachments
• [ ] Stock Adjustment Journal posted, COGS Impact Report reviewed
• [ ] Final Stock Valuation Report generated, signed, PDF archived

Following this routine turns a chaotic year‑end scramble into a repeatable, auditable process that any wholesale or pharmacy finance team can execute with confidence. The key is freezing movements, counting with mobile capture, and letting the ERP carry the variance logic through to the ledger — no spreadsheets passed around by email.

See how StockPRO can tighten stock control across your stores and warehouses.