Use Claude or Codex to prepare deferred revenue, service periods, monthly recognition schedules, and accounting review records in Sanka.
Last updated: May 29, 2026
This guide shows how to use Sanka to prepare deferred revenue and revenue recognition from order and billing terms. Start by asking Claude or Codex to structure the contract period and billing data, then review the schedule before using it for accounting.
Claude/Codex
Review this annual prepaid order and prepare deferred revenue and monthly recognition drafts in Sanka. Use the invoice amount, payment status, service start date, service end date, amendments, and cancellation terms. Do not post accounting entries yet.
Preparing revenue recognition draftI prepared deferred revenue and monthly recognition drafts. Please review service period, allocation basis, amendments, and accounting handoff before posting.
Ask for another RevRec check...
Before you start
Check that you have the following ready.
Orders, invoices, subscriptions, or contracts are available in Sanka
Service start date, service end date, billing amount, and payment status are known
Your team has a revenue recognition policy for annual, monthly, usage, and milestone contracts
Changes such as amendments, cancellations, upgrades, and downgrades can be tracked
You have permission to review revenue schedules and accounting handoff records
Ask AI to prepare the recognition basis
Ask Claude or Codex to turn order and billing terms into a reviewable schedule. Keep the result as a draft until finance confirms the calculation basis.
Sample prompt
/sanka Prepare a revenue recognition draft for this contract. Show invoice amount, collected amount, deferred revenue balance, service start and end dates, monthly recognition amount, and any amendment or cancellation risk. Do not post entries.
Review:
Contract and service period
Invoice amount, collected amount, and open balance
Deferred revenue balance
Monthly recognition amount and method
Contract changes that affect the schedule
Records that support the calculation
Connect billing, subscriptions, and deferred revenue
Revenue recognition should be connected to the same billing records that created the customer obligation. Before approving a schedule, confirm whether the source came from a one-time invoice, a HubSpot deal, a subscription, usage billing, or a milestone invoice.Check:
Source order, invoice, subscription, contract, or HubSpot deal
Service start date, service end date, renewal date, and billing frequency
Upfront invoice amount, collected amount, deferred balance, and open balance
Product or service lines that should be recognized differently
Accounting destination, journal handoff rule, and approval owner
Prepare deferred revenue accounting data
Use Sanka to prepare a reviewable deferred revenue table before accounting handoff.
Column
Purpose
Customer and contract
Shows which customer and agreement created the balance
Source invoice
Links deferred revenue back to the billing event
Service period
Explains the recognition start and end dates
Deferred balance
Shows the remaining liability before recognition
Monthly recognition
Shows how much revenue is recognized each month
Change event
Explains upgrades, cancellations, credits, or refunds
Approval status
Shows whether finance has approved the schedule
Review changes and approvals
If the contract changes, ask AI to explain the effect before changing the schedule. Finance should approve changes that affect recognized revenue.
Sample prompt
/sanka This contract was upgraded mid-period. Explain how the upgrade affects deferred revenue and monthly recognition. Prepare the revised schedule, but keep it pending review.
Before approval, confirm:
The old and new contract terms are both preserved
The revised schedule starts on the correct date
Any credit, refund, or additional invoice is reflected
The schedule can be explained from source records
Hand off to accounting
After review, prepare journal-ready data or accounting sync data according to your team's process. Sanka keeps the source records and change history connected so the accounting team can trace the schedule.
Checkpoints
Use Sanka logs and tables to review deferred revenue creation, schedule changes, approvals, and accounting handoff.
