Terms

Simple expectations for using BillCountr responsibly.

These plain-language terms explain account responsibility, product boundaries, business records, offline behaviour and safe use.

Account use

Authorized organization users only

Business settings

Controlled by the organization

Payment role

Records modes; does not process funds

Historical integrity

Corrections preserve the original record

What you need to know

Clear details, without the jargon.

01 · Agreement

Who these terms apply to

These product terms apply to organizations using BillCountr and the owners, managers, cashiers, auditors or other authorized users accessing that organization’s workspace. The person accepting commercial terms for a shop must have authority to do so.

02 · Accounts

Keep access accurate and secure

Organizations are responsible for assigning accounts to the correct people, configuring roles and permissions, removing access when staff leave, protecting login credentials and reporting suspected unauthorized use through the provided support channel.

03 · Acceptable use

Use BillCountr for lawful shop operations

Users must not attempt unauthorized access, cross-organization data access, service disruption, malicious code distribution, security-control bypass, fraudulent record creation or use that violates applicable law or another person’s rights.

04 · Configuration

The organization controls business settings

The shop is responsible for reviewing its profile, GST details, tax mode, invoice fields, payment modes, stock policy, feature toggles, staff permissions and output templates for its own operational and compliance needs.

05 · Records

Finalized business history is preserved

Finalized bills retain their calculation and settings snapshot. Corrections use cancellation, reversal and appended ledger records rather than changing the original document. Audit records are immutable by product rule.

06 · Payments

BillCountr records payment information

Cash, UPI, partial and udhaar describe how the shop records a sale or settlement. BillCountr is not a payment gateway, does not move those funds and does not guarantee payment completion outside the recorded shop workflow.

07 · Offline use

Offline work may wait for confirmation

Supported actions can be saved locally and used before server confirmation. Users should not recreate pending work. A real conflict—such as stale stock, changed duplicate data or removed permission—may require review before it can be applied centrally.

08 · Data and exports

Handle customer and business information responsibly

Organizations control the information entered into their workspace and the recipients of printed, shared or exported invoices, receipts, due lists and reports. Exported copies may no longer be protected by BillCountr’s access controls.

09 · AI assistance

Review proposed changes before confirming

AI-generated summaries and suggestions should be reviewed by an authorized user. Any assisted write must show the intended modification and receive explicit confirmation, but the organization remains responsible for the confirmed business action.

10 · Availability

Offline continuity does not remove every dependency

BillCountr is designed to keep core local work moving during connectivity loss. Server-backed confirmation, cross-device convergence, some exports, account recovery and administrative functions may require connectivity and operational services.

11 · Changes and termination

Commercial and legal rules need final completion

The final agreement must define subscription, renewal, taxes, service changes, suspension, termination, export windows, deletion, warranties, liability, indemnity, dispute resolution and governing jurisdiction before public commercial launch.

Common questions

Quick answers.

Does BillCountr guarantee that a recorded UPI payment succeeded?

No. BillCountr currently records the selected payment mode; it is not a payment gateway and does not itself confirm or settle the external transfer.

Who is responsible for GST and invoice settings?

The organization is responsible for reviewing its own business, tax and invoice configuration and for obtaining professional advice where required. BillCountr applies the configured rules consistently.

Can a finalized invoice be edited to hide a mistake?

No. The safe correction path preserves the original finalized snapshot and appends cancellation, stock reversal and ledger effects where applicable.

Are these the final legal terms?

No. They accurately describe current product responsibilities and boundaries, but registered-company, commercial, liability, dispute and jurisdiction terms still require legal completion before public launch.

Pre-launch legal completion required: replace this product-terms draft with a reviewed agreement containing the registered company identity, effective date, plans and billing, warranties, liability limits, indemnity, suspension, termination, post-termination data handling, dispute process and governing jurisdiction.