Property developer·2022 to present
A self-service portal for vendor contracts and payment requests
Suppliers and contractors had no portal for submitting payment requests against their contracts. The platform connects vendor submission, internal review, and status.
- Sector
- Real Estate, Vendor Operations
- My role
- Full-stack developer across the engagement: backend, frontend, integrations, releases, and production support.
- Stack
- Laravel, Vue.js, Inertia, Tailwind, MySQL, REST APIs, queued workers, AWS
A property developer had no vendor-facing system for suppliers and contractors to submit payment requests against their contracts. We built a self-service portal where a vendor can open a contract, submit a request with supporting documents, and follow its status through internal review. I have worked as a full-stack developer within the delivery team from the initial build onward.
Vendors had no system for submitting payment requests
Before the portal, a supplier or contractor could not sign in to submit a payment request, attach the required documents, or see its status. The company's internal system handled review and approval, but vendors had no direct way to start or follow that work.
A contractor requesting payment against an active contract now opens that contract in the portal, creates the request, adds the supporting documents, and submits it for internal review. The same request remains visible as its status changes, so the vendor can see what happened after submission without access to the company's internal system.
The portal manages the request and its status. It does not collect or disburse money through a payment gateway. Approval and finance work remain in the internal platform.
How I connected vendor submission to internal review
My contributions covered complete product slices rather than one layer of the application. I worked from the Vue and Inertia interface through the Laravel backend, data model, APIs, and integration with the internal request and approval platform.
Submitting a payment request creates the vendor-facing record and sends the work into the internal platform. Status changes made during review return to the portal. A failed or delayed synchronisation could otherwise leave the vendor and internal team looking at different versions of the same request.
I contributed to the submission and synchronisation path that keeps those records aligned. If the internal handoff fails, the portal does not mark the request as successfully submitted. Incoming status changes update the same request the vendor created.
One request connects the contract to internal review
After onboarding, vendors manage their profile and access the contracts available to their account. They can create a payment request against a contract, attach its supporting documents, receive notifications, and track the request's current status.
The admin portal covers vendor and user management, contract administration, payment-request oversight, activity history, dashboards, and reporting. This gives vendors and internal teams a shared view of the work without moving the internal finance process out of its existing system.
What I still support
The engagement has continued since 2022. When a vendor sees the wrong status, support work can involve the portal record, the integration, or the internal request. I continue to work across those parts of the system, including workflow additions, integration fixes, releases, and platform upgrades.