Back to Business documentation

Sales

Turn customer conversations into branded quotes and invoices, then track payments received.

Overview and core concepts

Turn customer conversations into branded quotes and invoices, then track payments received.

A customer is the billing relationship; contacts are people at that customer.

Products and services are reusable line items. Physical products can be enabled separately for Inventory; services cannot.

Draft documents can be edited. Issued documents follow explicit accept, convert, cancel and payment actions.

The primary currency controls invoice totals, applied payment amounts and Sales reports. Quotes show an optional equivalent only. Invoices can show an equivalent only or accept manually recorded payments in either currency at the frozen invoice rate. Actual currency and amount received are retained separately. Accounting supports configured base-currency automation; secondary display adds no FX journals, gain/loss calculation or automatic rate feed.

Customer 360, explicit partial deliveries/returns and optional base-currency Accounting posting with matching active apps and enabled workflows.

Before you start & permissions

Select the right company and confirm that this app is active.

Sales viewing plus the relevant customer, product, quote, invoice, payment or seller management permission.

Understanding permissions

Getting started & common workflows

  1. Select your company and open Seller details. Save the business identity, address, contact details, logo, default notes and terms.
  2. Create a customer and its contacts, then Products & Services.
  3. Create a quote, review its lines and totals, issue it and record acceptance. Convert the accepted quote to an invoice.
  4. Issue the invoice. Record each payment with the correct amount and currency. Download the branded PDF.
  5. In Seller details, choose the default document currency and optional secondary currency, rate date and display on quotes/invoices. Enter the rate as 1 primary major unit = X secondary major units (up to eight decimal places). New drafts copy these defaults; changing settings does not change existing drafts or issued documents. Search reference fields by name or number, use Arrow keys and Enter to select, Escape to close, and Load more for later server pages. Product search is independent on each line. Re-enter the rate after changing a draft’s primary currency. Issuing freezes the currency pair, rate, date and equivalent. Quote conversion copies the quote rate into an independently editable invoice draft.

Worked example

Fictional Cedar Studio creates a quote for two consulting sessions. After acceptance, convert it to an invoice. Record a partial payment, then the remaining amount; the invoice reflects the balance. Display-only fictional Lebanon example: primary USD, secondary LBP, 1 USD = 89,500 LBP, rate date 17 October 2026. USD 2,220.00 has an equivalent total of LBP 198,690,000. This is an example rate chosen by the company, not a live or official exchange rate. Equivalent-only invoices accept USD only. To accept LBP, choose Accepted payment currency before issuing the invoice. For a fictional USD 632.70 invoice at 89,500, the payment options show USD 632.70 or LBP 56,626,650. Record USD 200, then LBP 17,900,000 (USD 200 applied), then use the full remaining secondary balance to settle exactly. CedraStack records receipts manually; it does not process funds.

Related modules

Shared records and explicit handoffs keep work connected. Each module still requires its own access and permissions.

Troubleshooting

  • Missing create or payment action? Ask for the specific operation permission.
  • Cannot convert? Check the quote status and whether it was already converted.
  • Incorrect PDF identity? Review Seller details and the document’s saved seller information.
  • For a missing connected action, check the selected company, matching active apps, permissions, workflow enablement and readiness. Historical records are not backfilled.
Contact support

Current platform notes

  • Payment records document money received; CedraStack does not collect your customer payments.
  • Explicit stock fulfillment needs Sales + Inventory and an enabled workflow. Eligible invoice/payment posting needs Sales + Accounting, configured mappings and an open period; standalone Sales remains usable.
Module overview

Choose your next step