AP use case · Order-to-cash

Compliance shouldn't be
a second workflow.

E-invoicing and e-way bills are mandatory plumbing - but run as separate portal chores, they desync from actual billing and dispatch. Finnoto generates IRN and e-way inline with the invoice, tracks validity through transit, and keeps cancellations consistent across portal, books and buyer.

Compliance console

Invoice → IRN → e-way → dispatch,
one motion.

E-invoice run · today 214 documents
InvoiceIRNE-wayStatus
INV-9101 · BlinkitGenerated · 0.8sValid · 2 daysDispatched · in transit
INV-9104 · MT chainGeneratedPart-B pending! Vehicle assignment awaited
INV-9088 · cancelledIRN cancelled · 22hCancelledBooks & buyer synced
Validity watch
3 consignments within 8h of e-way expiry in transit - extensions filed proactively; zero detentions this quarter.
Clean cancellation
INV-9088 cancelled inside the 24h IRN window - credit path auto-selected where the window had passed.
IRN inline with billing · Part-B completed at vehicle assignment · validity tracked against live transit

Illustrative product behaviour - values shown are examples.

Why it's hard today

Portal-driven compliance
desyncs from reality.

When IRN and e-way happen in a portal after the fact, every mismatch between document, truck and timing becomes a detention, a penalty or a buyer rejection.

Two systems, one truth required

Invoice in the ERP, IRN on the portal - amendments and cancellations drift apart, and the buyer's 2B sees the difference even when you don't.

The 24-hour cancellation window

IRN cancellation is a 24-hour door. Miss it and you're into credit notes - fine if chosen, messy if discovered.

Validity meets traffic

E-way validity is computed in kilometres; trucks run in hours. Without live tracking against expiry, detentions are a matter of time.

The Finnoto difference: the invoice, IRN, e-way, dispatch and GRN are one record - compliance happens inside the order flow, not beside it.
How Finnoto runs it

Inline, not afterthought.

1
Generate at billing
IRN requested the moment the invoice finalises - schema-validated first, so rejections are rare and instant.
2
Complete e-way at dispatch
Part-A with the invoice, Part-B at vehicle assignment - no documents waiting on trucks or vice versa.
3
Track validity live
Expiry monitored against transit progress; extensions filed before deadline, flagged to logistics.
4
Keep everything consistent
Cancellations and amendments propagate to portal, books and buyer communication in one action.
FAQ

Frequently asked questions

Who needs e-invoicing?

Businesses above the notified turnover threshold must generate IRNs for B2B invoices - and buyers increasingly reject non-IRN invoices regardless, since their ITC depends on it flowing to GSTR-2B.

What happens if an IRN needs cancelling after 24 hours?

The portal window closes at 24 hours; after that the correction path is a credit note. Finnoto picks the right path automatically and keeps books, portal and buyer records consistent.

Can e-way bills be extended in transit?

Yes - validity can be extended within the rules before expiry. Finnoto tracks each consignment's remaining validity against live transit and files extensions proactively.

Make compliance a side effect of shipping.

IRN, e-way and dispatch in one motion - audit-ready by construction.

Talk to us