Salesforce MVP Hall of Fame (Shivanath Devinarayanan) · Founded 2022
Invoice processing
Accounts payable as a process, not a folder of PDFs. Capture, match, and a person on the exception.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
The stack
How we would assemble it.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Before and after
Invoices, before and after.
Today
With the agent
- Fields retyped from PDFs
- Fields extracted and checked
- PO mismatches found at payment
- Mismatches flagged on arrival
- Supplier asks where the money is
- Status visible on the record
Spec, shadow, gate
How the first agent goes live.
One named job. A shadow run before any write.
Week one
The job on one page: inputs, the write, the limit, who approves, and what it may never do.
Before go-live
The agent acts as the person it works for, with their access. Knowledge and permissions checked before it takes a job.
Shadow run
Shadow
The agent runs beside the person and writes nothing. You compare its calls with theirs.
Go-live
Writes go live behind a human approval. The gate loosens only where the shadow run earned it.
Every week
Every run is logged. On the Run plan we read the transcripts every week and fix what went wrong.
For example
One desk, for example.
Example
AP lead at a Sharjah building-materials supplier
Today: Supplier invoices arrive as PDFs in a shared inbox.
After: Each invoice is matched to its purchase order. Mismatches go to a named person before payment.
The job
What has to be true.
AP desk
The brief
Send the situation.
Name the process. Name the object. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.