Guides & tutorials

Quick start (5 minutes)

1. Sign up with your email and password and open the verification link we email you.
2. Open New invoice, enter the client's name and email, and add line items.
3. Press Save draft, check the preview, then Email invoice.
4. When your client pays you, open the invoice and press Mark paid.
5. Want automation? Create an API key and follow the API reference.

Invoicing basics: what to include

Requirements differ by country, so check local rules, but a good invoice normally has:

• The word "Invoice" and a unique invoice number
• The issue date and due date
• Your business name and contact details, and your tax or business registration number where required
• Your client's name and address
• An itemised list of goods or services with quantities and unit prices
• Subtotal, tax (rate and amount) and total due, with the currency
• Payment instructions and terms, such as late-fee policy

Getting paid faster

• Invoice immediately after the work is delivered, not at month end.
• Set a clear due date and short terms (7 to 14 days) where your market allows.
• Make paying easy: put your bank or wallet details in the notes.
• Be specific in descriptions so your client's finance team can approve without questions.
• Follow up politely a day before and a day after the due date.
• Agree terms in writing before work starts, including late fees.

Paying for your plan with USDT (TRC-20)

1. In Plan & billing choose USDT (TRC-20) and press Pay with crypto on a plan.
2. Copy the address and the exact amount (for example 50.037).
3. In your wallet or exchange choose USDT, then the network TRON (TRC-20). Never ERC-20 or BEP-20.
4. Send exactly the amount. If you withdraw from an exchange, make sure the fee is added on top so the full amount arrives.
5. Keep the screen open. When the transfer confirms, it flips to "Payment received" and a receipt arrives by email.

Paying for your plan with Bitcoin

1. Choose Bitcoin and press Pay with crypto.
2. Scan the QR code with a wallet that supports payment links. The address and amount fill in automatically.
3. Check the amount shown matches, then send. The wallet adds the network fee on top, so the exact amount arrives.
4. The screen shows "Payment detected" as soon as it hits the mempool and "Payment received" after confirmation.

Sending invoices in bulk from a CSV

1. Open Bulk send and press Download template.
2. Fill in one row per line item. Use the same email on several rows to put several items on one invoice (or use the group column to be explicit).
3. Save as CSV (in Excel: Save As → CSV UTF-8) and upload it.
4. Check the preview. Fix any errors it lists by line number, or choose to send only the valid rows.
5. Press Create & send all. Watch the progress bar. Anything that fails is listed with the reason.

Tip: try a first file with 2 or 3 rows addressed to yourself.

Getting a document signed

1. Open E-signatures. Choose Upload a PDF, drag the signature, date, name and text boxes onto the pages and add your signers. (Or write or paste the document text for a quick, text-only request.)
2. Enter the signer's name and email and choose how long the link stays valid.
3. Press Send for signature. The signer gets an email with a secure link.
4. When they sign (or decline) you get an email. A signed PDF with the audit trail is attached and available in the dashboard.

For important contracts, have a lawyer check the wording and whether an electronic signature is acceptable for that document type.

Using the AI assistant

Click the chat button at the bottom right of your dashboard. Try:

• "Invoice Maria at maria@example.com for 10 hours of consulting at $80, due 2026-12-20"
• "I need to invoice all my clients from a spreadsheet"
• "How do I get an API key?"

The assistant prepares things and you confirm. Always check the details before pressing a button.

Email deliverability

Invoices are useless if they land in spam. Three DNS records prove an email really comes from the domain it claims:

• SPF lists the servers allowed to send for a domain.
• DKIM adds a cryptographic signature to each message.
• DMARC tells receivers what to do when SPF or DKIM fail.

We send from a domain with all three configured. Because replies go to your own address, set up SPF/DKIM on your own domain as well. Tell clients to add our sending address to their contacts if an invoice is missed.

Using the API safely

• Keep keys on your server, never in a web page or mobile app.
• Use one key per integration so you can revoke only what leaks.
• Rotate keys regularly: create the new key, deploy, then revoke the old.
• On 429, wait for Retry-After. Don't retry in a tight loop.
• Log the id returned by create calls, so retries don't create duplicates.

Understanding limits

Two limits apply. Requests per minute protects the service and resets every minute. The invoice quota counts emails sent: per day on every plan. Check your usage on the Plan & billing tab, or in the API through the X-Quota-Remaining header.