e-Invoicing API
New
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.
Overview
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.
- Category
- Tax & Compliance Services
- Coverage
- Reported e-invoices carrying an Invoice Reference Number
- Input
- Invoice Reference Number from a reported e-invoice
- Output
- The invoice details available: parties, document reference and date, recorded values and reported status
- 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.
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Reference in progress
The request and response reference for this endpoint is not published yet.
Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:
- Endpoint URL and method
- The host, path and HTTP verb for this service.
- Authentication
- How a request identifies itself, and where credentials come from.
- Request parameters
- Field names, types, which are required, and validation rules.
- Response schema
- The success body, field by field, with a real example.
- Error codes
- What each failure means and which are worth retrying.
- Rate limits
- Request ceilings, and what happens at the ceiling.
No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.
Use cases
- 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 this service does
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 a check runs
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.
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.
Send the Invoice Reference Number
Your application sends the Invoice Reference Number carried by the reported invoice your team received.
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.
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.
Questions
- What do I send to validate an e-invoice?
- 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.
- What details come back for an Invoice Reference Number?
- You get the invoice information recorded against the reference. That covers supplier and recipient registration details, the document number and date, the values and tax breakdown recorded, and the status of the reported invoice. What you receive changes with the data source and with the record itself.
- How is this different from e-Invoice OCR?
- e-Invoice OCR reads an invoice image or PDF and returns the fields printed on it. This service starts from the reported reference and returns the information registered against it. Many finance teams use both, one to capture the document and one to check it.
- Do I need consent to check a vendor's e-invoice?
- Invoice records describe dealings between businesses. Validate references from documents your organization received or was asked to finance. Keep the response inside the finance systems that need it, and handle it under your existing vendor data rules.
- How do I get access to the e-Invoicing API?
- Use Get API and tell us about your invoice volumes and where the check belongs in your process. The service contract covers access and the integration documentation.
- Why do e-invoice results differ from one record to another?
- Records differ in what was reported against them, and data sources differ in what they can return. A reference may also resolve to an invoice that has since been cancelled, which is itself information a payables workflow needs.
Catalog entry last updated .