Vendor setup
Vendor record, payment terms, default financial dimensions.
Why it mattersEvery field on a purchase invoice can inherit from here — dimensions, currency, cash discount code.
Follow a purchase and a sale station by station. Every step that posts drops into the same chart of accounts, the same dimension rules, the same ledger.
Vendor record, payment terms, default financial dimensions.
Why it mattersEvery field on a purchase invoice can inherit from here — dimensions, currency, cash discount code.
Customer record, credit terms, default financial dimensions.
Why it mattersCredit-limit checks and default dimensions both key off this one record for every order that follows.
Vendor record, payment terms, default financial dimensions.
A purchase order for an item, quantity, and location.
Matched against the PO and receipt — plus any freight or handling charges.
Dimensions resolve, the invoice posts to the ledger.
Posts to the ledgerScheduled and settled — cash discount applied if still earned.
Posts to the ledgerCustomer record, credit terms, default financial dimensions.
Item, quantity, and location — with live inventory reserved.
Posts the receivable — and the item's inventory and cost-of-goods-sold in the same step.
Dimensions resolve, the invoice posts to the ledger.
Posts to the ledgerPayment received — aging and cash discount tracked automatically.
Posts to the ledgerPick a document and watch it post. Each line finds its account through the same rules, picks up the same dimensions, and lands in a voucher that must balance.
No dimensions set on the invoice — the customer’s default set is inherited
A voucher cannot post until it balances
One posting raises the receivable, the tax, and the stock movement together — they cannot drift apart.
Sales invoices, purchase invoices, free-text invoices and payment journals all resolve through this one engine — one chart of accounts, one set of dimension rules.
Three instruments from the payments desk. Move them and watch the rules respond exactly as they do in the product.
Code 1%7: pay within 7 days of the invoice date and 1% comes off. Drag the payment date.
Settling posts two extra lines — Cash Discount Taken and Cash Discount Offset — and the invoice still closes in full.
A 12,000.00 USD invoice under three payment schedules.
Equal fixed installments; whatever is left over becomes the final payment. Schedules are currency-specific, and optional minimum and maximum amounts are checked when the invoice posts.
A 2,000.00 payment. Every fee rule that matches fires — they stack, not compete.
Trade agreements price by customer, group, quantity break and date. Change the sale and watch the engine choose.
Ranges are half-open: From is inclusive, To is exclusive — so 100 belongs to [100, ∞), not [10, 100).
Rules are published by posting a Trade agreement journal. Validation rejects duplicates and overlapping ranges, so the engine is never left guessing.
Tickets never touch the ledger. They move through the statuses your team defines, against the response time their priority promises. Three real outcomes of the same workflow:
Created automatically from the “oil-change-monthly” template, on a rental agreement’s monthly schedule
Every new ticket lands in your Initial status and draws its number from the sequence you choose.
Assign an agent and the ticket steps into your Assigned status — and the agent is notified in real time.
Each priority carries a response-time target. The status that stamps “resolved at” decides whether the SLA was met.
Statuses such as Cancelled demand a reason. Every change — who, when, from what — is kept in Status history.