# Invoicing \[Request payment into the team's accounts, in crypto or by bank transfer]

An invoice requests a single amount of a single token into one of the team's accounts (there are no line items), payable in crypto or, if enabled, [by bank transfer](#pay-by-bank). Invoicing is free: no fee on issuing or on crypto payments. Only [Owners](/teams/roles) create and manage invoices; any member can view them.

See also [Recurring](/invoicing/recurring), [Paying](/invoicing/paying), and [Tracking](/invoicing/tracking).

## Issuing

From the *Invoices* page, select *Create*:

1. Enter the payee and payer names, the amount and token, and the issue and due dates. A memo and file attachments are optional.
2. Pick the receiving account: any of your [accounts](/accounts), including an [automation](/accounts#automation-accounts)'s deposit address.
3. The payer's email is optional. With it, the invoice is emailed on creation; without it, you get the invoice link to share yourself.

Invoice numbers increment automatically per team.

## Pay-by-bank

Pay-by-bank lets the invoicee pay in fiat from their bank account. It requires the team to have [banking](/banking) set up with a virtual account in the matching currency, and the requested token to be:

* **USDC** on Base, Ethereum Mainnet, or Tempo, payable in USD
* **EURC** on Base or Ethereum Mainnet, payable in EUR

Turn on the *Allow pay by bank* toggle that appears in the create form. The payer covers a 0.25% processing fee, added to the bank amount owed.

Bank payments settle to the account and network configured in the bank settings, even when the invoice specifies a different account or network.

## Programmatic access

Invoicing is web-only today: the [CLI / MCP](/introduction/agents) has no invoice commands.