The problem BlockReceipt solves

The Problem It Solves

1. Stopping the "Silent Killer" of Indonesian SMEs Corporate fraud is not just an annoyance; it is a systemic economic drain. In Indonesia alone, fraud costs the economy Rp 89 Trillion annually. For Small and Medium Enterprises (SMEs), this is often fatal: 1 in 3 businesses fail within their first 5 years , with a significant portion of these failures traced directly to hidden purchasing fraud that erodes profitability.
2. Closing the "18-Month" Detection Gap Traditional auditing is reactive and slow. On average, internal fraud schemes operate for 18 months before they are discovered. By the time the fraud is caught, the damage is already done, costing businesses an average of Rp 500 Million per incident. Existing tools like Excel or centralized accounting software are vulnerable because data can be altered retroactively by bad actors.
3. From "Trust Me" to "Cryptographic Truth" BlockReceipt replaces manual trust with cryptographic verification.

• Tamper-Proof Records: We solve the problem of data manipulation. Once our AI extracts the data and the smart contract locks it , the record is immutable. A dishonest employee cannot go back and change a "10" to a "100" to embezzle the difference.
• Privacy-Preserving Verification: We solve the dilemma of transparency vs. privacy. Using ZK Proof Verification , companies can prove the validity of their transaction data to auditors or partners without exposing sensitive vendor agreements or trade secrets.
• Automated Compliance: We eliminate the bottleneck of manual verification. Smart contracts execute workflow approvals automatically based on pre-defined rules, ensuring that no transaction bypasses company policy.

In short: BlockReceipt transforms a receipt from a piece of paper into forensic evidence, reducing the fraud detection timeline from 18 months to minutes.

Challenges I ran into

1. The Paradox of Public Transparency vs. Corporate Privacy
   The Hurdle: Our value proposition relies on the "Transparency" and "Immutability" of the Lisk blockchain. However, our target customers (SMEs and Enterprises) cannot have their sensitive vendor agreements, pricing strategies, and purchase details exposed on a public block explorer. We hit a wall: How do we prove a transaction happened on-chain without doxxing our client's internal finances?

The Solution: We re-architected the data flow to separate Verification from Storage.

Off-Chain: The sensitive PDF and extracted data are encrypted and stored on IPFS.

On-Chain: We generate a cryptographic hash (Digital Fingerprint) of the data. The Lisk Smart Contract only stores this Hash, the Timestamp, and the Approver's Address.

Result: This allows auditors to verify the integrity of the receipt (by hashing the local file and comparing it to the on-chain record) without ever exposing the raw data to the public network.

2. "Garbage In, Immutable Garbage Out" (AI vs. Smart Contracts)
   The Hurdle: Our AI OCR engine performs at "over 95% accuracy". While high, this leaves a 5% margin for error. In a standard app, you just edit the database. But in our model, we promised a "Smart Contract Lock" that "digitally locks critical data". If the AI misreads a 1 as a 7 and we write that to the blockchain immediately, we have created an immutable error, destroying user trust.

The Solution: We implemented a "Two-Phase Commit" pattern in our Smart Contract logic:

Phase 1 (Soft State): The AI extracts the data and presents it to the user.

Phase 2 (Hard Lock): We require an explicit cryptographic signature from the authorized user (Collaborator/Manager ) to confirm the data is correct. Only after this signature does the smart contract execute the lock() function. This ensures that only verified, human-approved data becomes immutable.

3. UX Friction for Non-Web3 Natives
   The Hurdle: Our target market is traditional businesses ("Non-VAT Companies," "SMEs"). They are used to Excel, not MetaMask. Forcing a wallet signature popup for every single receipt upload would destroy the user experience and increase "Switching Cost", which we claimed would be low.

The Solution: We utilized the efficiency of the Lisk L2 network to batch verify transactions where possible. For the "Professional" and "Enterprise" tiers , we designed the system to allow for session keys or delegated signing, where the user logs in securely (e.g., "Continue with Google" ), and the backend manages the blockchain interaction transparently, maintaining the "Seamless migration" promise.