docs: PE-9349 align invoicing docs with app

src/pages/invoicing/index.mdx

@@ -11,14 +11,23 @@ See also [Recurring](/invoicing/recurring), [Paying](/invoicing/paying), and [Tr
 
 ## Issuing
 
-From the *Invoices* page, select *Create*:
+From the *Invoices* page, select *Create invoice*:
 
-1. Enter the payee and payer names, the amount and token, and the issue and due dates. A memo and file attachments are optional.
+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. You may add the payer's email to have Splits send the invoice to the payer. You can also copy the invoice link to share it directly.
+4. Choose *None*, *Weekly*, *Monthly*, or *Annually* under *Repeats*.
+
+A one-off invoice with the payer's 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.
 
 Invoice numbers increment automatically per workspace.
 
+## Managing invoices
+
+From the *Invoices* page, any workspace member can copy or open an invoice link, download its PDF or attachments, and open a duplicate in the create form. The duplicate needs new dates, CC emails, and any attachment re-entered; only Owners can create it.
+
+Owners can add or edit the memo, resend the email with an optional note if the payer's email is present, or void an invoice that is neither paid nor void. Owners can mark an invoice paid or mark a paid invoice unpaid; see [Tracking](/invoicing/tracking).
+
 ## Pay-by-bank
 
 Pay-by-bank lets the invoicee pay in fiat from their bank account. It requires the workspace to set up [a virtual account in the matching currency](/banking) and request the token:

src/pages/invoicing/recurring.mdx

@@ -1,12 +1,12 @@
 ---
 title: Recurring invoices
-description: Issue the same invoice on a weekly or monthly schedule, with due dates relative to each issue date, until paused.
+description: Issue the same invoice on a weekly, monthly, or annual schedule, with due dates relative to each issue date, until paused.
 ---
 
 # Recurring invoices [Issue the same invoice on a schedule]
 
-When [issuing an invoice](/invoicing), turn on *Make recurring* and pick a weekly or monthly interval. Each occurrence creates a new invoice with the due date set the same number of days after its issue date, and emails the payer if the invoice has their email.
+When [issuing an invoice](/invoicing), choose *Weekly*, *Monthly*, or *Annually* under *Repeats*. Each occurrence creates a new invoice with the due date set the same number of days after its issue date, and emails the payer if the invoice has their email. The form shows when the first invoice will be issued.
 
 Schedules run until paused: there is no end date or occurrence limit. If the first issue date is in the future, only the schedule is created, and the first invoice generates on that date. If the issue date is today or in the past but its due date has not passed, the first invoice is issued when the schedule is created. If the first due date has passed, Splits either issues that occurrence at the next available run or skips it and advances to the next occurrence; the form previews which will happen before creation. New occurrences generate daily at 11:00 UTC.
 
-View, edit, and pause schedules from the *Schedules* tab on the *Invoices* page. Like all invoicing, managing schedules requires the [Owner](/workspaces/roles) role.
+From the *Schedules* tab on the *Invoices* page, any workspace member can view a schedule's timeline and download its attachments. Owners can edit a recurring schedule or pause and resume any schedule. An Owner can also send an active one-time schedule now instead of waiting for its scheduled send. Only Owners can manage schedules; see [Roles](/workspaces/roles).