Update README.md (#31951)

Changes for creating invoice via QB

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.

- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] If paths of existing endpoints are modified without backwards
compatibility, checked the frontend/CLI for any necessary changes

## Testing

- [ ] Added/updated automated tests
- [ ] Where appropriate, [automated tests simulate multiple hosts and
test for host
isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing)
(updates to one hosts's records do not affect another)

- [ ] QA'd all new/changed functionality manually

For unreleased bug fixes in a release candidate, one of:

- [ ] Confirmed that the fix is not expected to adversely impact load
test results
- [ ] Alerted the release DRI if additional load testing is needed

## Database migrations

- [ ] Checked table schema to confirm autoupdate
- [ ] Checked schema for all modified table for columns that will
auto-update timestamps during migration.
- [ ] Confirmed that updating the timestamps is acceptable, and will not
cause unwanted side effects.
- [ ] Ensured the correct collation is explicitly set for character
columns (`COLLATE utf8mb4_unicode_ci`).

## New Fleet configuration settings

- [ ] Setting(s) is/are explicitly excluded from GitOps

If you didn't check the box above, follow this checklist for
GitOps-enabled settings:

- [ ] Verified that the setting is exported via `fleetctl
generate-gitops`
- [ ] Verified the setting is documented in a separate PR to [the GitOps
documentation](https://github.com/fleetdm/fleet/blob/main/docs/Configuration/yaml-files.md#L485)
- [ ] Verified that the setting is cleared on the server if it is not
supplied in a YAML file (or that it is documented as being optional)
- [ ] Verified that any relevant UI is disabled when GitOps mode is
enabled

## fleetd/orbit/Fleet Desktop

- [ ] Verified compatibility with the latest released version of Fleet
(see [Must
rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md))
- [ ] If the change applies to only one platform, confirmed that
`runtime.GOOS` is used as needed to isolate changes
- [ ] Verified that fleetd runs on macOS, Linux and Windows
- [ ] Verified auto-update works from the released version of component
to the new version (see [tools/tuf/test](../tools/tuf/test/README.md))

handbook/finance/README.md

@@ -139,20 +139,26 @@ Use the following steps to update the [💸Finance department KPIs](https://docs
 ### Create an invoice
 
 To create a new invoice for a Fleet customer, follow these steps:
-1. Go to the [invoice folder in Google Drive](https://drive.google.com/drive/folders/11limC_KQYNYQPApPoXN0CplHo_5Qgi2b?usp=drive_link).
-2. Create a copy of the invoice template, and title the copy `[invoice number] Fleet invoice - [customer name]`.
-    - The invoice number follows the format of `YYMMDD[daily issued invoice number]`, where the daily issued invoice number should equal `01` if it's the first invoice issued that day, `02` if it's the second, etc.
-3.  Edit the new invoice to reflect details from the signed subscription agreement (and PO if required).
-    - Enter the invoice number (and PO number if required) into the top right section of the invoice.
-    - Update the date of the invoice to reflect the current date.
-    - Make sure the payment terms match the signed subscription agreement.
-    - Copy the customer address from the signed subscription agreement and input it in the "Bill to" section of the invoice.
-    - Copy the "Billing contact" email from the signed subscription agreement and add it to the last line of the "Bill to" address.
-    - Make sure the start and end dates of the contract and amount match the subscription agreement.
-    - If professional services are included in the subscription agreement, include as a separate line in the invoice, and ensure the amounts total correctly.
-    - Ensure the "Notes" section has wiring instructions for payment via SVB.
-4.  Download the completed invoice as a PDF.
-5.  Send the PDF to the billing contact from the "Bill to" section of the invoice and cc [Fleet's billing email address](https://fleetdm.com/handbook/company/communications#email-relays). Use the following template for the email:
+1. Go to the Invoice page on our billing system.
+2. Select “Create Invoice” on the right, and you will be directed to a new page to create an invoice.
+3. Under the “Add customer” dropdown box, select an existing customer, or add a new customer. The customer is the entity that will be receiving the invoice. 
+   - To add a new customer: Update the company name, contact person, billing email address, and “Bill to” address fields in the next page.
+4. Change the invoice number. 
+   - The invoice number follows the format of `YYMMDD[daily issued invoice number]`, where the daily issued invoice number should equal `01` if it's the first invoice issued that day, `02` if it's the second, etc.
+5. Edit the new invoice to reflect details from the signed subscription agreement (and PO if required).
+   - Enter the invoice number (and PO number if required) into the top right section of the invoice.
+   - Update the date of the invoice to reflect the current date.
+   - Make sure the payment terms match the signed subscription agreement.
+   - Validate if the customer address from the signed subscription agreement matches the default Bill to address shown on the invoice. 
+   - Validate if the email from the signed subscription agreement matches with the email in the email field on the invoice.
+   - Make sure the start and end dates of the contract and amount match the subscription agreement.
+   - If professional services are included in the subscription agreement, include as a separate line in the invoice, and ensure the amounts total correctly.
+   - Ensure the wiring instructions for payment via SVB are listed in in the invoice. 
+6. Download the completed invoice as a PDF.
+   - Rename the pdf copy `[invoice number] Fleet invoice - [customer name]`.
+   - Save a copy of the PDF into the invoice folder.
+
+7. Send the PDF to the billing contact from the "Bill to" section of the invoice via the Fleet billing email address. Use the following template for the email:
 
 ```
 Subject: Invoice for Fleet Device Management [invoice number]