> For the complete documentation index, see [llms.txt](https://docs.bluepro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluepro.ai/plans-billing/invoicing-essentials-get-paid-in-person-vs.-send-it.md).
# Invoicing Essentials: Get Paid In Person vs. Send It
### Starting an Invoice
* **From a job (easiest):** open the job, tap **Invoice** (customer/job pre-filled).
* **From scratch:** **+ → Invoice →** pick customer → pick job.
### Adding What You Did
The **Add Items** screen is your price book — already priced. Search, or filter with **All / Services / Materials** pills; tap to add; use **+ / –** for quantity. A running total builds at the bottom.
> 🎞️ **CLIP —** Searching, tapping items, adjusting quantities.
#### Something not in the price book?
Tap **+ → Custom Item.** Name it, set service/material, price, quantity, and taxable.
> 💡 **Tip — Save it for next time.** Flip on **Save to Price Book** and it's ready on the next job.
>
Tap **View Cart** when done.
### Fine-Tuning in the Cart
* **Dates** (issue & due) · **Edit a line** (tap to edit, swipe to delete) · **Discount** ($ or %) · **Modifiers** (e.g., *After Hours +10%*) · **Tax** (**Automatic** from address, or **Manual Rate**) · **Material display** (**Itemized / Listed / Bundled**).
> 💡 **Tip — Material display only changes what the customer sees** — not your job profit. 💡 **Tip — Customer-facing notes & photos** (up to 10) near the bottom are **shown to the customer** — great for before/after photos; keep private notes off.
### Two Paths to Record a Payment
When you open the invoice and tap **Record Payment**, BluePro asks how you want to record it: **Charge Card** or **Record Manually**. The difference is simple — are you running the customer's card right now, or logging a payment they already made another way?
#### Option A — Charge Card — process the payment now
Pick this to run a card through BluePro. You'll see the invoice total, what's already been paid, and the balance due. Enter the **Payment Amount**, then choose a **saved card** or select **Enter new card**. Don't have the card on hand? Tap **Request Card from Customer**. Tap **Charge** to process it.
Then **Send Receipt** (text/email).
#### Option B — Record Manually — log a payment taken another way
Pick this for cash, check, or any payment that didn't go through BluePro. Enter the **Payment Amount**, choose the **Payment Type** (Cash, Check, Bank Transfer / ACH, Wire Transfer, Money Order, or Other), set the **Payment Date**, and add a **Receipt #** or **Notes** if you want. Tap **Record Payment** to log it.
>
> 💡 **Tip — You don't have to collect the full amount.** Both paths let you enter a partial Payment Amount, so you can take a deposit now and collect the balance later. The invoice tracks what's paid and what's still due.
### Payment Request Options
| Option | What it does |
| ---------------- | ------------------------------------------------------------------------------- |
| **Full** | Charges the entire amount (usual choice). |
| **Deposit** | Part up front — $ or %. |
| **Partial** | A specific amount now, the rest later. |
| **Installments** | 2–24 payments, weekly/bi-weekly/monthly/quarterly. BluePro builds the schedule. |
### FAQ
* **"Record Payment" vs "Send to Contact"?** Record = money now (card/cash/check). Send = customer pays later (PDF/payment link).
* **Pay online from the text?** Yes — payment link.
* **Cash/check?** Record Payment → Record Manual Payment.
* **Deposit then bill rest?** Payment Request → Deposit, or take payment then send for the balance.
* **Save for later?** Save Draft / Save Without Sending.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bluepro.ai/plans-billing/invoicing-essentials-get-paid-in-person-vs.-send-it.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.