ATL282: Difference between revisions
mNo edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[File:ATL282.jpg|thumb|Blockchain in Modern ERP]] | |||
= ATL282 — Blockchain Enabled ERP = | = ATL282 — Blockchain Enabled ERP = | ||
'''Program:''' Accounting Technology Lab | '''Program:''' Accounting Technology Lab | ||
| Line 55: | Line 57: | ||
* Should firms stay with traditional accounting software or begin learning the new generation of ledgers? ATL282 explains why the answer may depend on future control requirements. #AccountingSoftware #CAS | * Should firms stay with traditional accounting software or begin learning the new generation of ledgers? ATL282 explains why the answer may depend on future control requirements. #AccountingSoftware #CAS | ||
* Listen to ATL282 for a practical discussion of blockchain-enabled ERP, tamper-evident audit trails, shared transactions, and stronger data integrity. #AccountingTechnologyLab #Blockchain | * Listen to ATL282 for a practical discussion of blockchain-enabled ERP, tamper-evident audit trails, shared transactions, and stronger data integrity. #AccountingTechnologyLab #Blockchain | ||
== Products, Services, Companies, and Social Accounts == | |||
{| class="wikitable sortable" | |||
{| class="wikitable" | ! Company or product | ||
! | ! Role in the discussion | ||
| | ! Social account | ||
|- | |||
| Microsoft Dynamics | |||
| ERP example used in the discussion of non-deletable entries, reversals, and enterprise controls | |||
| Not verified | |||
|- | |||
| Oracle Fusion | |||
| Example involving integrated intercompany reconciliation and enterprise financial and supply-chain capabilities | |||
| Not verified | |||
|- | |||
| SAP | |||
| Enterprise platform discussed in connection with ERP controls, food provenance, and supply-chain records | |||
| Not verified | |||
|- | |||
| IBM | |||
| Discussed with SAP in connection with food provenance and recall applications | |||
| Not verified | |||
|- | |- | ||
| Workday | |||
| | | Example involving verifiable professional credentials and payroll-related controls | ||
| Not verified | |||
|- | |- | ||
| Infor | |||
| | | Enterprise application provider identified among the implementation scenarios | ||
| Not verified | |||
|- | |- | ||
| Sage Intacct | |||
| | | Midmarket accounting platform cited when discussing capabilities moving beyond tier-one ERP systems | ||
| Not verified | |||
|- | |- | ||
| Epicor | |||
| | | ERP provider identified among the implementation examples | ||
| Not verified | |||
|- | |- | ||
| QAD | |||
| | | Manufacturing ERP provider identified among the implementation examples | ||
| Not verified | |||
|- | |- | ||
| BILL | |||
| | | Payables platform used to illustrate communication between organizations and visibility into pending transactions | ||
| Not verified | |||
|} | |} | ||
== Suggested Hashtags == | == Suggested Hashtags == | ||
#AccountingTechnologyLab #ATL282 #Blockchain #DistributedLedger #DLT #ERP #AccountingTechnology #AuditTech #InternalControls #DataIntegrity #FinTech #ClientAccountingServices | #AccountingTechnologyLab #ATL282 #Blockchain #DistributedLedger #DLT #ERP #AccountingTechnology #AuditTech #InternalControls #DataIntegrity #FinTech #ClientAccountingServices | ||
Latest revision as of 13:27, 6 November 2026

ATL282 — Blockchain Enabled ERP
Program: Accounting Technology Lab
Release date: November 7, 2026
Hosts: Randy Johnston and Brian F. Tankersley, CPA.CITP, CGMA
Runtime: 25:30
Primary topic: Cryptographic controls, distributed-ledger audit trails, shared transaction records, and the movement of blockchain-enabled ERP capabilities into smaller accounting systems
200-Word Episode Summary
Blockchain may have vanished from the technology hype cycle, but its strongest accounting use case is becoming practical: protecting ERP records with cryptographic evidence. Randy Johnston and Brian Tankersley explain why conventional relational databases leave a control gap—administrators can alter tables directly, while each party usually sees only its own side of a transaction. The hosts examine how distributed-ledger technology can make changes tamper evident without replacing the ERP. Journal entries can be grouped into a Merkle tree, reduced to a root hash, and anchored to an external ledger with a timestamp. A sidecar design can capture write-ahead logs while the core system continues processing transactions in SQL. Shared records could also keep one company’s accounts payable aligned with another company’s accounts receivable and support automated contract checks, reconciliations, and payment release. Examples include pharmaceutical traceability, food provenance and recall controls, professional-credential verification, payroll compliance, intercompany reconciliation, and customs clearance. The discussion also considers cryptographic privacy, through which a party may prove compliance without disclosing every commercial detail. Although many examples involve enterprise platforms, Randy and Brian expect these controls to move down-market. Their conclusion: blockchain-enabled audit trails could give smaller accounting systems substantially stronger data integrity, much as electronic signatures moved from specialized technology to an everyday business control.
Key Takeaways
Conventional relational ERP systems may allow privileged administrators to modify database tables directly, creating a control and audit-trail risk. Distributed-ledger technology can make unauthorized changes tamper evident by exposing broken cryptographic hashes. Merkle trees can consolidate batches of ERP transactions into a root hash that is anchored to an external ledger with an immutable timestamp. A sidecar architecture can capture write-ahead logs and create cryptographic proofs without replacing the ERP database or materially burdening transaction processing. Shared ledgers could align one organization’s accounts payable with another organization’s accounts receivable, reducing reconciliation delays and disputes. Smart-contract-style controls could match purchase orders and invoices, perform contract checks, and release payments when defined conditions are satisfied. Cryptographic proofs may help organizations demonstrate compliance with covenants, sanctions requirements, or other rules while limiting disclosure of sensitive commercial information. Potential applications include drug traceability, food recalls, professional credentials, payroll compliance, intercompany accounting, and customs clearance. Enterprise platforms are demonstrating these capabilities first, but the hosts expect stronger cryptographic controls to appear in smaller accounting systems and client accounting services platforms.
Catchy Quotes and Video Locations
- 00:01:24–00:01:33 — Brian F. Tankersley: “In a standard relational ERP, anybody that’s a system administrator can modify the database tables directly.”
- 00:02:15–00:02:27 — Brian F. Tankersley: “With standard relational ERP, you can’t see the other side of the transaction. You don’t know if it’s a real transaction or not.”
- 00:05:03–00:05:08 — Brian F. Tankersley: “It may not be tamper proof, but it’s going to be tamper evident.”
- 00:05:59–00:06:13 — Brian F. Tankersley: “It aggregates all of those kind of into a batch of transactions into one root hash, and then that’s anchored on chain with an immutable timestamp.”
- 00:07:24–00:07:42 — Brian F. Tankersley: “The enterprise sidecar architecture…captures the write-ahead logs without taxing the ERP performance.”
- 00:12:41–00:12:55 — Brian F. Tankersley: “We can mathematically verify regulatory compliance, debt covenant ratios, or sanctions checks without revealing unit costs or supplier identities.”
- 00:23:30–00:23:58 — Randy Johnston: “We’re going to go from siloed databases…to locking the audit trail down with cryptographic certainty.”
- 00:25:02–00:25:20 — Brian F. Tankersley: “We can now have much higher certainty surrounding the data integrity of what we have than we’ve ever had before.”
20 Social Media Posts
- Blockchain may be out of the hype cycle, but its most useful accounting application could be arriving now: stronger ERP audit trails backed by cryptographic evidence. #AccountingTechnology #Blockchain
- A conventional ERP administrator may be able to alter database tables directly. ATL282 examines how distributed-ledger controls can make those changes visible. #ERP #InternalControls
- “Tamper proof” is usually too strong. “Tamper evident” is the better description of what cryptographic ERP controls can deliver. #Audit #DataIntegrity
- What happens when an ERP transaction changes after the fact? A DLT-anchored audit trail can expose the change through a cascading failure of its hashes. #Blockchain #ERP
- Merkle trees can turn a batch of accounting transactions into one root hash, then anchor that proof to an external ledger with a timestamp. #AccountingTech #DLT
- Blockchain-enabled ERP does not necessarily require replacing the database. A sidecar can capture write-ahead logs while the core system continues using SQL. #ERP #Technology
- Imagine one company’s accounts payable and another company’s accounts receivable sharing a synchronized record. Reconciliation could become faster and more reliable. #Accounting #Automation
- Shared ledgers could support purchase-order matching, invoice validation, dispute handling, and automatic payment release. #AccountsPayable #FinTech
- Can an organization prove compliance without revealing every confidential business detail? Cryptographic privacy may offer a path. #Compliance #Cybersecurity
- Drug traceability is more than an inventory problem. Reliable chain-of-custody records can help identify fraudulent or unauthorized pharmaceutical lots. #SupplyChain #Blockchain
- Food provenance systems can combine source records, timestamps, locations, and refrigeration telemetry to identify and lock suspect batches faster. #FoodSafety #DLT
- Cryptographically verifiable professional credentials could help hospitals and other employers confirm licenses more quickly. #WorkforceTech #Compliance
- Payroll rules, employment histories, and labor-audit evidence are additional candidates for tamper-evident records. #Payroll #InternalControls
- Shared cargo records could improve tariff calculations and customs clearance for time-sensitive shipments. #SupplyChain #ERP
- Enterprise accounting platforms are testing controls that may eventually reach smaller organizations and client accounting services practices. #CAS #AccountingTechnology
- Blockchain-enabled ERP and AI-powered ledgers are related trends, but they are not the same thing. One focuses on record integrity; the other may automate analysis and processing. #AI #Blockchain
- Better audit evidence starts with better system design. Cryptographic proofs could help auditors test whether transaction records changed after posting. #AuditTech #Assurance
- Electronic signatures once felt specialized. Today they are routine. Cryptographic ERP controls may follow a similar path. #DigitalTransformation #ERP
- Should firms stay with traditional accounting software or begin learning the new generation of ledgers? ATL282 explains why the answer may depend on future control requirements. #AccountingSoftware #CAS
- Listen to ATL282 for a practical discussion of blockchain-enabled ERP, tamper-evident audit trails, shared transactions, and stronger data integrity. #AccountingTechnologyLab #Blockchain
Products, Services, Companies, and Social Accounts
| Company or product | Role in the discussion | Social account |
|---|---|---|
| Microsoft Dynamics | ERP example used in the discussion of non-deletable entries, reversals, and enterprise controls | Not verified |
| Oracle Fusion | Example involving integrated intercompany reconciliation and enterprise financial and supply-chain capabilities | Not verified |
| SAP | Enterprise platform discussed in connection with ERP controls, food provenance, and supply-chain records | Not verified |
| IBM | Discussed with SAP in connection with food provenance and recall applications | Not verified |
| Workday | Example involving verifiable professional credentials and payroll-related controls | Not verified |
| Infor | Enterprise application provider identified among the implementation scenarios | Not verified |
| Sage Intacct | Midmarket accounting platform cited when discussing capabilities moving beyond tier-one ERP systems | Not verified |
| Epicor | ERP provider identified among the implementation examples | Not verified |
| QAD | Manufacturing ERP provider identified among the implementation examples | Not verified |
| BILL | Payables platform used to illustrate communication between organizations and visibility into pending transactions | Not verified |
Suggested Hashtags
- AccountingTechnologyLab #ATL282 #Blockchain #DistributedLedger #DLT #ERP #AccountingTechnology #AuditTech #InternalControls #DataIntegrity #FinTech #ClientAccountingServices
