Public demo on NEAR testnet. tUSDC is a zero-value test token. The demo data is shared: everyone signs in with the same demo accounts and sees the same runs.
Payroll for teams paying on NEAR

Run payroll with a clear approval trail.

Prepare a payroll batch, route it to the right reviewers, and verify every wallet payout on NEAR testnet. A vault contract releases funds only after the approvals your policy requires.

See how it works
  • Up to 1,000 rows per run
  • One or two approvers, enforced on-chain
  • Consolidated or detailed posting
November payroll
Version 1 · sentfund-payroll-sample-1000.csv
Sample data
56.69086tUSDC
Paid
1,000 recipientsTwo approvers in sequenceDetailed posting
  1. Approver 1
    Approved
  2. Approver 2
    Approved after step 1
RecipienttUSDC
Matthew Miller0.05
Sophia Young0.04
Patricia Miller0.03
+ 997 more
Wallet payouts1,000 / 1,000 paid
1,000 posting entries · same totalReleased by the vault contract
Upload

Drop in a 1,000-row file. Nothing is accepted until every row passes.

Use our Excel template or your own CSV or tab-delimited TXT. SentFund checks the whole file, keeps your row order and shows every problem with its row and column.

  • Exact money, no roundingSix decimals, totals computed on the server.
  • Regional Excel settings handledSemicolon-separated files are detected; comma decimals get a clear fix-it message.
  • Read-only review in file order50 rows per page with the source row number next to every payment.
sentfund-payroll-sample-1000.csv
93.9 KB · CSV · UTF-8
Validated
Rows
1,000
Exact total
56.69086
Currency
tUSDC
Errors
0
First rows of the review table, in file order
File rowNEAR accountReceiverAmount
2gjn-emp-0001.testnetMatthew Miller0.05
3gjn-emp-0002.testnetSophia Young0.04
4gjn-emp-0003.testnetPatricia Miller0.03
5gjn-emp-0004.testnetSusan White0.05
6gjn-emp-0005.testnetSteven Anderson0.06
Rows 1–5 of 1,000 · source row numbers from the filePage 1 of 20
Rejected file exampleRow 61: invalid NEAR account ID. Fix the file and upload it again.
How it works

From spreadsheet to verified payouts

Every run is an immutable version. What the approvers saw is exactly what the contract pays.

  1. Prepare

    Add rows by hand or upload up to 1,000 rows. Fix problems in the file, upload again, and the earlier version stays until a new one passes.

  2. Approve

    The run goes to one or two assigned reviewers, in sequence or in parallel. The vault contract checks every approval, so no one can skip a step or approve their own run.

  3. Pay and reconcile

    The vault reserves the total and pays each wallet in tUSDC. Reports show one consolidated entry or one entry per recipient, with matching totals.

Approval paths

The policy your admin picks is the policy the contract enforces

Each run keeps the reviewers and release mode it was submitted with, even if the admin changes the settings later.

One approver

For small teams. One reviewer approves, then the release worker pays automatically.

  1. Maker submits the run.
  2. Approver 1 approves.
  3. Automatic release: the vault contract pays recipients only after final approval.

Two in sequence

Approver 2 can only act after Approver 1 has approved on-chain.

  1. Maker submits the run.
  2. Approver 1 approves first, then Approver 2.
  3. Automatic release: the vault contract pays recipients only after final approval.

Two in parallel

Either reviewer can go first; both approvals are required. Here the maker releases the payment.

  1. Maker submits the run.
  2. Approver 1 and Approver 2 approve in any order; both approvals are required.
  3. Maker releases: the vault contract pays recipients only after final approval.
Posting modes

Same payouts, the accounting view you need

Recipients receive exactly the same amounts either way. Only the company ledger changes: one entry per run, or one per recipient.

Consolidated

1 company entry for 1,000 recipients

Consolidated posting example
ReferenceDescriptiontUSDC
SFD-NOV-0001November payroll56.69086
Total56.69086

Detailed

1,000 company entries, one per recipient

Detailed posting example
ReferenceDescriptiontUSDC
SFD-NOV-0001-0001Payout line 10.05
SFD-NOV-0001-0002Payout line 20.04
… 998 more lines …
Total56.69086
On-chain proof

Check every payout yourself on NEAR testnet

The vault and the tUSDC test token are live contracts. Every approval and payout is a public testnet transaction.

See a payroll run end to end

Sign in as the maker, an approver, the admin or an employee (Payroll Advance). Demo data only.