How Provis automated XBRL reports for TitanRP, and is making its systems safer.
TitanRP is a London-based firm that handles technical reporting for companies. Its reports must follow a strict structure or the receiving system can reject them. Provis automated their generation in XBRL. It is also reviewing the infrastructure and databases for security issues, which is still under way.
- XBRL report generation
- Security review
Client: TitanRPTechnical and financial reporting, LondonReports are automated. The safety work is still going.
- XBRL reports
- Job A: done
- Reports are made automatically in the exact format the receiving system accepts, so fewer get rejected
- Security review
- Job B: still going
- Not finished. Provis starts from read access, and the client approves every change first
At a glance
- Problem
Reports had to follow strict structure and formatting rules, and an invalid report could be rejected. The existing infrastructure and databases also had security issues that needed to be put right.
- Solution
Automated generation of the reports in XBRL, and a review of the infrastructure and databases to improve security without disrupting the live system.
- Status
The XBRL work is done. The security work is ongoing and is not complete.
- Client
- TitanRP
- Industry
- Technical and financial reporting for companies
- Market
- London, United Kingdom
- Services
- Report automation, infrastructure and database security review
- Standard
- XBRL (eXtensible Business Reporting Language)
- Access
- Provis starts from read access. Every change is explained to the client and approved first.
Reports that have to be exactly right, on systems that cannot stop.
TitanRP is a London-based client that handles technical reporting requirements for companies. Its reports have to follow strict structural and formatting rules, and an invalid report can be rejected by the system that receives it. They are filed in XBRL, which stands for eXtensible Business Reporting Language, a standard for exchanging structured business and financial reporting information.
Its existing infrastructure and databases also had security issues. These needed to be put right, and the live system could not be disrupted while they were.
How a company report is usually prepared and filed
- Figures gatheredfrom the company's records
- Tagged by handeach figure matched to the standard
- Checkedone wrong tag can make the report invalid
- Filedthe receiving system accepts or rejects it
A typical flow for businesses like this, not a record of this client.
A valid report every time, and safer systems without a stop.
The two problems Provis took on, and where each stands.
-
Reports had to match a strict structure
The receiving system can reject a report that does not follow the required structure and formatting, so every report had to be right.
What Provis builtAutomated XBRL report generationProvis learned the client's reporting requirements and its existing process, then automated generating the reports in XBRL. The generated reports follow the structure and formatting that are expected. This work is done.
-
Security issues in a system that cannot stop
The client's existing infrastructure and databases had security issues, and the system had to keep running while they were fixed.
What Provis is doingA security review, without disruptionProvis is reviewing the current system and infrastructure, investigating the concerns, and improving security without unnecessarily disrupting what already works. It starts from read access. Before any change, it explains its findings to the client and waits for approval. This work is ongoing, not finished.
Two workstreams: one finished, one still running.
- Workstream A: XBRL reports (done)Learn the client's requirements and process, then automate report generation in the required structure
- Workstream B: infrastructure and security (ongoing)Review the system, investigate the concerns, and improve security without disrupting it
-
Reports: generated in XBRL, in the structure and formatting the receiving system expects.
-
Review: the current system, the infrastructure and the databases, looking at the security concerns.
-
Access: read access to start with. Provis explains each change to the client and gets approval first.
How the security work runs:
Nothing changes until the client says yes.
Provis reads the system, explains what it found and what it understands, and only then makes a change. The aim is better security without unnecessarily disrupting a system that is in use.
Read access first; every change is explained and approved by the client.
Ongoing: this workstream is not complete.
How Provis builds software platformsWhat an XBRL report looks like on the way out.
Illustrative screens, designed in TitanRP's style (a mobile view of the tool); the real tool is private. The companies and figures shown are made up. Select one to enlarge it.
-
The filing listEvery report and its status
-
Match figures to tagsMost lines matched for you
-
Validation resultsPasses, warnings and errors
-
Preview the reportFigures and tags together
-
Ready to submitChecks passed, one step left
Reports automated. Security work still going.
The XBRL work is done. The infrastructure and security work is ongoing, and it is not complete.
After launch
Still working with the client.
Provis works on the security review from read access, and brings every change to the client for approval first.
The concerns under review sit in the client's existing infrastructure and databases, which must keep running throughout.
Provis has delivered 200+ projects since 2012, with a team of 25+ engineers, designers, QA and project leads.
Every Provis build comes with 24/7 monitoring and support after launch.
How every Provis project runs
- One project leadyour single point of contact
- A written weekly update and a demoof what was built that week
- A staging link and your repoyou see the work as it is built; the code goes straight into your repo
- QA before launchour QA team tests every feature
- Yours from day onecode repo, cloud account and domain in your company's name; our team joins as collaborators, and you can remove access at any time
- Our team works in India, on ISTUTC+5:30: 1.5 hours ahead of Dubai, 4.5 ahead of London (5.5 in winter), 9.5 ahead of New York (10.5 in winter)
Need reports in a strict format, or systems made safer?
Tell us what has to be generated or secured, and what cannot be allowed to stop. We will come back within two working days with an approach, a rough timeline and a rough cost range. No charge, no commitment.
WhatsApp usSend us a message
indicates a required field