Feature

Let your customers edit their own invoice

Recipients add PO numbers, fix billing entities, update addresses, and correct AP contacts right on the invoice link. Every change is versioned. You see what changed. You can revert anything in one click.

See it in action Back to all features →

The problem

You send an invoice. Your customer emails back: "We need a PO number on this before AP can process it." You edit. You resend. They email again: "Actually, the billing entity is our subsidiary, not the parent. Here's the correct address." You edit. You resend. By now the invoice has drifted from the original and you've lost track of who asked for what.

This is the default experience with every invoicing tool. JupiterInvoice solves it by making the invoice a shared document, not a one-way PDF.

What the recipient can edit

PO number

Inline add or edit. AP typically owns this number, not the person who hired you. Let AP add it themselves.

Billing entity

The legal name that goes on the invoice often differs from the trading name your contact uses. They can correct it without a support ticket.

Billing address

Full structured address: street, city, region, postal code, country. AP knows their own address better than you do.

AP contact

Name and email for accounts payable. Future invoices route to them automatically.

Tax ID / VAT

VAT number for EU, GSTIN for India, EIN for US subsidiary billing. Goes on the invoice where it belongs.

Comments

Two-way thread right on the invoice. Better than another email chain referencing "your last invoice."

What you see as the sender

When the recipient edits, you get an email with a clean diff. Inside your invoice detail page, the "Recipient changes" panel lists every edit with a timestamp and a Revert button. Nothing is irreversible.

→Email notification within seconds of any edit, with a before/after diff.
→Version history stored as immutable snapshots. Every edit, PO change, forward, and revert is in the log.
→One-click revert per change. If AP picked the wrong billing entity, you restore the previous version without rebuilding the invoice from scratch.
→Slack notification in your team channel so nothing gets missed.

Who uses this

Freelancers

Every client has a different billing process. Let them fill in their own details.

Teams leaving Stripe Invoicing

Stripe doesn't let recipients edit anything. That's the gap we fill.

How recipient editing works

Does the recipient need an account?

No. The invoice link is the only credential. Anyone with the link can view and edit the fields that belong to them. This is by design: AP teams aren't going to sign up for a new SaaS product to process a single invoice.

What if the recipient makes a bad edit?

You can revert any recipient change from your invoice detail page. Every edit creates an immutable version snapshot, so revert restores the exact pre-edit state. The revert itself becomes a new version, so there's no erasure of history.

Which fields are editable versus approval-required?

PO number, billing entity, billing address, AP contact, and tax ID are direct-edit: the recipient changes them, you're notified, you can revert. Price, line items, discounts, currency, and due date require sender approval (coming soon in a change-request workflow).

Can the recipient edit after the invoice is approved or paid?

No. Once an invoice is approved for payment or marked paid, it locks. Edits stop being possible on both sides. This protects the payment record.

Do recipient edits change the original PDF?

Yes. The invoice is re-rendered after any edit, and the cached PDF is regenerated on next download. AP always sees the current state, not a stale snapshot.