Skip to content

Published services, current details, and clear categories.

Explore APIs

e-Invoicing API

Validate a reported e-invoice from its Invoice Reference Number and read the details held for it. Your accounts payable and finance teams then pay against an invoice they have checked.

TAX INVOICEsupplier gstin27ABCDE1234F1Z5document noINV/2026/0042document date14-08-2026signed qrirna1b2c3d4e5f6071829c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4VALIDack 14-08-2026
Request and response

You confirm the required fields and consent steps with us during onboarding.

You send

Invoice Reference Number from a reported e-invoice

You receive

The invoice details available: parties, document reference and date, recorded values and reported status

Coverage
Reported e-invoices carrying an Invoice Reference Number
Typical users
Accounts payable and shared-service teams, marketplaces, lenders, expense platforms and ERP teams
Coverage note
Business-to-business invoices reported in India. Available fields vary by data source and by the individual record.
Overview

What you can do with the e-Invoicing API

Under e-Invoicing, a business above the notified turnover threshold reports each business-to-business invoice for registration before issuing it. The invoice comes back carrying an Invoice Reference Number that identifies it. A document that was never reported carries no valid reference. This API works from that reference. It validates the Invoice Reference Number you submit and returns the invoice information available against it in a structured response. Your finance team can then confirm that a vendor bill matches an invoice that was actually reported before releasing payment. This service does not read documents. Where you have an image or a PDF and need the fields lifted off it, use the e-Invoice OCR service. The fields returned here vary by data source and by the individual invoice record.

  • Starts from the reported reference

    The check works from the Invoice Reference Number carried by a reported invoice, rather than from a scan of the document. Where you need fields lifted off an image or a PDF instead, the e-Invoice OCR service covers that.

  • Fields an invoice reference lookup can return

    You can get supplier and recipient registration details, the document number and date, and the values and tax breakdown recorded against the reference. The response also carries the status of the reported invoice, including cancellation. Available fields vary by data source and by the individual invoice record.

  • A check before a vendor bill is paid

    Connect the validation to an invoice intake queue, an ERP posting step, a vendor portal or an expense platform. The bill is then checked before you schedule it for payment, instead of after the money has gone.

  • Backing for an invoice discounting decision

    Where an invoice is presented for discounting, validating its reference supports the decision to advance funds against a document that was actually reported.

How it works

The five-step e-Invoicing API workflow

Our team walks you through the exact request and response for this service during onboarding.

Step 1

Agree how you will use the invoice check

Tell us where the validation belongs in your payables or financing process. Get API is where that conversation starts, and the service contract follows it.

Step 2

Add the check to your payables systems

Add the validation to your accounts payable queue, ERP posting step, vendor portal or financing workflow. Onboarding includes the technical documentation your developers need.

Step 3

Send the Invoice Reference Number

Your application sends the Invoice Reference Number carried by the reported invoice your team received.

Step 4

Read the invoice details returned

The information available against that reference comes back in a structured response. Field availability follows the data source and the record itself.

Step 5

Act on the invoice result

Use the response for the payment, posting or financing decision you collected it for, and keep it with the payables record for later review.

Industries

Where teams use e-Invoicing API

These sectors build the check into a decision they already make.

  • Enterprise finance

    Vendor invoice check before payment is released

  • Lending and NBFC

    Invoice check before a receivable is discounted

  • Marketplaces

    Seller invoice check before settlement

  • Staffing platforms

    Monthly manpower vendor billing check

  • Logistics and freight

    Carrier invoice check before freight settlement

  • Travel and expense

    Corporate invoice check before credit is claimed

What is e-Invoicing?

Under e-Invoicing, a business above the notified turnover threshold reports each business-to-business invoice for registration before issuing it. The invoice comes back carrying an Invoice Reference Number and a printed QR code. That reference is what makes the document identifiable later.

The consequence for you as the buyer is direct. A bill that was never reported carries no valid reference. A bill whose reference will not resolve is worth stopping before payment.

Checking the reference is a control that belongs on the buyer's side of the transaction.

Why this check starts from the Invoice Reference Number

This service starts from the Invoice Reference Number, and that changes what the check can tell you.

Reading an invoice image gives you the fields printed on it. That helps with data capture, though it says nothing about whether anyone reported the document. Starting from the reference works the other way round: it describes what was registered, and you can compare it against the document your vendor sent.

Where you need fields lifted off a PDF or a photograph, the e-Invoice OCR service covers that. The two services complement each other, and finance teams often run both.

What a mismatched invoice reference tells you

Most references resolve cleanly. The work sits with the ones that do not.

A reference that will not resolve means you cannot tie the bill to a reported invoice. Send it to a supplier query and keep it out of the payment run. A reference that resolves to different values or a different buyer points to a document that was altered, mistyped or misdirected.

A reference that resolves to an invoice since cancelled is worth catching, because the bill may already be approved. Decide early which case stops a payment and which one raises a query.

Teams that validate reported invoices

Enterprise finance teams run the check in accounts payable before they schedule an invoice for payment. A document that cannot be resolved to a reported invoice is a tax exposure as well as a payment risk.

Lenders and NBFCs financing receivables use it to establish that an invoice presented for discounting was really reported and not assembled for the financing.

Marketplaces validate seller invoices before settlement, because the platform's tax position rests on documents raised by independent sellers.

Logistics buyers check carrier invoices before freight settlement. Hospital procurement teams check distributor invoices across a long supplier list.

Travel and expense teams check the invoices a corporate account receives from airlines, hotels and agents, where recoverable tax depends on properly reported documents.

How to check a reported invoice online

Treat the check as a step in your payables process:

  • Capture the reference from the invoice as received, typed in or extracted.
  • Validate it and retrieve the invoice information recorded against it.
  • Compare the supplier, document and value details against the bill you are about to pay.
  • Check whether the reported invoice has since been cancelled before you release payment.
  • Keep the response with the payables record so a reviewer can see what you checked.

Where the invoice check sits in accounts payable

Connect the check to an accounts payable queue, an ERP posting step, a vendor portal, an expense platform or a financing workflow.

Where it sits decides what it protects. At intake it stops a questionable document before it enters the ledger. Before payment release it catches an invoice cancelled after you booked it.

In a financing workflow it supports the decision to advance funds against a receivable. High-volume teams place it at intake and repeat it at release.

Rules for validating vendor invoices

Invoice records describe dealings between businesses. Validate references on documents your organization received or was asked to finance, and keep the check away from exploring another party's activity.

Keep the retrieved information inside the finance systems that need it, and apply the rules you already apply to vendor records. Be ready to show what you checked when a result holds a payment. Your contract with us decides which checks you can reach.

FAQ

Common questions

What teams ask before they integrate e-Invoicing API.

The Invoice Reference Number carried by the reported invoice. The check works from that reference, not from a scan or a PDF of the document.

Related

More in e-Invoicing & e-Way Bills

GST, Udyam and company records, directors, PAN-linked business lookups, e-invoicing and business document OCR.

Browse Business & KYB APIs
Get started

Add e-Invoicing API to your workflow

Tell us how you plan to use it. Our team sets up API access, agrees your pricing and takes you through onboarding.