From documents to usable records
Could differences in document layouts create repeated interpretation or manual-entry work? Which formats and exceptions would matter most?
Independent foundations. Possible collaboration.
A clearer investment picture. Room to collaborate.
Struct Capital is currently independent investment portfolio management software for investors in Rwanda. Its document and portfolio technology may become a foundation for carefully scoped institutional collaboration.
Investor usefulness comes first.
Investors can organize supported records through manual entry and document imports without a broker partnership. That independent path must remain useful whether or not an institution chooses to collaborate.
Understand the independent workflowCurrent positioning
Struct Capital is not a broker, exchange or custodian. It does not execute trades or hold investment funds.
No broker partnership, institutional client or commercial integration is asserted on this page. The opportunities below are exploratory, not available institutional products.
Explore possible collaboration modelsQuestions to validate
Start with the work, not an assumed solution.
These are hypotheses for discussion, not findings from verified customer research. A useful collaboration would begin by learning where, if anywhere, the real friction lies.
From separate records to a clear account
Could comparing transaction records and statements reveal a useful reconciliation problem? What would staff need to review before trusting a result?
From information to explanation
Could clearer portfolio reports help answer recurring investor questions? What evidence would show a meaningful improvement?
Present in the investor app
Existing technology. A starting point to evaluate.
Import, recordkeeping and report-generation implementations provide concrete foundations to examine.
Their presence in source code does not establish public release availability, parser accuracy across formats, production readiness for institutions or service-level commitments.
See the investor application’s featuresSupported PDF import and review
The investor application has document-import orchestration and extracted-data review before saving. This is a starting point for investigation, not proof of every issuer’s format or institutional-scale processing.
Investment records and schedules
Bond and share entry, transaction history, and coupon/maturity schedule views exist in the app. They organize investor records; they do not administer an institution’s bond allocations or settle transactions.
Portfolio and annual reports
Portfolio and annual PDF report generation exist in the app. These reporting foundations are not an institutional reporting service, regulatory filing product or assurance of audited results.
Potential future models · Not current products
A defined problem. An agreed scope.
These are possible ways to collaborate if demand, feasibility and appropriate agreements are established. They are not a service catalog, pilot commitment or delivery promise.
A document-workflow pilot
Potential financial document processing, client statement interpretation and investment transaction reconciliation for a narrowly defined workflow. Begin with permission-cleared examples and agreed review criteria.
A reporting or investor-software project
Potential portfolio reporting, bond allocation administration or investor-facing software shaped around a validated institutional need. Each would require its own product scope and readiness assessment.
An authorized integration
Potential account synchronization, institutional APIs or broker-specific integrations only where the institution agrees and the customer gives appropriate authorization. No direct account connection is offered today.
Principles for any future collaboration
Define permission before access.
These are requirements to establish before an integration or pilot, not a claim that institutional controls or legal approvals already exist.
- Explicit purpose and authorization
- Agree what the work is for, who may provide the data, and the applicable legal basis. Any future account connection would require institutional agreement and appropriate customer authorization, with a clear scope and revocation process.
- Limited data and access
- Define necessary fields, permitted recipients, access boundaries, retention, deletion and processing locations before any customer-data exchange. Start evaluation with synthetic or properly anonymized, permission-cleared material.
- Reviewable results
- Agree how people would check extracted records, handle exceptions and correct errors. Evaluate accuracy against the particular formats and workflow rather than assuming every statement or PDF is compatible.
- Dedicated readiness review
- Assess security, privacy, operational responsibilities and applicable requirements with the appropriate reviewers before a pilot. No security certification, blanket encryption promise or regulatory approval is claimed here.
Collaboration is optional. Independence is foundational.
A broker may choose not to collaborate. Investors must still be able to use the supported manual-entry and document-import workflows without changing brokers or waiting for an agreement.
Uploading a broker-issued PDF does not create a partnership, connect a brokerage account or grant access to a broker’s customer database. Document-format support and a commercial relationship are separate things. Unsupported PDFs may require an available manual workflow.
Read the broker-independence FAQDirection, not a delivery schedule
Progress depends on evidence.
Institutional opportunities are optional future paths. There are no promised launch dates or automatic steps into brokerage or trading.
01 · Current focus
Strengthen independent investor tools
Prioritize record clarity, reliable imports, understandable reports and investor feedback. Public-release readiness is a separate gate.
02 · Potential next step
Validate a specific institutional need
Establish the problem and willingness to pursue a scoped pilot. Proceed only with agreed evaluation criteria, responsibilities and readiness reviews.
03 · Only if justified
Consider a repeatable service
Evaluate reporting, processing or authorized integrations only with demonstrated demand, appropriate agreements and support capacity. Preserve the independent investor workflow.
Bring a workflow worth understanding.
Describe a potential collaboration in general terms: the document or reporting task, where review is needed, and what a useful outcome would mean. An inquiry creates no partnership or service commitment.
Choose “Institutional inquiry” on the contact page. Do not send customer records, investment PDFs, credentials or confidential commercial information.
Website inquiry delivery is not available yet. The contact page explains the current limitation; no message can be sent at this time.