Documentation
Documentation
Start typing to search…

What does Zenskar implementation entail?

🔖

Important

Integrating Zenskar with your system takes only 3-6 weeks, depending on the complexity of your requirements.

The optional pilot program

The primary objective of the pilot program is to showcase the capabilities of Zenskar: a modern, flexible, no-code billing infrastructure for your business. However, the pilot program is optional if you have already chosen Zenskar as the billing infrastructure for your business.

Implementation roadmap

Objectives

Time frame

Zenskar's responsibilities

Your responsibilities (Zenskar will be your guide)

  1. 🤝 Align on the requirements, and get 🆗 approvals from all relevant stakeholders.

  2. 😊 Fulfill custom feature requests, if any.

Weeks 1-2

  1. Align with you on the requirements for going live, such as:
    • contracts,
    • invoice formats,
    • usage data structure,
    • revenue recognition/AR nuances.

  2. Build and ship custom feature requests, if any.

  1. Get stakeholders' approvals on the requirements for going live, such as:
    • contracts,
    • invoice formats,
    • usage data structure,
    • revenue recognition/AR nuances.

  2. Get approvals on custom feature requests.

⚙️ Configure your Zenskar sandbox account with contracts, customers, usage data/aggregates, and journal entries.

Weeks 1-2

Configure your sandbox based on mutually agreed-upon requirements for contracts, customers, usage data/aggregates and journal entries.

  1. Share contracts and customers data.

  2. Usage data:
    • Let Zenskar pull usage data from your data sources, such as data warehouse and spreadsheets. 🚧 Note: you do not need to allocate engineering bandwidth.

    • Alternatively, push usage data using Zenskar's data-ingestion API. 🚧 Note: you must allocate engineering bandwidth.

ℹ️ Optional:
Connect test/production accounts of your CRM/ERP/Tax/Payment software with Zenskar’s sandbox account.

Week 3

Assist you in connecting test/production accounts of your CRM/ERP/Tax/Payment tools with Zenskar’s sandbox account.

Connect test/production accounts of your CRM/ERP/Tax/Payment software with Zenskar’s sandbox account.

🧪 Testing:
Compare Zenskar with the existing process for a sample set of contracts, invoices and journal entries for the last billing cycle in the sandbox account.

Week 4

Assist you in comparing the invoices and journals generated by Zenskar with the invoices and journal entries in your existing setup.

Generate invoices and journal entries on Zenskar and compare them with the invoices and journal entries generated by your existing setup.

⚙️ Configure your Zenskar production account for automation.

Week 5

Assist you in configuring live contracts, customer details, and setting up ongoing usage data, and aggregates in your Zenskar production account.

Configure live contracts, customer details, and set up ongoing usage data and aggregates in your Zenskar production account.

ℹ️ Optional (if you want to migrate historical data into Zenskar):
Import historical contracts, customer details,invoices, and journal entries into your Zenskar production account.

Week 6

Assist you in importing and configuring historical contracts, customer details, invoices and journal entries into your Zenskar production account.

Import/configure historical contracts, customer details, invoices and journal entries into your Zenskar production account.

🚀 Sign-off and go live.

Week 6

Ensure everything is ready to go live.

Go live on your Zenskar production account.

Data migration and integration options

The documentation on data migration and integration options describes various options for migrating historical data and for integrating contemporary data for both sales-led and product-led motions.

Updated 18 days ago