Skip to content
Hoursmith Docs
Payouts

Forward a reviewed bill by email

Review the exact recipient, message, receiving instructions, and PDF before forwarding an unpaid team bill.

Owners and Admins on Agency can forward an approved, positive-total, fully unpaid team bill. Draft, void, deleted, partially paid, and paid bills are ineligible. Sending an email neither pays the bill nor changes its balance.

Set up the destination and receiving instructions

  • Add the payee's private receiving method: a label, optional currency, and structured banking instructions. You can make one active method the default; choose exactly one for this bill's PDF.
  • Add a workspace destination with a name, exact email address, optional CC, and a Wise, Airwallex, or custom label. Supply the real address yourself. A provider label does not connect an account or establish a payment integration.
  • Configure the workspace email sender. Team bills use a separate team_bill subject/body template. Banking instructions belong in the PDF, not in template variables.

Receiving methods describe where the payee receives funds; they are not the workspace's outgoing payment methods. A method's currency does not convert or settle the bill. Archiving a method removes it from future choices and clears its default without choosing a replacement; historical copies remain.

Review, then send

  1. Open the eligible bill and select the destination and receiving method.
  2. Preview From, Reply-To, To, CC, subject, message, and the exact PDF attachment. Previewing sends nothing.
  3. Check that the attachment and recipients are correct, then confirm sending.

The reviewed snapshot expires after 24 hours. Changes to the bill, payment state, method, destination, or sender require a fresh review. The PDF must be under 10 MB; Wise destinations also require fewer than 10 pages. Use compact bill grouping where possible, or handle the bill outside this email flow rather than splitting it into duplicate bills.

If provider acceptance is uncertain, Hoursmith does not automatically retry. Check the destination inbox or provider before intentionally sending again. A repeat send requires confirmation after reviewing delivery history; retrying the same operation after a lost response returns the same delivery.

Delivery evidence and privacy

History retains the status, recipients, actor, time, error, and authenticated download of the exact sent attachment. The encrypted snapshot is immutable: later method/destination archival or eligible bill deletion does not rewrite it. Owners/Admins can still read sent history after downgrade, but new deliveries require Agency.

The recipient receives the deliberately shared attachment, not app access or a public bill link. For a minimal notification after payment instead, use payment confirmation.

Was this page helpful?

On this page