Help & support

Purpose: filter purchases, sales, ITC, reconciliation and compliance metrics.

• Select valid From and To dates where From is not later than To, then choose Apply.
• “Not available” means no persisted population exists for that metric; it is not replaced with an estimated value.

Purpose: review commercial entitlement and administer tenant defaults.

• SaaS foundation: review plan, license status, renewal date, quotas and current usage.
• Tenant settings: save language, time zone, INR or permitted currency, financial-year start month, date/number format, session timeout, password policy and notification defaults.
• Branding: save approved HTTPS logo/favicon URLs, theme colours, support contacts, footer, login message and verified custom domain.
• Only tenant administrators with the matching SaaS permission can change settings. Read-only commercial access does not grant administration.

Purpose: manage tenant membership with one primary role per account.

• Invite a user with name, work email and exactly one approved tenant role. Platform roles cannot be assigned here.
• Use role assignment to move a user to another least-privilege role; do not combine operational roles as a shortcut.
• Deactivate access when a person leaves or no longer needs the workspace. Reactivate only after authorization is reconfirmed.
• API User is for controlled machine access and must not be used as an interactive shared login.

Purpose: review the current subscription and create an idempotent hosted-provider checkout.

• Select an enabled Razorpay or Cashfree provider, plan, interval and operation. Promo code is optional.
• Continue to secure payment creates a checkout and redirects only to a validated HTTPS provider URL. A failed request does not confirm or capture payment.
• Use Invoices and Payments for tenant-scoped history. Retry only a failed payment and confirm the provider result before another attempt.

Purpose: configure the source of purchase and sales books through one guided workspace.

• Select Business Central, SAP S/4HANA, Zoho Books, TallyPrime, BUSY, Custom ERP or file import.
• For cloud ERP, enter the provider endpoint and approved OAuth/service credentials, validate the connection, discover or enter the company, map it, choose synchronization scopes, then queue the first sync.
• For TallyPrime, BUSY or a private Custom ERP, download the Local Sync Agent and deployment guide from the same screen. Install it on an approved machine that can reach both ERP and GST360.
• For Excel, CSV or JSON, continue to Reconciliation and use the source-import form.
• A saved connection is not proof of imported data. Confirm completion and record counts in Background jobs.

Purpose: map a tenant to TaxPro and retrieve supported GST return data through the Integration Hub.

• Save the provider mapping and encrypted API/OAuth credentials, then validate health before synchronization.
• Select GSTR-1, GSTR-2B or GSTR-3B, enter the required return period, choose Manual, Full or Delta mode, and queue synchronization.
• Respect the provider rate limit. Review latency, failure details and retry/dead-letter status before retrying.

Purpose: load books/GST source records, execute the selected comparison, and review exceptions.

• Upload CSV, JSON or XLSX using the displayed template fields and a six-digit MMYYYY GST period. Preview/validation errors must be corrected before processing.
• Load both sources required by the chosen reconciliation type for the same period. For GSTR-3B, set Direction to Purchase for ITC and Sale for liability.
• Select the reconciliation type and period, then run it. Review matched, partial, mismatched, missing, duplicate and pending-review items.
• Use bulk accept, reject, ignore, assign, comment, status update or export only after filters identify the intended population. Decisions are audited and cannot be silently rewritten.

Purpose: store tenant files through the controlled storage abstraction.

• Upload an allowed file with category, folder, tags and optional retention date. MIME, extension, size, quota and malware checks run before acceptance.
• Use metadata update to rename or recategorize without replacing content; use Copy to create a new managed document reference.
• Archive or soft-delete records that are no longer active. Restore only within the retention policy and when no legal restriction blocks it.
• Download uses an authenticated tenant-scoped request. Never expose local storage paths or permanent public URLs.

Purpose: run and reuse tenant-aware analytics.

• Save a report with a clear name, report code and parameter JSON that matches the selected report definition.
• Queue Excel, PDF or CSV export with valid From/To dates. Large exports run in the background; check Background jobs and Documents for the result.
• Create a schedule using the required time zone and daily, weekly, monthly, quarterly or approved cron frequency. Disable obsolete schedules rather than leaving unwanted delivery active.

Purpose: control personal delivery channels and notification state.

• Enable only the email, SMS, WhatsApp, push or in-app channels approved for your account. Set language, digest mode, priority and quiet hours.
• Mark an item read after review or archive it when no longer needed. Archiving does not erase the audited delivery record.
• Provider delivery, retries and dead-letter information is visible only to roles with notification administration permission.

Purpose: monitor queued, running, completed, failed and cancelled work.

• Inspect job type, tenant, queue, attempts, progress, duration and failure before acting.
• Retry only after correcting the cause. Cancel only the intended queued/running job and verify the resulting state.
• Repeated failures must be escalated with job ID, queue, correlation reference and the sanitized error message.

Purpose: record a controlled decision on an item assigned to the current approver.

• Review the request, timeline, comments, attachments, SLA and decision context.
• Choose Approve, Reject, Send back or Request changes and provide a meaningful reason where required.
• Do not act for another approver unless a valid delegation exists. Every decision and reassignment is retained in the approval history.

Purpose: queue OCR or AI analysis for a managed document and retain the provider result for review.

• Select an active document/version, operation, model and optional instruction. Requests are quota checked and executed as background work.
• Provider status must be Ready before real processing; Not configured means Azure Document Intelligence or Azure OpenAI settings are absent.
• Retry only failed work and cancel only queued/running work. Treat extracted or generated content as a draft requiring human verification.

Purpose: request a new tenant or commercial assistance.

• Trial: provide legal/company name, valid GSTIN, unique workspace slug, administrator contact, time zone and a strong confirmed password; then complete email verification.
• Contact sales: provide business contact details, expected users/GSTINs/companies, integrations, data volume and target date. Do not include taxpayer files, credentials or payment data.

Purpose: operate Synvexa control-plane functions; these forms are never tenant-user functions.

• Platform Team: a Super Admin may create or deactivate Platform Support users. Support is read-only and cannot grant Super Admin.
• Tenant Provisioning: create, retry, suspend or reactivate a tenant; monitor database provisioning, fleet migration, backup and restore-validation operation IDs.
• Pause, resume, cancel or retry a fleet operation only under an approved change/recovery ticket.
• Platform Billing: review platform-wide payments, subscription/revenue indicators and failed transaction operations. Tenant credentials must never be used for control-plane work.