Workflows & examples
Common workflows
1. Order to cash
- A sales order is confirmed in Sales.
- When goods ship (Inventory → Goods Issue) or the order is fulfilled, a draft invoice is generated in Finance.
- The AR clerk reviews, edits the draft if needed, and sends the invoice; a journal entry posts to Accounting.
- The customer pays; the payment is matched and reconciled against the bank feed.
- If it goes overdue, Dunning and the AR Collector chase it automatically.
2. Procure to pay
- A purchase order is approved in Procurement.
- Goods are received (Inventory → GRN).
- A supplier bill is created from the PO; three-way matching validates it against the PO and GRN.
- The bill is approved, scheduled, and paid; a journal entry posts automatically.
3. Expense reimbursement
- An employee files a claim in Finance → Expenses with a receipt.
- The Expense Auditor screens it; it routes through multi-level approval.
- Once approved, it is scheduled for reimbursement and posts to Accounting.
4. Time and materials billing
- An employee logs hours in Time Tracking against a project or client.
- Finance sets a rate card once for that engagement (or the entry uses a manually entered rate).
- A manager approves the entry under Timesheet Approvals; it becomes billable.
- The billable hours are converted into a customer invoice from Finance → Timesheets, carrying the rate that was on each entry.
Common tasks
Edit a draft invoice before it’s sent
- Open the invoice from Finance → Invoices.
- Confirm its status is draft (or rejected) — sent invoices can’t be edited.
- Click Edit, change the customer, due date, notes, or any line item, then Save.
Set up a rate card so billable time flows into an invoice
- Go to Finance → Timesheets → Settings and create a rate card with a name, hourly rate, and currency.
- On a time entry (yours or a colleague’s), select the rate card — the hourly rate fills in automatically.
- Approve the entry, then bill it from Finance → Timesheets.
Set up a recurring invoice template
- Go to Finance → Recurring → New Schedule.
- Set the customer, line items, amount, and frequency (monthly or annual).
- Save — XBuddy generates each invoice automatically on the cycle date going forward.
Trace an invoice back to its source documents
- Open the invoice detail page.
- Review the Document Chain panel to see the quotation, sales order, delivery order, or timesheet entries that produced it, and any payments or credit notes it produced.
A worked example — from draft to cash
The same order as in Sales: 20 pumps, 6% discount, VAT 10% — 258,500,000 ₫ gross.
Draft
Finance → Invoices → New, or convert the sales order. Converting inherits the customer, lines, currency and payment terms; typing them again is how they drift apart. A draft changes nothing anywhere — no ledger entry, no receivable, no dunning clock.
Send
Send is the moment everything happens: the invoice number is assigned, the receivable exists, the ledger entry posts, and the due date starts the clock. It needs invoices:send, which invoices:write does not include.
If the GL posting fails — a missing mapping, a closed period — the invoice still sends but carries a posting failed flag. It is visible on the detail page and repostable; it does not disappear.
Payment
Record payment with invoices:payments. One payment can settle several invoices: allocate 258,500,000 ₫ across them and the system posts one bank entry and one journal entry, not one per invoice.
A partial payment leaves the invoice partial_paid. Nothing rounds it off for you.
If something was wrong
| Situation | What to do | Why |
|---|---|---|
| Draft, never sent | Delete it | Nothing has happened yet |
| Sent, nothing paid, wrong amount | Void and reissue | Void writes a reversing journal entry; it does not erase history |
| Sent and paid | Credit note | A settled invoice is not voided — reverse it with a document that says so |
| Right invoice, wrong customer paid | Void the payment, record it again | The payment carries the allocation, not the invoice |
Collections
Once past due, the dunning ladder picks it up: a gentle reminder, then a firm one, then escalation for approval. Each rung is a draft — nothing is emailed to a customer without a person approving it. The staged count and the sent count are different numbers, and the screen shows both.
Data in and out
Comes from
| Source | What arrives |
|---|---|
| Sales | Sales orders and delivery orders converting into invoices |
| Service Management | Contract, milestone and time-and-material billing events |
| Projects | Approved billable hours and milestone amounts |
| Procurement | Purchase orders and goods receipts becoming bills |
| CRM | The customer and their payment terms |
| Timesheets | Approved, billable, not-yet-invoiced hours |
Goes to
| Destination | What leaves |
|---|---|
| Accounting | Every posting: AR, AP, VAT, bank, cost of sales |
| Reports | Aging, cash flow, revenue, margin, project P&L |
| Dunning | Overdue invoices entering the ladder |
| Analytics | Revenue and collection dashboards |
| Customers | The invoice PDF and reminder emails, after a person approves |