Official Table Schema

Before you can start writing scripts to extract your data you need to have an understanding of the available models, fields and relationships in the data model in Mobiloan.

Primary Model	Description
Affordability	This “affordability” Data Model Is Tailored To Capture Detailed Financial Information, Both Income And Expenses, Allowing For A Comprehensive Analysis Of An Individuals Financial Situation And Affordability, Associating Them With Clients.
Address	This "address" Data Model Has Various Attributes That Represent Information Related To Physical Addresses And Is Structured For Managing And Organizing Information Related To Physical Addresses, Associating Them With Clients.
Agent	The “agent” Data Model Represents A Comprehensive Structure For Managing Information About Agents, Including Personal Details, Pay Out Methods, And Relationships With Other Models Such As Commission Rules And Brokers.
Agent_commission_rule	The “agent Commission Rule” Data Model Captures Rules For Agent Commissions, Including Their Status, Name And Authorized Agent Categories. The Authorised Categories, Loan Products And Business Branches Associated With The Rule Are Also Stored On The Commission Rule.
Application	The “application” Data Model Captures Comprehensive Information About Loan Applications, Including Applicant Details, Financial Information, Status, And Various Dates. It Also Establishes Relationships With Other Models And Includes Measures For Data Security And Optimization. The Application Is Also Associated With A Business Branch, Client, Client Category, Loan Product, Loan And Where Appropriate An Agent.
Allps	The ”allps” Data Model Represents A User Entity ("allps") With Various Attributes Such As Name, Logon Name, Password, And Associated Branches. Permissions For The Allps User Are Stored In JSON Fields On The Allps Object.
Area	The “area” Data Model Captures Information About Geographical Areas, Including Their Location, Status, Associated Branch, And Various Attributes Such As Suburb, City, And Province. It Also Establishes Relationships With Other Models Like The Branch The Area Belongs To And The User Responsible For Capturing The Area.
Audit_log	The “audit Log” Data Model Captures Detailed Information About Audit Log Entries, Including The Corresponding Model Involved, The Operation Performed, And The Associated Entities. It Establishes Relationships With Other Models And Includes Indexes For Optimized Data Retrieval.
Avs	The “AVS” Data Model Captures Detailed Information About AVS (account Verification Service) Transactions, Including Service Provider, Response Details, Client Information, And Bank Account Details. It Establishes Relationships With Other Models Including The Branch, Client And Bank Account Models And Includes Indexes For Optimized Data Retrieval.
Billing	The ”billing” Data Model Captures Detailed Information About Billing Entries, Including Their Type, Frequency, Description, Quantity, And Cost. The Display Format Provides A Concise Representation Of The Fee Type And Rate For Easy Reference. Billing Objects Are Associated With Each Mobiloan Client And Form The Basis For Their Monthly Billing.
Bank_account	The “bank Account” Data Model Is Designed To Represent Information Related To Bank Accounts Within The Mobiloan System. Captured Information Includes Account Status, Name, Type, Account Number, Bank And Validation Status. The Bank Account Belongs To A Client.
Bank_statement	The “bank Statement” Data Model Captures Detailed Information About Bank Statements And Transactional Data, Including Status, Source, Response Details, And Associated Entities Such As Branches, Clients, Bank Accounts, And Documents. It Establishes Relationships With Other Models And Includes Indexes For Optimized Data Retrieval.
Branch	The ”branch” Data Model Captures Detailed Information About Branches, Including Name, Date Created, Branch Reference, Branch Manager, Contact Details, Physical Addresses And My Mobiloan Associations. It Also Establishes Relationships With Area, Allps And The Company Objects.
Broadcast	The “broadcast” Data Model Captures Details About Broadcasts, Including The Type (Operator Or Application), Creation Date, Start And End Dates, Title, Message, And The Recipients Types Based On Their Affiliation To A Branch Or Their Role Within The Business.
Category	The “category” Data Model Captures Comprehensive Details About Client Categories, Including The Category Status, Client Types, I.e. Old Age, Disability And Other Grant Recipients As Well As Workers And Government Pensioners, And The Associated Name. The Configuration Requires Establishing The Level Of Detail For A Clients Physical Address, Affordability Requirements, Client Information Detail, Credit Bureau Details, Employment Details, Loan Products, Repayment And Pay Out Methods, And Associates The Category With Employers And Branches.
Client	The “client” Data Model Captures A Wide Range Of Information About Clients, Including Personal Details, Contact Information, Client Or Grant Types, Marketing Preferences, And Holds Status. A Client Has A Number Of Links To Related Objects, Address, Area, Branch, Category, Employment, Employer, References, Beneficiaries, Affordability Assistant, Notes, Affordability, My Mobiloan Application, Bank Statement, Credit Report As Well As The Last Loan Linked To The Client.
Client_credit_payment	The “client Credit Payment” Data Model Captures Detailed Information About Credit Payment Responses Initiated On Client Bank Accounts, Including Payment Response Details, Client And Bank Information, Associated Loans And Branch.
Collection	The “collection” Data Model Captures Comprehensive Information About Collections, Including Details About The Loan, Client, Repayment, And The Actions Taken During The Collection Process. The Collection Is Associated With Areas, Branch, Client, Loan And Operator Objects.
Company	The “company” Data Model Comprehensively Captures Details About A Company, Covering Its Registration Information, Address, Debt Collection Specifics, Credit Bureau Details, Communication Service Providers, And Settings Related To The My Mobiloan Online Service.
Config	The “config” Data Model Serves As A Comprehensive Configuration Object, Allowing Administrators Or System Users To Fine-Tune Various Aspects Of The Application Or System, Including Authentication, Third-Party Integrations, General Settings, Alerts, SMS Configurations, Commission And Wallet Settings, ALLPS Automation, And Billing Preferences.
Compuscan	The ”compuscan” Data Model Stores Detailed Information About Credit Enquiries, Outcomes, And Various Credit-Related Metrics Obtained From Credit Bureaus. It Includes Details Such As The Outcome, Type Of Enquiry, Result Type, Date, Credit Status, Ratings, Active Accounts, Address Information, Decline Reasons.
Demand_letter	The “demand Letter” Data Model Captures Details About Demand Letters, Including Creation Date, Associated Loan Number, Loan Balance, Loan Initiation Date, And Due Date. It Establishes Relationships With Client, Loan, And Operator Entities.
Document	The “document” Data Model Captures Details About Documents, Including Creation Date, Document Name, Images, And Attachments (PDFs). It Establishes Relationships With Document Type, Client, Loan, And Application Objects.
Document_type	The “document Type” Data Model Captures Details About Document Types, Including Their Status, Name, Classification, Required Status And Frequency, Authorized Capture Source, Bypass Warning, Validity Period And Associated Document Categories.
Email	The “email” Data Model Is Designed To Store Details About Emails, Including Sender And Recipient Addresses (with Support For Multiple Addresses), Subject, Body, Attachments, And Relationships With Branch And Sender Entities. An Email Belongs To A Branch And An Operator, I.e. The Email Sender.
Email_verification	The “email Verification” Data Model Is Designed To Store Information About The Verification Of Email Addresses, Including Details About The Email, Verification Status, Associated Account, Domain Information, MX Records, Personal Attributes, Location Details, And The Sender Or Operator Involved In The Verification Process.
Data_export	The “data Export” Data Model Is Designed To Store Information About The Export Of Data, Including Details About The Destination, Associated Model, Date And Time Of Creation, Filters, Query Time, Count, Table Matrix, Output Details (URL, Email Address, File Size), And Relationships With Branch, Employer, And Operator Models.
Employer	The “employer” Data Model Is Designed To Store Information About Employers, Including Their Status, Details, Default Work Settings, Characteristics, Relationships With Branches And Employment Types, Associations With Multiple Employments And Clients.
Groupsrus	The “groups R Us” Data Model Is Designed To Store Information About Insurance Policies Offered By Groups R Us, Including Details Such As Coverage Amounts, Benefits, Premiums, And Associated Relationships With A Client And A Loan.
Employment	The “employment” Data Model Captures Detailed Information About An Individuals Employment, Including The Employers Name, Occupation, Start Date, Department, And Other Relevant Details Including Pay Frequency And Normal Pay Day.
Instalment_receipt	The “instalment Receipt” Data Model Captures Detailed Information About Instalment Receipts, Including Amounts For Loan Amounts Split Between, Capital, Initiation Fees, Interest, Service Fees, Discount, Insurance, VAT As Well As Any Overpayment Amounts. The Instalment Belongs To A Branch, Client, Loan, Presentment And Transaction In Mobiloan.
Log	The ”log” Data Model Is A Generic Representation Of Log Entries, Including A Name Or Title, Creation Timestamp, Content Stored In JSON Format, And Metadata Stored As JSON. The Model Is Suitable For Recording Various Types Of Events Or Activities In A System, Providing A Structured Way To Store And Retrieve Log Information.
Login_audit_log	The “login Audit Log” Data Model Is Tailored For Logging User Login And Logout Events. It Includes Timestamps For Login And Logout, Establishes Relationships With Relevant Objects Such As Branches, Operators, And Workers.
Loan	The “loan” Data Model Is Designed To Comprehensively Capture And Manage Details Related To Loans, Covering Aspects Such As Identification, Status, Dates, Pay Out And Repayment Methods, Attachments, Key Personnel Including Originators, Evaluators And Payers, Affordability, Instalment Details And Loan Product Details. It Also References Any Agents Associated With The Loan, Online Applications, Branches, Client And Employment Details As Appropriate. This Robust Model Provides A Foundation For Handling Various Processes And Interactions Within The Loan Management System.
Loan_transaction	The “loan Transaction” Data Model Is Designed To Capture And Organize Information About Specific Transactions Related To A Loan. It Includes Details About Dates, Transaction Types, Instalment Information, Including Capital Repaid, Initiation Fees, Interest, Service Fees, Discounts, Insurance, VAT, Overpayments (if Applicable) And The Transaction Total. Loan Transactions Are Associated With A Branch, Client And Loan.
Loan_insurance	The ”loan Insurance” Data Model Is Designed To Manage Various Aspects Of Insurance Policies Associated With Loans. It Includes Details About Policy Status, Type, Premiums, Options, Authorized Frequencies, Age And Capital Restrictions, Affordability Reserve, Authentication Details And Account Numbers.
Loan_product	The “loan Product” Data Model Is Designed To Manage The Configuration Details Of Various Loan Products, Including Their Status, Authorized Frequencies, Relationships, Capital Details, Cooling-Off Period, Instalment Details, Credit Type, Interest Rates, Service Fees, Initiation Fees, Discounts, And Employer Requirements. The Model Provides A Comprehensive Set Of Parameters To Define And Customize Different Loan Products Within The System.
Notification	The "notification" Data Model Captures Essential Information Related To Notifications, Including Creation Time, Message Content, Read Status, Badge Count, Recipient Details (specifically Effective On IOS), And Sender / Operator Details.
Note	The “note” Data Model Stores Information About Notes, Including Their Status, Creation Date, Text Content, And The Associated Client And Operator.
Operator	The “operator” Data Model Manages Information About Operators, Including Their Personal Details, Status, Relationships With Other Models For Example An Operators Role, Branch Associations And Device.
Payout_method	The "payout Method" Data Model Is Designed To Manage Information About Different Methods For Processing Pay Outs, Including Their Status, Basic Details, Withdrawal Fees, Associated Branch Information.
Presentment	The “presentment” Data Model Manages Detailed Information About Financial Components Presented, Responses Received, Associated Clients, Loans, And Transactions.
Purpose	The “purpose” Data Model Provides A Structured Way To Categorize And Manage Various Loan Purposes. It Includes Information About The Purposes Status, Type, And Associations With Loans.
Reference	The “reference” Data Model Captures Information About Personal References Related To Clients, Including Their Personal Details, Relationship To The Client, And Status.
Repayment_method	The “repayment Method” Data Model Captures Details Related To Different Methods Of Loan Repayment, Including Payment Types, Fee Percentages, Date Adjustments, Tracking Periods, And Authorized Banks.
Role	The “role” Data Model Captures Comprehensive Details About User Roles, Including Their Rights, Authorization Limits And Various Permissions Related To Loan Origination, Client Evaluation, Maintenance, Tools, Transactions, Messaging, Access Permissions And Setup.
Sms	The “sms” Data Model Captures Details About SMS Messages, Including Their Purpose, Timestamps, Message Content, Status, Context, Counts, And Associations With Various Entities Like Branches, Clients, Agents, References, And Operators.
Batch_sms	The “batch Sms” Data Model Captures Information About Batches Of SMS Messages, Including Timestamps, Details About The Batch (such As Message Content And Recipient Count), The Template Type, And Associations With Branches, SQL Queries, And Operators.
Session	The “session” Data Model Encapsulates User Session Information, Preferences, And Various Workflow-Related Details, Providing A Comprehensive Representation Of A Users Interaction Within The System.
Sql_query	The ”sql Query” Data Model Is Used To Store Mysql Queries For All Reports Linked To An Instance.
Sql_result	The “sql Result” Data Model Is Used To Temporarily Store Mysql Query Results Linked To An Instance.
Table	The “table” Data Model Is Used For Rendering Tables In Mobiloan. These Objects Are Temporary In Nature.
Temp	The “temp” Data Model Is Used For The Temporary Storage Of Data In Mobiloan.
Transaction	The “transaction” Data Model Captures Comprehensive Information About Financial Transactions In Mobiloan, Including The Type, Transaction Group, Amounts, And Unique Transaction Identifiers. A Transaction Can Be Linked To An Agent, Area, Branch, Client, Loan, Users, Other Transactions, Suppliers, Reconciliations And Transaction Categories.
Transaction_category	The “transaction Category” Data Model Provides A Comprehensive Framework For Categorizing And Managing Various Financial Transactions Based On Their Class, Transactor, And Other Characteristics.
Transaction_recon	The “transaction Recon” Data Model Serves As A Record For Reconciled Financial Transactions, Capturing Balances, And Providing Insights Into Any Variances. It Maintains Associations With Relevant Geographical Areas, Operators, Branches, And Workers. The Inclusion Of Transaction Associations And Contra Transactions Enhances The Models Utility In Tracking And Analyzing Financial Activities Within A Specified Reconciliation Period.
Transaction_supplier	The ”transaction Supplier” Data Model Is Designed To Store Information About A Transaction Supplier, Including Status, Scope (branch Or Company-Wide), Default Transaction Settings, And Associations With Specific Branches And Related Transactions. This Model Is Useful For Managing And Analyzing Financial Interactions With Suppliers Within Mobiloan.
Voice_call	The “voice Call” Data Model Captures Comprehensive Details About Voice Calls, Including Destination Information, Call Details, And Associations With Other Objects Within The System. It Is Designed To Facilitate The Tracking And Analysis Of Voice Communication Activities.
Wallet_action	The “wallet Action” Data Model Records Different Types Of Wallet-Related Actions, Including Creation, Edits, And Cancellations. It Captures Essential Details About The Responses, Financial Aspects, And Associated Identification Numbers, Enabling Efficient Tracking And Analysis Of Wallet Transactions.
Worker	The “worker” Data Model Is A Device, Captures Details About User Accounts, Including Basic Information, Enrolment Details, Relationships With Other Entities, For Example Branch, Company And Operator.

ACCESS TO OFFICAL TABLE SCHEMA EXPORT

A password protected file will be sent to you for reference purposes.

Users wishing to make use of the custom sql functionality must please email [e-mail] requesting a copy of the full data model.

Not that dissemination or distribution of the data model or extracts thereof will be in direct violation of your non disclosure agreement and will result in prosecution.

Below is an extract from the Mobiloan data model. For protection in intellectual property purposes we have only shown one model in the extract.

<?xml version="1.0" encoding="UTF-8"?>
<data-model>
    <!-- TRANSACTION -->
    <model name="transaction" label="Transaction">
        <field name="transaction_type" label="Transaction Type" type="single-choice">
            <option key="cash">Cash</option>
            <option key="debit_order">Debit Order</option>
            <option key="wallet">Wallet</option>
            <option key="eft">EFT</option>
            <option key="credit_card">Credit Card</option>
            <option key="pos">POS</option>
            <option key="payout">Payout Deduction</option>
            <option key="payroll">Payroll Deduction</option>
            <option key="journal">Journal</option>
            <option key="insurance">Insurance</option>
            <option key="other">Other</option>
        </field>
        <field name="transaction_group" label="Transaction Group" type="single-choice">
            <option key="loan_capital">Loan Capital</option>
            <!-- linked to client, loan -->
            <option key="loan_instalment">Loan Instalment</option>
            <!-- linked to client, loan, collection -->
            <option key="commission">Commission</option>
            <!-- linked to agent_id -->
            <option key="purchase_sale">Purchase and Sale</option>
            <!-- linked to any -->
        </field>
        <field name="date_created" label="Date Created" type="datetime" />
        <field name="category" label="Category" type="text" />
        <field name="transactor" label="Transactor" type="text" />
        <field name="description" label="Description" type="text:paragraph" />
        <!-- Loan and Instalment No -->
        <field name="amount" label="Amount" type="number" />
        <field name="balance_amount" label="Balance Amount" type="number" />
        <field name="transaction_number" label="Transaction Number" type="text" />
        <field name="image" label="Image" type="photo" />
        <field name="attachment" label="PDF" type="attachment" media="application/pdf" />
        <field name="user_transaction" label="User Transaction" type="boolean" />
        <!-- Relationship -->
        <belongs-to model="agent" />
        <belongs-to model="area" />
        <belongs-to model="branch" />
        <belongs-to model="client" />
        <belongs-to model="loan" name="payout_loan" />
        <belongs-to model="loan" name="repayment_loan" />
        <belongs-to model="operator" />
        <belongs-to model="operator" name="transactor_operator" />
        <belongs-to model="worker" name="user" />
        <belongs-to model="transaction" name="linked" />
        <!-- cash rounding journal or settlement journal -->
        <belongs-to model="transaction" name="contra" />
        <belongs-to model="transaction_supplier" />
        <belongs-to model="transaction_recon" />
        <belongs-to model="transaction_recon" name="contra_recon" />
        <belongs-to model="transaction_category" />
    </model>
</data-model>

With reference to the above model below is an explanation of the the various tags :

Tag Name	Tags	Description
data-model	<data-model></data-model>	This denotes the start and end of the mobiloan data model.
model	<model></model>	This indicates the start and end of a model. The name attribute will be the table reference you will use when querying or joining tables.
field	<field /> or <field></field>	This indicates a field for a model and will always be wrapped in a model tag. The name attribute will be the table reference you will use when querying fields or joining tables. The type attribute is also worth bearing in mind when deciding on how to filter your data using your WHERE clauses.
belongs-to	<belongs-to />	This is a relationship tag and represents how this object is related to other models. The relationship can be described as one to one which means an object can only be linked to another single object. For example if a transaction belongs to a client you can join the related client to the transaction using the client_id stored on the transaction table.

MODEL COMPLETENESS

For purposes of demonstration the above model does not include the index or display or has-many tags and related values as these are irrelevant to users when building your mySQL queries.