XBRL is not that hard. We offer a cloud-based, simple, fast and highly price competitive XBRL engine that can be explained in 4 simple steps:
Step 1: Extracting data from your report
Step 2: Converting data to an XBRLfile
Step 3: Validating an XBRL file
Step 4: Visualizing an XBRL file – making it readable again
…All with our turbocharged XBRL engine in the center.
Please click on a step and choose your step of interest – or click the center to learn more about how advanced users communicate directly with our engine through our XBRL API!
So you have a report in e.g. Excel, Word, PDF or similar that you want converted to XBRL? In step 1 we extract all the data-“bricks” needed and prepare it for XBRL conversion in step 2.
Input: Excel, Word, PDF, InDesign etc.
Output: JSON (typically for use in step 2)
So you have the data-“bricks” available – either from your own data source or extracted from step 1? In step 2 we convert your data to XBRL, which is basically a matter of aligning your “bricks” in a specific order.
Input: JSON, XML, CSV, SQL etc.
So you have an XBRL file that you now need validated against the taxonomy validations and XBRL filing rules to see if it is compliant? In step 3, we do just that at high speed and return a validation report.
Output: Validation report
So you have an XBRL file that you can’t make sense of by just opening it in a Notepad editor – but need to review the data-“bricks” in it either for auditing or for import into your own system? In step 4, we render the XBRL file into a format that you can read, use and understand – and it even allows you to “walk the wheel” again and re-convert an edited file back to XBRL.
Output: HTML, JSON, Excel, iXBRL etc.
So you are a system builder or maybe a bank or insurance company who needs one or more steps from our XBRL wheel? Our engine is the key to all 4 steps, and we can integrate one or more steps directly into your own system by using our simple, but yet powerful XBRL API.