S2P: Sourcing -> Procurement -> Payment

What you'll achieve

S2P (Source to Pay) is an end-to-end approach to manage purchase request -> purchase order -> invoice -> approval -> payment. This guide summarizes the baseline steps and key points for running S2P in Sanka.

S2P overview

• Make the full state from request to payment visible
• Standardize approval rules across departments to prevent missed or duplicate payments
• Use reports to understand spend trends and drive improvement

Steps

1. Set up vendors and approval rules Organize partner information and define approval rules by amount and department.
2. Create purchase orders Register the PO based on the request and clarify amount, delivery date, and owner.
3. Capture invoices Import invoices or payment requests and link them to the PO.
4. Receive and match Check quantity, amount, and delivery dates, then adjust when needed.
5. Run approvals Route approvals based on the defined flow and record results.
6. Complete payment and record Confirm payment date and method, then update payment status.
7. Visualize with reports Review spend trends and department patterns in dashboards.

Operating tips

• Make PO number, invoice number, and due date mandatory fields.
• Define rules for exceptions (variances, urgent payments) and keep records.
• Run weekly/monthly reviews to detect delays or duplicates early.

Common pitfalls

• POs and invoices do not link
  • Standardize PO numbers and vendor naming.
• Approvals stall
  • Review approver permissions and notification settings.
• Missed payments
  • Create a due-date view and check it daily.

Related pages

• Purchase Order object
• Bill object
• Accounts payable operations
• Approval workflows
• Dashboard