Repository navigation
docs: PE-9349 align invoicing docs with app - #60
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
zherring
requested changes
Oct 15, 2026
| 1. Enter the payee and payer names, the amount and token, and the issue and due dates. A memo and one file attachment 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. | ||
| 3. Add a customer email if you want Splits to email the invoice. You can also add comma-separated CC emails when a customer email is present. Without a customer email, copy the invoice link to share it yourself. |
Contributor
There was a problem hiding this comment.
don't like that we're switching from payer to customer here, should switch back to remain consistent and be applied across this pr.
| 3. Add a customer email if you want Splits to email the invoice. You can also add comma-separated CC emails when a customer email is present. Without a customer email, copy the invoice link to share it yourself. | ||
| 4. Choose *None*, *Weekly*, *Monthly*, or *Annually* under *Repeats*. | ||
|
|
||
| A one-off invoice with a customer email is sent when you create it by default. If its issue date is in the future, *Send on issue date* appears: turn it on to create a one-time schedule that emails the invoice on that date. Recurring invoices always send on their issue dates, so this control cannot be changed for them. |
Contributor
There was a problem hiding this comment.
same comment, payer, not customer
zherring
reviewed
Oct 15, 2026
| 1. Enter the payee and payer names, the amount and token, and the issue and due dates. A memo and one file attachment 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. | ||
| 3. Add the payer's email if you want Splits to email the invoice. You can also add comma-separated CC emails when the payer's email is present. Without it, copy the invoice link to share it yourself. |
Contributor
There was a problem hiding this comment.
this is obtuse and doesn't pay attention to the intention behind it.
"Add comma-seperated emails to CC other parties." but, y'know, better?
"Without it" is bad, change it to something like "You may also copy the invoice link to share with your payer." or something better
easier to do it myself
tweak
zherring
self-requested a review
October 15, 2026 15:46
zherring
self-requested a review
October 15, 2026 15:46
zherring
marked this pull request as ready for review
October 15, 2026 15:51
juliogarciag
approved these changes
Oct 15, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
node scripts/check-prose.mjs src/pages/invoicing/index.mdx src/pages/invoicing/recurring.mdx(clean)pnpm build(passed; existing Vocs slot warnings)Tracks PE-9349.
Prompted by: @zherring in Discord thread