Understand the Slip object, current revenue behavior for Slip records, and legacy Slip Type settings in Sanka.
Last updated: June 2, 2026
The Slip object is the Sanka object used for sales-side revenue evidence. In current customer-facing wording, many workflows describe this behavior as Revenue, but Revenue is not a separate object in Sanka. It is the current business meaning used when reviewing Slip records for billing and accounting.This page also explains Slip Type, which may still appear in older workspaces, imports, templates, saved actions, or support tickets. Do not treat Slip Type as a required field for current revenue accounting flows.
Claude/Codex
Review this Slip or revenue-related issue before changing data. Show the source order, subscription, invoice, customer, line items, amount, tax, revenue date, Slip Type if present, related journal entry, duplicate risk, and missing fields. Do not edit accounting records yet.
Reviewing Slip recordI reviewed the Slip record. Confirm the source record, customer, line items, amount, tax, revenue date, and accounting lineage before creating or changing downstream records.
Ask about another Slip issue...
What a Slip record represents
A Slip record represents sales-side evidence used before billing or accounting output is accepted. It helps your team confirm what commercial event created revenue and how that event connects to invoices, payments, and journal entries.Common fields include:
Slip ID or record ID
Customer company or contact
Source record, such as deal, order, subscription, or invoice
Line items, quantity, unit price, tax, amount, currency, and notes
Revenue date, issue date, or service period
Related invoice, order, subscription, payment, and journal entry
Record owner, source, action history, import history, and audit trail
Slip records are not a replacement for correcting the source transaction. If an invoice, payment, inventory movement, or journal entry is wrong, fix or correct the source record instead of silently editing the Slip evidence.
Current revenue behavior
Revenue is the current business wording for how Slip records are used in sales-side accounting. Use Revenue wording when you explain the business flow, but keep the object identity as Slip.
Deal or estimate records should lead to an order when the customer accepts the commercial terms.
Orders are the normal source for invoices and subscriptions.
A Slip record can be created from, or associated with, the order, subscription, or invoice before journal review.
Journal entries should be reviewed against the Slip record and source invoice, payment, bill, or manual accounting decision.
If a conversion or journal action asks for an order or revenue link first, that is expected behavior. Create or resolve the missing source record, then rerun the action from the action history instead of forcing a journal or invoice without lineage.
What Slip Type means
Slip Type is legacy classification data for older Slip records and settings. It can help explain historical records or old templates, but current revenue behavior does not depend on an active Slip Type field.Expected behavior:
Existing Slip records remain readable according to workspace permissions and views.
Old Slip Type values may remain on historical data, imports, or templates.
New Slip records should not require users to choose a Slip Type for current revenue accounting behavior.
Accounting-sensitive actions should validate Slip revenue evidence, source records, orders, invoices, payments, and journal entries instead of relying on Slip Type.
If a legacy label appears in a URL or template, the business behavior should still be checked against the current Slip, invoice, payment, or journal entry record.
How to troubleshoot
The UI says Slip but the business discussion says revenue
Treat Slip as the object and revenue as the current business wording for sales-side accounting behavior. Confirm the Slip record, source record, customer, line items, amount, tax, date, and related journal entry.
A CSV or import file contains Slip Type
Treat Slip Type as legacy data unless the import is explicitly updating older Slip records. For current revenue workflows, confirm the source record, customer, line items, amount, tax, currency, and date instead.
A PDF template still says Slip
Check whether the template is intentionally preserving historical wording. If the document is used for current sales accounting, update the visible label only after confirming that the document type and customer-facing workflow are still correct.
AI cannot decide whether this is legacy or current behavior
Ask AI to classify the issue first: Slip record, Slip Type setting, CSV/PDF label, invoice/payment issue, or journal-entry issue. Escalate if the customer expects current revenue behavior but the product still requires Slip Type.
Checkpoints
Before replying to a Slip-related support question, check whether the customer is asking about a record, a label, an import file, a PDF template, or the current revenue accounting flow. Keep the object identity as Slip and keep Slip Type references limited to legacy compatibility.
Search Sanka...
Review Slip lineage
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
3Slip draft reviewed2026/05/20 10:00Slip 0031Checked source order, customer, line items, amount, and taxClaude / Codex
2Slip record updated2026/05/20 10:20Slip 0031Confirmed revenue evidence from the source orderOperations user
1Journal source checked2026/05/20 10:30May revenue journalConfirmed journal entry used the Slip and invoice sourceFinance user
Slip review should confirm the commercial source before accepting billing or journal output.
