Add Co-funding Info in Projects & Budget Bills
Brought co-funding data online across projects and budget bills for precise attribution and cost-sharing transparency across multiple regions.
- Role
- Senior Backend Engineer
- Timeline
- 2026
- Team
- 4
- Domain
- E-Commerce / Budget & Finance
- Stack
- 8 tech
- Status
- Live
Overview
This project standardizes how co-funding information is recorded in Project Management and Budget Bill systems, replacing manual offline tracking of platform-vs-seller cost splitting. As the lead backend engineer, I drove the technical assessment, requirements document, and backend design for rolling co-funding data out across multiple regions.
Gallery
A backend has no screens, so its "UI" is the operational surface: the API contract, the ops flow, and the cross-service change map.
Problem & Solution
Without an online co-funding data model, cost-sharing ratios and caps were tracked manually — low transparency, higher error risk, and weak budget attribution across projects and budget bills. This grew more problematic as co-funding expanded to more regions.
I designed the backend changes to embed co-funding metadata into core campaign and budget flows: a new co-funding info table, additional columns in existing budget structures, and updates to key APIs and interface contracts used by the proposal, budget, and gateway layers (set-budget, get-proposal, create-bill, list-bills APIs). I led requirement clarification with PM, aligned the design with the earlier budget-foundation work, and prepared it for technical review.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
Co-funding is modeled as first-class metadata: the Budget Service persists ratios, caps, and source-project types in co-funding info table, while the Proposal Service and Gateway carry the new fields through their interface contracts. A mandatory "Source Project Type" on project items and a "Co-fund Info" section on budget bills drive attribution across multiple regions.
Features
- Mandatory "Source Project Type" on project items
- Co-fund ratios & caps captured per budget bill
- Transparent platform vs seller cost splitting
- New co-funding info table
- Updates to set-budget / get-proposal / create-bill / list-bills APIs
- Cross-service interface contract changes (Proposal / Budget / Gateway)
- Multi-region rollout
Tech Stack
Engineering Challenges
Co-funding logic had to fit existing project, proposal, budget, and gateway flows without fragmenting implementations. Fix: map requirements into shared schema and contract updates across services rather than one-off patches.
The design had to cover multiple regions and reuse the earlier budget foundation. Fix: align co-fund data modeling with the earlier budget-foundation work for consistency and reuse.
Outcomes
Lessons Learned
Financial data integrations benefit from a simple, shared metadata model early in design. Treating co-funding as a first-class object across services — not a one-off field patch — made the solution clearer, easier to review, and more extensible for future markets.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.