Migration from revio or Revi PS to pruvia
Last updated: · fastview ag, Suhr
Professionally responsible: Marco Zanetti and Reto Ackermann, fiduciaries and certified auditors, fastview ag
If you have documented your audits in revio so far, you can import the dossier export of a financial year as a PDF into pruvia. If you have worked with Revi PS or another program, you set up the engagements via the commercial register, record the prior years with opinion and report date, and import the previous year’s trial balance. This page describes both routes, what you then check yourself, and what pruvia costs.
From revio
Import the dossier export of a financial year (PDF): planning, ICS, controls, audit procedures with initials, notes and attachments.
Route 2From Revi PS or another program
Take over engagements per commercial register, file prior years with their dossier, import the previous year, audit the new year in pruvia.
In brief: migration from revio
- What is imported is the complete dossier export of a financial year as a PDF.
- pruvia reads the text of the file in your browser, without AI.
- You choose which areas are taken over; the takeover writes into the selected file.
- Imported list entries and texts (procedures, controls, risks, IT systems, open items, closing meeting points, ICS notes, assessments, derivation of materiality, engagement team) carry the marker “revio”; master data, type of audit, risk and audit approach per area as well as attachments do not. A repeated takeover replaces the marked entries instead of duplicating them.
- Financial years that were audited entirely in the legacy system are marked collectively as a transition year.
From revio: which file you need
pruvia expects the complete dossier export of a financial year as a PDF, i.e. the full documentation with all chapters (e.g. engagement basis, risk assessment, ICS, audit of the financial statements, notes, overview of attachments). pruvia recognises the file by the header with company, registered office and year and by the section codes. If this structure is missing, pruvia reports “No revio dossier detected” and takes over nothing.
Not suitable are the auditor’s report, the comprehensive report to the board of directors and individual working papers. How the export is created in the legacy system is described in its documentation.
What pruvia takes over from the revio dossier
Before the takeover, pruvia shows for each area how many entries were recognised in the file. Each area can be selected or deselected individually.
Master data and type of audit
Company, registered office and balance sheet date. The import sets the type of audit to “ordinary audit” – check it.
Trial balance for the reporting year and previous year
From the structured financial statements in the export, by item (not by account). The items are mapped to the chart of accounts by their description; you check the mapping in the data import.
Knowledge of the business
Main activity, legal structure, ownership, previous audits and engagement team. Only empty fields are filled; the texts are marked as drafts.
Materiality, risks, audit approach
Materiality as a manual value with documented derivation (basis, rate, performance materiality, clearly trivial threshold), risk and audit approach per audit area, and the risk register.
Fraud
The assessment texts on revenue recognition and earnings management as well as the risk indicators. You assess the presumption yourself.
ICS questionnaire and IT controls
Questions and answers per process, including the IT general controls, as a note on the matching ICS component.
Key controls
Into the control inventory with nature, type, frequency, responsible persons, documentation, IT system and risk. Tests of design and operating effectiveness remain open.
IT landscape
Systems and applications per financial reporting process into the IT environment (ISA-CH 315). You confirm audit relevance and outsourcing.
Audit procedures
With initials and date as own procedures (the assessment is set to “OK” and must be checked) in the assigned audit area, with the numbering of the legacy system. Also working papers such as engagement acceptance, external confirmations, stock-take and events after the balance sheet date, as well as the concluding assessment per audit field.
Close areas (optional)
Off by default. If selected, pruvia closes only those audit areas whose imported procedures are all initialled – intended for a year that is already completed.
Notes
As open items or as points for the closing meeting, with priority, initials and original date.
Attachments
Only files embedded in the PDF, placed in the assigned audit area where the overview of attachments names an assignment; otherwise without area. The log states how many of the attachments listed in the overview are missing from the export.
After the takeover, pruvia shows a log with the number per area and with warnings, for instance on audit fields without a matching audit area or on negative liability items that pruvia reclassifies to the asset side.
What you do yourself
- Check the trial balance: you verify the mapping of the items in the data import. The account details of the audit fields are in the imported procedures, not in the trial balance. For the following year, import the client’s trial balance as usual.
- Check the type of audit and the balance sheet date, especially for a limited statutory examination.
- Controls: tests of design and operating effectiveness are not part of the takeover.
- Procedures: the imported procedures remain own procedures and are not mapped to pruvia’s audit programme. Initials appear as abbreviations from the legacy system.
- Attachments that are not embedded in the PDF are filed separately.
- Auditor’s report of the prior year: is not taken over. You can file it with the rest of the dossier as a file under the prior year.
The takeover overwrites existing values of the selected file in master data (incl. type of audit), data import (trial balance), planning (materiality, risk and audit approach per area, fraud texts), ICS (remark, notes) and the analysis text per audit area. It is therefore best to take the dossier over into a file in which no work has been done yet.
Taking over a revio dossier: step by step
- Prepare the engagement and file. Create the engagement in pruvia if it does not yet exist, and select the file of the financial year documented in the dossier.
- Open the takeover. In the engagement’s master data, the card “Prior years & documentation” contains the button “Import dossier export …”.
- Choose the PDF. pruvia reads the file page by page in the browser and shows company, registered office, financial year, balance sheet date, number of pages and engagement team. If the year or company differs from the selected file, pruvia points this out.
- Select areas and confirm. You see the number of recognised entries per area, deselect what you do not need, and confirm the takeover into the displayed file.
- Read the log and check. Then check data import, planning, ICS, audit areas and open items. The imported list entries and texts carry the marker “revio”.
- Mark older years. For years audited entirely in the legacy system, use “Record transition year” (see below).
Switching from Revi PS
For Revi PS there is no dedicated takeover of the audit file in pruvia. The switch runs via the building blocks pruvia provides for every change of software; they apply equally to other programs. The previous dossier is kept as a file under the prior year.
- Take over engagements per commercial register. On the page “Engagements & responsibilities”, “Take over engagements per register” searches the SOGC for the name of your audit firm (by UID if one is stored) and checks for each company via Zefix whether you are registered there as auditor. pruvia creates the selected companies as engagements. You record individual engagements via the company search in the commercial register.
- Mark years audited in the legacy system. “Record transition year” marks, for one financial year, all engagements with an empty file collectively as audited in the legacy system, each with opinion and report date (see Transition year).
- File the dossier. In the engagement’s master data, the card “Prior years & documentation” lists opinion, report date and balance sheet date for each prior year. There you file the archived audit file as files (PDF, ZIP, Excel, up to 50 MB per file) and record since which financial year you have been the auditor.
- Record the previous year. For the first year in pruvia, import the previous year’s trial balance separately as Excel, CSV or PDF; as soon as its balance sheet balances, it serves as the comparative figures. Upload the previous year’s financial statements with the auditor’s report as a PDF, for reconciling the opening balance sheet.
- Audit the new year in pruvia. Importing the trial balance of the reporting year creates leadsheets and an audit programme per audit area; from this year on you document planning, ICS and audit procedures in pruvia.
pruvia does not read planning, audit procedures or ICS documentation from Revi PS. What is documented in the legacy system remains traceable there or as a filed document under the prior year. How to export data from the legacy system is described in its documentation. More on the first year and the first-time audit: Transition year and prior years when changing software.
Years audited in the legacy system: transition year
Under “Engagements & responsibilities”, “Record transition year …” marks in one step all engagements whose file is empty for a selected financial year (no import, no audit areas, no report) as audited in the legacy system. For each engagement you record the audit opinion (unqualified, qualified, adverse, disclaimer) and the report date; a date can be set for all rows without a date at once.
The engagement overview then shows “Completed · legacy system”, the opinion and the general meeting deadline based on the report date. You file the archived audit file – any files such as PDF, ZIP or Excel – per engagement and year in the card “Prior years & documentation”. More on this, including the first year in pruvia and the first-time audit: Transition year and prior years when changing software.
Price
Each additional audit engagement costs less the more engagements you manage. Examples per year, excl. VAT:
- 20 audit engagementsCHF 2'100
- 50 audit engagementsCHF 3'775
- 100 audit engagementsCHF 6'375
- 200 audit engagementsCHF 11'375
Orders in steps of 5, minimum purchase 10 audit engagements, purchase on invoice (payable within 30 days). For more than 1000 audit engagements, pruvia prepares an individual offer. The dossier takeover is part of the software and not a separate item in the price list. Calculate the price for your number of engagements.
Frequently asked questions
Can I switch from Revi PS to pruvia?
Yes. There is no dedicated takeover of the audit file from Revi PS. You take over the engagements per commercial register, mark the years audited in the legacy system as a transition year with opinion and report date, file the previous dossier as a file under the prior year, and import the previous year’s trial balance. You audit the new financial year in pruvia.
How do my engagements get into pruvia?
“Take over engagements per register” searches the SOGC for the name of your audit firm and checks for each company via Zefix whether you are registered as auditor; pruvia creates the selected companies as engagements. From a revio dossier, pruvia additionally takes over company, registered office and balance sheet date.
Can I continue to use my revio dossiers?
Yes. pruvia imports the complete dossier export of a financial year as a PDF into the file of that year: planning, ICS, controls, audit procedures with initials and date, notes and embedded attachments. In addition, you can file the original dossier as a file under the engagement’s prior year.
What does the migration cost?
There is no separate item in the price list for the dossier takeover; it is part of pruvia. The basic licence costs CHF 1'500 per year including 10 audit engagements; further audit engagements are charged at a decreasing price per engagement (e.g. 50 audit engagements CHF 3'775 per year, excl. VAT).
How long does the takeover take?
Reading runs in the browser page by page; the duration depends on the size of the PDF, and pruvia shows the progress. The real work lies in the checking afterwards, above all the mapping of the trial balance and the audit areas. How much time that takes depends on the engagement.
What happens to audits in progress?
You have two routes: complete the audit in the legacy system and mark the year in pruvia as a transition year, or take the dossier export of the current year over into the file and continue working in pruvia. Imported procedures keep their initials and date; their assessment is set to “OK” and must be checked; tests of design and operating effectiveness of the controls must then be documented in pruvia.
How do I handle years that were audited in the legacy system?
With “Record transition year” you mark, for one financial year, all engagements with an empty file collectively as audited in the legacy system, each with opinion and report date. The engagement overview shows these years as “Completed · legacy system” and calculates the general meeting deadline from the report date.
Are the account balances taken over?
pruvia builds the trial balance for the reporting year and previous year from the structured financial statements in the export, i.e. by item. The account details of the audit fields are in the imported audit procedures. For the following year, import the client’s trial balance as usual.
Can I repeat the takeover?
Yes. A repeated takeover replaces the previously imported procedures, controls, risks, IT systems, open items and closing meeting points carrying the marker “revio” instead of duplicating them. Trial balance and materiality are set anew.
Where is the data stored?
pruvia is operated on servers in Switzerland. The PDF is read in the browser, without AI; what is stored are the imported contents and, if selected, the embedded attachments. Details are set out in the privacy policy.
Try pruvia
The system tour shows pruvia with sample data, without registration. For questions about migrating from revio, Revi PS or another program, book an online demo or write to us.