The problem SuiRoll solves

The Problem Suiroll Solves

Paying contractors involves more than sending money. Teams must collect invoices, calculate adjustments, verify wallet addresses, approve payments, and confirm that everyone received the correct amount.

For small teams that already hold stablecoins, this work can be scattered across spreadsheets, messaging threads, wallets, and blockchain explorers. The operator must manually connect what should be paid with what actually settled.

This creates four recurring problems:

• Repeated manual work: Moving payment information between tools takes time and introduces opportunities for mistakes.
• Payment errors: Duplicate invoices, conflicting amounts, and unexpected adjustments can go unnoticed before authorization.
• Fragmented execution: Sending individual transfers means repeated actions and more transactions to track.
• Uncertain outcomes: A submitted transaction still needs confirmation and reconciliation. Retrying without checking can risk duplicate payment.

How Suiroll Helps

Suiroll connects contractor-payroll preparation, review, authorization, and settlement in one workflow:

1. Prepare: Save contractor details and import CSV/XLSX payroll files or enter payments manually.
2. Review: Calculate exact amounts, exclude duplicate invoices, block conflicting inputs, and flag unusual increases.
3. Approve: Review the payment plan, check readiness, and authorize it with the treasury wallet.
4. Pay: Execute multiple contractor payments through one Sui Programmable Transaction Block.
5. Reconcile: Verify settlement against the approved plan and retain exportable payment records.

The user controls authorization. Suiroll provides checks and evidence to support that decision.

Why Sui

Sui’s Programmable Transaction Blocks allow the payroll transfers to execute atomically: the batch’s transfers complete together or none complete. Failed transactions can still incur gas costs.

Suiroll uses on-chain evidence to verify the result before marking payroll Paid & reconciled, connecting the original payment plan to confirmed execution.

Who It Serves

Our initial customers are small Sui ecosystem teams, agencies, and distributed businesses that already hold stablecoins and pay contractors willing to receive them.

For founders and finance operators, Suiroll offers a repeatable process with less tool switching, clearer payment controls, and traceable records.

The current prototype demonstrates this workflow on Sui Testnet with testnet USDC. It focuses on contractor payouts, not statutory payroll, tax filing, or bank withdrawals.

Suiroll turns a contractor spreadsheet into an approved, verified stablecoin payday.

Challenges we ran into

Challenges We Ran Into

Although we had explored blockchain before, building Suiroll was our first time bringing Sui, wallet integration, and payroll operations together in a complete application. Turning our existing knowledge into a reliable payment workflow presented several challenges.

Sui and wallet integration

Connecting a wallet was only the beginning. We needed to handle transaction construction, gas fees, signature verification, and settlement confirmation.

One bug appeared after wallet approval: the payroll was approved, but submission failed. We traced it to social-login signature verification, which required a configured Sui client to validate zkLogin signatures. We corrected the integration and added regression tests.

Reliable payroll execution

Sending tokens was not enough—we also needed exact calculations, duplicate-invoice protection, and safe recovery from network errors.

We implemented integer-based calculations, database-backed invoice reservations, and settlement verification. Separating uncertain transaction outcomes from confirmed failures helped prevent unsafe payment retries.

Connecting the full workflow

Integrating the frontend, Supabase, AI-assisted imports, and Sui introduced issues with database setup, unexpected AI response formats, and development-server state.

We resolved these through documentation, debugging, isolated integration checks, and workflow testing. We ultimately completed a three-recipient testnet payroll and reconciled its payments.

The biggest lesson was turning separate technologies into one dependable experience, where every step from importing payroll to confirming payment works together.