xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Finance & Accounting/The Tax Center
OVERVIEW · Last reviewed

The Tax Center

The Tax Center brings the India-compliance records and actions in xMatix Finance into one area. Posted sales and purchase documents supply the underlying tax transactions; return processors then build the supported GST tables for a registration and period. Review the generated figures against their source records and portal data before treating any return as ready to file.

Start with the GST Console

The first-party TaxCenterWidget is the intended operational starting point for GST returns when a tenant has an AppPage that embeds it. Choose an active GST registration and a financial year, select a monthly or annual period, and use the filing cards to open the matching return record. The widget summarizes records already held in xMatix; it does not itself submit a return to a government portal.

For a regular registration, a monthly row presents GSTR-1, GSTR-2B and GSTR-3B. An Input Service Distributor (ISD) registration presents GSTR-6 for a month. The annual row presents GSTR-9. AppPage availability is tenant configuration: if no Tax Center route has been provisioned, use the return entity lists and actions directly. See The GST console for the precise selection, status and provisioning behavior.

What is implemented

AreaCurrent product behavior
GSTR-1Processes books-side outward supplies, compares books and portal-side rows, records carry-forward or ignore decisions, and records a Filed state and filing date
GSTR-2BProcesses books-side inward supplies and compares them with portal-side statement rows; imported IMS status can affect GSTR-3B, but xMatix does not currently expose a supported Accept/Reject decision action
GSTR-3BComputes supported tables from the selected GSTR-1, GSTR-2B and tax-ledger sources, preserves manual rows, and records filing acknowledgment details
GSTR-9Rolls up supported annual tables from filed monthly returns and ledgers, then validates and records the annual filing
E-invoicingStages an e-invoice payload from an Invoice and stores status, IRN, acknowledgment and signed response fields back on that Invoice; external submission requires an explicitly configured integration flow
E-way billsCreates a Draft EWayBill from an Invoice; an external flow must submit it and write generated details back before it is authority to move goods
TDS/TCSProvides withholding transactions, challan preparation/posting/CSI verification/correction actions, quarterly-return processing and related certificate records
Form 26ASProvides statement, line and reconciliation entities plus a server reconciliation engine; attaching a statement file does not parse it into lines automatically

These distinctions matter when reading a record screen. A saved header, Draft row or staged payload proves only that xMatix has prepared or stored data. It does not prove that a portal accepted a filing or generated an external number.

A reliable review sequence

  1. Confirm the legal registration, PAN/TAN where applicable, and statutory period.
  2. Confirm the source invoices, bills, credit notes, payments or withholding rows are posted and belong to that scope.
  3. Run the supported processor or compute action and reconcile its result to source control totals.
  4. Load portal-side data through an explicit import or integration where the workflow requires it, then investigate every difference.
  5. Complete manual rows and retain the external evidence required by your filing process.
  6. Record filing state only after the external filing has actually occurred.

Do not repair an unexpected return total by silently changing a derived row. Correct the source transaction or use the documented manual or override mechanism for that return, then recompute and retain an explanation.

What is in this section

Screens and actions remain permission-gated. If an implemented page or action is absent, first confirm the user's security profile and that the relevant metadata action has been configured for the tenant.

A note on statutory content

Rates, thresholds, due dates and portal rules change. This documentation describes the behavior implemented in the reviewed source; it is not tax advice and must not be used as the authority for a current statutory figure or deadline. Confirm current requirements with the government portal and your tax advisor.