Invoicing · 發票

The invoice that delivers itself, chases itself, and proves itself

Create it four ways — including from a contract PDF or a chat. Send it as a tracked link that handles its own passwords. Let the reminder ladder do the chasing, confirm the payments your client reports, and keep gap-free numbers with a frozen record of what was sent.

If your account doesn't show Invoices, write to hello@pitchstation.ai.

4ways to create 4×auto reminders 4invoice languages 1API call to deliver
An invoice flying out of its envelope along a tracked path with sent, viewed, and paid checkpoints
Everything after "send"

Most tools make an invoice. This one finishes the job.

An invoice here isn't a PDF you email into the void — it's a live, tracked document with a lifecycle, a chase engine, and a paper trail.

Create four ways manual · description · contract · chat

Type it, describe it ("invoice Northbrook HK$12,000, NET 14"), upload the contract and bill a milestone, or chat it into shape. Zero-fabrication rule: AI is told never to invent an amount, and every draft waits for your review.

Delivery that gates itself

Clients with an account get a sign-in link; everyone else gets link + password in the same email, rotating on every resend. You never manage invoice passwords.

You see "viewed"

No more "did you get my invoice?" — when your client opens it, the open log shows it. Issue it in English, 简体中文, Tiếng Việt or Español; its labels, dates, buttons and emails follow.

Reminders you never write

Due−3 · due day · +7 · +14 — polite, automatic, deduped; they pause when your client reports paying and stop once it's paid. Opt out per invoice; nudge manually anytime.

Numbers with no gaps

Gap-free registers assigned at send (INV-2026-0042). Drafts carry a DRAFT stamp and no number; a voided invoice keeps its number, so the sequence never breaks.

Many identities, one account

Bill as multiple entities — each issuer has its own legal block, logo, and its own register (HK-…-0001 beside SG-…-0001). Built for platforms and groups.

Clients answer back

"I've paid ✓" claims (you confirm before they count), questions that land in your inbox with context, and receipts that close the thread professionally.

Corrections done right

Edits revise the same link; paid invoices lock; credit notes correct the record, in full or line by line.

Runs from your phone

Install /m/invoices — the badge counts what needs you now; a push lands the moment a client reports payment.

The lifecycle

Draft → Sent → Paid. Everything else is automatic.

DRAFTUnnumbered scratch space — edit, preview, delete freely
→
SENTNumber minted · tracked link · reminders armed · identity frozen
→
Getting paid

Paid on your own rails — your client reports it, you confirm it

Your bank details, FPS 轉數快, PayNow, a QR code or your own payment link show under How to pay. Your client pays you directly, taps I've paid and can attach proof; when you confirm, the receipt goes out, your webhook fires, and a fully paid invoice flips to PAID.

A claim never touches the balance until you confirm it
Confirm the amount that arrived, mark it "received, clearing", or dismiss it with a reason your client sees
Proof (photos, iPhone HEIC or PDFs) is visible to you only, and you can redact it
Partial payments count: the balance updates and the reminders keep going
Paid another way? Record it yourself, with a reference and proof
Automatic reminders pulsing along a timeline until a milestone turns paid
Two platforms exchanging invoice documents over glowing data streams
For platforms & developers

The whole integration is one call

Idempotent by your order id, atomic (failure creates nothing), test-mode safe against production, with signed webhooks back so you never poll. Already collected the money elsewhere? Receipt mode issues the numbered PAID document in the same call.

# one secret · one call · delivered & being chased
curl -X POST https://pitchstation.ai/api/invoices \
  -H "Authorization: Bearer $PAT" \
  -d '{ "external_ref": "order-417", "send": true,
        "client_email": "ap@acme.com", "currency": "USD",
        "items": [{ "description": "Machines x3", "unit_cents": 250000, "qty": 3 }] }'
→ 201 { "number": "INV-2026-0031", "url": "https://…/s/…", "password": "…" }
Why it's safe to run your billing here

The paper trail is the feature

Provenance on every paymentEvery payment records who vouched for it, with its method, reference and date.
Frozen at sendYour seller identity is frozen at an invoice's first send, and each send keeps a sha256-hashed PDF copy where PDF rendering is on — renaming your company never rewrites an issued invoice.
Abuse-boundedDaily send caps stop a leaked API token at the limit, and a burst of new recipient domains emails you an alert.
Test mode for realTEST-series invoices: no emails, permanent stamp, self-purging. Your CI hits production safely.
Get started · 開始使用

Send your next invoice from here

Set your letterhead, add how clients pay you, and send. The chasing, tracking, and record-keeping are already done.

Create a free account →

No card required · if your account doesn't show Invoices, write to hello@pitchstation.ai · full deep-dive: /developers