Customer record is the master
Every quote, SO, invoice, receipt and credit note posts to the customer record. KYC, GSTIN, PAN, credit limit and contracts sit at the top of the screen, the full transaction history below.
Accounts Receivable | Customer 360
Quotes, sales orders, invoices, receipts, credit notes, payment history, credit limit, contacts and documents on the same customer record. The same record sales, AR and the CFO post against, with no second master to reconcile.
How it works
Every quote, SO, invoice, receipt and credit note posts to the customer record. KYC, GSTIN, PAN, credit limit and contracts sit at the top of the screen, the full transaction history below.
Sales sees pipeline plus open SOs and last contact. AR sees outstanding plus payment timing plus aging. CFO sees concentration, exposure and DSO. The screen is the same record, three lenses.
When a customer is shared across entities, the master record rolls up bills, payments and exposure across the group. Per-entity overrides handle entity-specific contracts and payment terms.
Every change to the customer record (KYC update, credit limit revision, contact change) captured with user, role and timestamp. Hash-chained per Rule 11(g).
What the system does
| Capability | Input | Output |
|---|---|---|
| Unified customer record | Quotes, SOs, invoices, receipts, credit notes | Single timeline per customer |
| Live KYC posture | GSTIN, PAN, MSME, address proofs | Verification status with last-checked timestamp |
| Credit limit + utilisation | Open SOs + open invoices + receipts | Available credit, in real time |
| Document repository | Contracts, MSAs, customer POs | Searchable, versioned, hash-verified |
| Multi-entity rollup | Per-entity transactions | Group-level customer view |
| Role-aware screen | User role + customer record | Sales / AR / CFO lens on the same data |
Unified customer record
Live KYC posture
Credit limit + utilisation
Document repository
Multi-entity rollup
Role-aware screen
Compliance + integrations
Every change captured. Every transaction linked. The audit trail is built in, not bolted on.
Regulations we work within
Rule 11(g), Companies Act
Append-only edit trail across the customer record.
DPDP Act 2023
PII fields tagged for retention and access control per the Digital Personal Data Protection Act.
Section 128, Companies Act
8-year retention of customer records and transactions.
Connects to
Customer 360 FAQ
Yes. The header KPIs and sections are configurable per role. Sales sees pipeline and last contact; AR sees outstanding and payment timing; CFO sees concentration and DSO. Configurable per workspace.
Available credit equals limit minus open invoices minus open SOs (configurable). The check runs at SO save and at invoice generation. Breaches block the next SO with a CFO override path.
Both. The customer record is shared at the group level (one PAN, one credit history). Per-entity overrides handle entity-specific contracts, payment terms and credit limits.
Yes. One-click export packages the customer ledger, open invoices, contracts and KYC documents in a hash-verified format. Aligned with the SA 505 audit procedure for external confirmations.
More in Accounts Receivable
Per-customer credit limits, utilisation tracking, exposure aging, on-hold logic at the SO step.
See Credit ManagementOutstanding statement per customer; bulk send via email or WhatsApp.
See Customer Statement of AccountMulti-currency invoices with IRN, QR and EWB auto-generated. Tax engine applies CGST/SGST/IGST per place of supply.
See GST Invoice GenerationUpload your customer master. The unified record, with KYC posture, open invoices, payment history and credit utilisation, surfaces in 10 minutes.