# Send invoices and get paid

> Bill a customer for one amount or line by line, with a discount, tax and a due date if you need them. Share its link or email it with its PDF, let them pay in full or in parts, and follow every payment.

Source: https://railbed.com/docs/user-guide/invoices/ · Updated: 2026-11-18 · Railbed user guide

For AI assistants: the index of every docs page, with the rules for an integration, is https://railbed.com/docs/llms.txt

## When to use an invoice

Use an invoice when you sell by quote, by phone or in person: one amount for a consultation or a custom order, a project with several parts, a retainer, a deposit and a balance, or a sale your team closed by hand. There is one kind of invoice: for a single amount, give it one line, and leave out what you don't need. It can add a discount and tax, have a due date, and let the customer pay in parts and add a tip.

Invoices made while setting up your account, in Railbed in Telegram, in [Railbed for Slack](https://railbed.com/docs/user-guide/slack.md), through the [API](https://railbed.com/docs/api/payment-links.md) or by an AI assistant are listed in **Invoices** too, and open their own page: [Invoices made in other apps](https://railbed.com/docs/user-guide/payment-links.md). To sell the same product to many buyers, use a [checkout page](https://railbed.com/docs/user-guide/checkout-pages.md).

An invoice never moves money itself. Each payment toward it is an ordinary payment: the customer chooses how to pay on Railbed's payment page, and the sale settles to your wallet like any other.

## Build an invoice

1. Check Test or Live mode, then open **Create** and choose **Invoice**, or choose **New invoice** in **Invoices**. The preview beside the form shows what your customer will see as you type.
2. Under **Bill to**, enter the customer's **Name** and **Email**. Start typing to pick one of your **Saved customers**. **Company**, **Phone** and a billing address are optional. The name and email are needed only for Railbed to email it: shared by its link, an invoice can go out without them, and the customer gives their email as they pay.
3. Under **Line items**, choose the **Currency** and add a line for each thing you're billing: a description, a quantity (hours can be `2.5`) and a price. **Add line** adds another, up to 50.
4. **Add discount** takes a percentage or a fixed amount off the subtotal. **Add tax** adds a rate, as a percentage of what's left after the discount, and a name such as `VAT`. The total updates as you type.
5. Under **When it's due**, choose **On receipt**, **7 days**, **14 days**, **30 days** or a date.
6. Under **How they can pay**, choose what fits the sale (below).
7. **More details** holds a **Reference or PO number**, a **Note to the customer**, your **Terms** and, if more than one person can own invoices, its **Owner**.
8. Under **Customer details**, choose what the customer fills in themselves besides their email: name, phone, date of birth or addresses, each **Don't ask**, **Optional** or **Required**. **More to ask** adds an email-list box or a question of your own (a PO number, for example). It works as on a checkout page: [Ask buyers for their details](https://railbed.com/docs/user-guide/checkout-pages.md#ask-buyers-for-their-details).
9. **Payment settings** holds the rest, folded until you change something; its summary line says what is set now:
   - **Card providers**: how the customer reaches a card provider, as on a checkout page. **Buyers choose** (the default) shows them the list, **Smart Routing** sends them straight to the best provider for them, and **One provider** sends them to the one you pick. With Smart Routing or Buyers choose, turn off **Offer every card provider** to tick only the providers this invoice offers. The total is checked against their minimums, and the ones offered follow your [card provider order](https://railbed.com/docs/user-guide/buyer-experience.md#provider-order).
   - **Pays to**: which wallet it pays, once an owner has saved another one ([below](#pay-another-wallet)).
   - **After payment, send them to**: your own thank-you page ([below](#send-the-customer-to-your-thank-you-page)).
10. Choose **Create invoice**, or **Save draft** to finish it later. A draft is only visible to your team.

In Live mode, an invoice needs a payout wallet that can receive Live payments. Until the business has one, the form says why and offers the fix, or Test mode to try it out.

| Field | What to enter | Example |
|---|---|---|
| Name and email | Who the invoice is made out to. Needed to email it; optional when you share its link | Alex Morgan, `alex@example.com` |
| Line description | What the line is for, up to 200 characters | Brand workshop, half day |
| Quantity | Up to two decimals | `2.5` |
| Price | The price of one unit | `1,200.00` |
| Currency | USD, EUR, GBP, CAD, AUD, INR or SEK, one per invoice | `USD` |
| Reference or PO number | Optional, up to 64 characters | `PO-7781` |
| Note to the customer | Optional, shown on the invoice and its PDF | Thank you for the project. |
| Terms | Optional, printed at the foot of the invoice | Payment due within 14 days of the invoice date. |

The total and each payment toward it must be one a card provider can take, from about 2.00 USD to 100,000.00. The form says when it isn't.

## How your customer can pay

- **Pay in full** is the default. Turn on **Let them pay in parts** to accept part payments, and set a **Smallest first payment** to ask for a deposit. Each part must also be one a card provider can take, and never more than what's left.
- **Let them add a tip** offers 10, 15 or 20 percent, or another amount. A tip is shown apart everywhere and never counts toward what's owed.
- **Email a receipt for each payment** sends the customer a receipt when a payment arrives, with any tip shown apart and what's left to pay. It's on for new invoices.
- **Remind them by email** sends reminders on the days you tick around the due date: before it, on the day and after it. Reminders are off until you choose days, and they stop once the invoice is paid, voided or expired.

## Send it

After you create an invoice, its page opens with the email ready to send.

- **Send invoice** (on a draft) creates it and emails it in one step. It needs the customer's name and email. **Email invoice** emails one already created. Once it has been emailed, the button reads **Send reminder**. Add a message if you like.
- **Get link only** creates it without an email, so you can share the link or QR code from the **Share** card yourself.

The email comes from your business's name ("Your Business via Railbed"), shows the amount, due date and lines, carries a button to the customer's page and attaches the invoice's PDF. Replies go to the person who sent it, or for an automatic reminder to the invoice's owner, else your support address.

**In Test mode nothing reaches the customer.** **Send test copy** emails a copy marked `[Test]` to you instead, and Test invoices never send reminders or receipts.

An invoice can be emailed at most once a minute and ten times a day, and a business can send 200 invoice emails a day. An address that bounced or marked an earlier email as spam isn't emailed again; the invoice says so. The **Emails** card lists each email and whether it was delivered.

## What your customer sees

The customer opens the invoice from the email or link. They see your name and logo, the lines and totals, the due date and anything already paid. If you allowed it, they choose **In full** or **Part of it**, add a tip, and choose **Pay**. Railbed's payment page then lets them pay by card, as on any Railbed checkout. When it ends, they can go back to the invoice. A paid invoice thanks them, lists what arrived and offers the receipt as a PDF.

The page never shows your team, notes you didn't write for the customer, or anything about your account. A Test invoice can be paid only by your team, with simulated money.

## Statuses

| Status | What it means |
|---|---|
| Draft | Saved, not created. No link yet; only your team sees it |
| Sent | Created and shared or emailed, not yet opened |
| Viewed | The customer opened it |
| Partially paid | Some of it has been paid |
| Overdue | Unpaid or part paid after its due date. The due date runs to the end of that day everywhere |
| Paid | Paid in full |
| Void | You stopped collecting it |
| Expired | An invoice made in another app that ran out of time |

The **Invoices** list shows what's outstanding, overdue and paid in the last 30 days, per currency. Use the status chips to see **Drafts**, **Unpaid**, **Overdue**, **Partially paid**, **Paid**, **Void** or **Expired**, and the search to find an invoice by number, customer or reference.

## Change, copy or stop an invoice

- **Edit** changes anything until the customer starts a payment. After that, the lines, discount, tax, currency and customer are fixed, and you can still change the due date, reminders, receipts, note, terms and owner. Changes show on the customer's page and PDF at once.
- **Duplicate** starts a new draft with the same customer, lines and settings.
- **Void invoice** stops collection: the customer's page says it's no longer payable, and no more reminders go. A payment already under way still completes and counts. A paid invoice can't be voided.
- **Delete draft** removes a draft for good. A created invoice can't be deleted; void it instead.

## Pay another wallet

An invoice pays your payout wallet unless you choose otherwise. Once an owner has saved another wallet under [Settings → Payout wallet → Other wallets](https://railbed.com/docs/user-guide/wallet-and-settlement.md#other-payout-wallets), **Payment settings** shows **Pays to**: choose the wallet this invoice pays. You can only pick a saved wallet, never type an address, and in Live a wallet Railbed's checks refuse can't be chosen. The wallet is chosen before the invoice is created; after that, **Edit** can't change it and **Duplicate** copies it.

An invoice that pays another wallet is paid by card only, because crypto payments go to your payout wallet. Changing your main payout wallet doesn't affect it. While an unpaid invoice pays a wallet, that wallet can't be removed from Settings; void the invoice first, or wait until it's paid.

## Send the customer to your thank-you page

Under **Payment settings**, fill **After payment, send them to**. You can include `{PAYMENT_ID}` and `{REFERENCE}`:

Example: Example success URL

```text
https://example.com/thanks?payment={PAYMENT_ID}&order={REFERENCE}
```

In Live mode it must be a public `https://` page on your own site: an `http://` address, `localhost`, a private network address, an address with a username and password, or a Railbed link is refused, because a customer who has just paid couldn't open it, or would be shown a fresh checkout and pay again. Test mode also accepts `http://` and `localhost`. Leaving it empty shows Railbed's on-screen receipt. [The buyer experience](https://railbed.com/docs/user-guide/buyer-experience.md) explains the two-tab flow.

## PDF and export

**PDF** downloads the invoice as your customer sees it. A paid invoice reads as a receipt. **Export** downloads the list you're looking at as a CSV, up to 10,000 rows.

## Sales teams

Give a salesperson the **Sales** role on the **Team** page ([roles](https://railbed.com/docs/user-guide/branding-and-settings.md#team-roles)). They can make, send and change their own invoices and see only those. Every invoice records who created it and who owns it; owners and managers can give an invoice to anyone who can own one.

Once more than one person can own invoices, owners and managers see **By owner** on the Invoices page: each person's invoiced total, what's been paid and what's still unpaid, per currency. Choose a person to see only their invoices. An invoice made with an API key that names no owner counts under "No owner".

## Build it into your own systems

Developers can create, send, void and list invoices with the [Invoices API](https://railbed.com/docs/api/invoices.md) and follow them with [invoice webhook events](https://railbed.com/docs/webhooks/events.md#invoice-events). Payments toward an invoice carry its id.
