Property developer·2022 to present
A self-service portal for vendor contracts and payment requests
Suppliers and contractors had no direct way to submit a payment request or follow its review. We built a portal connected to the internal approval system.
- Sector
- Real Estate, Vendor Operations
- My role
- Full-stack developer across the backend, frontend, integrations, releases, and production support.
- Stack
- Laravel, Vue.js, Inertia, Tailwind, MySQL, REST APIs, queued workers, AWS
In 2022, our team built a self-service portal for a property developer's suppliers and contractors. Vendors can open a contract, submit a payment request with the required documents, and follow its progress through the client's internal review process.
I have worked across the portal from the initial build onward as a full-stack developer.
Giving vendors a view into the process
Before the portal, vendors had no account where they could submit a request against a contract, attach the supporting documents, or check what happened next. The company already had an internal approval process, but it did not give suppliers and contractors a direct way into it.
The portal fills that gap without exposing the internal system. A vendor signs in, chooses an active contract, creates the request, adds the documents, and submits it for review. The request stays visible as its status changes.
Despite the name, the portal does not move money through a payment gateway. It handles the request for payment and its review status; approval and finance work remain in the internal platform.
Connecting two applications without hiding failures
My work covered complete features across the Vue and Inertia frontend, Laravel backend, data model, APIs, and the connection to the internal request and approval platform.
Submitting a request creates the vendor-facing record and sends the relevant work into the internal platform. Status updates made during review come back to that same request in the portal.
The failure cases matter here. If the internal handoff fails, the portal does not tell the vendor the request was successfully submitted. The integration records what happened so the support team can investigate and retry it instead of leaving both applications silently out of sync.
What vendors and administrators can do
Vendors can manage their profile, view the contracts available to their account, create requests, attach supporting documents, receive notifications, and follow the current status.
The administration side covers vendors and users, contracts, payment-request oversight, activity history, dashboards, and reporting. Vendors get the information they need without gaining access to the client's internal finance workflows.
Ongoing work
The portal has been in production since 2022. A support issue can cross the portal record, the integration, and the internal request, so I continue to work across all three rather than treating the portal as a standalone frontend.
That work includes new workflows, integration fixes, releases, platform upgrades, and day-to-day production support.