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
SOLUTIONS · SERVICE NETWORKS

Bill on site. Claim what’s covered.

Estimates the customer approves before work starts, GST-compliant bill-on-site from the technician’s device, covered lines routed to warranty claims automatically — and all of it posting to the books.

Request a demo Explore Service Networks →

Service revenue leaks at the edges: work done but never billed, work billed but never approved, covered work billed to the customer, claimable work absorbed as cost. xMatix closes the edges by making billing a property of the job itself: estimate approved before work, payer decided per line, invoice or claim generated from the job card.

Estimates the customer said yes to

Findings become recommended jobs; the estimate carries parts, labour and tax; and the customer's approval or decline stamps the document and every line before work begins. Declined items persist as future opportunities on the asset instead of evaporating.

The payer is on the line, not in an argument

Each job line routes by rule — contract- covered lines consume entitlement or generate claims, chargeable lines generate invoices, internal work books as expense. One visit can mix all three, and each party pays exactly its share.

Bill on site, GST-correct

The technician raises the invoice at the doorstep from the job card — GST-compliant, offline if needed, with e-invoice registration completing when the device reconnects. Collections capture on the spot and allocate to the invoice; the ledger posts from the documents automatically.

Claims with a full lifecycle

Covered lines assemble into claims with the job's evidence, batch for the payer, take decisions per line and settle into credit notes automatically on approval — approved, rejected and reclaim positions live, ageing visible, recovery rate a managed number. It is the same claims engine that runs the network's commercial claims, so finance learns one lifecycle for both.

Common questions

Can one service visit produce both an invoice and a claim?

Yes — payer classification is per line: covered lines route to claims, chargeable lines to the customer invoice, internal lines to expense. The split is decided by the contract before work, not negotiated after.

How does bill-on-site work?

The technician generates the GST-correct invoice from the job card on the mobile app — offline if necessary — collects payment against it, and e-invoice registration completes on reconnection for mandated businesses.

What keeps completed work from going unbilled?

The job card is the billing source: completed lines must resolve to an invoice, a claim or an expense, so "finished but never billed" shows up as an exception list instead of a year-end write-off.

How do service claims get settled?

Claims batch for the payer, take per-line approve/reject/reclaim decisions, and settle into credit notes and inventory adjustments automatically on approval — with ageing and recovery rate visible throughout.

RELATED
See the visit end with the invoice.
Request a demo