External quality-system inspections tend to follow evidence rather than departmental boundaries. A reviewer may begin with a supplier invoice, move to a bank statement, then ask for the goods-received entry, the batch certificate and the storage record. If the laboratory purchase log treats an Open Banking payment reference as an afterthought, that chain can break at the point where proof of payment meets proof of supply. Research-use-only materials add a further requirement: the record should show that the purchase was made for controlled laboratory or analytical research, that the material is not for human or veterinary use, and that handling follows local COSHH and laboratory safety arrangements.
Why an Open Banking Reference Belongs in the Purchase Log
A purchase log is often designed around what was bought: catalogue number, pack size, supplier, quantity and storage location. For external inspection, that is only part of the story. The payment reference is the bridge between the bank transaction and the procurement record. Pay-By-Bank or Open Banking checkouts usually generate a reference that the payer should quote or retain; without it, a bank statement may show several similar amounts to the same supplier and become difficult to reconcile. The inspection question is not simply whether money left the account, but whether the payment can be tied to a specific order, invoice, delivery and batch document.
A practical log entry should therefore carry the supplier name, order date, order confirmation number, payment method, exact payment reference, payer name, amount, currency, invoice number, goods-received note, tracking or dispatch reference where available, batch label reference, CoA file name and storage location. The exact reference matters: transcribe it character for character rather than shortening it or relying on a screenshot name. Where the supplier publishes Pay-By-Bank or Open Banking as its checkout route, record that method consistently, and keep payment evidence with the order evidence. A controlled field for the payment reference is better than burying it in a free-text note, because free text is hard to search and easy to misread during a document review.
There is also a governance reason. Research materials are supplied strictly for controlled laboratory and analytical research. They are not medicines, medical devices, injectables, treatments or food supplements, and they are not for human or veterinary use. A log that links the payment reference to an approved research requisition helps demonstrate that the purchase was made through the expected route. It also separates procurement approval from payment confirmation: the person authorising the order and the person releasing the payment may not be the same. Recording the reference, date, amount and approver makes that separation visible without storing bank login details.
Designing the Fields and Evidence Links for Inspection
A controlled vocabulary and minimum fields
The log should use a small controlled vocabulary so that entries remain searchable under inspection conditions. Statuses such as ordered, payment initiated, payment confirmed, dispatched, received, checked and closed are more useful than free-text notes. Fields should distinguish the transaction date from the order date and the goods-received date, because supply and payment processes may run on different timelines. A unique internal purchase ID can sit alongside the supplier order number and the bank reference, but the bank reference should never be overwritten by the internal ID. If a correction is needed, retain the original entry and add a dated correction note.
Each row should point to an evidence bundle: order confirmation, payment confirmation, invoice, delivery documentation, goods-received check, batch CoA and storage record. The supplier’s published FAQs state that a CoA is provided for every product, and the homepage lists “CoAs Janoshik Analytical Reports”; those statements should be checked against the actual batch document received, not treated as a substitute for it. If a published purity headline such as “≥99% Verified Purity” is referenced in a tender or inspection file, attribute it to the supplier’s current published wording and reconfirm it on the batch CoA. The live site should be checked in the month of use because catalogue details and headline figures can change.
Batch traceability deserves a defined field. Vial labels may combine a SKU code and expiry date, for example BPC10-03/27, and that reference should be copied exactly when querying documentation. Restocked products may share an Internal Test Reference with earlier stock; the reference links to associated sample testing reports, but it does not by itself prove that separate deliveries came from the same production lot or that separate independent testing took place. Vial cap colour is not an indicator of identity, analytical quality or manufacturing origin. For inspection purposes, the batch CoA and label reference should be recorded alongside the order, not filed only in a separate quality folder.
Reconciliation, Exceptions and Supplier Evidence Before Inspection
Reconciliation should be run before the inspection, not during it. Select a sample of purchase log rows and trace each one from bank statement or payment confirmation to order confirmation, invoice, goods-received note and batch documentation. Look for duplicate references, truncated references, payments made from a shared finance account, multiple orders of identical value, and missing goods-received entries. Where a mismatch is found, record the exception, the evidence reviewed, the person who resolved it and the corrective action. Do not delete the original row; an inspector is usually more concerned with controlled correction than with a perfectly clean but unexplained log.
Open Banking evidence needs careful handling. The supplier’s published FAQs and a March 2026 blog post describe Pay-By-Bank or Open Banking through providers such as Wallid, regulated by the FCA, and state that card payments are not accepted because research-use-only scientific materials fall into high-risk merchant categories. The same published wording says that bank login details are not stored. These are supplier statements to be reconfirmed on the live site and retained with the inspection file; they are not legal advice and should not be presented as an audit conclusion. Where supported, the checkout may list major UK banks, but availability can change and should not be assumed.
For any supplier entry in the log, record the catalogue page used at the time of order and the payment wording shown at checkout. Where Research Sciences is the supplier under review, the public catalogue can be checked through Uk peptides; retain the relevant page or screenshot with the month of access, and confirm the batch CoA that accompanies the specific delivery. Marketing lines such as “24hr UK Delivery” should be read as published promotional wording rather than a guaranteed arrival promise; the site’s own dispatch terms and tracking information should be checked at the time of ordering. Before the inspection, export the reconciled row, attach the supplier page evidence and file the batch CoA with the payment confirmation so the record can be produced as one package.
