Understand how slip records work in Sanka, including sales slips, withdrawal slips, deposit slips, transfer slips, delivery slips, PDFs, associations, and AI checkpoints.
Last updated: May 29, 2026
The Slip object stores transaction evidence and operational documents such as sales slips, withdrawal slips, deposit slips, transfer slips, and delivery slips. Use slip records when your team needs a document or internal proof of a transaction, movement, delivery, or adjustment without changing the original invoice, payment, disbursement, or inventory record directly.This reference explains what a slip should contain, how it connects to finance, inventory, and PDF templates, and what to check before creating, editing, issuing, importing, or troubleshooting slips with AI, actions, workflows, CSV, integrations, or manual entry.
Claude/Codex
Review this slip request before creating anything. Show the slip type, source record, customer or supplier, line items, amount, tax, delivery or transaction date, related invoice/payment/disbursement/inventory record, PDF template, duplicate risk, and missing fields. Do not issue the slip yet.
Reviewing slip draftI reviewed the slip request. Please confirm slip type, source record, line items, amount, tax, related records, and PDF template before issuing the document.
Ask for another slip check...
What a slip record represents
A slip record represents supporting evidence for a transaction or operational event. It may be used for customer-facing documents, supplier-facing documents, warehouse handoffs, internal accounting support, or audit review.Common slip types include:
Sales slip: proof of a sale, transfer of goods, or sales-related transaction
Withdrawal slip: proof of outgoing cash, funds, goods, or other withdrawal movement
Deposit slip: proof of incoming funds, receipt, or deposit movement
Transfer slip: proof of a transfer between accounts, locations, departments, or other internal buckets
Delivery slip: proof of delivery, shipment, or handoff to a customer or warehouse
A slip is evidence or documentation. It should not be used as a silent replacement for the source record when an invoice, payment, disbursement, inventory transaction, or journal entry needs to be corrected.
Key fields and relationships
Common fields include:
Slip ID or record ID
Slip type
Customer, supplier, location, department, or other related party
Related source record, such as order, invoice, payment, disbursement, inventory transaction, or journal entry
Line items, quantity, unit price, tax, amount, currency, and notes
Issue date, delivery date, transaction date, or posting date
Record owner and status
PDF template, files, messages, or attachments
Source details from UI, CSV, integrations, actions, workflows, or AI-assisted creation
Slips often sit near other records but do not always create them automatically. For example, a delivery slip may support delivery evidence, while the inventory transaction records the stock movement and the invoice records the customer billing request.
Create or review a slip safely
Create a draft or review the planned slip before issuing a customer- or supplier-facing PDF.
Sample prompt
/sanka Prepare a slip draft from this source record. Keep it as a draft and show slip type, customer or supplier, source record, line items, quantity, amount, tax, issue date, delivery or transaction date, related invoice/payment/disbursement/inventory record, PDF template, and any missing fields. Do not send or download the final PDF yet.
Before creating a slip, confirm whether the source record already has a slip or document attached. Duplicate slips can confuse customers, warehouses, accounting teams, and audit review.
Issue PDFs and documents
Slips can be downloaded or issued as PDFs when the workspace uses document templates. The PDF output depends on the selected template and the data saved on the slip and related records.Before issuing a PDF, check:
The correct slip type is selected
Customer, supplier, sender, recipient, and address fields are correct
Line items, quantities, tax, currency, and totals match the source record
Delivery, transaction, or issue date is correct
The selected PDF template includes the required fields
The document has not already been sent or attached in another place
If the PDF layout or data is wrong, check the slip record and document template settings before treating it as a PDF generation bug.
Expected behavior
When a slip is created successfully:
It appears in the Slip object list unless it is archived or filtered out by the current view
Slip type, owner, source, related party, dates, line items, amounts, tax, currency, and notes are saved
It can be associated with source records such as invoices, payments, disbursements, orders, inventory transactions, or journal entries
It can be exported, imported, reported, and included in workflows when the workspace supports those operations
PDF output follows the configured document template and current record data
Creating a slip does not automatically guarantee that accounting, inventory, payment, or invoice records are also created
If the slip is only documentation, changing it may not change the source transaction. Correct the source record when the underlying invoice, payment, disbursement, stock movement, or accounting entry is wrong.
Troubleshooting
A slip is missing from the list
Check the current view filters, archive view, permissions, slip type, owner, source record, and whether the slip was created in a different workspace or object flow.
The slip type is wrong
Confirm whether the event is a sale, withdrawal, deposit, transfer, or delivery. If the wrong slip type was issued externally, create a corrected slip or follow your team’s cancellation process instead of silently editing sent evidence.
Line items or amounts do not match the source record
Compare quantity, unit price, discount, tax, currency, rounding, and source associations. If the source invoice, payment, disbursement, or inventory transaction is wrong, correct that record first.
The PDF output is missing fields
Check whether the slip has the required record values and whether the selected document template includes those fields. Also confirm whether you are previewing the latest saved template.
A duplicate slip was created
Check whether an action, workflow, CSV import, integration, or AI-assisted request ran more than once. Before archiving duplicates, confirm which slip has the correct source record, PDF, message, and audit trail.
AI cannot decide whether this is a bug
Ask AI to compare the slip type, source record, related records, template settings, action history, import history, permissions, and audit trail. Treat it as a possible bug only after confirming the source data and template are correct.
Checkpoints
Before creating, issuing, importing, correcting, or replying to a slip support case, check the slip type, source record, related party, line items, dates, amount, tax, currency, PDF template, related invoice/payment/disbursement/inventory/journal record, duplicate risk, permissions, and audit trail.
Search Sanka...
Review slip evidence
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
3Slip draft reviewed2026/05/20 10:00Delivery slip 0031Checked order, line items, delivery date, and PDF templateClaude / Codex
2Slip issued2026/05/20 10:20Delivery slip 0031Downloaded reviewed PDF for warehouse handoffOperations user
1Source record checked2026/05/20 10:30Order 1042Confirmed invoice and inventory records were separate from the slipSanka user
Slip review should confirm whether the slip is documentation only or whether the source transaction also needs a correction.
