Vendor Invoice Portal - Infrastructure

Vendor Invoice Portal for Infrastructure Projectson Laravel and MySQL

Vendors submitted invoices by email and physical delivery, then phoned to ask what had happened to them. Kansoft built a self-service portal that unifies procure-to-pay and invoice-to-pay, automates three-way matching, and shows every vendor their own status in real time.

60% · faster procurement workflow3-way · automated PO/GRN/invoice matchingSelf-service · vendor status tracking
The Client

A vendor network paid through an inbox.

Sterlite Power builds power transmission infrastructure, which means a large network of vendors and suppliers working across concurrent projects. Keeping those vendors paid on time is not an administrative detail; it is what keeps sites moving.

Invoices arrived by email or physical delivery, were validated by hand, and travelled through procurement and finance systems that did not talk to each other. The vendors could not see any of it.

Architecture diagram for this engagement is being drawn.

The Problem

Four ways a manual payment cycle slows a project down.

Each delay is small in isolation. Across a vendor network supporting multiple concurrent projects, they accumulate into a working-capital problem for the suppliers and a continuity risk for the client.

01

Invoices arriving by email

Submission depended on email and physical delivery, which created bottlenecks, lost documents and material delay in the payment cycle.

02

P2P and I2P disconnected

Procure-to-pay and invoice-to-pay ran as separate processes with nothing linking purchase orders, goods receipts, invoice submission and payment approval, producing duplicate effort and reconciliation problems.

03

Manual validation, cascading errors

Checking invoices and procurement documents by hand was slow, and re-entering data between systems introduced inaccuracies that propagated through the approval chain.

04

Vendors could not see status

With no visibility into their own invoices or payments, vendors called and emailed procurement and accounts payable for updates, consuming staff time on both sides.

What We Recommended

Unify the two workflows, then let vendors serve themselves.

Automating invoice processing alone would have left the reconciliation problem untouched, because the root cause was two processes that never met. The portal matters for the same reason: every status call a vendor makes is a cost created by not showing them the answer.

PHASE 01

Workflow mapping

The complete P2P and I2P flows traced end to end, identifying every manual touchpoint and every bottleneck in the existing process.

PHASE 02

Self-service portal

A vendor-facing portal for submitting invoices, uploading supporting documents, viewing purchase orders, tracking payment status and managing account details without contacting anyone.

PHASE 03

Process unification

The previously disconnected procurement and invoicing workflows joined into one system with end-to-end traceability from requisition to payment.

PHASE 04

Automation layer

Automated validation, three-way matching across PO, GRN and invoice, rule-based approval routing, and configurable exception and escalation handling.

Technology Stack

Chosen for a vendor network with mixed technical capability.

The portal has to be usable by every supplier, from large contractors with their own systems to small vendors working from a phone.

PHP Laravel
Portal, workflow engine and rule-based approval routing
MySQL
Unified transaction record across procurement and payment
REST APIs
Integration with internal procurement and finance systems
Three-way matching
Automated PO, goods receipt and invoice reconciliation
Rule-based workflow
Approval routing with automatic exception and escalation handling
Vendor master link
Onboarding, compliance verification and performance tracking
Measured Outcomes

From an inbox and a phone call to a cycle that explains itself.

Four measured changes between the manual payment cycle and the unified platform now in use.

60%↑
Procurement workflow
P2P and I2P unified into one process with end-to-end traceability
Digitised
Invoice processing
Submission, validation and three-way matching automated
Real-time
Vendor visibility
Status and expected payment dates without contacting anyone
Removed
Follow-up overhead
Self-service replaced routine calls to procurement and accounts payable
What Changed for the Business

Four changes that mattered as much as the numbers.

Faster payment is the obvious benefit. The structural one is that procurement and finance now share a single record of what happened.

One traceable record

Requisition, order, receipt, invoice and payment sit on one thread, so reconciliation stops being an exercise in matching two systems that disagree.

Vendors stopped calling

Real-time status and expected payment dates are visible to the vendor who needs them, removing the follow-up loop that consumed procurement and accounts payable time.

Errors stopped propagating

Automated three-way matching and the removal of manual re-entry mean inaccuracies are caught at source rather than discovered downstream in an approval chain.

Supplier relationships improved

Predictable, visible payment cycles matter commercially to vendors, particularly smaller ones, and that shows up in how they price and prioritise work.

Engagement

How the work was shaped.

Practice
Custom Software Development · API & Integration Development · Legacy App Modernisation · Dashboard Design & Development
Platform & stack
PHP Laravel · REST APIs · MySQL
Industry
Energy & Utilities
Timeline
Dedicated team, ongoing engagement
Why Kansoft

Procurement and finance understood as one process.

Vendor portals fail when they digitise invoice submission and leave the reconciliation problem in place, because the delay was never really in the submission. Understanding how three-way matching, approval routing and payment scheduling interact is what makes it possible to join P2P and I2P into something traceable end to end, and building for a network with very mixed technical capability is what makes vendors actually use it.

Paying a large vendor network through manual workflows?

Tell us how invoices reach you and where they stall. We will map the P2P and I2P flows and show what unifying them would change.

Book a Free Call