- Borrower
- Drexel Burnham Lambert
- Lender
- Drexel Burnham Lambert
Receivables audit demo
Find duplicate pledges and compare transaction fingerprints.
Try the example records. Changes stay on this page; reset or refresh to start again.
Step 1Check collateral
Is any collateral pledged twice?
Review receivables with more than one active pledge.
1 receivable needs review · 2 receivables checked
| Collateral | Active pledges | Result | Review |
|---|---|---|---|
| AR-001 | 2 | Needs review | |
| AR-002 | 1 | No duplicate |
How this audit works
Two or more active records for the same collateral trigger a review, including repeats for the same lender. Released records are excluded. A clear result only covers entries in this ledger.
Collateral IDs ignore letter case and extra spaces. With no active records, the check cannot establish whether a receivable exists or is available.
Step 2Compare records and hashes
Do both records agree?
Match 10 fields across the borrower’s and lender’s copies. Date and time use UTC.
Comparing fingerprints
Calculating SHA-256 for both standardized records.
| Transaction field | Borrower’s record | Lender’s record |
|---|---|---|
| Parties | ||
| Lender name | Drexel Burnham Lambert | Drexel Burnham Lambert |
| Client name | NVIDIA Corporation | NVIDIA Corporation |
| Date and time | ||
| Transaction date (UTC) | 2026-09-15 | 2026-09-15 |
| Transaction time (UTC) | 09:30:00 UTC | 09:30:00 UTC |
| Collateral details | ||
| Collateral type | Term Loan B (TLB) | Term Loan B (TLB) |
| Quantity | 1000 | 1000 |
| Unit price | 100 | 100 |
| Currency | USD | USD |
| Payment details | ||
| Payment due date | 2026-10-15 | 2026-10-15 |
| Payment terms | Net 30 | Net 30 |
Parties
- Borrower
- NVIDIA Corporation
- Lender
- NVIDIA Corporation
Date and time
- Borrower
- 2026-09-15
- Lender
- 2026-09-15
- Borrower
- 09:30:00 UTC
- Lender
- 09:30:00 UTC
Collateral details
- Borrower
- Term Loan B (TLB)
- Lender
- Term Loan B (TLB)
- Borrower
- 1000
- Lender
- 1000
- Borrower
- 100
- Lender
- 100
- Borrower
- USD
- Lender
- USD
Payment details
- Borrower
- 2026-10-15
- Lender
- 2026-10-15
- Borrower
- Net 30
- Lender
- Net 30
Show SHA-256 inputs and hashes
This demonstrates hash-based change detection, one building block of blockchain systems. The SHA-256 fingerprints are calculated for real; the ledger is an editable example.
Borrower
Show SHA-256 input and hash
STANDARDIZED STRING
DREXEL BURNHAM LAMBERT|NVIDIA CORPORATION|2026-09-15|09:30:00Z|TERM LOAN B (TLB)|1000|100|USD|2026-10-15|NET 30SHA-256Calculating…Lender
Show SHA-256 input and hash
STANDARDIZED STRING
DREXEL BURNHAM LAMBERT|NVIDIA CORPORATION|2026-09-15|09:30:00Z|TERM LOAN B (TLB)|1000|100|USD|2026-10-15|NET 30SHA-256Calculating…Matching SHA-256 fingerprints show that the standardized records agree. They do not independently verify the pledge. Record-owner labels, transaction IDs, collateral IDs and ledger status are excluded from this fingerprint.
Date and time are separate fields: YYYY-MM-DD and HH:mm:ssZ. Z means UTC (UTC+00:00); every visitor sees the same time. Text is uppercased, trimmed and repeated spaces collapsed. Quantity and unit price keep up to six decimal places; extra leading and trailing zeros are removed. Ten plain ASCII fields are joined with | in table order before hashing. Payment due date is a calendar date; payment terms are compared as text and do not calculate it automatically.
Run manipulation test
Change one value and compare the original and test SHA-256 fingerprints.
USD
The other nine fields use the borrower’s original record. The ledger stays unchanged.
Calculating fingerprints1 of 10 field changed
Original unit price100 USD
Test unit price150 USD
Original SHA-256
Calculating…Test SHA-256
Calculating…Show SHA-256 input and hash
STANDARDIZED STRING
DREXEL BURNHAM LAMBERT|NVIDIA CORPORATION|2026-09-15|09:30:00Z|TERM LOAN B (TLB)|1000|150|USD|2026-10-15|NET 30SHA-256Calculating…Step 3Review the pledge ledger
Pledge ledger
Add or update the records used in your collateral checks.
| Transaction | Collateral | Client / lender | Calculated total | Status | Edit |
|---|---|---|---|---|---|
| TX-0012026-09-15 09:30:00 UTC | NVIDIA CorporationDrexel Burnham Lambert | 100,000.00 USD | Active | ||
| TX-0022026-09-15 09:45:00 UTC | NVIDIA CorporationLehman Brothers | 75,000.00 USD | Active | ||
| TX-0032026-09-15 10:00:00 UTC | NVIDIA CorporationLehman Brothers | 100,000.00 USD | Active |
TX-0012026-09-15 · 09:30:00 UTC
Active- Collateral
- Client / lender
- NVIDIA Corporation · Drexel Burnham Lambert
- Calculated total
- 100,000.00 USD
TX-0022026-09-15 · 09:45:00 UTC
Active- Collateral
- Client / lender
- NVIDIA Corporation · Lehman Brothers
- Calculated total
- 75,000.00 USD
TX-0032026-09-15 · 10:00:00 UTC
Active- Collateral
- Client / lender
- NVIDIA Corporation · Lehman Brothers
- Calculated total
- 100,000.00 USD
3 records · 3 active275,000.00 USD active
How ledger records affect the audit
The ledger and counterparty comparison are separate. Entering a comparison record does not add a ledger entry. Every ledger row is included in the collateral audit.
This is an editable proof of concept, without immutable history or a blockchain connection. The example adapts the Blockchain Audit POC workbook with ten classroom matching fields. Calculated totals are quantity × unit price, rounded to two decimal places for display in this demo. Totals are not an additional matched field; no tax, discount or exchange rate is applied.