Sanka is a cloud ERP that helps you manage the full Order → Stock Allocation → Billing → Payment process on a single platform.
This page gives an overview of a typical order-to-cash flow and how to design your sales operations around it in Sanka.
Sales operations in Sanka are built around the following objects and steps:
Order entry
Capture who you sell to, what you sell, for how much, and under what terms.
Stock allocation
Reserve inventory against orders and coordinate with warehouses and purchasing.
Billing / invoicing
Issue invoices based on shipping, acceptance, or monthly closing rules.
Payment & receivables
Record payments, match them to invoices, and track open receivables.
The following sections walk through each step at a high level.
Start by registering an Order in Sanka as the origin of your transaction.
Typical data points:
Customer: linked to Company and Contact
Commercial terms: payment terms, closing date, billing account
Products / services: selected from the Item object
Quantity and price: including tax settings and discounts
Delivery conditions: warehouse, shipping method, requested delivery date
Because the order drives stock allocation, billing, and cash collection, it is important to capture the basic 4W clearly: who you sell to, what you sell, at what price, and by when.
Related documentation (English):
/en/commerce/order-object
/en/contact/company-object
/en/contact/contact-object
/en/item/item-object
After order entry, allocate stock as needed. Sanka uses Inventory and Inventory Transaction objects to keep track of on-hand, reserved, and available inventory.
Key points:
Track per order whether stock is fully allocated, partially allocated, or unallocated
Check inventory by warehouse (Location) when deciding where to ship from
Coordinate with purchasing and production when inventory is insufficient
By managing stock allocation explicitly, you reduce the risk of overselling, double allocation, or delayed shipments.
Related documentation:
/en/item/inventory-object
/en/item/inventory-transaction-object
/en/item/location-object
/en/process/inventory-allocation
Based on your commercial rules, create Invoices from orders.
Typical patterns:
One-time billing on delivery or acceptance
Monthly closing (for example, month-end closing / next-month payment)
Project-based or milestone-based partial billing
By linking orders and invoices, you can always see:
How much has already been billed for each order
How much remains unbilled
Related documentation:
/en/commerce/invoice-object
After issuing invoices, record Payments and match them to the correct invoices.
Example workflow:
Check bank statements or payment service reports
Register payment records in the Payment object
Link each payment to the relevant invoices
Handle partial payments or bulk payments that cover multiple invoices
This makes it easier to monitor:
Open receivables by customer
Overdue invoices and collection risks
Related documentation:
/en/commerce/payment-object
Once your order-to-cash data lives in Sanka, you can use Report and Dashboard to monitor and improve your sales operations, for example:
Order, shipment, and revenue trends by segment or channel
Bottlenecks in stock allocation and shipping
Collection performance and aging of receivables
---
Sanka’s sales operations workflow is designed to connect orders, inventory, billing, and cash collection end to end. Start with a simple flow that matches your current process, then iterate and refine as your team gains familiarity with the system.
