Ginesys 360See. Trust. Act.
Ginesys · internal · plan for feedback, 21 Nov 2026

Ginesys 360

Know every customer. Grow every customer.

Every night it reads our systems and joins them into one view of every customer and every product. It starts small: every customer, what we bill, what is outstanding, and what we bill against what the customer is licensed for. Every morning it shows where the two disagree, in ₹, and where to fix it.

Plan for feedback. Nothing is in use yet.
Billing appbilled Licence applicensed Product appsapp usage CRM appsupport Cloudcloud cost Ideas portalideas Google Sheetsthe rest Ginesys 360joined every nightone customer, whole Seeevery customer, whole Trustwhere systems disagree, in ₹ Actfix it in its own system

Why this is the lifeline

In a SaaS business about 90% of the work is keeping and growing the customers we already have; about 10% is adding new ones. Ginesys 360 is the system for the 90%.

Where it is going

By 9 am every working day, anyone who deals with customers can open any customer and, in under a minute, know what they have, what they pay, what they cost us, how healthy they are and why, what is due, and what is wrong in our own systems.

See

One page shows the whole customer.

Trust

Numbers are reconciled across systems first, and each says how complete it is.

Act

Each difference carries its own action, and is fixed in its own system.

What is built first

The first release is small

Only seven screens are built first. Everything else on this page is the direction: it comes later, phase by phase, as its data arrives. We build a piece only when enough is known to build it, and a screen may change as data comes.

Customers

Every customer with a live subscription. You see the customers you manage.

The customer's page

Billed and licensed, product by product, and the subscriptions.

Subscriptions

From the billing app alone. Every live subscription, ARR by product group, and every line to download.

Outstanding

From the billing app alone. Open invoices by age; over a year in red; receipts not yet adjusted.

Billed vs Licensed

Not Billed, Not Licensed, Cannot Compare, Matched. Each row with a reason and a status.

Data Check

Under Admin. What came in last night, source by source. Bad rows are held back.

Mappings

Under Admin. Each billing product, its product group, and the licence it is compared with.

The menu, in two zones

For everyone, by roleHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs LicensedLater, as their data comesLicencesCloudApp usage
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log

Billing and every ₹ value are shown by role: see People and Rules. Home has no screen of its own yet.

Three hand-kept sheets stop

Once these screens are in use, the accounts team stops three sheets: licence reconciliation (Billed vs Licensed), subscription lines for MIS (Subscriptions) and debtor outstanding (Outstanding).

ARR is recurring only

₹83.8 crore. A quarterly line is counted four times, a monthly line twelve times. One-time charges, one-time licences and one-time discounts are left out.

Where it stands

The mock of these screens is accepted as the shape to build from. The screens are built when enough is known: replies are awaited from teams.

Two more sheets wait for cloud information. Licence expiry reminders stay with the licence app. Cloud cost, app usage, margin and health come in later phases.

Where your feedback is needed

What made a customer leave?

The signs you saw before it happened.

What would you open this for?

The one list that changes your day.

Which sheet belongs here?

Each can be added as a source.

What is missing?

Tell Prashant. Screens may change as data comes.

The story of one customer

The same customer, the same four events, told twice. Sample customer; this is how it goes today, and where Ginesys 360 is going. The first release already shows the unpaid invoices and finds the unbilled users; the health colours come in a later phase.

Todayfour people each see one piece AugUsers cut 60 to 45Only the accounts team knows OctTwo invoices unpaidOnly finance knows NovTickets pile upOnly support knows RJan: renewalThe customer leaves"We never saw it coming" Every system knew a part. Nobody saw the whole.
With Ginesys 360one line, seen by everyone, the next morning A13 AugHealth turns Amber"Users 60 to 45" is on theaccount manager's home R5 OctOverdue: Health turns RedThe territory managersees it too ANovThe team actsTickets cleared, dues paid;15 unbilled users found GJan: renewalThe customer renewsand ₹1.8 lakh a year ofleakage is now billed Same systems, same people. The difference is that the pieces are joined, every night.

Nothing new to type

Every fact was already in a system. Ginesys 360 only reads and joins.

Seen the next morning

Not at renewal, and not when someone happens to check.

Hours given back

The checks that people do by hand in sheets today are done every night. Three of the accounts team's sheets stop with the first release.

Today: many systems, no whole

The billing app knows what we charge, the licence app what we license, each product app what is actually used, the cloud providers what it costs. Each system is right about its own part. None of them talks to the others, and no one of them can replace the rest.

Billing appCustomersSubscriptionsInvoicesPaymentsFinance Licence appLicencesUsers, storesInstancesSign-insAccounts Product appsUsers in useStores in useLocationsApp usageProduct teams CRM appTicketsSLA breachesProjectsAccount ownerSupport, delivery CloudServers, tenantsData sizeCloud costCloud team Ideas portalIdeas raisedVotesProduct team Google SheetsReconciliationsUsage, storageHosting listWhoever keeps it No link between any two. The only bridge today is a person with a spreadsheet.
4 systems

to open to answer one question about one customer.

0

places where a customer's licences, billing, support and cost are seen together.

By hand

is how billing is checked against licences today: exports pasted into a sheet.

Sheets kept by hand today, and what takes them over

The accounts team keeps these sheets by hand. Three of them stop once the first release is in use and trusted.

Kept by hand todayTaken over byWhen
Licence reconciliation sheetBilled vs LicensedFirst release
Subscription lines sheet, for MISSubscriptionsFirst release
Debtor outstanding sheetOutstandingFirst release
Cloud reconciliation sheet, with duesA later phaseWaits for cloud information
Data capacity billing sheetA later phaseWaits for cloud information
Licence expiry remindersNot taken upStays with the licence app

Other checks done by hand today: Ginesys POS and Zwing POS user licence checks are done by Billed vs Licensed; running servers against live customers comes later, with Licensed vs Cloud.

How it works

It only reads. Every night it does the same steps, so every page is ready in the morning. Data is at most one day old.

2 am7 am 1 Readeach sourcesystem, as it is 2 CheckData Check holdsback bad rows 3 Mapto the billingapp's customer 4 Reconcilewhere systemsdisagree, in ₹ 5 Allocatelater: sharedcost by product 6 Measurelater: cloud cost,margin, health 7 Showready whenyou sign in the first release: steps 1 to 4, and 7 later phases, as their data arrives It never writes to any system. Wrong data is fixed in its own system, and the next night shows it.

The four words

One word for each system. Screens use only these words.

Billing app

Billed

What we charge the customer for.

Licence app

Licensed

What the customer is entitled to.

Cloud providers

Cloud

What we run for the customer, and what it costs. An on-premise customer has cloud cost zero.

Product apps

App usage

What the customer actually uses.

Billed vs Licensed: firstLicensed vs Cloud: laterLicensed vs App usage: laterRevenue vs Cloud cost: later

One hub: the customer comes from the billing app

Billing appthe customer:one row per BA code Licence appLicensed Cloudlater Product appslater CRM applater Ideas portallater Any new sourcelater

Every system maps only to the hub

Systems are never mapped to each other, pair by pair. Each one has a single mapping: its own record to a BA code.

Nothing is dropped

A record that matches no customer is shown as "Not in the billing app". A customer with nothing on the other side is shown too.

Prevention at source, detection here

The licence app checks the BA code against the billing app when a customer is created. Ginesys 360 still compares every line, every night.

The first release

Billing: Subscriptions and Outstanding

Both come from the billing app alone. Nothing is compared with another system, so they can be used as soon as the billing app is read every night.

Subscriptions

₹83.8 crore

ARR, recurring only, before tax. Billing app, 21 Nov 2026.

Every live subscription: 799 customers, 1,597 subscriptions, 5,797 lines. ARR by product group, and every line to download for MIS. It replaces the accounts team's subscription lines sheet.

Outstanding

₹14.0 crore

1,258 open invoices, 513 customers. Billing app, 21 Nov 2026.

Open invoices, aged from the due date in four buckets: not due, 1 to 90 days, 91 to 365 days, over a year. Over a year is a red alert. It replaces the accounts team's debtor outstanding sheet.

ARR is recurring only

A quarterly line is counted four times, a monthly line twelve times. One-time charges, one-time licences and one-time discounts are left out. Recurring is what the billing app marks as recurring.

Unadjusted is shown apart

₹0.50 crore is received and not set against an invoice. It is the accounts team's list to clear. It is not netted from outstanding.

No single billing model per customer

One customer can be on different billing models for different products. So a customer carries no billing label here; each line says whether it is recurring.

The first release

Billed vs Licensed

What we bill (billing app) against what the customer has (licence app), by customer and by product, every night. Every row falls into one of three groups, or it is Matched.

First match by hand, 21 Nov 2026customers With a live subscription, billing appBilling app: 799 customers with a live subscription799 Live customers, licence appLicence app: 722 live customers722 On both sidesOn both sides: 692 customers692 With no differenceNo difference: 617 customers617

Real totals from the first match, done by hand before any rule was coded. Of the 692 customers on both sides, 617 agree on every product and every count.

Not Billed
70 rows

The customer has it in the licence app and we do not bill it. This is the leakage.

Whole customer 30One product 18Extra units 22
Not Licensed
120 rows

We bill it and the customer does not have it in the licence app.

Not yet set up 9Access switched off 8One product 5Extra units 98
Cannot Compare
4 groups

Billed, with no licence record to compare with yet. Nothing to do until the source comes.

EaseMyGSTQlik BIIntegrationOMS user counts
Matched
617

Customers where billed and licensed agree, product by product and count by count.

Counts are from the first match by hand, 21 Nov 2026. They will move once the nightly run takes over.

Every row carries a reason

The system works out the reason. On the screen it is a filter: one click shows only those rows, with their count.

GroupReasonWhat it meansFirst match
Not BilledWhole customerLive in the licence app, with no live subscription at all30
Not BilledOne productThe customer is billed, and holds one product we do not bill18
Not BilledExtra unitsMore users or sites licensed than billed22
Not LicensedNot yet set upBilled, and not in the licence app yet: onboarding pending9
Not LicensedAccess switched offBilling goes on for a customer whose access is switched off8
Not LicensedOne productOne billed product has no licence5
Not LicensedExtra unitsMore users or sites billed than licensed98

Every row has a status

OpenSet by the system, the nightthe difference is found ExplainedSet by a person, with a reason:temporary licence, internal customer FixedSet by the system, when a laternightly run no longer finds it fixed in its own system: the next run closes it

Nothing is corrected here

The data is fixed in its own system: the billing app or the licence app. Each row opens that exact record.

Every ₹ value is ARR

The yearly value of a recurring line: a quarterly line is counted four times, a monthly line twelve times. One-time charges, one-time licences and one-time discounts are left out. So it adds up to the ARR of ₹83.8 crore.

How units are counted

ERP users = core site + additional users. Ginesys POS users = sites + additional users: each site carries one user. Confirmed on real data.

Production by default

Production licences are compared. A Sandbox is compared only where a Sandbox product is billed.

Each product group has a stated licence source

Not every product is licensed through the licence app. Until its source comes, a product group shows as Cannot Compare, not as a difference.

Product groupLicence sourceIn Billed vs Licensed
ERPLicence appCompared
Ginesys POSLicence appCompared
Zwing POSLicence appCompared
OMSLicence appCompared by product; user counts wait for the OMS team's answer
InsightXLicence appCompared
EaseMyGSTUsage from its own applicationCannot Compare until the source comes
Qlik BIThe BI team's licence monitorCannot Compare until it can be read
IntegrationThe integration team, in a later phaseCannot Compare until the source comes
ServicesNothing to licenseRevenue only

Nine product groups. POS is always two: Ginesys POS and Zwing POS. Discounts are revenue only too: each goes to the product it belongs to.

The first release

Data Check

Every source system passes through Data Check each night, before anything is reconciled. One bad row never stops the rest: good rows go on, bad rows wait.

Held back

The row is left out of reconciliation until it is fixed. It keeps yesterday's numbers, with a mark.

Warning

The row is reconciled, with a mark.

Note

Shown only.

One tab per source

A summary on top, then a tab for each source system. A new source gets its own tab when it is connected.

Grouped by the one check

"Account manager missing" is one line. Open it to see the customers. One fix closes many rows.

Fixed in its own system

Each row links to its own system. The next nightly run closes the row by itself.

One other action

"Accept as exception", with a reason. Nothing else can be done to a row here.

Later phases

What comes after, as the data arrives

Honest about its data

Our systems will not agree on day one. Later, every number says how complete it is, and the system has its own health card.

Coverage 87% 87%Coverage Month 1Month 662%87%

Illustration. Coverage is the share of revenue that comes from customers whose data is complete. It starts low and rises as sources are corrected.

CompletePartialIncompleteStale

Shared cloud cost is split by a stated rule

One platform serves many customers and products. Its cost is divided by a driver the cloud team agrees (data size, users, tenants), down to each product, and the split is always shown.

Shared platform cost split by data size ERP 44%Ginesys POS 32%OMS 16%Others 8% ERP 44%Ginesys POS 32%OMS 16% Others 8% "ERP margin 71% (82% of cost direct, 18% allocated)"

Illustration, sample ratios.

History of numbers, not of tickets

Each customer's numbers are saved nightly: trends by week, month, quarter, year.

Gaps are skipped, never invented

If a customer was held back for ten nights, the trend joins the two solid ends.

AI suggests, fixed rules compute

AI proposes a mapping and a person confirms it once. The comparing is done by fixed rules: the same answer every night.

Later phases · the direction

Three lenses, later

The first release has no lens and no action word. The three lenses come when cloud cost, app usage and support data are in. There is no overall score: a large customer in trouble must never look like a small one doing well.

The first release

No action word. Each difference carries its own action.

A row in Billed vs Licensed or in Data Check says what to do, and where:

Open in the billing appOpen in the licence appMark as explainedAccept as exception
Later

At most three words, when health and margin exist

One word per customer, worked out from the lenses by fixed rules:

Needs actionWatchAll good
Later · Lens 1 · How much does it matter?

Tier

Customers Tier A: 17% of customersTier B: 30% of customersTier C: 53% of customers ABC Profit in ₹ Tier A: 80% of profitTier B: 15% of profitTier C: 5% of profit A: 80%15%

The 80/20 rule: Tier A is the few customers who together give the first 80% of our profit.

ABC
Later · Lens 2 · Will it stay?

Health

G A R MoneySupportDeliveryUse

From overdue, tickets and SLA breaches, late projects, and falling app usage.

GreenAmberRed
Later · Lens 3 · Do we earn well on it?

Margin

0% Ginesys average Good: 84%Good: 72%Thin: 46%Thin: 22%Loss: -24% GoodThinLoss

Revenue vs Cloud cost, against the Ginesys average margin.

GoodThinLoss
Tier Health Margin At most three wordslater, not in the first release Needs actionWatchAll good
Later

Profit in ₹ and margin in % are two different things

₹1 lakh profit95% marginSmall customer ₹2.1 cr profit70% marginLarge customer: ranked first

"Most profitable" means the most profit in ₹. The margin gap then shows what a customer would add at the Ginesys average margin: the list of where fixing pays most.

Later

Flags: plain facts, each with the date it started

OverdueHeavy loadGone quietNew

Renewal and expiry reminders stay in the licence app. They are not repeated here.

New customers come first

The longer a customer stays, the stickier it becomes. A customer in its first year that turns Amber or Red goes to the top of the Needs action list, whatever its Tier.

Customer-wise and product-wise

Every number is held per customer and per product, in nine product groups: ERP, Ginesys POS, Zwing POS, OMS, Integration, InsightX, Qlik BI, EaseMyGST, Services.

What the first release looks like

The seven screens that are built first, drawn with sample data. Pick a screen below. The menu is in two zones: for everyone, by role, Home, Customers, Billing and Reconciliation; for the keepers only, Admin. This shape is accepted as the one to build from. Screens of later phases are drawn when their data arrives; these seven may change too, as data comes.

Customers · Every customer with a live subscription
MenuHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs Licensed
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log

Customers

Every customer with a live subscription in the billing app. You see the customers you manage: an account manager their own, a territory manager their territory, executives and accounts all.

Customers799With a live subscription
ARR₹83.8 croreRecurring only, before tax
Matched617Billed and licensed agree
Not Billed70Rows; licensed, not billed
Not Licensed120Rows; billed, not licensed
Find a customerTerritory: AllAccount manager: AllNature of business: AllState: AllDifferences: Any
CustomerNature of businessCityStateTerritoryAccount managerARR, ₹Billed vs Licensed
Kavya Silks
KAVYAS
Brand with EBOKolkataWest BengalEastR. Banerjee18,40,0002 Not Billed
Urban Loom
URBLOOM
MBOPuneMaharashtraWestS. Kulkarni9,60,000Matched
Northgate Retail Private Limited
NORTHG
MBOLucknowUttar PradeshNorthA. Mehra6,25,0001 Not Licensed
Saffron Street
SAFFST
BrandHyderabadTelanganaSouthP. Reddy22,10,000Matched
Meenakshi Textiles
MEENTX
WholesalerCoimbatoreTamil NaduSouthP. Reddy4,80,000Cannot Compare
Blue Thread Apparels LLP
BLUETH
Brand with EBOBengaluruKarnatakaSouthN. Rao31,75,0001 Not Billed
Rangoli Kids
RANGKD
MBOJaipurRajasthanNorthA. Mehra3,36,000Not yet set up

Showing 7 of 799. The brand is shown where the billing app has one, otherwise the customer name; the BA code is beneath. Nature of business, city, state, territory and account manager are read from the billing app. ARR is recurring only, and is shown only to people who may see Billing.

Customer's page · One customer: about, billed and licensed, subscriptions
MenuHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs Licensed
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log
Customers / Kavya Silks

Kavya Silks

Kavya Silks Private Limited · BA code KAVYAS
2 Not BilledIn the licence app: Enabled
Nature of businessBrand with EBO
City, stateKolkataWest Bengal
TerritoryEast
Account managerR. Banerjee

Billed and Licensed, product by product

Billed is from the billing app, Licensed from the licence app (Production).

Product groupWhat is countedBilledLicensedResultWhat to do
ERPUsers (core site + additional)1416Not Billed: 2 unitsOpen in the billing app Mark as explained
ERPFinanceYesYesMatched
Ginesys POSSites2222Matched
Ginesys POSUsers (sites + additional)3030Matched
InsightXLicenceNoYesNot Billed: productOpen in the billing app Mark as explained
EaseMyGSTGSTINs3No licence source yetCannot Compare
ServicesDatabase services1Nothing to licenseRevenue only

Subscriptions in the billing app

SubscriptionPlanStartedNext invoiceLinesARR, ₹
S04512Yearly1 Apr 20261 Apr 2027915,20,000
S05230Quarterly1 Oct 20261 Jan 202723,20,000

The quarterly subscription bills ₹80,000 a quarter; its ARR is four times that. ARR is recurring only: one-time charges are left out.

Subscriptions · Billing: every live subscription
MenuHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs Licensed
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log

Subscriptions

Billing. Every live subscription in the billing app, as of last night. ARR is recurring only: a quarterly line is counted four times, a monthly line twelve times; one-time charges, one-time licences and one-time discounts are left out. This screen replaces the accounts team's subscription lines sheet.

Customers799With a live subscription
Subscriptions1,597992 yearly, 571 quarterly, 34 other
Lines5,797On 143 products
ARR₹83.8 croreRecurring only, before tax

ARR by product group

Product groupARR, ₹ croreShareWhat is in it
ERP30.737%Users, finance, production, operating units, data packs, hosting
Ginesys POS30.236%POS management, sites, users
OMS5.97%Standalone, enterprise and managed
Integration5.26%Loyalty, topics, inbound APIs, recurring custom integration
Zwing POS4.05%Users
EaseMyGST3.64%E-documents, GST returns
Qlik BI1.52%Users, apps
InsightX1.42%Users, data lake
Services1.32%Recurring only: DB, managed and team leader services
Total83.8100%
ViewBy Customer 799By Subscription 1,597By Line 5,797Download Lines
Product groupAll 799ERP 600Ginesys POS 504EaseMyGST 220OMS 143Zwing POS 42More
CustomerAccount managerProduct groupsSubscriptionsLinesPlanNext invoiceARR, ₹
Blue Thread Apparels LLP
BLUETH
N. RaoERP, Ginesys POS, EaseMyGST314Yearly1 Apr 202731,75,000
Saffron Street
SAFFST
P. ReddyERP, Ginesys POS29Yearly15 Jun 202722,10,000
Kavya Silks
KAVYAS
R. BanerjeeERP, Ginesys POS, EaseMyGST211Yearly, Quarterly1 Jan 202718,40,000
Urban Loom
URBLOOM
S. KulkarniERP, OMS16Quarterly1 Jan 20279,60,000
Northgate Retail Private Limited
NORTHG
A. MehraERP, Ginesys POS17Yearly1 Apr 20276,25,000

Showing 5 of 799, largest ARR first. Download Lines gives every line with customer, product, product group, quantity, price, plan, dates and whether it is recurring, for MIS.

Outstanding · Billing: open invoices, by age
MenuHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs Licensed
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log

Outstanding

Billing. Open invoices in the billing app, as of last night: posted, not fully paid. Age is counted from the due date. You see the customers you manage. This screen replaces the accounts team's debtor outstanding sheet.

Outstanding₹14.0 crore1,256 invoices, 513 customers
Not due₹0.87 crore
1 to 90 days₹8.56 crore
91 to 365 days₹4.30 crore
Over a year Red alert₹0.27 crore
Unadjusted₹0.50 croreReceived, not set against an invoice
TabsBy Customer 513By Account Manager 65By Territory 5Invoices 1,258Unadjusted 833Download
AgeAll 513Not due 611 to 90 33191 to 365 164Over a year 19
CustomerAccount managerTerritoryInvoicesNot due1 to 9091 to 365Over a yearUnadjustedOutstanding, ₹
Harbour Lane Stores
HARBLN
R. BanerjeeEast604,80,0009,60,0000014,40,000
Blue Thread Apparels LLP
BLUETH
N. RaoSouth37,90,0003,10,00000011,00,000
Northgate Retail Private Limited
NORTHG
A. MehraNorth403,12,0003,12,0001,10,00007,34,000
Kavya Silks
KAVYAS
R. BanerjeeEast204,60,000001,20,0004,60,000
Meenakshi Textiles
MEENTX
P. ReddySouth201,20,0001,20,000002,40,000

Showing 5 of 513, largest overdue first. Invoices lists each invoice with its number, dates, amount, paid, TDS and balance. Unadjusted lists the payments and credit notes sitting on a customer account with no invoice set against them. It is the accounts team's list to clear, and it is not netted from outstanding.

Billed vs Licensed · One page, four sub-tabs
MenuHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs Licensed
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log

Billed vs Licensed

Nightly run of 21 Nov 2026, 2:00 am. What we bill (billing app) against what the customer has (licence app), by customer and product.

The customer has it in the licence app and we are not billing it. This is the leakage. Pick a reason to see only those rows.

ReasonAll 70Whole customer 30One product 18Extra units 22
StatusOpen 64Explained 6Fixed this month 11Account manager: AllProduct group: All
CustomerProductReasonBilledLicensedARR, ₹Open forStatusWhat to do
Harbour Lane Stores
HARBLN
ERP, Ginesys POSWhole customer
Subscription ended 14 months ago
None12 users, 6 sites12,60,000212 daysOpenOpen in the licence app Mark as explained
Tara Handlooms
TARAHL
Ginesys POS, usersExtra units31403,78,0009 daysExplained
Temporary licence till 30 Nov
Change the reason
Kavya Silks
KAVYAS
ERP, usersExtra units14161,68,00012 daysOpenOpen in the billing app Mark as explained
Mango Tree Fashions
MANGOT
Ginesys POS, sitesExtra units18211,26,0005 daysOpenOpen in the billing app Mark as explained
Indigo Bazaar
INDIGB
ERP, FinanceOne productNoYes90,00067 daysOpenOpen in the billing app Mark as explained
Blue Thread Apparels LLP
BLUETH
InsightXOne productNoYesNo list price yet41 daysOpenOpen in the billing app Mark as explained

Showing 6 of 70, largest ARR first. ARR is the yearly value of the recurring lines: a quarterly line is counted four times, a monthly line twelve times; one-time items are left out. Fixed is set by a later nightly run, when the difference is gone.

We are billing it and the customer does not have it in the licence app. Shown here: only the customers not yet set up (onboarding pending).

ReasonAll 120Not yet set up 9Access switched off 8One product 5Extra units 98
StatusOpen 9Explained 0Account manager: AllProduct group: All
CustomerProductReasonBilledLicensedARR, ₹Open forStatusWhat to do
Cedar and Clay
CEDARC
ERP, Ginesys POSNot yet set up8 users, 4 sitesNone9,24,000100 daysOpenOpen in the licence app Mark as explained
Juniper Lane
JUNIPL
ERP, Ginesys POSNot yet set up6 users, 2 sitesNone5,88,00018 daysOpenOpen in the licence app Mark as explained
Pebble and Pine
PEBBLP
Zwing POSNot yet set up12 usersNone3,60,000324 daysOpenOpen in the licence app Mark as explained
Rangoli Kids
RANGKD
ERP, Ginesys POSNot yet set up5 users, 3 sitesNone3,36,0003 daysOpenOpen in the licence app Mark as explained
Amber Road Retail
AMBERR
ERPNot yet set up4 usersNone3,36,0006 daysOpenOpen in the licence app Mark as explained

Showing 5 of 9, largest ARR first. The reason for a long wait will come from project information, when that source is connected.

Billed, with no licence record to compare with yet. Nothing to do here until the source comes.

Product groupWhyWaiting for
EaseMyGSTLicensed in its own application, not in the licence appUsage from the EaseMyGST application
Qlik BILicences are kept in the BI team's licence monitor, not in the licence appA way to read the licence monitor
IntegrationLive integrations are not in the licence appThe integration team, in a later phase
OMS, user countBilling counts a minimum per user, the licence counts users. The product itself is comparedThe OMS team's answer

Services and discounts are revenue only and are not compared. Production is compared by default; a Sandbox only where a Sandbox product is billed.

Billed and licensed agree. Nothing to do. Shown so that a matched customer can be opened and checked.

CustomerProductBilledLicensedResult
Urban Loom
URBLOOM
ERP, users99Matched
Urban Loom
URBLOOM
Ginesys POS, sites1212Matched
Saffron Street
SAFFST
ERP, users2424Matched
Saffron Street
SAFFST
Zwing POS, users4040Matched

Showing 4 rows. 617 customers have no difference at all.

Data Check · What came in last night, source by source
MenuHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs Licensed
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log

Data Check

What came in last night, before it was reconciled. Nothing is corrected here: each row is fixed in its own system, and the next nightly run picks it up.

Billing app · read 2:04 am Source gate passed
Received 812Passed 498Warning 300Held back 14
Row count is within 2% of the night before.
Licence app · read 2:11 am Source gate passed
Received 722Passed 717Warning 5Held back 0
Row count is within 1% of the night before.

One tab per source system. Each new source gets its own tab and its own checks when it is connected. Held-back customers keep yesterday's numbers and carry a mark.

CheckSourceOutcomeRowsNewOwner
BA code on more than one customerBilling appHeld back110Accounts
Customer with no BA codeBilling appHeld back31Accounts
Next invoice date passed by more than 30 daysBilling appWarning967Accounts
Account manager missingBilling appWarning842Customer success
Territory missingBilling appWarning520Customer success
Licence Valid on a Deactivated customerLicence appWarning55Accounts
Line with quantity zero or belowBilling appNote2404Accounts

Showing 7 of 9 checks, grouped by the one check that closes them.

CheckOutcomeRowsNewOwner
BA code on more than one customerHeld back110Accounts
Customer with no BA codeHeld back31Accounts
Next invoice date passed by more than 30 daysWarning967Accounts
Account manager missingWarning842Customer success
Territory missingWarning520Customer success
Owner's email is not a company IDWarning310Accounts
Product with no product groupWarning220Accounts
Line with quantity zero or belowNote2404Accounts

BA code on more than one customer · 11 rows Held back

One BA code must stand for one customer. Until the two records are merged in the billing app, or accepted as a group sharing one code, this customer is not reconciled.

CustomerWhat is wrongNights openOwnerFix it inOr
Kavya Silks
KAVYAS
On 2 customer records, both with live subscriptions12AccountsOpen in the billing appAccept as exception
Saffron Street
SAFFST
On 2 customer records; one has no live subscription12AccountsOpen in the billing appAccept as exception
Meenakshi Textiles
MEENTX
On 3 customer records5AccountsOpen in the billing appAccept as exception

Showing 3 of 11. An accepted exception is kept with who accepted it and why.

CheckOutcomeRowsNewOwner
Licence Valid on a Deactivated customerWarning55Accounts
CustomerWhat is wrongNights openOwnerFix it inOr
Northgate Retail Private Limited
NORTHG
Access is switched off; the ERP licence is still Valid1AccountsOpen in the licence appAccept as exception
Indigo Bazaar
INDIGB
Access is switched off; the Ginesys POS licence is still Valid1AccountsOpen in the licence appAccept as exception

Showing 2 of 5.

Mappings · Admin: products
MenuHomeCustomersBillingSubscriptionsOutstandingReconciliationBilled vs Licensed
Admin, for the keepers onlyData CheckMappingsPeople and AccessRun Log

Mappings: products

Each product sold in the billing app, the product group its revenue belongs to, and the licence it is compared with. The billing app's own product tag is used where there is one; the rest are mapped here once and seldom change.

Products on live subscriptions120In 9 product groups
From the billing app tag90Nothing to do
Mapped here30No tag in the billing app
To confirm0New products appear here
Billing productTag in the billing appProduct groupRevenue typeCompared withStatus
Cloud ERP Core Site Annual Subscription with 1 userERP user countERPLicenceERP users (1 each)From tag
Cloud ERP Additional User Annual SubscriptionERP user countERPLicenceERP usersFrom tag
Ginesys POS Site Annual Subscription with 1 userGinesys POS site countGinesys POSLicenceGinesys POS sites, and 1 user eachFrom tag
Zwing POS User Annual SubscriptionZwing POS user countZwing POSLicenceZwing POS usersFrom tag
EaseMyGST Return Annual SubscriptionEaseMyGSTEaseMyGSTLicenceNo licence source yetFrom tag
Cloud ERP Data Pack (add-on)NoneERPData packNothing to licenseMapped here
Database Services (per quarter)NoneServicesServicesNothing to licenseMapped here
Custom Integration Annual ChargesNoneIntegrationCustom integrationNo licence source yetMapped here
Subscription Recurring DiscountNoneSpread over the subscriptionDiscountNothing to licenseMapped here
Ginesys POS Sandbox Site Monthly SubscriptionGinesys POS site countGinesys POSLicence, SandboxGinesys POS sites (Sandbox)From tag

Showing 10 of 120. A product with no tag is also listed in Data Check, so that it gets tagged in the billing app.

Customers, people and rows on these screens are made up for illustration. On Customers and Billed vs Licensed, the totals (799, 617, 70, 120 and the reason counts) are from the first match by hand, 21 Nov 2026; on Subscriptions and Outstanding, the summary figures and the ARR by product group are from the billing app, 21 Nov 2026. Status counts, filter counts and everything on Data Check and Mappings are sample numbers.

Three steps. Small first.

Not everything is there on day one. Each phase is finished and in use before the next begins, and the data gets better every night.

What is built first

The first release: seven screens, one reconciliation

CustomersThe customer's pageSubscriptionsOutstandingBilled vs LicensedData CheckMappings

The menu, for everyone by role: Home, Customers, Billing (Subscriptions, Outstanding), Reconciliation (Billed vs Licensed). For the keepers only: Admin (Data Check, Mappings, People and Access, Run Log). Licences, Cloud and App usage appear later, as their data comes.

Where it stands: the mock is accepted as the shape to build from. The screens are built when enough is known; replies are awaited from teams. Rebuilding is cheap, so a screen may change as data comes.

Step 1 · Seethe first release: billing, and billed against licensed Step 2 · Knowwhat we run, what is used, what it earns and costs Step 3 · Acthealth 1Foundationsign-in, roles,nightly run,Data Check 2Billing app,licence appread every night 3Customers,Subscriptions,Outstandingbilling app alone 4Billed vsLicensedin use 5Licensed vsCloudwhat we run 6Licensed vsApp usagewhat is used 7More licencesourcesEaseMyGST,Qlik BI,Integration 8MarginRevenue vsCloud cost 9Healththe lenses, and atmost three words Green is the first release. Each phase is in use before the next begins. No dates until each source can be read.
After Step 1 · the first release

Billing seen whole; billed and licensed reconciled

  • Every customer with a live subscription, on one list
  • Every live subscription, with ARR by product group
  • Outstanding by age, and receipts not yet adjusted
  • What is licensed and not billed, in ₹ ARR
  • What is billed and not licensed, with its reason
  • Source data held back or warned, every night
After Step 2 · later

What each customer earns and costs

  • Cloud running for a customer who is not licensed
  • App usage above the licence
  • EaseMyGST, Qlik BI and Integration compared too
  • Margin: Revenue vs Cloud cost, by customer and product
After Step 3 · later

Whom to look at first

  • Health, with direction
  • At most three words: Needs action, Watch, All good
  • Support and delivery counts, read from the CRM app
  • Ginesys as a whole, by week to year

It improves every night

On day one not every customer will match. Each correction in a source system shows the next morning: the row turns Fixed by itself, and coverage climbs.

target 95% Go-liveLater

Illustration, not a forecast.

What it eases

  • Three of the accounts team's hand-kept sheets stop: licence reconciliation, subscription lines for MIS, debtor outstanding
  • Two more sheets wait for cloud information; licence expiry reminders stay with the licence app
  • Hours spent pasting exports into sheets and comparing them
  • Finding unbilled licences months late
  • Customers who have paid and are not yet set up
  • Asking four teams for one customer's picture
  • Arguing about whose number is right

Who uses it, and the rules it keeps

About 70 to 80 people inside Ginesys, signed in with a company Google ID (gsl.in or ginesys.in). No customer or outside party.

Useread, decide, act ExecutiveGinesysas a whole Accountsbilling, dues,licences Cloudcloud, cost,data size Productmanagercustomers oftheir product Territorymanagercustomers intheir territory Accountmanagertheir owncustomers Operaterun it, keep it right Operatorsources, Data Check,mapping, nightly run Super adminpeople, roles,access Viewas

Who sees what

The menu is in two zones. Everyone gets Home, Customers and Reconciliation, filtered to their own customers. Billing, and any ₹ value, is shown by role. Admin is for the keepers only.

WhoCustomersBilling: Subscriptions, Outstanding, any ₹Billed vs LicensedAdmin
ExecutiveAllAll customersWith ₹No
Accounts (billing and licences, one team)AllAll customersWith ₹Yes
Territory managerTheir territoryTheir own customersWith ₹No
Account managerTheir ownTheir own customersWith ₹No
Cloud (the people who run and own the cloud)AllNot seenCounts, without ₹Data Check for cloud, later
Product (owner of a product)Their productNot seenCounts, without ₹No
The person who runs Ginesys 360AllAll customersWith ₹Yes

Admin holds Data Check, Mappings, People and Access, and Run Log. It is seen only by accounts and the person who runs Ginesys 360. The same accounts team does the billing and gives the licences, so there is no separate licence role. Later, with the Cloud phase: the Cloud role gives the cloud cost for each customer and reconciles it with the cloud bill in accounts, and sees total cloud cost and its break-up. The Product role sees revenue, cloud cost and gross margin by product, as a summary: what the product earns minus what its cloud costs. Neither sees these customer by customer in ₹ of billing. Executives see all of it.

What every role does

Each role sees the screens its role allows, filtered to its own customers. In the first release that is the seven screens; the numbers marked "later" come with their phase. More roles can be added in People and Access, with no new development.

CXOs

Executive

Does hereReads Ginesys as a whole: every customer, Subscriptions and Outstanding for all customers, and the differences between billed and licensed in ₹ ARR. Later: joined and churned, profit.
Acts inSets priorities.
Its own numbersARR by product group; outstanding by age; Not Billed and Not Licensed, open and fixed, in ₹ ARR. Later: profit; churn; coverage.
The accounts team: billing and licences

Accounts

Does hereWorks Billed vs Licensed every day, row by row; marks a difference Explained, with a reason. Uses Subscriptions for MIS and Outstanding for dues, in place of three hand-kept sheets; clears the Unadjusted list. Gives and corrects licences in the licence app. In Admin: works Data Check for the billing app and the licence app, and keeps Mappings.
Acts inThe billing app: adds or corrects billing lines, raises invoices, follows payment.
Its own numbersDifferences open, explained, fixed and new; leakage found and recovered in ₹ ARR; outstanding by age, over a year, and unadjusted.
The people who run and own the cloud · later phases

Cloud

Does hereFirst release: sees Customers, and Billed vs Licensed as counts without ₹; does not see Billing. Later: gives the cloud cost for each customer; reconciles the total with the cloud bill booked in accounts; sees what is allocated to customers and products and what is not (development, staging, internal sandboxes).
Acts inThe cloud providers: removes what is idle, right-sizes, keeps the cost sheet complete.
Its own numbersLater: total cloud cost and its break-up; share allocated to customers; idle cloud; cloud cost against the bill.
Owner of a product · later phases

Product

Does hereFirst release: sees the customers of the product, and Billed vs Licensed as counts without ₹; does not see Billing. Later: revenue, cloud cost and gross margin of the product, as a summary; Licensed vs App usage.
Acts inProduct and pricing decisions.
Its own numbersDifferences open on the product, as counts. Later: product revenue, gross margin, app usage against licensed.
Head of a sales territory

Territory manager

Does hereReads the territory: its customers, their subscriptions and outstanding, and the differences on them, by account manager. Later: health.
Acts inThrough the account managers.
Its own numbersARR and outstanding of the territory; differences open on it, in ₹ ARR. Later: joined and churned.
Account, customer success and sales managers

Account manager

Does hereSees only their own customers. Opens the customer's page before any call: what is billed, what is licensed, and any difference. Sees Subscriptions and Outstanding for their own customers. Later, one click opens the customer's tickets in the CRM app or its ideas in the ideas portal.
Acts inWith the customer; notes and follow-ups stay in the CRM app.
Its own numbersOutstanding on their customers; differences open on them; customers not yet set up. Later: health.
The person or small team that runs Ginesys 360

Operator

Does hereWorks in Admin: watches the Run Log and Data Check for every source; keeps Mappings and exceptions; uses View as. Later: allocation rules and the system health card.
Acts inAsks each source's owner to correct data in the source.
Its own numbersSources fresh or stale; rows held back; mappings to confirm. Later: coverage.
One or two people

Super admin

Does hereWorks in People and Access: adds people; sets each person's role and scope; adds new roles.
Acts inNothing outside.
Its own numbersUse of Ginesys 360: who opens it, how often.

Who sees which customers

Each square is the customers of one product in one territory. The filled squares are what that role may open.

Executive, Accounts, Cloud

Everything

Territory manager

One territory, every product

Account manager

Their own customers

Which account manager a customer has is read from the billing app, not kept separately here. Territory, and the final rule for who gets access, are still open. Which customers a role may open is one thing; whether it sees Billing and ₹ is another, and follows the table above.

View as

An Operator or Super admin can switch to see the app exactly as another role or person sees it: to check what they see, or to help them.

View asTerritory managerAccount managerProductExecutive

Read-only. A banner shows whose view it is. Every use is logged.

Every view and download is logged

Many people will see customers, and some will see ₹. The Operator can see who opened what and who downloaded what.

Role names are proposals. Nothing is ever changed in a source system from here.

In

  • Existing customers, from the day they are billed
  • Reading every system, sheet and uploaded file
  • Where systems disagree, in ₹, with an owner
  • Later: cloud cost, app usage, margin, health
  • Fixed screens, the customer's page, downloads
  • Subscriptions, outstanding and licences, line by line
  • Trends by week, month, quarter, year

Out

  • Leads and the sales funnel
  • Writing to any system, or fixing data here
  • Renewal and expiry reminders: they stay in the licence app
  • Tasks, notes and follow-ups
  • One overall score; rating our own staff
  • A report builder; real-time data
  • Ticket text, emails, call notes: counts only
  • Customers or partners signing in

The rules it keeps

1

Read only

It never writes to any system. Wrong data is fixed in its source.

2

One source of truth

Each fact is read from the one system that owns it. The customer comes from the billing app.

3

Every number explains itself

It opens down to its rows, or into the source system.

4

Honest about its data

Every number says how old and how complete it is.

5

Check, then reconcile, then rate

A held-back row is not reconciled. Later, no Health on a customer that is not mapped.

6

Nightly, never real time

At most one day old; ready when you sign in.

7

AI suggests, people decide

Fixed rules do the comparing and the rating.

8

Only reasons and exceptions are typed in

Why a difference is Explained; why an exception is accepted. No notes, no corrections.