> ## Documentation Index
> Fetch the complete documentation index at: https://docs.laso.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Automated payroll

> How we run automated payroll on Laso.

# Overview

We use Laso Finance agentic tooling to build Laso Finance.

Setting up and running payroll is a clear case where agentic tooling made a faster and safer process than humans. Twice a month, a persistent [Hermes Cloud Agent](https://portal.nousresearch.com/cloud):

1. Calculates payroll.
2. Verifies amounts with founder.
3. Pays on confirmation.
4. Generates, stores and sends payment records.
5. Updates our internal ledger.

It's a great example of keeping Laso Finance at the core of your agentic financial workflows, while extending functionality with external services.

#### *Tools Used*

| Tool | Type | Role in the flow |
| - | - | - |
| [Managed Agent Wallet](https://docs.laso.finance/guides/managed-agent-wallet.md) | Laso | Holds the USDC the agent pays from |
| [x402 Transfer](https://docs.laso.finance/api-reference/agent-wallet/pay-an-x402-endpoint-from-the-managed-wallet.md) | Laso | Pays x402 endpoints from the managed wallet |
| [Bank transfers](https://docs.laso.finance/guides/agent-bank-accounts.md) | Laso | Sends payouts to employee and contractor bank accounts |
| [Hermes Cloud Agent](https://portal.nousresearch.com/cloud) | External | The persistent agent that runs the twice-monthly cycle |
| [Harvest](https://www.getharvest.com/) | External | Time tracking, the source of billable hours |
| [AgentMail](https://agentmail.to) | External | Sends payment records and confirmation email |
| [Firebase MCP](https://firebase.google.com/docs/cli/mcp-server) | External | Reads and updates the internal ledger |
| [Mana](https://mymana.xyz/) | External | Stores generated payment records |

## Payroll Generation

The first step is calculating and confirming accuracy of total pay. Laso Finance employees and contractors track time in [Harvest](https://www.getharvest.com/), a time-tracking software.

**1. Retrieve hours**

Connects to [Harvest API](https://help.getharvest.com/api-v2/), collect
timesheet entries for all employees/contractors during the pay period.

**2. Calculate pay**

Pulls each recipients rate using [Firebase
MCP](https://firebase.google.com/docs/cli/mcp-server), calculating total pay
with hours and timesheet records.

**3. Draft the record**

Generates a pending payment record email and PDF, noting total time, pay,
and individual entries for the pay period.

**4. Send for confirmation**

Sends to founder via [Telegram](https://core.telegram.org/bots) with draft
email and PDF attachment for confirmation.

**5. Founder confirmation or denial**

In Telegram, founder can confirm, starting the next process. If payments
need editing, they are prompted within the Telegram chat and results are
re-reviewed.

![Telegram message from the payroll agent listing verified artifacts, confirming no funds were transferred and no email was sent, and asking the founder to reply YES to authorize the transfer. The founder replies YES.](https://mintcdn.com/lasofinance/X0J7eOOIVhC-rez3/images/confirmation.png?fit=max\&auto=format\&n=X0J7eOOIVhC-rez3\&q=85\&s=e4ae4704e7aba5631400a739efce5674)

The agent lists what it verified, states plainly that no funds moved yet, and waits for the founder to reply YES.

## Sending payment

Once the founder confirms the payment records, the agent starts sending payments. It varies payment rail by recipient preference.

All payments are funded by the agent's [Laso Solana wallet](https://docs.laso.finance/guides/agent-quick-start.md).

**1. Read the pay route**

The agent uses [Firebase Firestore
MCP](https://firebase.google.com/docs/cli/mcp-server) to read pay route data
and preferences for each recipient.

**2. Pay by the matching rail**

Based on that data, it either sends [USDC on
Solana](https://docs.laso.finance/api-reference/agent-wallet/send-usdc-from-the-managed-wallet),
bridges from Solana USDC to an external [Mana](https://mymana.xyz/) Base
USDC address, or sends a [bank
transfer](https://docs.laso.finance/api-reference/banking/send-a-bank-payout) all through Laso
services.

> [!TIP]
>
> Each recipient is paid on the rail they picked, from one wallet. Adding a new
> rail means adding a pay route to the recipient's record, not changing the
> payroll run itself.

## Post-payment

Once that payment is complete, the agent completes the loop by notifying recipients, and updating internal records.

**1. Extract payment confirmation**

For onchain payments, constructs a block explorer link. For bank transfers,
extracts the payment ID.

**2. Attach proof of payment**

Updates its draft payment record email and PDF attachment with that
confirmation.

**3. Notify the recipient**

Sends email to the recipient via [AgentMail](https://agentmail.to)
confirming the change.

**4. Update the ledger**

Debits the Laso Finance internal ledger with the corresponding amount,
transaction hash / ID, and link to the record of hours worked.

![Telegram message from the payroll agent headed Payroll completed, listing the destination, transfer ID, and a View on Solscan link, noting the transfer was independently verified on Solana. Below, an Email sent and verified section lists the recipient, CC, PDF filename for the 2026-08-16 through 2026-08-31 pay period, and message ID, followed by a Solscan preview card showing a 1,571.1 USDC transfer.](https://mintcdn.com/lasofinance/X0J7eOOIVhC-rez3/images/payroll-confirmation.png?fit=max\&auto=format\&n=X0J7eOOIVhC-rez3\&q=85\&s=3312d3e2ab39de603b0ef709cc026537)

The closing report: transfer ID and Solscan link for the payment, the recipients and PDF of the email it sent, and confirmation that it read the sent message back to check both.

By connecting our agent to Laso Finance and a few external services, a complicated external process is brought in-house. Legible, controllable, and safe.

## Build this yourself

> [card] [Managed agent wallet](https://docs.laso.finance/guides/managed-agent-wallet.md)
>
> Provision the wallet the payroll run pays from.

> [card] [Bank accounts](https://docs.laso.finance/guides/agent-bank-accounts.md)
>
> Set up the banking profile behind bank payouts.

> [card] [Send a bank payment](https://docs.laso.finance/guides/send-bank-payment.md)
>
> Register a payee once, then pay them by ACH.

> [card] [MCP server](https://docs.laso.finance/guides/mcp-server.md)
>
> Connect your own agent to these endpoints.

## See also

> [card] [Self-funding PPC agent](https://docs.laso.finance/how-we-use/self-funding-ppc-agent.md)
>
> An agent paid in contribution margin into its own Laso wallet and card.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.