Kindhearted Operations software
Log in Create account
Documentation ยท Invoice

Invoice Setup Overview

What this does

This overview explains what needs to be in place before Invoice works cleanly for billing, estimates, customer views, and payment collection.

Invoice also works best when the surrounding suite context is already in place, especially where billing is supposed to follow work from Booking and use shared customer or account records.

What must already be set up

  • the company must have an active Invoice subscription
  • the user must be assigned access to Invoice
  • if invoices or portal flows will collect payments, Stripe should already be configured
  • if you want branded public invoice or portal links, domains should already be configured
  • if documents should reuse shared customer, account, or address records, those records should already be clean in CRM
  • if documents should follow real operational work, the relevant booking or job context should already be correct in Booking

Why the Admin App matters here

If you are in Invoice and trying to find shared payment-provider setup, public host setup, or app assignment, those live in the Admin App.

That matters because:

  • customer payment flows can depend on Stripe setup from the Admin App
  • public invoice and portal links can depend on domain setup from the Admin App
  • staff access depends on app assignment from the Admin App

Why Booking and CRM also matter here

Invoice is where billing becomes customer-facing, but it often relies on context that started somewhere else first.

That matters because:

  • Booking can supply the job and work context that billing should follow
  • CRM can hold the customer, account, contact, and address records the document is supposed to reference

What you can set up inside Invoice

Once the shared setup is in place, Invoice has its own app-specific settings such as:

  • customer portal behavior
  • notes
  • operational work
  • notifications
  • terms
  • taxes
  • payments
  • visibility
  • permissions

Recommended setup order

  1. Finish shared setup in the Admin App.
  2. Assign the right people access to Invoice.
  3. Configure Invoice settings, payments, taxes, notifications, and visibility.
  4. Test customer-facing invoice and portal flows.

What stays incomplete if skipped

If Stripe or domains are missing, customer-facing invoice and payment flows may not behave as expected.

If customer or operational context is wrong upstream, the billing document can still be created, but it will be harder to keep the invoice aligned with the real work and the right party.

If app assignment is missing, users may not be able to access Invoice.

Related guides