Job Business Requirement Descrip3on for Technical Team Members, Freelancers & Interns

Nahar Om Family Office (www.nahar.om) is spearheading the incuba<on of various fintech Start-ups,
ac<vely seeking skilled individuals to infuse fresh insights and elevate the performance of our tech
plaDorms. If you are a proactive, adaptable individual with a diverse skill set, we encourage you to
apply. Join us in driving excellence across various facets of our organization!

Project 1: Loan Origina1on System and Loan Management System Enhancement

• Objec<ve: Complete pending modules of the Invoice Discoun<ng PlaDorm, focusing on API
Integra<ons.
• Progress: 50% development completed.
• Tech Stack: Django 4.2.7, Python 3.11, Nextjs 13.2, React 18.2.
• Required Coding Languages: Python, JavaScript (React).
• See Annexure A for more details on the Project

Project 2: Secondary Trading Pla=orm for Recurring Revenue Loans

• Task: Fetch data from the Loan Origina<on System through APIs.
• To make a new plaDorm which gets connected to Loan Origina<ons System
• Required Coding Languages: Python, API Integra<on (RESTful).
• See Annexure B for more details on the Project

Project 3: AI/ML Scorecard Development

• Goal: Create AI/ML scorecards using open source codes below.

• U<lize provided input parameters in Excel.
• Customiza<on and integra<on into the Loan Origina<on Engine.
• Required Coding Languages: Python, Machine Learning (ML), Ar<ficial Intelligence (AI).
• hcps://www.linkedin.com/pulse/its-2024-you-should-using-boos<ng-build-credit-risk-paul-
edwards-rgsic?utm_source=share&utm_medium=member_android&utm_campaign=share_via
• hcps://www.linkedin.com/posts/sudiptakghosh_enhancing-credit-scorecards-with-boos<ng-
ac<vity-7150718190589763585-PBdO?utm_source=share&utm_medium=member_android
• hcps://www.nvidia.com/en-us/on-demand/session/gtcspring21-s31327/
• hcps://github.com/rapidsai-
community/showcase/tree/main/event_notebooks/GTC_2021/credit_scorecard
• hcps://acrobat.adobe.com/id/urn:aaid:sc:AP:ae09aad3-66f0-46a9-8b41-13e2528f0810
• hcps://github.com/deburky/boos<ng-scorecards

Project 4: ONDC Integra1on

• Requirement: Integra<on with ONDC as a seller app for GST-based invoice loans.
• Required Coding Languages: Python, API Integra<on (ONDC).

Project 5: PFTPC Integra1on

• Task: Integrate with Public Tech PlaDorm for Financial Credit (PFTPC).
• No annexure available at this stage.
1
• Required Coding Languages: To be determined based on plaDorm specifica<ons.

Project 6: Supplynote Integra1on

• Objec<ve: Embed financial Loan Origina<on System into Supplynote for data collec<on on past sales
and credit offerings.
• Required Coding Languages: Python, API Integra<on (Supplynote).
• hcps://ionian-middle-97b.no<on.site/Checkout-Quick-Integra<on-
aae377f54c5940c59f603f503d491384

Project 7: SMS Parser Development

• Requirement: Customize SMS Parser using open source code.

• Required Coding Languages: Python.
• hcps://github.com/saurabhgupta050890/transac<on-sms-parser
• hcps://stackoverflow.com/ques<ons/22294546/what-is-the-best-way-to-parse-sms
• hcps://www.reddit.com/r/tasker/comments/vphiwt/parse_sms_text_place_data_into_google
_sheets/

Project 8: Tally Integra1on

• Goal: Offer a bridge or API for automa<c data retrieval on buyer and supplier ledgers, P&L, Balance
Sheet, and Invoices.
• Required Coding Languages: Python, Tally Integra<on.

Project 9: Bank Statement Analyser

• Task: Develop a Bank Statement Analyser based on open source code.

• Required Coding Languages: Python.

• hcps://medium.com/@_samkitjain/developing-a-bank-statement-analyser-7470bne5e2
• hcps://marketplace.uipath.com/lis<ngs/ocrolus-audit-resource
• hcps://www.reddit.com/r/Python/comments/f4oaag/bank_statement_analyzer_gui_with_pan
das/?onetap_auto=true&one_tap=true

Project 10: Influencer Tokeniza1on Pla=orm

• Idea: Integrate with APIs of open-source video and content plaDorms.

• Tokenize content with Intellectual Property wrapper.
• Integrate with Loan Origina<on System.
• Required Coding Languages: Python, JavaScript (React).

2
Project 11: Crowdfunding Pla=orm for Gaushalas

• Task: To make a crowdfunding website similar to Give India or Keco

• Gaushala project wireframes can be shared once the project is chosen
• Required Coding Languages: To be determined based on plaDorm specifica<ons.

How to Apply
We invite applica<ons from individuals proficient in the specified coding languages and enthusias<c
about contribu<ng to these dynamic projects. Detailed technical documenta<on and annexures are
provided for further clarity.

Candidates can choose one project or mul<ple projects as per their proficiency and interest. They can
go through the Annexures below – Project details are men<oned

You can apply as an individual or as a Team. For Applying, please choose 1 or more projects and submit
your porDolio of the previous work done at [email protected]

There will be a Task given aser the applica<ons are reviewed.

Miscellaneous Informa0on

Loca<on : Remote ( work from home)

S<pend: Depends on the Project Chosen

ANNEXURE A

Project 1 : Loan Origination System Platform

Seller
Ø Business onboarding
• Business Registration and Verification: Focus on the registration and verification
processes for businesses, ensuring their legitimacy on the platform.
• Document Verification: Allow businesses to upload necessary documents for validation,
including business verification. Documents like company documents, GST, ITR etc will be
uploaded which will be
• In-Person Verification Process: Implement in-person verification processes for
enhanced security and compliance.
• Account creation: User will set-up unique username and password, which will be used
for accessing the platform.
Ø KYC

3
 •
In-Person Verification Workflow: It will be implemented for businesses requiring full
KYC.
• Biometric Verification: Introduce biometric verification methods for added security.
• Geolocation Verification: Implement geolocation-based verification for user location
confirmation.
• User Notifications: Set up notifications to guide users through the full KYC process.
Ø Dashboard
• Overview Panel:
o Total Invoices Raised: Displays the total number of invoices that have been
submitted.
o Total Amount Due: Shows the cumulative amount of all the invoices raised that's
pending payment.
o Total Amount Funded: Summarizes the amount the seller has received from
investors for discounted invoices.
o Total Overdue: Highlights invoices that have surpassed their due date and are still
unpaid.
• Credit Overview: Graphical representation of
o Credit Used
o Credit Available
o Credit due (in n days)
o Option to increase credit
• Account overview: High level account overview show following information –
o Status
o Rating
o Type
o Total money borrowed
o Amount paid bac on time
• Detailed view of credit due and with filter options
• Invoice overview: Categorization of invoice – uploaded, active, past, due etc.

Ø Invoice submission and verification

• Invoice Submission Process: Enable businesses to submit invoices for investment,
including document uploads.
• Integration with Open Banking API: Integrate with open banking APIs for seamless
financial transactions and data access.
• Integration with ERPs and Accounting Software: Connect with external ERPs and
accounting software to streamline invoice data handling, e.g., integration with Tally, Zoho,
Busy, etc.
• Integration with Vendor Modules: Integrate with vendor modules to facilitate invoice
validation and verification, e.g., FK Vendor Hub, Amazon Vendor Central, etc.
• Invoice Validation Workflow: Develop workflows for invoice validation to ensure the
authenticity and eligibility of submitted invoices.

4
 • User Dashboard Enhancements: Enhance user dashboards to accommodate business
specific features and information.
• Security and Compliance Updates: Update security measures and compliance checks
to accommodate business accounts.
• Testing and Quality Assurance: Conduct thorough testing and quality assurance to
ensure the reliability of business onboarding and invoice submission processes.
• Documentation and Support: Provide documentation and support resources to assist
businesses during onboarding and invoice submission.
• User Feedback and Iteration: Gather feedback from businesses and iterate on the
onboarding and invoice submission processes for continuous improvement.
• Investment Process: Investors can select invoices and invest in them, marking the
beginning of the transaction process.
Ø Credit scoring service
• Integration with Credit Rating Agencies: Integrate with credit rating agencies to provide
credit scores to businesses.
• User Access to Credit Scores: Enable businesses to access their credit scores for
informed financial decisions.
• Credit Scoring Algorithms: Develop credit scoring algorithms to assess
creditworthiness.
Ø AML Measures
• AML: Enhance anti-money laundering (AML)
• User Training and Education: Provide user training and education on AML, policies,
procedures and tax implications
Ø Reporting and Analytics:
• Access to detailed reports showing invoice payment history, funding trends, and
transaction records.
Ø Profile Settings:
• Edit and update business or personal information.
• Configure notification preferences, such as email or SMS alerts

Admin

Ø Login
Ø User management
• User Listing: Comprehensive list of all registered users, segmented by type (e.g., Investor,
Seller).
• Account Verification: Review, approve, or decline submitted KYC documents or account
registration requests.
• User Activity Monitoring: Access logs detailing user actions for security and audit
purposes.

5
 • Role Assignment: Define or change user roles, adjusting permissions and access levels
as needed.
Ø Invoice & Transaction Management:
• Invoice Review: Approve, decline, or flag invoices submitted by sellers for further
verification.
• Transaction History: Detailed record of all transactions, including funding, withdrawals,
and reinvestments.
Dispute Resolution: Manage and resolve any disputes between users, especially related to
payments or transaction terms.

Ø Dashboard
• Overview: Upon logging in, the admin is presented with an overview dashboard. This
dashboard provides key statistics and metrics related to the invoice discounting process. It
may include data such as the number of active discounting requests, approval rates, and fee
collection.
• Manging Discounting request: The admin can view and manage all the active invoice
discounting requests. This includes -
o Reviewing pending requests awaiting due diligence.
o Checking the status of approved requests.
o Monitoring requests awaiting client payments.
o Tracking completed requests.
• Due Diligence Review: For pending requests, the admin can access detailed information
about the due diligence process.
• Approval or Rejection: Based on the due diligence results, the admin can approve or reject
the discounting requests.
• Fee Management: The admin can access a fee management section to review and manage
fees collected from each discounting transaction. They can view the fee amount collected
from each transaction and ensure it aligns with the agreed-upon fee structure.
• Audit Trail: The admin can access an audit trail that records all actions taken within the admin
panel. This is crucial for maintaining a transparent and compliant process
• Regulatory Compliance: Monitoring the entire process for compliance with financial
regulations and ensuring that the discounting process adheres to legal and ethical standards.
This user's journey includes regulatory oversight and intervention if necessary.

Ø Buyers and sellers

• List of buyers will be displayed along with relevant information of the buyer.
• Admin will be ablet to add a buyer.
• List of sellers will be displayed under seller section
• Admin will be able to create a seller.
Ø Risk management
• Risk Parameter Settings: Set and adjust risk parameters for evaluating invoice quality or
user authenticity. APIs can be integrated to calculate risk score for an invoice.

6
 •Flagging System: Review and manage items or users flagged by the system for potential
risks.
• Audit Logs: Detailed logs of all activities on the platform, essential for identifying irregular
patterns or ensuring compliance.
Ø Reporting & Analytics
• User Statistics: Detailed analytics regarding user sign-ups, activity levels, and retention
rates.
• Financial Reports: Generate reports on platform financials, including transaction volumes,
revenue, and fee collections.
• Feedback & Reviews: Access and review feedback provided by users to understand areas
of improvement.

Integrations
Ø KYC related integration
Ø Payment gateway integration
Ø Bank integrations.
Ø Integration with credit rating agencies.
Ø ERP software's like ZOHO, TALLY etc.
Ø Reporting software's.
Ø Other third-party APIs.

User Journey

Ø User Journey for Seller (Company X).

• Step 1: Invoice Generation - Company X generates a $500,000 invoice for the completed
metaverse project. They send the invoice to the client with net 60 days payment terms.
• Step 2: Due Diligence - Company X identifies the need for immediate cash flow for their
AR/VR project. They research and select a financial institution (Investors) specializing in
invoice discounting. They provide the necessary documentation and information to Investors
for the due diligence process. They await the results of the creditworthiness assessment and
reliability evaluation of their client.
• Step 3: Invoice Submission - Once Investors approve the discounting process, Company X
submits the $500,000 invoice to Investors for discounting. They provide any additional
information or documents required by Investors.
• Step 4: Fund Release - After submission, Investors approve the invoice and release 90% of
the invoice value, which is $450,000, to Company X. Company X receives the immediate cash
flow they need for their AR/VR project.
• Step 5: Client Payment - Company X's client pays the full invoice amount of $500,000 to
Investors on the 60th day as per the payment terms. This payment goes directly to Investors.
• Step 6: Remaining Balance and Fees - Investors deduct a 2% fee ($10,000) and release the
remaining balance of $40,000 to Company X. Company X successfully secures the remaining
funds.
7
 Annexure B

Project 2 : Secondary Trading platform

Objectives
To design and develop an intuitive and user-friendly trading platform specifically for
recurring revenue contracts

To enable the fragmentation of larger contracts into smaller chunks, thereby

democratizing access for retail investors

To offer a seamless UI/UX with a smooth and responsive mobile application interface for
end-users and web interface for an Admin

To integrate a robust machine learning-powered recommendation engine to personalize

feeds for buyers based on their investment preferences

To construct a scalable and extensible system architecture that can accommodate

additional features and future use cases

To facilitate user onboarding with KYC processes and wallet creation, leveraging
Decentro's or any other API services

8
 To research and integrate the best payment transactions aggregator for large
ticket sizes

To determine the appropriate technology stack that aligns with the platform's
performance and security requirements

To manage data effectively, ensuring robust data analytics capabilities for

strategic decision-making and enhanced user engagement

To provide a detailed project timeline with key milestones, facilitating transparent

progress tracking

User Journeys
The below section outlines the major journeys that are core of the platform and
doesn’t cover rest of the journeys for this document but will be included in the final
design and development.

Onboarding

The onboarding journey for buyers and sellers on your platform comprises several
distinct steps, designed to guide users from registration to the operational use of
their accounts:

1. Registration: Users begin their journey by registering on the platform. This step
likely involves providing basic personal information and setting up login
credentials.

2. KYC Process (Decentro): After registration, users proceed to the Know Your
Customer (KYC) process facilitated by Decentro. This process is critical for
compliance with financial regulations and typically requires users to submit bank
details and PAN (Permanent Account Number) details for identity verification.
9
 3. Wallet Creation and Deposit (The partner is yet to be figured out): Once
KYC is complete, users can create their digital wallets. This is an essential step
for enabling transactions on the platform. Following wallet creation, users can
deposit funds into their accounts, which signifies the completion of the
onboarding process and readiness to engage in trading activities.

This streamlined process is designed to be user-friendly and efficient, ensuring that

users can quickly become active participants in the trading platform.

Buyer's Journey to Place a Bid:

The above diagram outlines the process a buyer goes through on the platform to
place a bid on a recurring revenue contract:

1. Platform Access and Contract Search:

The buyer starts by accessing the platform through a mobile interface.

They enter their desired Internal Rate of Return (IRR), which the system
uses to filter contracts.

The buyer views contracts that match their criteria. This involves the buyer's
system sending a GET request to the API server, which in turn queries the
database for relevant contracts.

2. Bid Placement Process:

The buyer selects a contract to bid on from the list of matches.

They place a bid on the selected contract. This step involves the buyer's
system sending a POST request with bid details to the platform's API server.

3. Bid Confirmation:

Upon placing a bid, the bid details are inserted into the database.

The buyer receives a confirmation of the bid, indicating successful

completion of the process.

10
Seller Journey to Respond to a Bid:

The above diagram depicts the steps a seller takes to manage bids on their listed
contracts:

1. Bid Review and Decision Making:

The seller receives a notification of a new bid, prompting them to review the
bid details through the platform's interface.

After reviewing, the seller makes a decision on the bid. If they decide to
accept it, they confirm acceptance through the interface.

2. Bid Acceptance and Ownership Transfer:

Upon acceptance, the API server updates the contract status to reflect the
new ownership.

The seller then initiates a money transfer to complete the sale, and the
system confirms the new ownership of the contract.

3. Counter OFer or Bid Rejection:

If the seller does not want to accept the bid, they have two options:

Make a counteroffer through the interface, which the API server then
updates with the counter-offer details.

Discard the bid entirely through the interface, and the API server marks
the bid as 'discarded'.

Admins user journey:

11
The above diagram depicts actions the admin can take on the web platform:

1. Listing New Contracts: The admin has the ability to initiate the listing of
new contracts, overseeing their addition to the platform and ensuring they are
accurately represented in the database.

2. Setting Trading Limits: The admin is responsible for defining minimum and
maximum trading limits, which are crucial in managing the scale and scope of
transactions on the platform, particularly for retail buyers in a secondary trading
context.

3. Configuring Liquidity Bot Engine: The admin configures and manages

the liquidity bot engine, setting parameters that dictate the bot's operational
behavior, including the types of bids it should accept each day.

4. Monitoring and Managing Trades: The admin uses a dashboard to monitor live
trading activities, review transactions, and assess the overall health and
performance of trading operations on the platform.

Flow chart
A tentative high-level flow chart, though not comprehensive, that describes the
actions that can be taken by the user and the tentative API contracts. This could
change during the first 3-4 weeks when we gather all requirements.

12