Configure business settings and integrations safely

Settings affect future work and can change what clients see. Make small, deliberate changes, then review a draft before sending a real document.

Business settings versus your account

Check the workspace name first. The selected business supplies its invoice branding, contact details and business defaults. Account & Billing, your password and sign-in security belong to your own login, even while you work in another owner's team.

Members do not have the same settings permissions as owners and admins. If a setting is unavailable, check your role instead of asking someone to share their password.

Review invoice defaults

1. Check the business name, address and contact information.
2. Review currency, invoice numbering and payment instructions.
3. Check reusable notes, footer text and message templates.
4. Use Settings → Invoice templates to manage saved line-item templates; these are different from email message wording.
5. Create or open a draft and inspect the result before sending.

Do not enable VAT, CIS, reverse-charge, deposit, progress or final-invoice options merely to match a screenshot. Use the mode appropriate to the actual work and confirm the treatment with your adviser. Advanced modes may require Pro. Template selection never copies another invoice's customer, status or sending schedule.

Connect only what you need

Developer API access and Stripe Autopilot have their own setup and eligibility requirements. Read the current API documentation, use credentials only on trusted servers, and never include a key in browser code, screenshots or a public repository.

API-created invoices still require valid inputs and applicable sending approval. An API call is not a way around account restrictions. Keep automation's workspace/owner scope explicit and check responses before retrying a write.

The demo contains no live provider connection, API key or HMRC submission. Features behind rollout controls are not made generally available by their presence in help documentation.

See workspace scope, saved templates and automation checks.