A detailed explanation of the key screens/tabs you will come across when creating reports in Workbooks.
- Welcome to the Knowledge Base
- Introduction
- Training
- Desktop Environment
- Preferences
- Activities
- Cases
- Forecasts & Quotas
- Importing Data
- Leads
-
Marketing
- Introduction to Marketing
- Marketing Campaigns
- Mailing Lists
- Products
- Mailshots
- Upload Library
- Templates
-
Workbooks Web Insights
- Tracking Code
- Setting up the Plugin
- Viewing Web Insights Data on your Form Layouts
- Domain Names and Online Activities
- Gator Popup
- Reporting incorrect Leads created through Web Insights
- Reporting on Web Insights data
- Using UTM Values
- Why aren’t Online Activities being created in the database?
- Why is GatorLeads recording online activities in a foreign language?
- Using HubSpot with Workbooks
- Event Management
- Compliance Records
- GatorMail Integration
- Opportunities
-
Integrations
- Mapping
-
Electronic Signing Tools
-
Docusign Integration
- DocuSign Functionality
- Setting up the DocuSign Integration
-
DocuSign - Worked Examples
- DocuSign Example - Taking Payments
- DocuSign Example - Updating Related Records
- Docusign Example - Multiple Document Sends
- DocuSign Example - Creating a Template for Cases
- DocuSign Example - Creating a Template for Organisations
- DocuSign Example - Creating a Template for People
- DocuSign Example - Unified PDF
- DocuSign - Reporting
- Adobe Sign Integration
-
Docusign Integration
- Creditsafe Integration
-
Zapier
- Introduction to Zapier
- Available Triggers and Actions
- Linking your Workbooks Account to Zapier
-
Setting up Zaps
- Posted Invoices to Xero Invoices
- Xero payments to Workbooks Tasks
- New Case to Google Drive folder
- New Case to Basecamp Project
- New Workbooks Case to JIRA Ticket
- Jira Issue to new Case
- 123FormBuilder Form Entry to Case
- Eventbrite Attendee to Sales Lead and Task
- Facebook Ad Leads to Sales Leads
- Wufoo Form Entry to Sales Lead
- Posted Credit Note to Task
- Survey Monkey responses to Tasks
- Multistep Zaps
- Outlook Integrations
- People & Organisations
- Reporting
- Dashboards
- Transaction Documents
- Auditing
-
Configuration
- Introduction to System Administration
- Users & Security
- Database
- Accounting
- Email & Integration
- Customisation
- Automation
- PDF Configuration
- Contact Support
- Releases & Roadmap
- Workbooks Glossary
Reporting with multiple currencies
Reporting with multiple currencies
Workbooks warns you when a report calculates a value across more than one currency by displaying "Multi-currency" in the cell. This can occur when the report is first defined, or later when the records contain values in more than one currency. There are a variety of solutions to this problem.
Summarising financial transactions
Workbooks financial transactions are defined in a "document currency": the currency that all of the line items are declared in and that the customer pays in, or that the supplier is paid in. Transactions also have a "home currency" that the line item values are converted to, so that you can estimate the value of the transactions in your own currency. For many companies this simple distinction means that you can easily report on the home currency values to ensure that you calculate values in one consistent currency.
The home currency is attached to an Own Organisation - the Own Organisation operates in that currency for tax purposes. You may have more than one Own Organisation, for example one for each currency zone in which you are recognising revenue. If you have multiple Own Organisations, then you likely have multiple currencies and will need to ensure that your reports are designed with that in mind.
Wholly independent subsidiaries in each tax jurisdiction can be represented by Own Organisations, and so employees in each location may create their own reports to analyse transactions in their Own Organisation. Because these reports will have criteria to restrict the set of transactions to those in the Own Organisation, all of the transactions will have the same home currency, thus ensuring that the calculations are valid.
If you wish to create reports that combine transactions across multiple currencies in one report, then you must make sure that you separate the values by currency. For example you can group by the home currency of the transactions to produce separated totals.
Summarising other currency values
Currency values in records other than transaction documents and custom field currency values are not forced to a particular currency. To create reports on these currency fields you must decide on a convention that controls the currencies of these values to ensure that they can be combined in reports later.
Where the user can choose a currency for a field, Workbooks only offers a choice of the currencies defined on the Own Organisations in the database. So, for a single-currency database this issue is avoided very simply: the user can only choose that one currency.
In a database with multiple currencies you must train your users to choose a currency according to your business needs. For a custom field currency value on a transaction document or a line item we would recommend that it should hold a value in the document currency because the user will probably know or be able to calculate it easily.