If you’re maintaining Subscript manually (not syncing it from a CRM, or from a CSV file), you’ll find this tutorial below interesting. We cover:
https://www.loom.com/share/f482bc5c788347189aa059b40489e300
<aside> 👀 Transactions in Subscript can be of several recognition types. Learn more in Transaction Recognition definitions and Product mappings.
</aside>
For recurring transactions, Subscript will show your customers as churned when the recurring revenue ends. This depends on the recognition type of the transaction.
Linear transactions will be marked as churned automatically once the end date passes, if there’s not a renewal transaction following it. The end date is required for linear transactions.
Till-canceled transactions (for auto-renewing contracts) will be marked as churned only when you add an end date to it.
Until the end date, the till-canceled transaction will add revenue continuously (and invoices, if you’re using Subscript Billing and has an invoicing schedule for this transaction).