How to Create Invoices for Small Business

An invoice is more than a PDF with a logo. For a small business, it is the record of what you charged, what was paid, and what is still owed—especially when work spans multiple days, partial deposits, or repeat B2B buyers.

KyoskGo includes invoicing inside the vendor workspace so totals, currency, and payment status stay on the server with the same discipline used for orders.

When you need invoices (not only receipts)

Use invoices when:

• A corporate client pays on net-15 or net-30 terms.
• You deliver catering, bulk orders, or custom fabrication in stages.
• You want a formal number (`INV-YYYY-NNNN` style) for accounting.
• Partial payments are expected before and after delivery.
• You must match an order to a bill the customer’s finance team will process.

For simple same-day counter sales with immediate full payment, an order record plus payment entry may be enough. Invoicing adds structure when money and fulfillment are not instant.

How KyoskGo invoices are structured

Each invoice belongs to one business (tenant-scoped). Typical fields include:

• Invoice number.
• Subtotal, discount, tax, and total in the business currency.
• Amount paid and balance due.
• Status such as draft, issued, partial, paid, cancelled.
• Optional link to an order and customer.
• Issue date and due date when applicable.
• Notes for terms or delivery context.

Vendors manage invoices from the business invoices area in the dashboard. Customers do not create invoices; they pay against invoices the vendor issued or records payments against.

Step 1: Create a draft invoice

Start in draft when numbers may still change.

Include:

• Accurate line-level or summary amounts that match your quote.
• Tax and discount only if they reflect your real policy.
• Customer reference when the buyer is known in your customer list.
• Link to an order when the invoice is fulfilling a specific checkout.

Draft status means you can edit before the customer should treat it as official.

Step 2: Issue the invoice

Issuing locks in the formal state: issued timestamp, visible obligation to pay, and a number the customer can reference.

After issue:

• Communicate the invoice number and amount due.
• Point to payment instructions (UPI, bank transfer, cash, or methods you accept).
• Set expectations on due date if you use one.

Do not issue duplicate invoices for the same work without cancelling or adjusting the old one.

Step 3: Record payments against the invoice

Payments reduce balance due through backend logic that prevents race conditions on concurrent entries.

You can record:

• Full payment in one entry.
• Partial payment (status moves to partial until total is covered).
• Payment linked from approved customer proof on related orders when that workflow applies.

The system recalculates status: partial while `amount paid < total`, paid when balance reaches zero (subject to cancellation rules).

Overpayment is blocked at validation so accounting stays clean.

Step 4: Keep invoices aligned with orders

If an invoice is tied to an order:

• Order totals and invoice totals should tell the same story unless you deliberately invoice extras (delivery fee added later, change order).
• When the invoice is fully paid, order payment status should reflect settlement through the shared payment services—not a manual guess in two places.

Splitting truth between a spreadsheet and KyoskGo defeats the purpose of one platform.

Currency and rounding honesty

Invoice currency comes from the business configuration. Display and storage should not flip currencies based on who is viewing the page.

Money calculations use precise decimal handling on the server to avoid floating-point surprises on tax and partial payments.

What invoices do not replace

• **Tax filing advice:** KyoskGo records transactions; your accountant still defines GST/VAT reporting.
• **Automatic legal compliance in every country:** You are responsible for required fields on invoices in your jurisdiction.
• **Guaranteed online card capture:** Customer payment may still be manual confirmation depending on your setup (see the payments guide).

Workflow examples

Home baker — event deposit

1. Customer confirms custom cake by message.
2. Vendor creates draft invoice for 50% deposit.
3. Issue invoice; customer pays via UPI and uploads proof.
4. Vendor approves proof; partial status recorded.
5. After delivery, second invoice or balance payment completes the job.

Shop — wholesale restock

1. Repeat retailer orders through vendor-assisted checkout.
2. Order generates with backend total.
3. Vendor issues monthly invoice linking multiple orders or one consolidated invoice—pick one pattern and stick to it.
4. Retailer bank transfer recorded when finance pays.

Service provider — milestone billing

1. Booking or order captures scope.
2. Invoice issued per milestone.
3. Work continues only when payment policy allows.

Related resources

• How to accept payments for local business orders
• For professional services
• For freelancers

FAQ

Can I edit an invoice after issue?

Business rules may restrict editing issued invoices to protect audit integrity. Prefer credit notes or new adjustment invoices if your process requires changes after issue.

What happens if I cancel an invoice?

Cancelled invoices should not receive new payments. Attempts to pay cancelled invoices are rejected by the service layer.

Do customers get an email automatically?

Notification behavior depends on your messaging configuration. Always send the invoice number and amount due through your primary customer channel.

Can one payment cover multiple invoices?

Use your vendor payment workflow for the supported pattern in your deployment. When in doubt, record payments per invoice so balances stay obvious.

Is invoicing available on every plan?

Feature access depends on subscription plan and feature gates enforced on the backend. If invoicing is blocked, upgrade or adjust plan—not UI-only workarounds.