Blockchain in Supply Chain Management: What It Proves, and What It Does Not

A distributed ledger proves one thing very well: that a record has not been altered since it was written. That is a narrow and genuinely useful guarantee.

It proves nothing at all about whether the record was true when it was written. A falsehood entered into an immutable ledger becomes a permanently tamper-evident falsehood. Almost every disappointing blockchain supply chain pilot has failed at that seam, between the physical world and the first keystroke, rather than anywhere in the cryptography.

For an Ottawa business evaluating this, the question worth asking is not whether the technology works. It is which of your existing obligations it discharges, and which it leaves exactly where they were.

What the ledger actually gives you

The gap in the right-hand column has a name in the field: the oracle problem. Every claim about the physical world enters the system through a sensor, a scanner, or a person, and the ledger inherits whatever accuracy that source had. An auditor meets the same wall from the other side, which is why an immutable ledger evidences existence well and completeness not at all. Sealed containers, tamper-evident tags and calibrated IoT sensors narrow the gap. They do not close it.

The obligations it does not remove

This is where most business cases quietly overstate the benefit.

The CRA still wants its own records, in its own formats

If your books are electronic, you must keep them in an electronically readable format for six years from the end of the last year they relate to, and you must be able to produce a copy the CRA can process on its own equipment. Keeping a paper printout does not discharge the electronic obligation, and neither does an archive that can only be read by the application that created it. That is the core of the CRA’s electronic record keeping circular, and it is the requirement a proprietary or consortium ledger is most likely to fail.

Before committing to a platform, ask the vendor a blunt question: can this system export the complete transaction history, with the supporting detail attached, into a common data interchange format an auditor can analyse. If the answer is a dashboard, the answer is no. See digital record keeping and the CRA and record retention in Canada.

GST/HST input tax credits still need supplier information, not hashes

To claim an input tax credit, you need prescribed information from the supplier, and how much depends on the size of the transaction. The thresholds are $100 and $500, raised from the long-standing $30 and $150 on 20 April 2021, and a great deal of accounting commentary has not caught up. Above the higher threshold you need, among other things, the supplier’s GST/HST registration number and a description sufficient to identify the supply. The full chart is in the documentary requirements for claiming input tax credits.

A ledger entry proving that goods moved from A to B is not that information. It is also worth confirming that a supplier’s registration number is live using the CRA’s GST/HST registry, because an ITC claimed against a number that was never registered is denied on review no matter how well documented the shipment was. The mechanics are in GST/HST input tax credits.

Where a shared ledger does earn its keep here is in matching: three-way reconciliation of purchase order, receipt and invoice across two organisations that both trust the same record. That is a real reduction in dispute handling and in the reconciliation work that precedes every close.

Food traceability rules are prescriptive about content, not technology

Under the Safe Food for Canadians Regulations, a business must be able to trace food one step back and one step forward, with specified information and records accessible in Canada. Retailers must retain trace-back documents for two years after the sale. Electronic records can sit on a server outside Canada provided they remain accessible from within it. The requirements are set out in the CFIA’s traceability requirements.

Notice what the rule demands: specified data, retained, retrievable. A distributed ledger can be an excellent way to satisfy that, because it makes the handoff records shared rather than reconciled after the fact. It is not itself compliance, and a system that captures elegant provenance while omitting a required data element is a failed system with a good user interface.

Where the return actually comes from

Strip away the framing and the credible savings in a supply chain ledger are narrow and specific:

• Reconciliation labour. Two parties disputing what was shipped, when, and in what condition is expensive. A single shared record removes the dispute rather than resolving it
• Working capital timing. Payment released on a verified delivery event rather than on a monthly invoice cycle shortens the cash conversion cycle at both ends. This is often the largest genuine benefit and the one least discussed
• Recall scope. The cost of a recall is driven by how precisely you can identify affected lots. Narrowing a recall from a production week to a specific pallet is a direct, measurable saving
• Counterfeit exposure. Only in categories where counterfeiting is a real loss, which is fewer categories than vendor material implies

Against that, the costs are ordinary and predictable: integration with the ERP you already run, per-transaction network cost, the tagging or sensor hardware, and the participation of counterparties who have no obligation to join. That last one kills more pilots than any technical constraint. A traceability network with one participant is a database with unusual overheads.

Software and hardware acquired for the project are not a single deduction either. Systems software and general-purpose computer equipment fall in a different capital cost allowance class from custom application software, and the timing of the deduction affects the business case materially. See capital cost allowance explained.

A decision sequence worth following

1. Is the record disputed BETWEEN organisations?
   ├─ NO ──> a shared ledger solves a problem you do not have.
   │         A well-run database is cheaper and easier to audit.
   └─ YES
      │
2.    Will the counterparties actually join and enter data?
      ├─ NO ──> stop. Provenance with a gap in it proves nothing.
      └─ YES
         │
3.       How does data enter at the physical boundary?
         ├─ Manual keying ──> the ledger inherits that error rate.
         │                    Fix capture before fixing storage.
         └─ Sealed / sensor-verified ──> continue
            │
4.          Can the platform export a complete, auditor-readable
            history in a common interchange format?
            ├─ NO ──> it fails IC05-1R1. Do not sign.
            └─ YES ──> pilot on one product line, one supplier,
                       and measure reconciliation hours saved.

Step three is where honest projects slow down and where the value is decided. Step four is where an accountant should be in the room, because a system that cannot produce its own audit trail creates a compliance exposure that outlasts the pilot.

The summary worth keeping

Blockchain in supply chain management is a coordination technology, not a truth technology. It is worth real money where several organisations need to agree on one version of events and currently spend money disagreeing. It is overhead where a single company simply needs better internal records, which is the more common situation.

Whichever you choose, the CRA’s six-year electronically readable requirement, the GST/HST documentary rules and any sector traceability regime apply unchanged. Design for those first, then decide what the ledger adds.

If you are evaluating a traceability or supply chain platform and want the record-keeping and GST/HST implications assessed before you sign, that is worth a conversation first. Retrofitting an audit trail is considerably more expensive than specifying one.