Frequently Asked
Questions

Select Start Free Trial, enter your business and account details, choose an available plan and submit the registration form. Verify your email when requested, then sign in to complete company settings before creating transactions.

Open Settings and confirm the company name, GSTIN, address, state, invoice prefix, default notes and terms. Add customers, products or services, tax rates and opening stock so invoice creation is accurate and faster.

Open Sales / Invoices and select New Invoice. Choose a customer, enter invoice and due dates, add items, review GST and totals, save the draft, and post it once the details are final.

Yes. The interface is responsive and works in current mobile, tablet and desktop browsers. For the best security and performance, keep your browser updated and use a trusted network.

The dashboard summarizes sales, purchases, receivables, payables, profit, recent invoices, cash flow, GST and top-selling items using your recorded transactions. Values update as invoices, purchases, payments and expenses are entered.

Open Customers, choose Add Customer, and enter the customer’s name, contact details, billing address, GSTIN and state where applicable. Accurate GST and place-of-supply information helps the application calculate tax correctly.

Open Inventory and select Add Product. Enter the item name, SKU, HSN or SAC code, selling and purchase prices, GST rate, unit and stock details; service items can be maintained without physical stock where supported.

A draft remains editable and does not represent a finalized accounting transaction. Posting confirms the invoice, applies the business workflow such as balances and stock movement, and should only be done after verifying customer, tax and item details.

Company settings provide invoice-number configuration such as a prefix and sequence. Configure it before regular billing begins because changing numbering after documents are issued may affect continuity and compliance.

Use the left navigation for modules and the top search icon to locate invoices, customers and inventory records. On desktop, the menu button collapses the sidebar and remembers your preference; on mobile, it opens the navigation drawer.

Eligible plans may include a configurable trial with access to that plan’s enabled features and limits. While the trial is active, the header shows the exact expiry date and a link to select a paid plan before access ends.

A payment method is not required when the selected plan is configured for a free trial. To continue after the trial, select a plan and complete payment using one of the payment methods enabled in checkout.

Click your avatar in the top-right corner and choose My Profile. You can update your name, upload a JPG, PNG or WebP profile photo up to 2 MB, and change your password securely.

Open the question-mark icon from the authenticated header or choose FAQs from the public Resources menu. Search this knowledge base first, then contact support by email or phone when you need account-specific assistance.

The application supports GST-ready invoices, GSTIN details, HSN or SAC codes, intra-state and inter-state tax treatment, and GST reporting workflows. Your business remains responsible for validating tax configuration and filing obligations with its tax professional.

Tax treatment is determined from the supplier and customer states or place of supply. Intra-state transactions normally split tax into CGST and SGST, while inter-state transactions normally apply IGST; always confirm the place-of-supply details before posting.

Yes. Create a quotation with customer, validity, item, price, discount and tax details, then convert an accepted quotation into an invoice. Review the converted invoice before posting because commercial details may have changed.

Draft invoices can be revised before posting. Posted documents are intentionally more controlled to protect transaction history; if correction is required, use the permitted cancellation or adjustment workflow and retain a clear audit trail.

Open the invoice and use the cancellation action if your role has permission. Enter a meaningful reason; the application records the event and reverses applicable operational effects according to the implemented invoice lifecycle.

The application calculates line amounts from quantity and rate, applies configured discounts and taxes, and then calculates the grand total. Review rounding, place of supply, GST rate and item classification before finalizing the document.

Discounts can be applied where enabled in the invoice form or plan features. Confirm whether the entered discount is line-level or document-level and verify the taxable value and final GST calculation before posting.

HSN codes classify goods and SAC codes classify services for GST reporting. Store the appropriate code with each product or service so invoices and tax reports contain consistent classification data.

Yes. Configure default invoice notes and terms in Company Settings, then review them on each document. Use clear due dates, payment instructions, return conditions and legally reviewed terms suitable for your business.

Open the invoice from the invoice list and select its preview or print action. Use the browser print dialog or supported PDF action to save a copy, and verify the company identity, customer details, tax breakdown and totals first.

Common statuses distinguish drafts, posted or unpaid invoices, partially paid invoices, paid invoices, overdue invoices and cancelled documents. Status changes are driven by document actions, due dates and recorded payments rather than manual labels alone.

You can bill service or non-stock lines when the item setup and invoice workflow permit it. Use an appropriate SAC or description, tax rate and unit, and avoid treating a service as physical stock.

The due date indicates when payment is expected and helps classify outstanding invoices as current or overdue. Accurate due dates improve collection reports, reminders and cash-flow planning.

Use the global header search with an invoice number, or open Sales / Invoices and use available filters and sorting. Search results remain restricted to the signed-in tenant and the user’s authorized access.

Important actions such as posting and cancellation are written to the audit trail where implemented. Use Settings / Audit Logs to review accountable activity and avoid sharing user credentials between team members.

Record a receipt against the correct customer and invoice. The application updates the outstanding balance and payment status, allowing dashboards and receivables reports to distinguish unpaid, partially paid and paid invoices.

Open Bank & Cash or the relevant invoice payment action, select the customer and invoice, enter the amount, date, method and reference, then save. Confirm that the amount and destination account match the actual receipt.

Yes. Enter an amount lower than the invoice’s outstanding balance and the invoice will remain partially paid. Record each later receipt separately so dates, references and the remaining balance remain traceable.

You can record methods supported by the payment form, such as cash, UPI, card or bank transfer. Use the reference field for transaction IDs, cheque numbers or bank references to simplify reconciliation.

Use dashboard receivables, invoice statuses and the Receivables report to identify invoices past their due dates. Contact customers using your approved reminder process and record payments promptly when received.

Payments should normally not exceed the outstanding invoice amount unless an explicit advance or credit workflow exists. Verify the selected invoice and amount before saving to avoid incorrect customer balances.

Open the customer ledger or Receivables report to review invoiced amounts, receipts and the remaining balance. Use date filters where available to reconcile the report with customer statements.

Recorded customer receipts contribute to cash inflow summaries according to their transaction dates and configured accounts. Draft invoices alone do not represent received cash.

Open the purchase payment workflow from Purchases or Bank & Cash, select the purchase order or supplier obligation, enter payment details and save. Use a reliable external reference so the entry can be matched with the bank statement.

Payment recording settles a financial balance, while GST treatment generally comes from the underlying invoice or purchase document and applicable tax rules. Consult your accountant for timing rules relevant to your registration and transaction type.

Yes, when Razorpay checkout is configured and UPI is available for the account. Select a monthly or yearly plan, open secure checkout, choose UPI and complete authorization through the supported test or live payment environment.

The account is not activated from an unverified or failed payment. Return to Subscription, confirm the gateway configuration and payment details, and try again; contact support if money was debited but activation was not confirmed.

The server validates the Razorpay order, payment identifier and cryptographic signature and confirms the captured amount before activating the plan. Webhook verification provides an additional server-to-server event trail.

The subscription page presents the billing cycles configured for each published plan. Review the displayed price and period before checkout because the selected cycle determines the paid amount and subscription end date.

Compare SaptOne receipts and supplier payments with bank, cash and gateway statements for the same period. Investigate missing references, duplicate entries, timing differences and unmatched amounts before closing the period.

Open Inventory, choose Add Product and enter the name, SKU, unit, HSN, GST rate, prices and opening quantity. Use unique SKUs and accurate units so search, billing and stock reports remain reliable.

Stock is reduced when a sales invoice reaches the implemented posted state, not merely while it is an editable draft. This prevents incomplete documents from changing available quantity.

Stock increases according to the purchase receiving or completed-status workflow. Confirm quantities and purchase status carefully so ordered goods are not counted as available before they are received.

Opening stock is the quantity available when you begin using the system or introduce an item. Enter it once from a verified physical count and use subsequent purchase, sale and adjustment movements for later changes.

Where the invoice lifecycle supports reversal, cancelling a posted invoice restores the related stock movement and records the reason. Verify the item quantities after cancellation, especially if goods were physically returned separately.

Yes, services can be configured and invoiced without behaving like physical stock where supported. Use a SAC code and service-appropriate unit, price and GST rate.

Use inventory lists, dashboard alerts or reports that compare available quantity with the configured reorder level. Review low-stock items regularly before creating supplier purchase orders.

An SKU is your internal unique identifier for finding and managing an item. An HSN code is a standardized tax classification for goods; products can share an HSN category but should normally have distinct SKUs.

Yes. Store the normal cost and selling price separately so purchase entries, invoice defaults and margins use the appropriate values. You can review or override transaction prices according to permissions and workflow.

A return should use the appropriate cancellation, credit-note or return workflow so both financial and stock effects remain traceable. Avoid directly changing quantities when a documented business transaction should explain the movement.

Branch capability and limits depend on the selected plan and the modules configured for the deployment. Use the header branch selector for the active branch context; confirm branch-scoped inventory support before relying on location-level balances.

Perform a physical count, review posted sales, received purchases, cancellations and duplicate entries, then record an authorized adjustment if supported. Keep the reason and evidence for audit purposes.

Yes. Open global search and enter at least two characters from a product name. Results are limited to records belonging to the current tenant and link back to the inventory area.

A plan can enable inventory and set a configurable product limit or unlimited access. When the limit is reached, authorized users must upgrade the plan or have the plan configuration adjusted before adding more products.

Use consistent SKUs and units, post documents promptly, receive purchases only when goods arrive, record returns correctly and perform periodic physical counts. Restrict inventory actions to trained users and review audit history.

Click the top-right avatar, choose My Profile, update your name or select a profile image, and save. Accepted images are JPG, PNG and WebP up to 2 MB, and the saved photo appears throughout the authenticated interface.

Open My Profile and enter your current password, a new password of at least the required length, and its confirmation. Use a unique password and never share it with another team member.

Use the Forgot Password option on the login page when the recovery workflow is configured, or contact an authorized administrator or support. Never send your existing password by email or chat.

The login page supports the phone-login tab when a mobile number is stored for the user. Enter the registered mobile number and password; account verification and status rules still apply.

Roles group permissions that determine which modules and actions a user may access. Assign the minimum access needed for each job and review role assignments whenever responsibilities change.

No. System Admin is a platform-level role and bypasses tenant feature and usage restrictions. Subscription prompts and trial-expiry notices are intentionally hidden for Super Admin accounts.

Only when the user’s role permits the action and the tenant’s active trial or paid plan includes the feature. Both authorization and subscription entitlement checks protect restricted modules.

Trial accounts receive the features and limits of the selected plan until the displayed trial-expiry date. After expiry, plan-controlled modules may require activation of a paid plan.

The subscription status becomes active after verified payment, and access follows that plan’s enabled features, limits and paid period. Trial notices disappear automatically because the latest subscription is no longer in trial status.

Open the avatar menu and choose Logout, or use the Logout button at the bottom of the sidebar. The server clears the session and redirects to login using a CSRF-protected request.

Audit logs record supported security and business events with information such as the acting user, action, time and network address. They help administrators investigate changes and demonstrate accountability.

When the tenant plan enables branches, the header lists branches belonging to the tenant. Selecting one saves the active branch context for the session; branch limits and available workflows depend on plan configuration.

The role may lack permission, the tenant plan may not include the feature, the trial or subscription may have expired, or a configurable usage limit may have been reached. Ask the account administrator to review both role and subscription settings.

Business data is associated with a tenant identifier, and application queries scope records to the signed-in tenant. Permissions further restrict what individual users within that tenant can view or change.

Use a strong unique password, verify your email, keep contact details current, log out on shared devices and review audit logs. Administrators should promptly disable unused accounts and follow least-privilege access.

The current subscription checkout integrates Razorpay and supports methods enabled for the configured Razorpay account, including UPI, cards, netbanking and wallets. Gateway settings are managed by Super Admin.

Sandbox uses Razorpay test credentials and creates no real-money transaction, while live mode uses production credentials and can collect real payments. Keep sandbox as the default until live keys and webhook configuration have been verified.

Super Admin can manage payment settings in the administrative area, with environment variables available as fallback configuration. Secrets are encrypted or masked according to the settings implementation and should never be committed to source control.

Set the Razorpay webhook URL to the displayed application webhook path and use the same webhook secret in both Razorpay and Super Admin settings. Enable the relevant payment events and test signature validation before live launch.

Yes. Razorpay checkout explicitly enables UPI alongside cards, netbanking and supported wallets. Actual options shown depend on the gateway account, mode, device and Razorpay availability.

The application integrates Resend for outbound email notifications. Super Admin configures the API key, verified sender and related email settings before transactional messages can be delivered.

Check that Resend is enabled, the API key is valid, the sender domain or address is verified and the recipient is valid. Review application and provider logs for rejected requests, domain issues, suppression or rate limits.

Tally integration depends on the active plan and an implemented connector or export workflow. Confirm required fields, tax mappings and supported file format with support before treating an export as accounting-ready.

API access can be represented as a configurable plan feature, but usable endpoints and credentials depend on the deployment’s implemented API module. Contact support for current endpoint, authentication and rate-limit availability.

WhatsApp messaging is a configurable product feature, but delivery requires an approved provider integration and templates. Confirm setup, consent and message-cost requirements with the administrator or support team.

Email delivery requires working Resend configuration and a verified sender. Confirm the customer email, review the invoice, and use the supported send workflow when it is enabled for your deployment.

Razorpay webhook requests are validated using the configured webhook secret and signature before processing. Invalid signatures are rejected, and processed events are stored with a unique event key to reduce duplicate handling.

Complete successful, failed and cancelled sandbox payments; verify amounts, signatures, activation, duplicate webhooks and error redirects. Then add live credentials, register the live webhook, make a controlled transaction and reconcile it in Razorpay.

Yes. Super Admin can enable integration-related features per plan and configure relevant limits. Tenant users can use only the features included in their current valid trial or paid subscription.

Only trusted platform administrators should manage API keys and webhook secrets. Use separate sandbox and production credentials, rotate exposed secrets, restrict dashboard access and never paste secrets into tickets or public repositories.