Reconcile CD Wholesaler Invoices to the CD Register (UK)

To reconcile a UK community pharmacy CD wholesaler invoice to the CD register, extract every Schedule 2 line (and any Schedule 3 line retained against the invoice) with PIP code, drug, pack, quantity, invoice number and date, then verify each Schedule 2 line is matched by a register receipt entry citing that invoice. The running balance is reconciled to physical stock at the pharmacy's agreed cadence, with any variance dated, signed and investigated. Under the Misuse of Drugs Regulations 2001 the register must be preserved for two years from the date of its last entry, and that retention floor anchors the wider evidence trail this workflow produces.

The artefact at the centre of the work is a per-invoice, per-line, per-register-entry reconciliation matrix. One side carries the Schedule 2 (and retained Schedule 3) lines lifted from the monthly wholesaler invoice — AAH, Phoenix, Alliance Healthcare or a specialist CD wholesaler — with PIP code, drug, schedule, pack size, quantity, invoice number and date. The other side carries the corresponding register receipt entries for the same period. The matrix pairs the two, surfaces gaps, and becomes the workbook that demonstrates the cross-reference at GPhC, CQC or Accountable Officer review.

Three roles read the same workflow differently. The Responsible Pharmacist runs the routine monthly cycle in their branch, signs off the register entries, and owns the reconciliation against physical stock. The Superintendent Pharmacist standardises that cycle across every branch in the group, aggregates the per-branch matrices into a governance rollup, and holds the audit trail at organisation level. The specialist pharmacy accountant runs the matrix as a second pair of eyes on behalf of client pharmacies, catches what the branch missed, and produces the same artefact as a deliverable.

This is operational support for the registered professionals who carry statutory accountability for the register and its contents. Where the workflow touches regulatory or inspection positions, the article defers to the Misuse of Drugs Regulations 2001, the current edition of the Royal Pharmaceutical Society's Medicines, Ethics and Practice (MEP), CQC, GPhC and the Accountable Officer for the authoritative position. The aim here is the monthly housekeeping pattern that catches gaps in routine work rather than at inspection — the structure that lets the RP, Superintendent or accountant sign off the period and move on.

---

Schedule classification and what each schedule requires

The Misuse of Drugs Regulations 2001 (as amended) classify controlled drugs into five schedules and assign different record-keeping consequences to each. Most of the reconciliation work concerns Schedule 2; the other schedules sit inside the wider perimeter because the invoices that carry them are still retention-bound.

Schedule	Register entry	Invoice retention	Notes for community pharmacy
Schedule 1	Not relevant in normal community pharmacy supply (Home Office licence required to possess)	n/a	Mention only to delimit scope.
Schedule 2	Mandatory for every receipt and supply, with running balance expected in practice	2 years	Drives the bulk of the reconciliation work.
Schedule 3	Not required under the Regulations, with named exceptions (e.g. temazepam, where local practice and RPS MEP guidance support register-style recording)	2 years	Invoice still enters the reconciliation perimeter.
Schedule 4 (Parts I and II)	Not required	2 years	Sits in the invoice file for the retention period.
Schedule 5	Not required	2 years	Sits in the invoice file for the retention period.

The distinction between what the Regulations require (must) and what RPS MEP and inspection practice expect (should) is load-bearing for the rest of the article. The Regulations require register entry for Schedule 2 receipts and supplies; they do not, in their text, require a running balance per Schedule 2 CD. RPS MEP recommends running balance maintenance as best practice, and CQC, GPhC and Accountable Officer inspection looks for it in working practice. Schedule 3 register-style recording for temazepam is similarly expectation-led, not statute. Read each obligation against the source it originates from.

Regulation 23 of the Misuse of Drugs Regulations 2001 requires that controlled drug registers kept under regulation 19 be preserved for two years from the date on which the last entry is made. Invoices for Schedules 2 to 5 must also be retained for two years. The retention period applies to the invoice in its original form, including any CD lines on it — the audit object is the scanned and archived original, not a transcription of the CD section into a spreadsheet. The spreadsheet is the reconciliation working artefact; the invoice itself is the document of record.

RPS MEP also recommends practical retention beyond the statutory two-year floor for CDs, because late-arising criminal cases (the post-Shipman inquiry era reset the expectation here) can require evidence beyond what the Regulations strictly demand. The article notes that without prescribing how far past two years to go — that decision sits with the registered professionals at the pharmacy and with the group's governance policy.

Structurally similar receiving-log workflows exist in adjacent regulated industries, including the US veterinary controlled-substance receiving log built from wholesaler invoices, which uses a different regulatory regime (DEA, Form 222) but the same essential workflow — extract the controlled lines from the supplier-side document and pair them against the on-site register. The UK community pharmacy regime under the Misuse of Drugs Regulations is the subject here; the parallel is structural, not regulatory.

---

The invoice-to-register flow end-to-end

The reconciliation matrix only makes sense when the upstream chain is visible. Each step in the supply-to-stock cycle produces a document, and the documents are the audit trail. Pulling the chain apart explicitly is the easiest way to see where downstream sections fit.

1. The pharmacy raises an FP10CDF requisition for Schedule 2 (and certain Schedule 3) supplies from the wholesaler. The FP10CDF is the legal requisition document for community pharmacy CD ordering from a wholesaler and replaced the legacy requisition arrangements through the 2015 amendment. A copy is retained at the pharmacy; the retained copy is part of the same audit trail as the invoice and the register entry, and the FP10CDF requisition invoice reconciliation step expects the three to line up.
2. The wholesaler supplies the CDs and forwards the original FP10CDF to NHS Prescription Services at the NHSBSA. The pharmacy keeps its copy.
3. The wholesaler issues the invoice. CD lines are flagged on the invoice — AAH, Phoenix and Alliance Healthcare each surface a CD indicator, with format variations across the three. The CD section is therefore identifiable on the page even before extraction.
4. On receipt of stock, the Responsible Pharmacist (or a delegate operating under documented RP delegation) enters each Schedule 2 supply into the CD register. The entry carries date, drug, form, strength, quantity received, invoice number and supplier; the running balance for that drug is updated immediately. No alterations are made to existing entries — any correction is recorded as a dated, signed margin note rather than an in-place edit.
5. The running balance per Schedule 2 CD is maintained line by line, entry by entry, so the figure shown is always the current stock position on paper.
6. Periodic physical stock reconciliation against the running balance is performed at the pharmacy's chosen cadence. Variance is recorded, dated, signed and investigated; the investigation itself is documented even when the variance resolves to zero.

Schedule 3 invoices sit inside the perimeter too, even though most Schedule 3 lines do not generate a register entry. The invoice is retention-bound, and any Schedule 3 line that the pharmacy has elected to record (temazepam is the common case) joins the register side of the matrix. The reconciliation perimeter is therefore wider than the strict statutory register and tracks the invoice file rather than the schedule of legal compulsion.

Electronic CD registers have been permitted since 2008. Most community pharmacies operate either a paper register or an electronic register; a meaningful minority operate both, typically because the PMR (Titan, ProScript and others) writes to an electronic register while the branch retains a paper register for resilience. Where both exist, designate one as the primary source. Ambiguity between the two is what inspectors flag; the choice between them is yours.

This CD-specific cycle sits inside the broader pharmacy invoice processing workflow the same staff carry out monthly — wholesaler invoice in, supplier reconciliation, COGS posting, payment release — and alongside the dispensing-reimbursement leg of the month, where converting the NHSBSA FP34 Schedule of Payments to Excel handles the cash that comes in against the cost going out. The CD reconciliation is its own job with its own audience, but the calendar slot it occupies is shared with the wider monthly cadence.

Extracting the CD subset from the wholesaler invoice

The reconciliation matrix needs an input on the invoice side: every Schedule 2 line (and any Schedule 3 line the pharmacy retains against the invoice) lifted off the PDF into a structured row in a workbook. How that workbook is produced is the discrete operational decision that determines how robust the matrix is at scale. The choice sits between three honest options.

Option A: Manual visual scan and transcription. The pharmacy opens the PDF wholesaler invoice each month, finds the CD indicator on each page, and hand-transcribes the Schedule 2 and 3 lines into a workbook column by column. For a branch with a handful of CD lines per monthly invoice cycle, this is viable and proportionate. At any meaningful volume it becomes fragile — transcription error becomes its own inspection risk, since a register entry built from a mis-typed quantity or invoice number is itself a register fault. The honest cut-off varies by branch, but as a rule of thumb, once the monthly CD section runs to more than a page or two it is no longer the cheaper option in real terms.

Option B: CD flag on the routine wholesaler-invoice extraction. Most pharmacies (and most pharmacy accountants) already extract wholesaler invoices to Excel for COGS posting and supplier reconciliation. Adding a CD-flag column to the line-item extraction produces the CD subset as a filter on the same workbook the bookkeeper already runs each month — same monthly job, same input, two outputs. The reconciliation matrix then takes a filtered slice of the same data the cost-of-sales work uses. This is the natural fit where extracting AAH, Phoenix and Alliance wholesaler invoices to Excel is already the monthly workflow.

Option C: Scoped extraction of the CD subset. Where the bookkeeping extraction sits elsewhere (or is run by a different person in the practice), a CD-only extraction produces a per-line workbook with no non-CD noise to filter out: PIP code, drug description, schedule, pack size, quantity, invoice number and invoice date. That cleaner artefact is the most direct input to the matrix.

Options B and C both rely on the same underlying capability: AI-powered controlled-drug invoice line extraction configured by a prompt that asks for one row per invoice line, retains the CD indicator as its own column, and outputs the columns the reconciliation matrix needs. The same prompt runs against ten invoices or against twelve months of invoices for an annual audit; output is consistent across the batch.

CD indicator layouts vary across the three primary wholesalers, and any pharmacy or accountant running this workflow should anchor the extraction prompt to whichever pattern their main supplier uses. The column names in the output are what the matrix consumes — the prompt absorbs the layout difference upstream.

A worked example (anonymised — illustrative drug name, illustrative PIP code, illustrative invoice number):

PIP	Drug	Schedule	Pack	Quantity	Invoice number	Invoice date
0000001	Example CD A 10mg tab	2	28	6	INV-EXAMPLE-001	2026-04-15
0000002	Example CD B 5mg/ml oral solution	2	100ml	12	INV-EXAMPLE-001	2026-04-15
0000003	Example CD C 30mg cap	2	56	4	INV-EXAMPLE-001	2026-04-15

Each row in that workbook becomes a left-hand entry in the cross-reference matrix.

The cross-reference matrix

The matrix is a paired-side artefact. On the invoice side sits the per-line CD workbook: every Schedule 2 line lifted from the month's wholesaler invoices, with PIP code, drug, schedule, pack, quantity, invoice number and date. On the register side sits every Schedule 2 register receipt entry for the same period, drug by drug, with the date, quantity, supplier and invoice number cited in the register itself. The pairing key is drug plus pack plus quantity plus invoice number plus date. Each row in the matrix shows the invoice-side fields, the register-side fields, and the pairing status.

The work is a left-join and a right-join run against the same paired set.

Left-join (invoice to register). Every Schedule 2 invoice line should match a register receipt entry citing that invoice number. An invoice line with no matching register entry is a register gap, and a missing register entry for a Schedule 2 supply is the most frequently flagged CD finding at inspection. The matrix surfaces it as a row populated on the invoice side and empty on the register side. Investigate immediately: was the stock received but not recorded, was it received and recorded against a different invoice number, was it received late and entered into a later period's pages, or did the supply itself fail to arrive and the invoice not reflect a credit. Each of those answers leads to a different remediation, but the matrix is the trigger.

Right-join (register to invoice). Every Schedule 2 register receipt entry in the period should trace back to an invoice line for that wholesaler-supplied receipt, to a documented FP10CDF requisition, or to an internal-transfer record from another branch in the group. A register entry with no invoice-side counterpart and no supporting documentation is a separate audit concern — the stock entered the register from somewhere, and that somewhere needs to be documentable.

Within those two sides, four mismatch cases recur often enough to warrant a fixed decision tree:

• Invoice line, no register entry. Register gap. Investigate the cause; remediate by recording the receipt now via a dated margin note in the register that references the original receipt and the original invoice. Do not retro-fabricate the original receipt date, and do not alter any existing entries — the corrective note is the audit object.
• Register entry, no invoice line. Trace to the FP10CDF copy and to any internal-transfer log. If neither produces a counterpart, the register entry needs documentary substantiation appended to the file, and the supply route needs review at the next governance step.
• Quantity mismatch on a paired line. Investigate which side is correct (compare to the FP10CDF requisition quantity, the delivery note, and the physical count); document the resolution and append the supporting evidence to the CD invoice file.
• Invoice number missing on the register entry. This is the inspector's most-cited weakness because it isn't a missing receipt — the stock and entry are both there — it's a missing cross-reference. Add the cross-reference via a dated note that links the register entry to the invoice number, and tighten the routine entry procedure so the cross-reference is captured at entry rather than added later.

Where the pharmacy operates an electronic CD register, the register side of the matrix can be produced as a direct export from the register software — most PMR-integrated electronic registers support a date-range CSV export of receipt entries, which can then be imported into the matrix workbook alongside the wholesaler-invoice extract. The invoice-side workbook is the same whether the register is paper or electronic; the electronic route simply removes a transcription step from the matrix preparation.

---

Running balance reconciliation against physical stock

The matrix establishes that what entered the register matches what entered the pharmacy on paper. The running balance, reconciled against physical stock, establishes that what the register says is on the shelf is in fact on the shelf. Different question, different cadence, different evidence shape — but the same governance posture.

Three cadence options fit different pharmacy profiles cleanly:

• Weekly. Appropriate for high-CD-volume branches: hospital-adjacent settings, addiction-services dispensing, palliative-care-heavy lists, or any branch where the cost of investigating a four-week-old variance materially outweighs the cost of running the count more often. Weekly counts make any discrepancy small enough to trace to a single working week's activity.
• Monthly. Typical for community pharmacy. Aligned to the wholesaler-invoice cycle and the monthly cross-reference matrix, which means the same week of the month carries both the matrix run and the physical count. Combining the two into a single governance session is efficient and is the routine most groups standardise on.
• Per-RP-handover. Appropriate for locum-heavy branches where the Responsible Pharmacist changes frequently and continuity of accountability requires a documented hand-off at every change. The incoming RP wants to inherit a clean position; a witnessed count at handover establishes the position they then own.

Whatever cadence is chosen, the evidence shape is fixed: a dated entry in the register signed by the Responsible Pharmacist, the physical count itself (witnessed by a second registered professional or pharmacy technician where group governance requires it), the variance figure for each Schedule 2 CD counted (often zero, but recorded explicitly so the absence-of-variance is itself evidenced), and the investigation note for any non-zero variance. A clean count is a positive record of what was checked, not a silence about what wasn't.

The Regulations do not require a running balance per se — that is RPS MEP guidance and inspection practice rather than statute — but a Schedule 2 register that lacks one reads as incomplete regardless of the Regulations' literal text. Variance recording is the piece inspectors weight most heavily: a non-zero variance that is dated, signed and investigated is acceptable; a non-zero variance that sits unrecorded, or a clean count that is silent about whether a check happened at all, is the finding.

The inspection evidence pack

When an inspector arrives — GPhC for the registered pharmacy as a whole, CQC where the premises falls within its registration scope, or the Accountable Officer on a CD-specific governance review — the question is whether the documentation sits in one place and tells a single coherent story. The pack is the answer to that question, assembled in advance so the routine produces it rather than the inspection demanding it.

What the pack contains, item by item:

• The CD register itself, whether paper, electronic, or both with a designated primary, showing a running balance maintained line by line for each Schedule 2 CD.
• The CD invoice file holding every retained wholesaler invoice for the two-year window (or longer, per RPS MEP practical recommendation), with the CD lines identifiable on each. Most groups archive scanned originals; the original PDF from the wholesaler is the object of record.
• The retained FP10CDF requisitions matching the supplies that came in over the period, filed alongside the corresponding invoices.
• The periodic stock reconciliation evidence: the dated, signed register entries that record each physical count, the variance recorded against each count (including zero), and the investigation note for any non-zero variance.
• The cross-reference matrix, ideally as a per-month workbook with a per-quarter compilation: invoice side, register side, pairing status, with any open items flagged and the remediation status visible. This is the CD inspection workbook the pharmacy hands across at the start of the review.
• Any margin-note corrections in the register, dated and signed, with the underlying remediation traceable back to the matrix entry that surfaced the issue.

Each inspecting body emphasises different parts of the pack:

GPhC. The standards for registered pharmacies cover CD record-keeping as part of the medicines management standard. The GPhC inspector reviews the pharmacy's controlled drugs records as part of the wider inspection of pharmacy services and looks for records that are present, accurate, accessible and consistent with the running practice of the branch. The matrix and the running-balance evidence are the artefacts that demonstrate the routine, not just the records.

CQC. Most community pharmacies are not registered with CQC; the registration scope captures distance-selling pharmacies, certain hospital-adjacent settings, and a defined set of other services. Where CQC does inspect, its CD framework weights cross-reference and reconciliation heavily, and the matrix is the natural way to demonstrate both. CQC's mythbuster 28 on controlled drug management is framed for GP practices rather than for community pharmacy; reading across from it is reasonable for the underlying principle, but community pharmacy professionals should not assume the GP-specific guidance maps directly onto pharmacy practice.

The Accountable Officer. The AO model, operating at PCN, ICB or Trust level under the post-Shipman structures, holds a broader view across the local healthcare economy and reviews CD governance evidence particularly across multi-site groups. An AO who asks for the group's reconciliation evidence expects an artefact that aggregates per-branch matrices into a governance position rather than nine separate inspection packs in nine separate folders.

The practical asset the matrix provides at inspection is straightforward: a single workbook that pairs invoice-side to register-side makes demonstrating the cross-reference trivial. Without it, the demonstration becomes the inspector flipping between the invoice file and the register manually, which makes the routine look implicit even when it has in fact been run. The matrix turns implicit work into visible work.

The shape of the pack — supplier-side document extracted into a workbook, paired against an on-site record, retained for a statutory period, presented as a single evidence artefact — repeats across other UK compliance regimes, including the UK AWRS URN verification workflow for alcohol retailers under HMRC.

---

Multi-site governance and the superintendent view

At single-branch scale the matrix is a workbook the Responsible Pharmacist produces each month and signs off. At group scale it becomes a governance instrument. The Superintendent Pharmacist holds organisation-level accountability for CD governance across every branch, and the move from per-branch routine to a group posture is what makes Superintendent Pharmacist CD governance across multiple sites materially different from running, say, nine individually compliant branches in parallel.

The unlock is standardisation. Same monthly cycle at each branch, same workbook shape on the invoice side, same column structure on the register side, same matrix template into which both feed. Once the per-branch matrices share a shape, three rollups become possible at the group level:

• Branch by month by reconciliation status. A heatmap-shaped view: every branch on the rows, every month on the columns, every cell showing one of clean / open exceptions / not yet completed. The Superintendent reads this in seconds and sees where to look.
• Branch by month by variance count and variance value. Drift in either direction surfaces a branch whose routine has slipped well before an inspection would.
• Branch by Schedule 2 CD by running balance trend across months. Useful for spotting systemic drift on a particular drug at a particular branch — the kind of pattern a per-month review at the branch will not catch on its own.

Exception escalation is the routine that makes the rollup work as governance rather than as a report. A branch-flagged gap — a missing invoice cross-reference, an unresolved variance, an overdue physical count — escalates from the branch to the Superintendent on a defined timeline with a defined remediation owner. The escalation route is itself an audit artefact: a documented escalation that was resolved within the defined window reads very differently to an inspector or to an Accountable Officer than a silent gap that was eventually noticed.

The Accountable Officer's need for CD reconciliation evidence across a group then has a natural home. An AO asking for governance evidence across the pharmacies in their area expects to see the per-branch matrices feeding into a single dashboard, not nine pharmacy folders presented in parallel. The pack the AO reviews is the rollup, not the raw register pages.

The specialist pharmacy accountant cohort produces the same rollup as an outsourced second pair of eyes for a client portfolio. Branch matrices feed into the accountant's review, and the matrix and the rollup become deliverables of the engagement alongside the accounts work. The structure here also sits inside the wider operational picture of healthcare accounts payable automation that the group already runs across its branches — the same wholesaler invoices that feed COGS posting feed the CD matrix, and the same standardisation that makes group AP work makes group CD governance work.

---

Common failure modes and how to catch them before inspection

The matrix is an early-warning system. The catalogue below is the menu of what it warns about — six failure modes that recur often enough at inspection that the routine should be designed to surface them in the routine work, with the remediation path defined in advance so it does not have to be improvised under inspection pressure.

Missing invoice cross-reference on register entries. The single most-flagged CD finding at inspection. The receipt is in the register, the stock is on the shelf, but the register entry does not cite the invoice number that supplied it. Detection in the matrix: a row with the register-side fields populated but the invoice-number cross-reference blank or wrong. Remediation: a dated margin note in the register adding the cross-reference, alongside a review of the routine register-entry procedure so the cross-reference is captured at the moment of entry rather than added later. This is the failure that most rewards getting the routine right at the front end.

Running balance not maintained. Register entries are present and accurate, but the running balance column is missing, has lapsed, or shows arithmetic that no longer reconciles. Detection in the matrix: a register-side row with no balance figure, or a balance figure that does not follow from the previous entry. Remediation: re-establish the running balance prospectively from a known good physical-count anchor, document the anchor explicitly (date, count, witness if used), and resume the routine. Do not retro-fabricate a running balance backwards through the register — the entries that exist stand as they are, and the anchor is the visible reset.

Stock variance not investigated and documented. Physical-count entries are dated and signed, but the variance figure is absent or the investigation note is missing for a non-zero variance. Detection: count entries without a paired variance entry. Remediation: change the stock-reconciliation routine so that recording the count and recording the variance (and the investigation note where the variance is non-zero) are a single action, not two. Splitting them invites the second half to be skipped under time pressure.

Mixed paper and electronic registers without a clear primary source. Both registers are present, both are being updated, but they have drifted, or it is unclear which the pharmacy treats as authoritative. Detection: an end-of-period balance that differs between the two on spot check, or a register entry that exists in one but not the other. Remediation: nominate one as primary in writing, define a mirror cadence (most groups mirror at end-of-shift), and log any divergence as it is found rather than tidying it away silently. The decision between paper-primary and electronic-primary is local; the absence of a decision is the inspection issue.

Locum-handover continuity gaps. Register entries are thin or absent across a locum period, or the running balance shows a discontinuity at the handover. Detection: the matrix shows register-side gaps that cluster around RP changes. Remediation: a documented locum CD hand-off step at every RP change, including a witnessed physical count for each Schedule 2 CD and a register sign-off by the outgoing and incoming RP. The handover note then sits in the file alongside the relevant register entries.

Invoice retention falling short. Gaps in the CD invoice file, or premature destruction at the strict two-year mark. Detection: a matrix run that cannot retrieve the invoice referenced by an in-period register entry. Remediation: extend retention beyond two years in line with RPS MEP practical recommendation, and tighten the wider destruction schedule so the CD invoice exception is enforced rather than relied on as a verbal convention.

The no-alterations rule sits behind every remediation that touches the register itself: corrections are made by dated, signed margin notes, never by editing an original entry. Where a failure escalates into regulatory or criminal territory, the next step belongs to the registered professionals on site — the Responsible Pharmacist, the Superintendent Pharmacist, the Accountable Officer — and to the inspecting body. The matrix surfaces the issue; the people accountable for the register decide what to do with it.