Help centre
Use these checks for common account, billing, stock, udhaar and sync situations. They are designed to prevent duplicate work and preserve the shop’s history.
First check
Read the status shown on screen
Offline work
Do not recreate a saved action
Access issue
Check permission and feature toggle
Account help
Use your onboarding support channel
What you need to know
9 topics
01 · Account
Confirm that you are using the account assigned to the correct organization. If a staff account was deactivated or its password changed, its existing session may no longer be valid.
02 · Permissions
BillCountr shows work based on both the user’s permission and the organization’s feature settings. A feature can be unavailable even when the user’s general role appears correct.
03 · Billing
Review item quantity, price, discount, tax pricing mode, tax split, additional charges, payment amount and the settings snapshot used by the draft. Finalized totals come from the shared calculation result.
04 · Correction
Do not overwrite the historical invoice. Use the finalized-bill cancellation path so the original snapshot remains visible and stock or ledger effects are reversed through explicit appended records.
05 · Stock
Review the product’s movement history for finalized bills, purchases and adjustments. If the change came from an offline device, check whether it is pending sync or in conflict before entering a second adjustment.
06 · Udhaar
Open the customer’s unpaid invoices, record the received payment, select the invoice or invoices being settled, review the allocations and confirm. The original invoice stays unchanged while its open due reduces through ledger entries.
07 · Offline
Continue supported local work. Do not recreate an action that is already saved. When connectivity returns, BillCountr retries automatically and marks confirmed operations as synced.
08 · Conflict
A conflict means the action cannot be applied safely as-is—for example because stock changed, the payload differs from an existing operation, settings became stale or permission was removed. Review the stated reason instead of repeatedly retrying.
09 · Reports
Check the date range, organization, enabled report, filters and whether the source bills are finalized, cancelled, paid or due. Reports use stored finalization facts rather than recalculating draft bills.
Common questions
No. Pending sync means the work is already saved locally and is waiting for server confirmation. Recreating it can confuse the real-world transaction even though operation identity protects backend duplication.
Creating and cancelling are separate permissions. Shops can keep routine billing fast while reserving sensitive corrections for owners or managers.
Finalized bills keep their settings and calculation snapshot. This preserves the document the customer received and keeps reports auditable.
No. Audit records are immutable by product rule and cannot be edited or deleted, including by the owner.
BillCountr does not yet publish a public support email or telephone number in the product requirements. For organization-specific access, use the BillCountr team or implementation partner that onboarded your shop.
Ready for daily shop work
