Skip to content
RigoMind

Two products of our own.

Each takes a job that repeats every day, and gives the hours back to the people who were doing it.

Hospitality · In use with clients

RigoMind Hospitality AI

Answers guest enquiries in the guest's own language and channel, quotes from the property's own rates, and holds the room.

  • Guest enquiries on WhatsApp, web chat and email, in the guest's language
  • Rates and availability from the property's own systems
  • Holds, payment links and confirmations, written once

Our product for hotels, homestays and tour operators, with its own site and full details at hospitality.rigomind.com.

Visit hospitality.rigomind.com

RigoInvoice

In use with clients

An invoice arrives as an email, a PDF or a photograph taken on a phone. The fields are read off it by a model, every check is computed by application logic, and nothing is posted to Tally or the spreadsheet until a person approves it.

Document to ledger entryIllustrative. Left is the supplier's document; right is the ledger. Debits and credits balance, the tax is a real slab of the net, and nothing posts until a person approves.

Step 1 of 3, Received. Document INV-5514 arrives. The ledger shows the draft double entry with no checks run and nothing posted.

supplier document
supplier invoicereceived
Site works — phase 272,000
Materials8,400
fields read
  • referenceINV-5514
  • net₹80,400
  • tax₹14,472
  • total₹94,872
nothing validated yet
accounting ledger
INV-5514received
accountdrcr
Site works — phase 272,000
Materials8,400
Input GST14,472
Vendor payable94,872
balance94,87294,872
checks0 of 4 passed
  • lines sum to total
  • tax rate matches master (18%)
  • PO exists and is open
  • no duplicate reference
step 1 of 3MODEL
  1. 01 · Received

    Fields are read off the document. Nothing is trusted yet: no check has run and nothing is posted.

  2. 02 · Checks

    Checks run in application logic. Debits and credits both total ₹94,872, and the tax is 18 per cent of the net.

  3. 03 · Posted

    A person approves, and only then is the entry written to the ledger.

What changes

Estimates

Time to process 10 supplier invoices

An accountant, by handa day or more
With RigoInvoiceabout 12 minutes
40×faster, by these estimatesboth bars on one linear scale
3
ways an invoice can arrive
email, PDF upload or a phone photo
0–4
fields keyed by hand
per invoice, down from about 28
100%
of totals and tax checked
before anything is posted

The accountant's time moves from typing and re-checking to approving the entries the system flags.

Manual against automated
Manual intakeas found

Every invoice costs the same amount of attention as the one before it.

  1. person
    Open the email, find the attachment
  2. person
    Read the invoice, key the header fields
  3. person
    Key each line item
    where most errors enter
  4. person
    Check the arithmetic by hand
  5. person
    Re-key the whole thing into Tally
  6. person
    File the paper copy
With the system in placeas built

Attention is spent on the entries the system could not settle itself.

  1. system
    Intake from email, upload or photograph
  2. model
    Extraction of header and line items
  3. system
    Arithmetic and tax validation
    computed by application logic
  4. system
    Purchase-order cross-match
  5. person
    Review of flagged entries only
    the person sees exceptions
  6. system
    Posting to Tally with the source attached
Six steps become six steps. The difference is that five of them stop requiring a person, and the one that still does is the one where judgement is needed. The time this saves is shown above.
For your technical team — RigoInvoice
Input
Vendor invoices as email attachments, PDF uploads or mobile photographs
Processing
Visual-linguistic reading of header fields and line items
Deterministic core
Arithmetic verification, GSTIN validation, and purchase-order cross-match
Output
Posting to Tally, an ERP or a structured spreadsheet, with the source document attached
Invoice queueIllustrative interface. A row is never posted while a check is outstanding, and the reason for every hold is written on the row.
queue · today's batch
  • INV-5512posted
    Site contractor3,599
    4 of 4 checks
  • INV-5513posted
    Electrical supplier18,940
    4 of 4 checks
  • INV-5514review
    Materials supplier94,872
    4 of 4 checksabove the review threshold
  • INV-5515review
    Cement supplier5,900
    3 of 4 checkslines sum to total — held for review
  • INV-5516returned
    unreadable—
    1 of 4 checksdocument could not be read
  • INV-5517review
    Steel supplier11,300
    3 of 4 checksPO exists and is open — held for review
  1. A row is never posted while a check is outstanding.
  2. The reason for every hold is written on the row, not left to be inferred.
Invoice pipeline
03 · Extractionmodel

Header fields and line items are read off the document. Everything at this stage is a proposal.

proposed
{ "vendor": "Site contractor", "gstin": "27•••••••••1Z5", "invoice_no": "INV-5512",
"date": "2026-08-02", "lines": [ { "desc": "Cement OPC 53", "qty": 40,
"rate": 76.25, "amount": 3050 } ], "tax": 549, "total": 3599 }
// a proposal: nothing has been checked yet
Illustrative walkthrough of one invoice. Extraction is allowed to be wrong; validation is not, which is why the two are separate stages rather than one.

Have a job like this that repeats every day?

Book a demo and we will walk you through RigoInvoice on your own documents, and tell you whether it fits. For RigoMind Hospitality AI, visit hospitality.rigomind.com.

Book a demo