Start a recognition schedule
Apply a policy to an invoice, payment, or manual amount, and see which journal entries Kick posts.
Attach a policy to a payment or invoice already in Kick, or add a manual amount when the work has started and no source is in Kick yet.
Applying a policy from a source
A recognition schedule starts from the source that carries the amount to recognize. The source can be a transaction, an invoice or invoice line, or a manual amount. Applying a policy to that source creates the schedule.
Choose the source
From a transaction
Use a transaction when the payment is the record that carries the amount to recognize. In Accrual review, open the Recognition schedule column on the transaction and choose the policy.

After a policy is applied, open the row menu and click View recognition schedule. Edit this schedule opens the same schedule for a change.
A bank payment that includes tax or a deposit
From an invoice
Use an invoice when the invoice line is the amount to recognize. The invoice must be Open or Paid, and in USD. A Draft, Void, or Uncollectible invoice cannot start a schedule. In Accrual review, open the Recognition schedule column on the invoice line or invoice.
The whole invoice. The schedule uses the service lines minus the discount lines that point at them. Tax stays on sales tax payable. A deposit stays on customer deposits.
One service line. The schedule uses that line minus its share of the discount. Tax and discount lines follow the line they came from, and they have no schedule of their own.
Stripe
Schedule the Stripe charge, not the Stripe invoice line. Split the charge so the policy is on the service after the discount, and tax has no schedule. Match the charge to the invoice, and leave the invoice without a recognition schedule.
Apply manually
Use a manual amount when the work has started but the source is not in Kick yet, such as a migrated entity or a contract that began before the invoice exists.
Click Apply, then Add manually.
Enter Source label, Amount, and Term start. If the policy uses a specific date, enter Specific date. When the policy covers more than one entity, choose Entity.
Apply in bulk
When several rows use the same policy, select them from the review table and click Set recognition schedule. Each selected row becomes its own recognition schedule.
Set a schedule with a rule
Set the rule criteria first, then continue to the Actions section. Choose Set recognition schedule and select the policy. When the rule runs, Kick starts a recognition schedule for each matching transaction.
Auto confirm off leaves the schedule as a draft and posts nothing. Open Review rule-suggested revenue schedules and confirm it. Confirming posts the same entries as applying the policy directly, including future periods. Auto confirm on posts those entries when the rule runs.
A Split Rule can set a policy on each split line. Use that when part of the payment is tax or a deposit.
→ Rules
What posts
Post the schedule. Kick posts a recognition entry for every period, including future periods. Each entry debits the holding account, credits the revenue account, and uses that period's date. A rule with Auto confirm off posts nothing until you confirm the schedule.
On apply
The source amount moves to the holding account.
Kick debits the recognition account and credits the holding account on the term start.
No opening entry.
Each period, including future periods
Debit the holding account, credit the revenue account.
Debit the holding account, credit the revenue account.
Debit the holding account, credit the revenue account. This builds the holding asset.
When the customer pays
The payment clears accounts receivable. It does not credit revenue again.
The payment clears accounts receivable. It does not credit revenue again.
The payment clears the accrued-revenue asset. It does not credit revenue again.
A rule with Auto confirm off skips the apply and recognition entries until you confirm it from Review rule-suggested revenue schedules. Confirming posts the same entries. The payment row still waits for the customer to pay.
Last updated
Was this helpful?
