Microsoft SQL Server 2022 Reporting Services
SQL Server Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality.
Important! Selecting a language below will dynamically change the complete page content to that language.
- Paginated reports optimized for document generation and printing.
- A modern web portal you can view in any modern web browser.
Supported Operating Systems
Windows Server 2019, Windows Server 2016, Windows 10, Windows 11, Windows Server 2022
- .NET Framework 4.8 or later
- SQL Server Database Engine (2014 SP3 or later), to store the report server database
- Download the Evaluation Edition of Microsoft SQL Server
- Install SQL Server Reporting Services (SQLServerReportingServices.exe)
- Configure your report server using Report Server Configuration Manager
SSRS Install, Setup and Configuration
By: Joe Gavin | Comments (6) | Related: > Reporting Services Installation
SQL Server Reporting Services (SSRS) is another one of the major components of the Microsoft Business Intelligence (MSBI) stack. It's used to generate interactive and automated reports.
The SSRS installation used to be part of the SQL Server installer up through SQL Server 2016. As of SQL Server 2017, the installation has been moved to its own separate downloadable installer. It is still not overly complicated, but it is helpful to know where to get the installer and what to expect before you go through the installation process. This tip will show you how to obtain the installer and walk through the various screens and options that are part of the installation process for SSRS.
We'll walk through each of the steps of a new installation of SSRS 2019 on Windows Server 2019.
SSRS Minimum Hardware and Software Requirements
You'll likely have a lot more disk and memory than this, but the bare minimum hardware and software required to install SQL Server 2019 are:
- Windows Server 2016 or Windows 10 TH1 1507
- 6 GB of available hard disk space
- 4 GB memory
- 1.4 GHz minimum 64-bit CPU
And to install SSRS, you will need an already installed SQL Server.
SSRS 2019 Install
Obtain and run the ssrs installer.
Download the installer from the Microsoft Download Center here: Microsoft SQL Server 2019 Reporting Services .
Run the SQLServerReportingServices.exe executable when the download is complete, and the first screen will open.
- Click on 'Install Reporting Services'
Product key id required for a paid edition.
- Select 'Enter the product key' radio button and enter your product key
You will need to agree to the license terms.
- Click 'I accept the license terms' checkbox
You will be reminded an installed SQL Server is required to configure the SSRS server and are presented with one option to install Reporting Services.
This is where you will need to change the SSRS installation directory from the default on the C:\ drive.
- Configure SSRS install directory
At this point Reporting Services is installed and it's time to do some basic configuration to it before we can do anything.
- 'Configure report server' to open the Configuration Manager
Reporting Services Configuration Manager program opens, and we will see the machine name and instance will automatically populate. The first step is to connect to the SSRS server.
Best practice is to not use the default account to run any of the SQL Server services. This discussion is somewhat out of scope for this tip but Microsoft Docs has more information on configuring Windows service accounts for SQL Server here: Configure Windows Service Accounts and Permissions
- 'Service Account'
- Configure service account
Report Server Databases
The Report Server Database screen is where we create the databases ReportServer and ReportServerTempDB.
- 'Change Database'
We are creating a fresh installation of SSRS, so we leave the 'Create a new report server database.' radio button selected. Note: You would just select the 'Choose an existing report server database' button to point Reporting Services to an existing set of databases.
Verify Connectivity to SQL Server
It's a good idea to verify that we can successfully connect to the SQL Server with our credentials here before attempting the database creations.
- 'Test connection'
Continue if Test Connection was successful.
We can now verify our information is correct before proceeding with the database creations.
- Review Summary
Verify Successful Completion
We want to see that each step was successful.
- Verify all steps show Success
Now that we have our databases created it's time to create the SSRS web service. First, we create the Web Service URL.
- 'Web Service URL'
Next, we create the Web Portal URL.
- Web Portal URL
Then SSRS will restart.
Very URL Creation
Time to verify we can connect to both URLs.
- Click 'Web Service URL'
- Click on URL
We expect to see the default browser open to Report Server screen.
Now, we'll check the Web Portal URL.
- 'Web Portal URL'
We expect to see the default browser open to the Reporting Services Screen.
We now have a fully functional SSRS installation that is ready to deploy reports to. Following are some optional settings we can also configure.
- E-mail Settings
If you will have automated report subscriptions going to email, you will need to configure the email settings.
- Enter 'Sender Address' (This doesn't have to be a valid email address on your mail system but it does have to be in the format [email protected] or the SMTP server will reject it.)
- Enter your SMTP server name
- Expand dropdown and choose 'Username and password (Basic)' to enter SMTP credentials if required
- Choose 'Report server service account (NLTM)' to use service account to authenticate
Troubleshooting tip: If you experience any problems getting email working, Microsoft Docs has this very handy guide to troubleshooting SMTP issues using Telnet: Use Telnet to Test SMTP Communication on Exchange Servers . Even though it says Exchange, it's applicable to any SMTP server. It's a little awkward to use at first but a great way to very simply verify you can get through a firewall, and test sender address, etc.
- Subscription Settings
If you are automating reports to go to a file on a file share you can enter the credentials in the Subscription Settings tab.
- Check off 'Specify a file share account'
- Enter Windows account in the form DOMAIN\account
- Enter password
- Confirm password
Close Configuration Manager
- Now that we have a working installation of SSRS, you can find a wealth of further information here: SQL Server Reporting Services Administration Tips
About the author
Comments For This Article
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Start and stop the report server service
- 11 contributors
A report server is implemented as a Windows service that contains the Report Server web service, the web portal, and a background processing application. The service must be running if you want to use any report server functionality. Stopping the service stops all report server operations.
While the service is stopped, requests for scheduled report and subscription processing that would have occurred had the service been running are added to the queue. This is because jobs that are run by SQL Server Agent create the events. If you want to avoid a backlog of operations while the service is off, consider stopping SQL Server Agent as well.
You can use a variety of tools to start or stop the Report Server service, including the Reporting Services Configuration tool, SQL Server Configuration Manager, and the Services tool provided in Microsoft Windows.
SQL Server Configuration Manager is only an option for SQL Server Reporting Services 2016 and earlier. It does not include Reporting Services 2017 and later or Power BI Report Server.
If you're doing more than starting or stopping the service, such as changing the service account, you must use the Reporting Services Configuration tool. Using other tools to change the service account can break your Reporting Services installation and encryption key. For more information, see Configure the Report Server Service Account (Report Server Configuration Manager) .
You can't pause and resume the service. There aren't start parameters. Although there are no explicit dependencies, SQL Server Agent must be running if you support any subscriptions or scheduled report operations on the report server.
Use the Reporting Services Configuration tool
Start Reporting Services Configuration tool and connect to the report server.
On the Report Server Status page, select Stop or Start .
Use Administrative Tools
- In Administrative Tools, open Services .
- Right-click SQL Server Reporting Services (MSSQLSERVER) , SQL Server Reporting Services , or Power BI Report Server .
- Select Stop or Restart .
For Reporting Services 2016 and earlier versions, if you are running multiple instances or if the report server is running as a named instance, verify that the instance name in parentheses corresponds to the report server instance you want to stop or restart.
Report Server Configuration Manager (Native Mode) Start, Stop, or Pause the SQL Server Agent Service
Was this page helpful?
Submit and view feedback for
25 April 2014
SQL Server Reporting Services Basics: Building SSRS Reports
SQL Server Reporting Services is one of the most popular components of SQL Server, but it has always been surprisingly difficult to get from one place all the basic facts you need to get up and running from scratch, to the point of producing reports. Here Kathi Kellenberger quickly describes the basics of SSRS before showing how to build quick, simple reports.
SQL Server Reporting Services (SSRS) is a server-based reporting platform that allows us to create and manage a wide variety of different types of report, and deliver them in a range of formats. We can create basic reports containing tables and graphs, or more complex data visualizations, using charts, maps and sparklines. Our reports can draw their data from SQL Server databases, but also from other relational database such as Oracle, and other types of multi-dimensional or XML-based data sources such as SQL Server Analysis Services, Teradata, or Parallel Data Warehouse.
We can present our finished reports directly from the Reporting Services website, called Report Manager , or users can view them directly within their web- or Windows-based applications. End users can run reports on demand or schedule them as subscriptions. We can also install SSRS so that the reports run from SharePoint. This article is the first in a series that will provide in-depth coverage of the basics of report development with SSRS:
- Building SSRS Reports (this article) – covers the basics of SSRS, demonstrates how to build quick, simple reports, and will familiarize you with the basic Report Designer environment
- Customizing SSRS Reports (Part 2) – covers use of custom and aggregate functions, sub-reporting, the matrix control, drill-downs, and sorting.
- SSRS Visual Controls (Part 3) will take an in-depth look at the SSRS visual controls, notably the chart control.
- Deploying SSRS Reports (Part 4) walks you through deploying reports and the Report Builder tool
The report development examples in this series will work for SSRS 2008 R2 through 2012. Most of the examples will also work for 2008, and any I’ll call out any exceptions. If you are still using SQL Server 2005, please refer to Steve Joubert’s original SSRS series , upon which the example in this series are based.
SSRS through the ages
SSRS has been around for over 10 years, first shipping as an “add-on” for SQL Server 2000, and then fully integrated into SQL Server 2005. I first saw it demonstrated at the 2003 PASS Summit, and had the Beta version installed and running within a couple of days of getting back to work. Back in 2003, SSRS caused great excitement as it made available, for the first time, built-in reporting capabilities for SQL Server. If you owned SQL Server, you owned SSRS.
Since its integration into SQL Server 2005, Microsoft has made a number of improvements and added many new features. It had a big overhaul in 2008 and acquired a bunch of new features with 2008 R2 including:
- The tablix data region which allows us to convert a report area from a table to a matrix and back again
- Enhanced chart, and new gauge, data regions (thanks to the Dundas acquisition)
- Complete redesign of the Report Designer including a new Grouping Pane
- Formatting of text elements, not just at the textbox level
- Performance enhancements
- 2008 R2: KPIs, maps, sparklines, new functions, published Report Parts, and more
Since then, the basic features of the standard SSRS reporting tool haven’t changed. However, with SSRS 2012, Microsoft added Power View , providing a new way to create reports and geared towards business users. Power View is part of SSRS when installed in SharePoint integrated mode or as an add-in for Excel 2013. SQL Server 2014 was recently released, and there were no developer feature enhancements with this release.
This series of articles focuses on the development of reports. Keep in mind that SSRS can be deployed to SharePoint, but this series of article only covers the native deployment architecture.
An SSRS deployment must be associated with a SQL Server instance. On the instance will be two databases, by default:
- ReportServer – contains the report definitions, configuration, history, security of deployed reports and more
- ReportServerTempdb – much like tempdb , it is used as a workspace for building reports and doesn’t maintain any objects permanently.
We will also need a location for the Report Server Web Service , which can be on the same server as the databases, as in the simple deployment architecture shown in Figure 1, or on a different server. On whichever server we choose, we will have access to a Report Manager website that allows us to deploy and manage the reports. End users can run reports from Report Manager, create subscriptions, and publish their own reports if they have permission.
The end user sends an HTTP request for a report, providing any required parameters. The SSRS server finds the metadata of the report and sends a request for data to the data sources. The data returned by the data sources is merged with the report definition into a report. As the report is generated, it is returned to the client.
Installing and Configuring Reporting Services
There are many ways to design a Reporting Services deployment for your department or company, with SharePoint integrated mode gaining popularity. However, since this series is focused on report development, it will cover native mode only, and just enough about installation and configuration to help you get things set up on your development computer.
To follow along with this series of articles, you will need to install the development tool and set up the SSRS services. If the SQL Server media is not available, you can download an evaluation copy of SQL Server 2014 .
When running the SSRS installation, you will need to install the Database Engine and SQL Server Reporting Services in Native mode. It is easier to install both services at one time, because you can choose to have the installation process configure the SSRS services for you. If SSRS is installed later, or if you select not to configure it at installation, you will have to configure it manually. During installation, be sure to select these features:
- Database Engine
- SQL Server Reporting Services – Native (if installing 2008 R2, you’ll be asked on a subsequent screen to select the mode)
- Management Tools – Basic
- Management Tools – Complete
- Business Intelligence Development Tools or SQL Server Data Tools if available with the media you are using, which is dependent on the version
If given the choice, select Install and Configure .
SSRS Development Tools
Early versions of SQL Server used Business Intelligence Development Studio (BIDS) as the SSRS development tool. However, starting with SQL Server 2012, you will use SQL Server Data Tools – Business Intelligence (SSDT-BI), which may or may not be on the SQL Server media, depending on the version. Each tool runs as an add-in for Visual Studio. If you do not have Visual Studio in place, the BIDS or SSDT-BI installation will install a Visual Studio shell.
Just to add a little confusion, there is also an add-in called SQL Server Data Tools for Visual Studio 2012 . This is for database projects, not the BI tools that will allow you to create SSRS projects. It is not the option you want for SSRS development. You will also often see SSDT-BI abbreviated simply as SSDT.
The following table should help you navigate the options, understand the differences, and find the correct process for installing the development tool for your version of SQL Server.
If you were unable to let the installation process configure SSRS for you, or are installing SSRS after the initial engine installation, or maybe you decided to configure SSRS on your own for fun, you will need to launch the Reporting Services Configuration Manager .
As discussed, we need to associate SSRS with a SQL Server instance, where it can create the reporting databases ( ReportServer and ReportSereverTempdb ). When prompted, select the instance name and click Connect .
On the next screen, select the Database page on the left menu and click Change Database .
Select Create a new report server database and click Next . Enter the name of the SQL Server instance where you wish to create the reporting databases and click Next .
On the following screen, we configure the report databases. We can choose a different name from the default of ReportServer , if desired, but only do so if you have a good reason such as multiple instances of Reporting Services on the same server.
Continue clicking though the wizard and complete it. Once done, we need to configure the Report Server Web Service, so click the Web Service URL link.
Accept the defaults and click Apply . Finally, we need to configure Report Manager, so click the Report Manager URL link. Again, accept the defaults and click Apply .
Click Exit to dismiss the Reporting Services Configuration Manager.
Creating Basic Reports
Now that we’re all set up, it’s time to start building our first report. We’re going to build a report based on a ReportingDemo database. If you want to follow along, building the example report from scratch then you’ll need to create the database using the ReportingDemoDatabaseScript.sql script or, alternatively, by restoring the ReportingDemo.bak file, both of which you will find in the code file for this article (see the Code Download link at the end of the article ).
Alternatively, the download bundle also contains a copy of the completed SSRS project, FirstProject .
Using the Report Wizard
There are two ways to create SSRS projects within SSDT-BI. We can build the project manually, or we can get a kick start with the Report Wizard. Within the project we can create one or more reports. For example, we might have one project for all of the reports against a particular database, but that is not a requirement.
With the wizard, we can create only a relatively simple report, with one table or matrix data region containing text only.
Generally, the reports we create through the wizard won’t meet any but the most basic development requirements, but do not discount it entirely. It will allow us to get a report up and running with zero code and zero property setting, and the resulting report often makes a starting point for more complicated reports. Once we’ve created a report with the Report Wizard, we are free to modify it further as we wish, just as for a report we create from scratch, manually.
Our very first report project, FirstProject , demonstrates how to create a report with grouping levels including one of the dynamic features, collapsing and expanding sections. The report is essentially just a list of customers that we’ll group by state. The end result is not perfect, but it is a good start.
Open SSDT-BI and create a new project. Select the Report Server Project Wizard type. This will open up the New Project dialog. Create a new Reporting Services project called FirstProject . Click OK to start up the new report wizard. We can also kick off the wizard from within an existing project by right-clicking the Reports folder in Solution Explorer and selecting Add New Report .
The first dialog of note is Select the Data Source . Since this is our first data source, our only option is to create a new one.
Embedded versus Shared Data Sources
For the sake of this example, we will just create a new, embedded data source, which will be available only to the report in which it is embedded. However, a shared database source is available to all reports within a project, and once deployed, to any deployed report, from any project. If an existing shared data source exists, we should use it, and we have the option on this screen to make the current data source a shared data source. We’re going to set up a shared data source later in this article.
Select the New data source radio button and give the data source a name, usually referring to the database name, so in this case ReportingDemo . Leave the data source type as the default ( Microsoft SQL Server ).
Click the Edit button to bring up the Connection Properties dialog. Enter the name of the SQL Server instance hosting the data source, in this case the ReportingDemo database. The default option is to log on using Windows Authentication. If you are using SQL Server Authentication, choose that setting, and enter the username and password. Finally, select ReportingDemo and make sure you test the connection before you click OK .
Next up is the Design the Query screen. We can use the Query Builder by clicking the button at the top left but, in this case, simply enter SELECT * FROM Customer; into the Query string text box and click Next .
On the Select the Report Type dialog, we can choose between a tabular or matrix report. A tabular report is a traditional grid with column headings and rows of data, and it might contain grouping sections at the row level. A matrix report is like a pivot table. It can have column headings that expand across the top of the report. It can have grouping sections at the row and column levels. We’re going to start with a simple tabular report so choose Tabular and hit Next .
This brings up the Design the Table screen, where we specify what customer data we wish to include in our report, and how we wish to group it. Essentially, we need to specify how we will use each field (column) in the report. We might display some fields at the top of each page, use others for grouping, and others will form the detail level of the report.
In this case, we simply want to group the customer data by state, so select State in the Available fields box and click the Group button. If you group by more than one field, then make sure the fields are ordered (use the Up and Down arrows) to reflect the grouping level hierarchy you wish to see in the report. For example, State would be higher than City.
Add the other fields to the Details box.
On the Choose the Table Layout page, we have the choice of Stepped or Block . I don’t see a lot of difference between these layouts. After some experimentation, I found that the Stepped report had a row dedicated to the group label and that row was formatted with a background color. The Block report shows the group label on the first row of the detail and no special background. With the Block report, we do not have the option for drilldowns.
Select the Stepped option and check the Enable Drilldown checkbox, which will allow us to collapse and expand the data by state (the grouping column)
On the next screen, choose a style for your report (I chose Ocean).
The Choose the Deployment Location screen allows us to specify the Report Server to which we wish to deploy the reports in the project. For now, we will be working within SSDT-BI and not deploying the reports to the server, so we can just accept the defaults. When we are ready to deploy the reports, we can revisit these settings by right-clicking the project name and selecting Properties .
This brings up the final screen, Completing the Wizard , which simply summarizes our chosen report options, and lets us name the report and preview it. Name the report ReportWZ and click Finish to end the wizard.
After the wizard completes, we will see the report in the Design tab of the standard Report Designer.
Click on the Preview tab to view the report. The Preview tab allows us to run the report from SSDT-BI, without having to publish it first to the Report Server. If the report takes parameters, the Preview tab will ask us to fill them out before it runs the report. Since this report doesn’t take any arguments, it will display immediately.
Use the +/- symbols next to the State abbreviations to expand and collapse the grouping of the report.
Manual report creation
Whilst the FirstReportWZ report is simplistic, it does demonstrate how quickly we can generate reports using the Wizard, which is often useful for prototyping.
In this section, we are going to create another simple, but more realistic, report from scratch. It will demonstrate how to create and use a shared data source object, stored procedures, and how to format the report, set report properties and use report parameters.
Create a shared data source
A shared data source is a data source that is common to, and can be used by, all of the reports in the project. Once the shared data source is published to the report server, any published reports can use it.
In the previous section, we created a Report ing Demo data source that is embedded in the ReportWZ report, and so is available only to that report. However, generally, it is a bad practice to use embedded data sources. Let’s say we have 20 reports that access the ReportingDemo database, but a few months later some aspect of the connection information changes (such as the login credentials, or server name). We’ll have to open all twenty reports and edit the connection information appropriately. It is much better to define a single shared data source that all reports that need the ReportingDemo database can use.
Likewise, let’s say that our organization has deployed three SSRS sites: Development , Test and Production . If we embed the connection information in the report, we will have to change the data source properties each time we publish the report to Development, Test or Production. If we use a shared data source, the data source will be configured appropriately on each of three sites. We can configure a data source on each site with the same name but pointing to the appropriate servers. We can simply publish the reports to each site, and the reports will automatically use the connection information associated with that environment.
We can find in SSDT-BI’s Solution Explorer all the reports and other project-level objects. To add a new shared data source to the project, right-click on the Shared Data Source s folder and select Add New Data Source and then simply create a ReportingDemo data source exactly as described in the previous section. It’s not possible to edit the existing embedded data source to make it a shared one. We have to define it as a shared data source upon creation.
Add a new report
We’re now going to create another report to return customer information. In the previous example, we used a simple SELECT * query to define the data set for the report. Here, we’ll use a stored procedure. In this first example, we’ll use a basic stored procedure with no parameters, but later we’ll refine it to add parameters, and allow end users to filter the report data by parameter value (e.g. to view customers only from a particular state).
When creating a new report manually, we must always follow this sequence of steps before we can begin to add data-connected objects:
- Add the report
- Create a data source in the report, preferably pointing to a shared data source
- Create a dataset that points to the data source and contains your query
First we add the report to the project. From the menu select Project | Add New Item (or right-click on FirstProject in solution explorer). Select Report , name it FirstR eportMan.rdl and click Add . The new report will open up in Report Designer tool, at the Design tab.
Second, we define the database for the FirstReportMan report. On the left, you will see the Report Data window, used to manage the data sources, datasets and parameters of our report. At the top of the Report Data window, choose New | Data Source… from the dropdown list, which will open the Data Source Properties window, where we can either create a new embedded data source or point to a shared data source. We’ll change the name of the data source to ReportingDemo and select the Use shared data source reference option, selecting the ReportingDemo shared data source from the dropdown list.
Third, we create the Dataset . While the data source is the connection string, the dataset is the query definition. In this example, our dataset is a very simple, parameter-less stored procedure called spr_CustomerSelectAll and all it does is select all of the columns from the Customer table. The ReportingDemoDatabaseScript.sql script, in the code download, includes the code to create the stored procedure.
From the Report Data menu, choose New | Data Set… to open the Dataset Properties dialog. We can create a shared dataset or a dataset embedded in the report. Most of the time, the dataset will be embedded in the report. There are some exceptions to this, for example, when we have a parameter list we use in multiple reports. Name the dataset Customers and choose to embed the dataset in the report. Select the ReportinDemo data source from the dropdown. Select StoredProcedure as the command type, and choose spr_CustomerSelectAll in the stored procedure list.
We can repeat these steps to add multiple datasets to the report, but for now we only need the one.
Designing the report
As we’ve noted previously, at the top of the Report Designer window are two tabs: Design and Preview . The Design tab is the physical Report Designer where we design the report i.e. set up the data presentation of the report itself, plus any header and footer for the report pages.
Design the Report table
Let’s start by designing the basic report table. Click to Design tab of our FirstReportMan report. We’re going to build a tabular report, so we start by dragging a Table control from the Toolbox window, onto the body of the report. By default, the table shows a header row at the top, and a data (or detail) row at the bottom.
In the Report Data window, expand the Customers dataset, select FirstName and drag it to the first cell of the detail row of the table, then drag LastName into the second column, and CustomerStatus into the third. When we drag each column into the data row of the table, SSRS make a guess as to what to call the row in the corresponding header. We can expand and shrink the size of the columns by highlighting and dragging.
We can add additional columns to the table by right-clicking on one of the columns and selecting one of the two Insert Column options. We’ll add the DateOfBirth column to the report, so add a new column to the right of CustomerStatus , and then drag the DateOfBirth field from the dataset to the detail row of the new column. Alternatively, we can hover over the cell to see a popup list of fields from the dataset, and select D ateOfBirth
At this stage, we can click on the Preview tab to view the report.
Format the table header
Now we have a basic, very plain, tabular report, so let’s add some formatting to make it look better. We have lots of options such as adding background colors, changing the font or text color, adding italics or bolding, and more. In this example, we will change the background color of the header row.
To format all the cells in the header in the same way, click one cell to make the table handles appear. Then select the entire row by selecting the handle:
There are two ways to modify the properties. The first is to open the Properties window (F4), where we can set background color, font, and so on. The other method is to use the formatting toolbar. Whichever way you choose, set the background color for the headers to your preferred color and choose the bold font style.
Having formatted the header row, we can once again click on the Preview tab to view the report.
Add a Page header
We’ve worked on the table header, but the report page itself can also have a header and footer. Report headers and footers appear on every page of the report. To add one, move to Design mode and select Report | Add Page Header from the menu. A new band appears on the report above the body. From the toolbox, drag a text box onto the header, click on it and enter your header, “My First Report”. Select the textbox and modify the font and text style, as desired. Again, we can check our handiwork in Preview mode.
Starting with the 2008 release, as well as applying formatting to a textbox, we can also apply multiple formats to the text within a textbox. Clicking the edge of the textbox selects the textbox. Clicking inside the textbox selects the text. To try this, go back to the design view and select just part of the text in the “My First Report” textbox and apply different formatting, such as a different font. Now there are two formats within one textbox.
We can apply formatting to each detail field in the report table. Let’s start by beautifying that ugly DateOf Birth field. The time information is superfluous, so let’s format the date properly. Right-click on the cell that contains the date of birth, choose Text Box Properties . Next, navigate Number | Date and then set the preferred format (I used yyyy -mm- dd ).
Setting report level properties
When on the Design tab of the Report Designer a top menu item, Report , activates, from where we can:
- Turn on and off the header and footer sections for the report pages
- Open the Report Properties dialog and set various report properties, such as the print format
- Publish report parts – starting with 2008 R2, you can publish individual part of the report that can be used to build dashboards (we won’t cover this till later in the series)
- View the grouping section and ruler . For example, if the ruler is not visible, turn it on from Report | View | Ruler .
Navigate Report | Report Properties to open the Report Properties dialog. Some of the report properties are also available in the Properties (F4) window as well, but you may find that working in the Report Properties dialog is more convenient.
Setting up the report print settings is not intuitive, compared to other products. In the report Design tab you see your report with a ruler across the top. Since I am in the US, my ruler is set up in inches by default. A standard sheet of paper is 8.5 x 11 inches. The default setting in SSRS is to have a 1-inch (or 2 cm) margin all the way around the content area. So, at 8.5 inches wide with a 1-inch margin on the left and another on the right, we have 6.5 inches for content. If the report page is wider than 6.5 inches, it will spill over onto a second sheet of paper when printed. If there is just blank space in the extra area, you will get alternating blank sheets of paper when printed.
On the Page Setup tab of the Report Properties dialog, we can change the report to Landscape if we wish, switch to centimeters, modify the paper size or the margins. To avoid spill-over when printing, make sure that the width of the report plus the right margin plus the left margin is less than the width of the paper size.
Adding parameters to a report
There are two ways to add parameters to our reports. The first is simply to define parameters in the queries in the dataset, and then these will automatically be available as report parameters. The second way is to manually add report parameters through the Parameters section of the Report Data window.
We can use parameters to filter the data at the source, or for other reasons like giving the end-user control over one of the properties. We could also have a parameter that is used for both functions.
Parameters created by the dataset query
First, we will set up parameters using a dataset query. You can either continue working with the same report or create a new one that is a copy of the original.
To create a copy, right-click on FirstReportMan in the Solution Explorer and select C opy . Then right-click on the project name and select Paste . Rename the new report ParameterReport . Double-click the new report in Solution Explorer to open it in the designer. In the Report Data window, navigate to the Customers dataset and double-click it to bring up the properties. The Dataset dialog box opens and allows us to edit the query for the dataset. Change the stored procedure from spr_CustomerSelectAll to spr_CustomerSelectByState . A parameter called @ StateCD should appear in the Parameters folder. This parameter allows us to filter the data from the Customer table by State . Again, the ReportingDemoDatabaseScript.sql script in the code download includes the creation script for spr_CustomerSelectByState .
Switch to the Preview tab to view the report. Instead of the report just running and displaying all the data from the data source, there should be a place for us to enter a value for the @ StateCD parameter. Enter “CA” and click the View Report button to see only Californian customers.
To edit existing parameters, or to add new ones, switch to the Design tab of the Report Designer and expand the Parameters folder. Double-click the StateCD parameter to bring up the properties. First, we are going to make the prompt a little more friendly. On the General page, change the Prompt value to State .
We can also provide a list of possible values for the parameter. Select the Available Values page and from here we can provide either a hard-coded list, or connect the parameter to a dataset. The second method is the generally the best so that we can avoid the need to maintain the list manually.
Close the parameter properties. To connect a parameter to a dataset, we first need to create a new dataset. Using the skills you have learned so far, add a dataset to the report called StateList based on this query: SELECT DISTINCT State FROM Customer ORDER BY State ; .
Open the parameter properties once again and select Available Values . Choose Get values from a query. Under Dataset , select StateList . For the Value and Label fields, select State .
In this case, the Value and Label fields are the same. The Value field is the field that the database needs for the query. The Label field is the field that the end user should see. For example, if we have a list that has an ID and a description, the ID would be the Value field while the description would be the L abel field.
Manually created parameters
Tip: shared data sources, embedded datasets.
Generally, data sources are best shared and datasets are best embedded. However, queries to populate parameter lists are good examples of datasets you may want to share instead, since they can often be used for several reports.
Now let’s add a parameter that is not defined in a query and, therefore, must be created manually. In the Report Data window, click Add | New Parameter . Give the new parameter the name ReportTitle , and enter “Report Title” for the Prompt . Its data type should be Text . Click OK .
Back on the Design tab, right-click the report header textbox and choose the Expression option. Remove the original “My First Report” text and select Parameters under Categories . Double-click on the ReportTitle parameter. This text box will now display the value we pass to the Report Title parameter. Click OK .
Switch to the Preview tab and try it out.
Part 1 covered everything we need to build a basic SSRS report. In the next articles, we’ll get into more advanced options such as grouping, drill-downs, sorting and custom functions. Stay tuned.
SQL Monitor helps you manage your entire SQL Server estate from a single pane of glass. Proactively mitigate potential risks with instant problem diagnosis and customizable alerting – wherever your databases are hosted. No downtime, customer complaints, or wake-up calls at 3am.
Find out more
Subscribe for more articles
Fortnightly newsletters help sharpen your skills and keep you ahead, with articles, ebooks and opinion to keep you informed.
Rate this article
Kathi Kellenberger is a Customer Success Engineer at Redgate and a Microsoft Data Platform MVP. She has worked with SQL Server for over 20 years and has authored, co-authored, or tech edited more than 20 technical books. Kathi is a volunteer at LaunchCode, the St. Louis based organization providing free training and paid apprenticeships in technology. When Kathi isn’t working she enjoys spending time with family and friends, cycling, singing, and climbing the stairs of tall buildings. Be sure to check out her courses on Pluralsight .
Follow Kathi Kellenberger via
View all articles by Kathi Kellenberger
Introduction to SQL Server Spatial Data
- T-SQL Programming
Power Query Formula Language in Power BI Desktop
What’s new in T-SQL in SQL Server 2022
SSRS Tutorial: What is SQL Server Reporting Services?
What is SSRS?
SSRS stands for SQL Server Reporting Services is a reporting software that allows you to produce formatted reports with tables in the form of data, graph, images, and charts. These reports are hosted on a server that can be executed any time using parameters defined by the users. It is part of Microsoft SQL Server Services suite.
Types of reporting services
- Microsoft SQL Server Integration services which integrate data from different sources.
- Microsoft SQL Server Analytical service which helps for the analysis of the data
- Microsoft SQL Server Reporting service allows for generating a visual report of the data.
Here, are prime reasons for using SSRS tool:
- SSRS is an enhanced tool compared to Crystal Reports
- Faster processing of reports on both relational and multidimensional data
- Allows better and more accurate Decision-making mechanism for the users
- Allows users to interact with information without involving IT professionals
- It provides a World Wide Web-based connection for deploying reports. Hence, reports can be accessed over the internet
- SSRS allows reports to be exported in different formats. You can deliver SSRS reports using emails
- SSRS provides a host of security features, which helps you to control, who can access which report
Example of SSRS reporting
Consider a SSRS report example of a medical research institute where patients are recruited for various clinical trials.
The staff in the institute creates a database record for each patient.
Once they agree to be part of the trial, and the hospital gets the payment form the drug company based on the price at which it is ready to participate.
Without SSRS, the medical institute would need to manually email a report to the pharma company with the total number of weekly participants. The institute must also add details of every patient included in the trial, the number of drugs used, and all the unwanted situations. As a result, the time taken to collect and send this data in the correct format may consume loads of valuable time in the clinic.
If the institute were recording data, with the help of SSRS tool, they would be able to produce on-demand reports in a pre-defined format.
Features of SSRS
- Offers a Simple Object Access Protocol (SOAP) application and pluggable architecture
- Retrieve data from managed, OLE ODBC, and DB connections
- Allows you to create adhoc reports and save them to the server
- Display data in a variety of formats which includes tabular, free-form, and charts
- Create custom controls by using report-processing extension
- Embed graphics, images to the reports. You can also integrate with external content using SharePoint
- You can store and manage custom reports
- Chart and Gauge control feature allows you to display KPI data
How SSRS Works?
Now in this SSRS tutorial, we will learn how SSRS works:
- The report users are the peoples who work with the data as well as want some insights from data. They send a request to the SSRS server
- SSRS server finds the metadata of the report and sends a request for data to the data sources.
- Data returned by the data source is merged with the report definition into a report.
- When the report is generated, it is returned to the client.
SSRS has quite a complex architecture. The report services architecture includes development tools, administration tools, and report viewers.
Here, are important components of SSRS
It is an ad-hoc report publishing tool that is executed on a client’s computer. It has a drag and drop interface that is easy to use.
The Report designer tool helps to develop all types of reports. It is a publishing tool, that is hosted in Visual Studio or Business Intelligence Development Studio (BIDS).
The report managers check the report, matching it with the given requirements. They make decisions based on those reports.
It is a server which uses the SQL Server database engine to store metadata information
Report server database
It stores metadata, report definitions, resources, security settings, delivery data, etc.
Reporting services retrieve data from data sources like relational and multidimensional data sources.
Reporting Life Cycle
Every organization follows a standard reporting lifecycle which can be classified as follows:
Authoring: In this phase, the report author defines the layout and syntax of the data. The tools used in this process are the SQL Server Development Studio and SSRS tool.
Management: This phase involves managing a published report which is mostly part of the websites. In this stage, you need to consider access control over report execution.
Delivery: In this phase, you need to understand when the reports need to be delivered to the customer base. Delivery can be on-demand or pre-defined schedule. You can also add an automation feature of subscription which creates reports and sends to the customer automatically.
What is RDL?
Report Definition Language is shortly known as RDL. It describes all possible elements of a report using an XML grammar which is validated by an XML schema.
The report definition of an individual report is based on RDL. It contains instructions for rendering the design of the report at the run time.
Type of SSRS reports
Here, are types of reports which you can develop using SSRS tool.
Advantages of using SSRS
- It is faster and cheaper.
- Efficient reporting access to information that is residing in both MS SQL Server database or Oracle
- No need for expensive specialist skills
- In SSRS the default report designer is integrated with Visual Studio .NET. This allows us to create an application and reports in the same environment.
- The security is managed in a role-based method which can be applied to folders and reports.
- Subscription-based reports are automatically sent to the users.
- Faster production of reports on both relational and cube data
- Real time information to the business, providing better decision support
Disadvantages of using SSRS
Some limitations of SSRS are given below:
- There is no print button. So if you want to print something you need to export PDF, excel, word or other formats.
- All reports need parameters to be accepted by users.
- It is difficult to make changes in the custom code and debug expressions.
- Does not allow you to add page number or total pages in the report body
- Does not offer any method to pass values form sub-reports to the main report
- Page header always creates extra spaces on every new page.
- The SSRS full form is S QL S erver R eporting S ervices which allows you to produce formatted reports with tables in the form of data, graph, images, and charts.
- Three types of analytical SSRS services are 1) Integration 2) Analytics 3) Reporting.
- SSRS offers faster processes of reports on both relational and multidimensional data.
- SSRSS helps you to retrieve data from managed, OLE, ODBC, and DB connections.
- Report Builder, Report Designer, Report Manage, Report Server, Data sources are important SSRS components.
- Reporting life-cycle main based on three aspects 1) Authoring 2) Management 3) Delivery.
- Report Definition Language (RDL) describes all possible elements of a report using an XML grammar which is validated by an XML schema.
- Important types of SSRS reports are: 1)Parameterized reports 2)Linked Reports 3) Snapshot reports 4) Cached 5) Drill through Reports, etc.
- SQL Variables: SQL Server Declare, Set and Select Variable
- How to Create Login, User and Grant Permissions in SQL Server
- SQL Server Tutorial PDF for Beginners (Free Download)
- Top 40 SSIS Interview Questions and Answers (2023)
- Top 20 SSRS Interview Questions and Answers (2023)
Court Reporter & Legal Deposition Service in San Jose, CA
Since 1996, Advantage Reporting Services – Deposition and Court Reporting has delivered excellence in legal deposition and court transcription services to clients throughout California. With a reputation for personalized deposition service and attention to detail, we are your go-to document depository and source for accurate reporting of depositions, private trials, hearings, meetings and more.
Learn More Schedule Now
Your Legal Deposition Service
If there’s one thing you should know about us , it’s that at Advantage Reporting Services – Deposition and Court Reporting, we strive to go the extra mile in customer service. We know the importance of detailed reporting. We also understand that many situations require quick responses, high efficiency and last-minute plan adjustments. Our experienced staff is ready to assist you with these challenging situations. Whether you need personal delivery of a transcript, the last-minute location of an interpreter or the skills of a qualified court reporter in San Jose, CA, we have you covered. Our mission is your complete satisfaction. Our consistent achievement of this mission is the secret to our 20-year track record of success.
Advantage Reporting Services – Deposition and Court Reporting is available for a full range of services, including transcriptions for depositions, private trials and court trials, as well as hearings, meetings and audio playback. Our services also include Realtime, video services and document services. We are also proud to provide a beautiful conference room setting from which you can work with us. As an industry-leading court reporting service in San Jose, CA, we have found that our clients appreciate our superior service and in-depth knowledge of reporting. For over two decades, they have enjoyed the many benefits of partnering with Advantage Reporting Services, which include:
- We are locally owned and operated, established in 1996.
- We handle everything from documentation to video to presentations and more.
- Our experts apply professional standards to ensure detailed accuracy.
- We are committed to 100 percent customer satisfaction.
- We are a proud member of the Deposition Reporters Association (DRA).
Schedule a Professional Court Reporter
Contact the court reporters at Advantage Reporting Services – Deposition and Court Reporting today to receive the best in transcriptions, legal deposition service, and reporting for your event.
Proudly Serving San Jose, CA and surrounding areas, such as:
- Stockton, CA
- Modesto, CA
- Santa Cruz, CA
- Monterey, CA
- Santa Clara County, CA
- San Francisco County, CA
- Sacramento County, CA
- San Joaquin County, CA
- Stanislaus County, CA
- Santa Cruz County, CA
Crangle Reporting Services has provided state-of-the art court reporting services in Northern California for over 30 years. Owner Karen Crangle, C.S.R., along with a team of experienced certified court reporters and a proficient office staff, has built a reputation in the legal community for consistently providing accurate and timely transcripts. Our emphasis is on personal and professional service.
3756 Grand Avenue, Suite 305
Oakland, CA 94610
Email: [email protected]
Copyright © 2011 Crangle Reporting Services
FinCEN Beneficial Ownership Rule Effective January 1, 2024 – But With Reporting Deadline Extension
The beneficial ownership information (BOI) reporting rule implementing Section 6403 of the Corporate Transparency Act (CTA) was finalized by the US Department of the Treasury’s Financial Crimes Enforcement Network (FinCEN) in September 2022. The BOI rule starts taking effect on January 1, 2024, and, as a general matter, sets a 30-day deadline for covered companies formed after January 1, 2024, to submit required reports. However, on November 30, 2023 , FinCEN granted a partial reprieve by finalizing a rule that extends the time frame for submitting required reports from 30 days to 90 days. This extension, which applies only to companies created in 2024, means that a covered company created on or after January 1, 2024, must submit a report of its beneficial owners and related company information – a BOI report – within 90 days of receiving notice of the company’s creation or registration.
Non-exempt companies in existence as of December 31, 2023 (i.e., the end of this year) still must submit a BOI report by January 1, 2025. A reporting company that is created on or after January 1, 2025, must submit a BOI report within 30 days after receiving notice of the company’s creation or registration. Such companies should note, however, that the deadline reverts to 30 days on January 1, 2025, meaning that a company created late in 2024 can avail itself of the 90-day filing deadline extension only until the end of the year, then must complete the filing by the end of January (if the filing is not already due before then).
Even with the extension to the filing deadline for 2024, companies still should consider how the BOI rule may apply and what steps they need to take to meet its requirements. Below, we’ve provided an overview of some of the key elements of the BOI rule that can serve as a starting point for developing an action plan to address this new reporting regime.
What makes a company a covered ‘reporting company’?
A “reporting company” is any company formed in the US, or any foreign company that registers to do business in the US, by filing a document with a secretary of state or similar office, unless it comes within the scope of an exemption. There are 23 categories of exemptions from the BOI rule. Companies that qualify under any of these exemptions will not be “reporting companies” and will not need to file BOI reports (unless they later become non-exempt). Some of the exemptions likely to have broad relevance are noted below, and additional detail on each exemption, including the specific criteria, is provided by FinCEN in Section 1.2 of the Small Entity Compliance Guide . In spite of the breadth of the exemptions, however, many newly and recently formed privately held companies are not likely to qualify for an exemption, and thus will be subject to the BOI rule. Additionally, holding companies or other similar vehicles may in some cases not be within any of the categories of exemptions, though a detailed analysis may be required based on the specific facts and circumstances of a particular organization’s structure.
Key exemptions likely to exclude many companies from the BOI rule’s reporting requirements include exemptions for the following types of entities:
- Large operating companies, which the BOI rule defines to include any company that employs more than 20 full-time employees in the US, has more than $5,000,000 in gross receipts or sales in the US, and has an operating presence at a physical office within the US.
- Public companies, based on the BOI rule definition of a “securities reporting issuer.”
- Certain types of regulated entities, such as insurance companies, banks and credit unions, brokers or dealers in securities, and money services businesses (MSBs).
- Entities involved in private equity and venture capital – specifically, investment companies, investment advisers, pooled investment vehicles and venture capital fund advisers – subject to certain criteria.
- Subsidiaries of certain exempt entities, including larger operating companies, public companies, regulated entities such as banks (but not MSBs), and the exempt private equity and venture capital entities, are also exempt from BOI reporting, provided in each case that the subsidiary’s ownership interests are controlled, or wholly owned, directly or indirectly, by the exempt entity.
What do reporting companies need to do?
A reporting company must submit a BOI report to FinCEN that includes three types of information:
- Company information, such as full legal name (and any trade names), address, jurisdiction of formation, and taxpayer identification number (or equivalent issued by a foreign jurisdiction).
- Beneficial owner information, including the full legal name, date of birth, address, and the unique identifying number and image of a US passport, state driver’s license, or other eligible identification document for each individual identified as a beneficial owner.
- Company applicant information, for companies created or registered on or after January 1, 2024, which is the same information required to be provided for beneficial owners.
Companies must collect the required information and submit BOI reports through FinCEN’s Beneficial Ownership Secure System (BOSS). The final form of the BOI report has not yet been made available as of the date of this alert, and FinCEN is not yet accepting BOI reports.
A reporting company must file an updated BOI report to communicate changes to company or beneficial owner information (including the beneficial owners’ identities and previously submitted information for them) no later than 30 days after the date on which the change occurred. BOI report data also must be updated within 30 days after the date the company becomes aware of an inaccuracy in a previously filed BOI report or had reason to know of such inaccuracy. Company applicant information does not need to be updated on a reporting company’s BOI report in the event the information changes (e.g., a change in address of a company applicant), but a reporting company does need to file an updated BOI report if there are inaccuracies in previously reported company applicant information.
Companies are not otherwise required to submit BOI reports on an annual or other periodic basis as a matter of course.
What is a ‘beneficial owner’?
Under the BOI rule, a “beneficial owner” is any individual who, directly or indirectly exercises substantial control over a reporting company or owns or controls at least 25% of the ownership interests of a reporting company. The BOI rule describes four categories of “substantial control”:
- The individual is a senior officer (e.g., CEO, chief financial officer, general counsel).
- The individual has authority to unilaterally appoint or remove any such senior officer or a majority of the board of directors of the reporting company.
- The individual directs, determines or has substantial influence over important decisions made by the reporting company.
- The individual has any other form of substantial control over the reporting company.
Ownership interests for purposes of the BOI rule can include equity, stock or voting rights; a capital or profit interest; convertible instruments; options or other nonbinding privileges to buy or sell any of the aforementioned types of interests; or any other instrument, contract or other mechanism used to establish ownership. To determine whether an individual owns or controls, directly or indirectly, at least 25% of the ownership interests of the company, a reporting company may need to first identify the types of ownership interests, then calculate whether any single individual’s interests exceed 25%.
FinCEN’s Small Entity Compliance Guide provides additional information, including checklists, for identifying individuals who are beneficial owners based on the substantial control and ownership interests prongs, but companies with more complex ownership and/or governance structures may need to conduct a more detailed and nuanced analysis to identify beneficial owners.
What is a ‘company applicant’?
Reporting companies created after January 1, 2024, are required to identify and report company applicants. Each such reporting company will have at least one and a maximum of two company applicants. Under the BOI rule, a “company applicant” is defined as: (1) the individual who directly files the document that creates a domestic reporting company or first registers a foreign reporting company to do business in the US; and, if applicable, (2) the individual primarily responsible for directing or controlling the filing of the creation or registration document.
Reporting companies created or registered on or before December 31, 2023, do not have to report company applicants when they start reporting by January 1, 2025.
What is a ‘FinCEN identifier’ and why does it matter?
A “FinCEN identifier” is a unique identifying number that FinCEN will issue to an individual upon request. An individual may directly apply for a FinCEN identifier by providing the same information that a reporting company would submit on behalf of the individual as a company applicant or beneficial owner. (In certain instances, a reporting company may wish to obtain a FinCEN identifier and can request the issuance when filing its BOI report.)
A reporting company may report an individual’s FinCEN identifier in place of the required four pieces of information about the individual in BOI reports. An individual who is either a beneficial owner or a company applicant of a reporting company will therefore not need to provide personal information directly to the reporting company if the individual has obtained a FinCEN identifier and provides it to the reporting company instead. An individual must keep the information provided to FinCEN to obtain a FinCEN identifier (e.g., address information) updated.
Similar to the BOI report, FinCEN has not yet made public the final form of the FinCEN identifier application, and FinCEN is not yet accepting FinCEN identifier requests.
What are the penalties for noncompliance?
Any person who willfully provides, or attempts to provide, false or fraudulent BOI data to FinCEN – or willfully fails to report complete or updated BOI data to FinCEN – may be subject to civil or criminal penalties of up to $10,000 and up to two years in prison. A person fails to report complete or updated BOI data to FinCEN if, with respect to a reporting company, the person “causes the failure,” which could include an individual’s refusal to provide or submit required information for a reporting company’s BOI report.
Companies currently in existence have time to determine if the BOI rule applies, because it does not take effect until January 1, 2025, for companies created or registered on or before December 31, 2023. Nevertheless, such companies may wish to start developing processes to determine whether the BOI rule applies and to be able to evaluate whether newly created entities within the corporate family (e.g., subsidiaries, special purpose vehicles) are subject to the rule. Newly formed companies, and persons or entities that are involved in or create such companies – such as entrepreneurs, venture funds, and other investors and investment vehicles – will need to determine whether the BOI rule applies and, if so, how they will address reporting requirements. All covered companies should continue to monitor for updates from FinCEN regarding the reporting process generally, including the availability of the FinCEN reporting forms and access to the BOSS.
Please join Cooley for a webinar focused on the CTA and the new BOI reporting rule requirements that start taking effect on January 1, 2024.
This content is provided for general informational purposes only, and your access or use of the content does not create an attorney-client relationship between you and Cooley LLP, Cooley (UK) LLP, Cooley SG LLP, Cooley HK or any other Cooley entity (collectively referred to as “Cooley”). By reviewing this content, you agree that the information provided does not constitute legal or other professional advice. This content is not a substitute for obtaining legal advice from a qualified attorney licensed in your jurisdiction and you should not act or refrain from acting based on this content. This content may be changed without notice, and it is not guaranteed to be complete, correct or up to date, and it may not reflect the most current legal developments. This content may be considered attorney advertising . Do not send any confidential information to Cooley, as we do not have any duty to keep it confidential.
- Latest Headlines
- English Edition Edition English 中文 (Chinese) 日本語 (Japanese)
- Print Edition
- More More Other Products from WSJ Buy Side from WSJ WSJ Shop WSJ Wine
This copy is for your personal, non-commercial use only. Distribution and use of this material are governed by our Subscriber Agreement and by copyright law. For non-personal use or to order multiple copies, please contact Dow Jones Reprints at 1-800-843-0008 or visit www.djreprints.com.
Goods Deflation Is Back. It Could Speed Inflation’s Return to 2%.
Prices of durables have been falling for five straight months.
Dec. 3, 2023 7:00 am ET
After a historic run-up in inflation, Americans are now starting to see something they haven’t in three years: deflation.
Copyright © 2023 Dow Jones & Company, Inc. All Rights Reserved. 87990cbe856818d5eddac44c7b1cdeb8
What to Read Next
- TurboTax : Save up to $15 with TurboTax coupon 2023
- The Motley Fool : Epic Bundle - 3x Expert Stock Recommendations
- H&R Block Tax : Get 20% off H&R Block tax software products
- Top Resume : Top Resume Coupon: 10% Off professional resume writing
- eBay : Unlock 10% off orders $50+ with eBay promo code
- Groupon : Groupon coupon code: Extra 10% off jewelry & watches
Most Popular news
Most popular opinion, most popular opinion, recommended videos.
Copyright © 2023 Dow Jones & Company, Inc. All Rights Reserved
An official website of the United States Government
- Kreyòl ayisyen
- Search Toggle search Search Include Historical Content - Any - No Include Historical Content - Any - No Search
- Menu Toggle menu
- INFORMATION FOR…
- Business & Self Employed
- Charities and Nonprofits
- International Taxpayers
- Federal State and Local Governments
- Indian Tribal Governments
- Tax Exempt Bonds
- FILING FOR INDIVIDUALS
- Who Should File
- How to File
- When to File
- Where to File
- Update My Information
- Get Your Tax Record
- Apply for an Employer ID Number (EIN)
- Check Your Amended Return Status
- Get an Identity Protection PIN (IP PIN)
- File Your Taxes for Free
- Bank Account (Direct Pay)
- Debit or Credit Card
- Payment Plan (Installment Agreement)
- Electronic Federal Tax Payment System (EFTPS)
- Your Online Account
- Tax Withholding Estimator
- Estimated Taxes
- Where's My Refund
- What to Expect
- Direct Deposit
- Reduced Refunds
- Fix/Correct a Return
Credits & Deductions
- INFORMATION FOR...
- Businesses & Self-Employed
- Earned Income Credit (EITC)
- Advance Child Tax Credit
- Standard Deduction
- Health Coverage
- Retirement Plans
Forms & Instructions
- POPULAR FORMS & INSTRUCTIONS
- Form 1040 Instructions
- Form 4506-T
- POPULAR FOR TAX PROS
- Form 1040-X
- Circular 230
IRS announces delay in Form 1099-K reporting threshold for third party platform payments in 2023; plans for a threshold of $5,000 for 2024 to phase in implementation
More in news.
- Topics in the News
- News Releases for Frequently Asked Questions
- Multimedia Center
- Tax Relief in Disaster Situations
- Inflation Reduction Act
- Taxpayer First Act
- Tax Scams/Consumer Alerts
- The Tax Gap
- Fact Sheets
- IRS Tax Tips
- e-News Subscriptions
- IRS Guidance
- Media Contacts
- IRS Statements and Announcements
IR-2023-221, Nov. 21, 2023
WASHINGTON — Following feedback from taxpayers, tax professionals and payment processors and to reduce taxpayer confusion, the Internal Revenue Service today released Notice 2023-74 PDF announcing a delay of the new $600 Form 1099-K reporting threshold for third party settlement organizations for calendar year 2023.
As the IRS continues to work to implement the new law, the agency will treat 2023 as an additional transition year. This will reduce the potential confusion caused by the distribution of an estimated 44 million Forms 1099-K sent to many taxpayers who wouldn't expect one and may not have a tax obligation. As a result, reporting will not be required unless the taxpayer receives over $20,000 and has more than 200 transactions in 2023.
Given the complexity of the new provision, the large number of individual taxpayers affected and the need for stakeholders to have certainty with enough lead time, the IRS is planning for a threshold of $5,000 for tax year 2024 as part of a phase-in to implement the $600 reporting threshold enacted under the American Rescue Plan (ARP).
Following feedback from the tax community, the IRS is also looking to make updates to the Form 1040 and related schedules for 2024 that would make the reporting process easier for taxpayers. Changes to the Form 1040 series – the core tax form for more than 150 million taxpayers – are complex and take time; delaying changes to tax year 2024 allows for additional feedback.
"We spent many months gathering feedback from third party groups and others, and it became increasingly clear we need additional time to effectively implement the new reporting requirements," said IRS Commissioner Danny Werfel. "Taking this phased-in approach is the right thing to do for the purposes of tax administration, and it prevents unnecessary confusion as we continue to look at changes to the Form 1040. It's clear that an additional delay for tax year 2023 will avoid problems for taxpayers, tax professionals and others in this area."
The ARP required third party settlement organizations (TPSOs), which include popular payment apps and online marketplaces, to report payments of more than $600 for the sale of goods and services on a Form 1099-K starting in 2022. These forms would go to the IRS and to taxpayers and would help taxpayers fill out their tax returns. Before the ARP, the reporting requirement applied only to the sale of goods and services involving more than 200 transactions per year totaling over $20,000.
The IRS temporarily delayed the new requirement last year.
Reporting requirements do not apply to personal transactions such as birthday or holiday gifts, sharing the cost of a car ride or meal, or paying a family member or another for a household bill. These payments are not taxable and should not be reported on Form 1099-K.
However, the casual sale of goods and services, including selling used personal items like clothing, furniture and other household items for a loss, could generate a Form 1099-K for many people, even if the seller has no tax liability from those sales.
This complexity in distinguishing between these types of transactions factored into the IRS decision to delay the reporting requirements an additional year and to plan for a threshold of $5,000 for 2024 in order to phase in implementation. The IRS invites feedback on the threshold of $5,000 for tax year 2024 and other elements of the reporting requirement, including how best to focus reporting on taxable transactions.
"The IRS will use this additional time to continue carefully crafting a way forward to minimize burden," Werfel said. "We want to make this as easy as possible for taxpayers. We will work to make the new reporting requirements easier for them, and we'll work closely with third party groups, tax professionals and others to find the smoothest path to ensure compliance with the law. This is consistent with our Strategic Operating Plan. The IRS is focused on meeting taxpayers where they are and helping them get it right the first time."
Expanded information reporting, which will occur as the result of the change in thresholds for Form 1099-K, is important because it increases tax compliance and can reduce burden on taxpayers seeking to follow the law. The IRS believes that expansion must be managed carefully to help ensure that Forms 1099-K are issued only to taxpayers who should receive them. In addition, it's important that taxpayers understand what to do as a result of this reporting, and that tax professionals and software providers have the information they need to assist taxpayers.
The IRS will continue to provide information on IRS.gov/1099k .
Fact Sheet 2023-27 contains more details about this announcement.
CMS releases rule implementing new Medicaid renewal enforcement authorities
The Centers for Medicare & Medicaid Services Dec. 4 released an interim final rule implementing new enforcement authorities the agency will use if states fail to comply with new reporting requirements as they restore Medicaid eligibility and enrollment operations following the end of the Medicaid continuous enrollment condition. The Consolidated Appropriations Act of 2023 gave CMS new enforcement authority to require states to submit a corrective action plan, suspend disenrollments from Medicaid for procedural reasons, impose civil money penalties, and apply a reduction to the state-specific Federal Medical Assistance Percentage for failure to meet reporting requirements. The rule takes effect Dec. 6 with comments accepted through Feb. 2.
Related News Articles
Child Abuse Mandated Reporter Training
Free training is available for mandated child abuse reporters, so they may carry out their responsibilities properly and understand their critical role in the lives of children and families. For information regarding the content of the training modules, visit the Mandated Reporting Website to see which training modules are available now.
The OCAP’s Mandated Reporter Training has been launched with updated content and a fresh new look! Along with a general training for all mandated reporters, the website now includes updated training for child care providers, medical professionals, law enforcement, mental health professionals, social workers, clergy and volunteers. In the coming year, the general training, child care provider training, and school personnel training will be available in Spanish.
- One Page Reporting Tip Sheet
- Report Suspected Child Abuse or Neglect
- California Suspected Child Abuse Report Form 8572
- 8572 Instructions
- Promotional Materials
- What You Should Know About Mandated Reporting
The Office of Child Abuse Prevention 744 P Street, MS 8-11-82 Sacramento, CA 95814 (916) 651-6960
- Child Abuse Prevention Month
- Childhelp National Child Abuse Hotline
- Citizen Review Panels
- County Liaisons & ETO Users
- Funded Programs
- Funding Sources
- Grant Opportunities
- How You Can Help
- Kids' Art Contest Awards 2019
- Mandated Reporter Resources
- News and Events
- Parent Leadership and CAN Prevention Award Winners 2019
- Parent Leadership Month
- Parent Resources
- Prevent Child Abuse
- Report Abuse
- Safely Surrendered Baby
- Shaken Baby Syndrome
- State Childrens Trust Fund
- Press Releases
- Israel-Hamas War
- Russia-Ukraine War
- Latin America
- Middle East
- Asia Pacific
- Election 2024
- AP Top 25 College Football Poll
- Movie reviews
- Book reviews
- Financial Markets
- Business Highlights
- Financial wellness
- Artificial Intelligence
- Social Media
Europe reaches a deal on the world’s first comprehensive AI rules
The OpenAI logo is displayed on a cell phone with an image on a computer monitor generated by ChatGPT’s Dall-E text-to-image model, Friday, Dec. 8, 2023, in Boston. Europe’s yearslong efforts to draw up AI guardrails have been bogged down by the recent emergence of generative AI systems like OpenAI’s ChatGPT, which have dazzled the world with their ability to produce human-like work but raised fears about the risks they pose. (AP Photo/Michael Dwyer)
A ChapGPT logo is seen on a monitor in West Chester, Pa., Wednesday, Dec. 6, 2023. Europe’s yearslong efforts to draw up AI guardrails have been bogged down by the recent emergence of generative AI systems like OpenAI’s ChatGPT, which have dazzled the world with their ability to produce human-like work but raised fears about the risks they pose. (AP Photo/Matt Rourke)
File - OpenAI CEO Sam Altman, left, appears onstage with Microsoft CEO Satya Nadella at OpenAI’s first developer conference, on Nov. 6, 2023, in San Francisco. Negotiators will meet this week to hammer out details of European Union artificial intelligence rules but the process has been bogged down by a simmering last-minute battle over how to govern systems that underpin general purpose AI services like OpenAI’s ChatGPT and Google’s Bard chatbot. (AP Photo/Barbara Ortutay, File)
- Copy Link copied
LONDON (AP) — European Union negotiators clinched a deal Friday on the world’s first comprehensive artificial intelligence rules, paving the way for legal oversight of AI technology that has promised to transform everyday life and spurred warnings of existential dangers to humanity .
Negotiators from the European Parliament and the bloc’s 27 member countries overcame big differences on controversial points including generative AI and police use of face recognition surveillance to sign a tentative political agreement for the Artificial Intelligence Act .
“Deal!” tweeted European Commissioner Thierry Breton just before midnight. “The EU becomes the very first continent to set clear rules for the use of AI.”
The result came after marathon closed-door talks this week, with the initial session lasting 22 hours before a second round kicked off Friday morning.
Officials were under the gun to secure a political victory for the flagship legislation. Civil society groups, however, gave it a cool reception as they wait for technical details that will need to be ironed out in the coming weeks. They said the deal didn’t go far enough in protecting people from harm caused by AI systems.
“Today’s political deal marks the beginning of important and necessary technical work on crucial details of the AI Act, which are still missing,” said Daniel Friedlaender, head of the European office of the Computer and Communications Industry Association, a tech industry lobby group.
The EU took an early lead in the global race to draw up AI guardrails when it unveiled the first draft of its rulebook in 2021. The recent boom in generative AI, however, sent European officials scrambling to update a proposal poised to serve as a blueprint for the world.
The European Parliament will still need to vote on the act early next year, but with the deal done that’s a formality, Brando Benifei, an Italian lawmaker co-leading the body’s negotiating efforts, told The Associated Press late Friday.
“It’s very very good,” he said by text message after being asked if it included everything he wanted. “Obviously we had to accept some compromises but overall very good.” The eventual law wouldn’t fully take effect until 2025 at the earliest, and threatens stiff financial penalties for violations of up to 35 million euros ($38 million) or 7% of a company’s global turnover.
Generative AI systems like OpenAI’s ChatGPT have exploded into the world’s consciousness, dazzling users with the ability to produce human-like text, photos and songs but raising fears about the risks the rapidly developing technology poses to jobs, privacy and copyright protection and even human life itself .
Now, the U.S. , U.K. , China and global coalitions like the Group of 7 major democracies have jumped in with their own proposals to regulate AI, though they’re still catching up to Europe.
Strong and comprehensive rules from the EU “can set a powerful example for many governments considering regulation,” said Anu Bradford, a Columbia Law School professor who’s an expert on EU law and digital regulation. Other countries “may not copy every provision but will likely emulate many aspects of it.”
AI companies subject to the EU’s rules will also likely extend some of those obligations outside the continent, she said. “After all, it is not efficient to re-train separate models for different markets,” she said.
The AI Act was originally designed to mitigate the dangers from specific AI functions based on their level of risk, from low to unacceptable. But lawmakers pushed to expand it to foundation models, the advanced systems that underpin general purpose AI services like ChatGPT and Google’s Bard chatbot .
Foundation models looked set to be one of the biggest sticking points for Europe. However, negotiators managed to reach a tentative compromise early in the talks, despite opposition led by France, which called instead for self-regulation to help homegrown European generative AI companies competing with big U.S rivals, including OpenAI’s backer Microsoft.
Also known as large language models, these systems are trained on vast troves of written works and images scraped off the internet. They give generative AI systems the ability to create something new , unlike traditional AI, which processes data and completes tasks using predetermined rules.
The companies building foundation models will have to draw up technical documentation, comply with EU copyright law and detail the content used for training. The most advanced foundation models that pose “systemic risks” will face extra scrutiny, including assessing and mitigating those risks, reporting serious incidents, putting cybersecurity measures in place and reporting their energy efficiency.
Researchers have warned that powerful foundation models, built by a handful of big tech companies, could be used to supercharge online disinformation and manipulation , cyberattacks or creation of bioweapons.
Rights groups also caution that the lack of transparency about data used to train the models poses risks to daily life because they act as basic structures for software developers building AI-powered services.
What became the thorniest topic was AI-powered face recognition surveillance systems, and negotiators found a compromise after intensive bargaining.
European lawmakers wanted a full ban on public use of face scanning and other “remote biometric identification” systems because of privacy concerns. But governments of member countries succeeded in negotiating exemptions so law enforcement could use them to tackle serious crimes like child sexual exploitation or terrorist attacks.
Rights groups said they were concerned about the exemptions and other big loopholes in the AI Act, including lack of protection for AI systems used in migration and border control, and the option for developers to opt-out of having their systems classified as high risk.
“Whatever the victories may have been in these final negotiations, the fact remains that huge flaws will remain in this final text,” said Daniel Leufer, a senior policy analyst at the digital rights group Access Now.
Tech reporter Matt O’Brien in Providence, Rhode Island, contributed to this report.
We've detected unusual activity from your computer network
To continue, please click the box below to let us know you're not a robot.
Why did this happen?
For inquiries related to this message please contact our support team and provide the reference ID below.
Coding Corner: Overview of 2024 Coding Changes Impacting Cardiology
Dec 04, 2023
ACC News Story
Cardiovascular clinicians will see a number of coding changes starting Jan. 1, 2024. The ACC Advocacy team has prepared the following overview outlining the 23 new CPT ® codes, new HCPCS codes, and the deletion of HCPCS code G2066 that are important to cardiovascular clinicians. Additionally, the 2024 CPT/HCPCS book, which contains new introductory language, parentheticals and additional information pertaining to these new codes, is an important resource.
Phrenic Nerve Stimulator System Codes For Central Sleep Apnea: A total of 12 CPT codes were developed for the phrenic nerve stimulator system to treat central sleep apnea. Eight CPT codes (33277-33288) were developed for the insertion, removal, and removal and replacement of the phrenic nerve stimulator. These codes include vessel catheterization, all imaging guidance, and interrogation and programming, when performed. One new code was created for therapy activation of the implanted phrenic nerve stimulator system (93150) to be performed on another day. Two new codes were developed for the interrogation and programming of an implanted phrenic nerve stimulator (93151 and 93152) and one new code for interrogation without programming (93153).
Coronary Computed Tomography Fractional Flow Reserve: One new code (75880) was established for the noninvasive estimate of coronary fractional flow reserve derived from a coronary computed tomography angiography with interpretation and report. This code can be billed globally or with a technical component (TC)/professional component (PC) split. Previously, this service was reported using one or several of the four Category III codes (0501T-0504T), which will be deleted in 2024.
Intraoperative Epicardial Cardiac Ultrasound: Three CPT codes were established specifically for diagnostic intraoperative epicardial cardiac ultrasound. The global code is for placement and manipulation of transducer, image acquisition, and interpretation and report (76987). There are also component codes for placement, manipulation of transducer and image acquisition only (76988) and for interpretation and report only (76989). Separate from this family of codes is a CPT code for intraoperative ultrasound for thoracic aorta (76984).
Percutaneous Transluminal Coronary Lithotripsy: The American Medical Association developed an add-on CPT code (+92972) for intravascular coronary lithotripsy, which can be applied to eight PCI procedures (92920, 92924, 92928, 92933, 92937, 92941, 92943, 92975).
Deletion of HCPCS Code G2066: The Centers for Medicare and Medicaid Services (CMS) deleted G2066 and added refinement of existing CPT code 93297 and 93298 for interrogation device evaluations. CMS had created G2066 to report the TC of insertable cardiac monitor and implantable loop recorder remote interrogation in 2020 after 93299 was deleted. The 2024 Medicare Physician Fee Schedule (PFS) final rule now assigns TC to 93297 and 93298. Both 93297 and 93298 can be billed without modifiers to report the global service when a clinician/office performs both the professional and technical portion of remote interrogation. These codes can also be billed with the 26 modifier for the professional service only when the technical component is provided by another entity. In cases where another entity provides the technical component, the TC modifier will be billed for the technical portion only of the remote interrogation services.
Venography Codes For Congenital Heart Defect(s): Five new add-on codes were created for performing venography for congenital heart defect(s). First is a code for venography for anomalous or persistent superior vena cava when it exists as a second contralateral superior vena cava with native drainage to heart (93584). Other codes are for azygos/hemi-azygos venous system (93585), coronary sinus (93586), venovenous collaterals originating at or above the heart (93586) and venovenous collaterals originating below the heart (93588). All codes include catheter placement and radiological supervision and interpretation.
Ongoing Care Evaluation and Management (E/M) New Code G2011: In the 2024 Medicare PFS final rule, CMS implemented an HCPCS add-on code for "visit complexity inherent to evaluation and management associated with medical care services that serve as the continuing focal point for all needed health care services and/or with medical care services that are part of ongoing care related to a patient' single, serious condition or a complex condition"(G2011). This code can be applied to the following office/outpatient (O/O) services: 99202-99215. G2011 would not be payable when the O/O E/M visit is reported with modifier 25 (Significant Separately Identifiable E/M visit). CMS created this code to reflect the time, intensity and practice expense resources involved when practitioners furnish O/O E/M visits that enable them to build long-lasting relationships with their patients and address the majority of a patient's health care needs with consistency and continuity over longer periods of time. CMS has indicated that the relationship between the patient and the practitioner is the determining factor of when the add-on code should be billed. This relationship should be clearly defined in documentation. Since this is a new coding concept, CMS will consider developing additional educational materials as needed. This code will be reported by specialties and clinicians who rely on O/O E/M visits to report ongoing E/M services.
Office or Other Outpatient Services and Other E/M Changes: Several revisions were made in the E/M section of the CPT book for office/outpatient visits codes 99202-99215. Time ranges have been removed from office/outpatient E/M codes and replaced with a minimum of time spent with patients. For example, 99203 used to say "30-44 minutes of total time is spent on the date of the encounter" and now the code states "30 minutes must be met or exceeded". The office/outpatient services E/M codes now mimic the inpatient codes, articulating that medical decision making can determine the level of your E/M visit when performed with a medically appropriate history and/or examination. Clinicians can code their visits based on time or medical decision making. There are also new guidelines regarding time and consultations to review in the combined hospital inpatient and observation codes (99234-99239).
Split (or Shared) Visits: CMS finalized a policy for E/M visits furnished in a facility setting to allow payment to a physician for a split (or shared) visit (including prolonged visits), where a physician and advanced practice provider in the same group practice provide the service together (not necessarily concurrently), and the billing physician personally performs a "substantive portion" of the visit. CMS will now define a substantive portion of a split/shared visit to align with the new CPT guidelines for spilt or shared visits. CPT guidelines state: "The split or shared visits guidelines are applied to determine which professional may report the service. If the physician or other QHP performs a substantive portion of the encounter, the physician or other QHP may report the service. If code selection is based on total time on the date of the encounter, the service is reported by the professional who spent the majority of the face-to-face or non-face-to-face time performing the service." This CMS policy allows the billing provider to continue to be determined by either total time or medical decision-making (MDM) performed with the exception of critical care visits, which do not use MDM, only time.
Clinical Topics: Cardiovascular Care Team, Invasive Cardiovascular Angiography and Intervention, Noninvasive Imaging, Interventions and Imaging, Computed Tomography, Nuclear Imaging
Keywords: ACC Advocacy, Current Procedural Terminology, Centers for Medicare and Medicaid Services, U.S., Fractional Flow Reserve, Myocardial, Outpatients, Inpatients, Phrenic Nerve, Coronary Sinus, Healthcare Common Procedure Coding System, American Medical Association, Computed Tomography, Computed Tomography Angiography, Percutaneous Coronary Intervention, Medicare, Catheterization, Referral and Consultation, Delivery of Health Care, Fee Schedules, Group Practice, Lithotripsy, Critical Care, Hospitals
You must be logged in to save to your library.
Jacc journals on acc.org.
- JACC: Advances
- JACC: Basic to Translational Science
- JACC: CardioOncology
- JACC: Cardiovascular Imaging
- JACC: Cardiovascular Interventions
- JACC: Case Reports
- JACC: Clinical Electrophysiology
- JACC: Heart Failure
- Current Members
- Campaign for the Future
- Become a Member
- Renew Your Membership
- Member Benefits and Resources
- Member Sections
- ACC Member Directory
- ACC Innovation Program
- Our Strategic Direction
- Diversity and Inclusion
- Our History
- Our Bylaws and Code of Ethics
- Leadership and Governance
- Annual Report
- Industry Relations
- Support the ACC
- Jobs at the ACC
- Press Releases
- Social Media
- Book Our Conference Center
- Acute Coronary Syndromes
- Anticoagulation Management
- Arrhythmias and Clinical EP
- Cardiac Surgery
- Chronic Angina
- Congenital Heart Disease and Pediatric Cardiology
- COVID-19 Hub
- Diabetes and Cardiometabolic Disease
- Geriatric Cardiology
- Heart Failure and Cardiomyopathies
- Invasive Cardiovascular Angiography and Intervention
- Noninvasive Imaging
- Pericardial Disease
- Pulmonary Hypertension and Venous Thromboembolism
- Sports and Exercise Cardiology
- Stable Ischemic Heart Disease
- Valvular Heart Disease
- Vascular Medicine
Latest in Cardiology
- Clinical Updates & Discoveries
- Advocacy & Policy
- Perspectives & Analysis
- Meeting Coverage
- ACC Member Publications
- ACC Podcasts
Education and Meetings
- Online Learning Catalog
- Understanding MOC
- Products and Resources
- Image and Slide Gallery
- Certificates and Certifications
- Annual Scientific Session
Tools and Practice Support
- Quality Improvement for Institutions
- Accreditation Services
- Clinical Solutions
- Clinician Well-Being Portal
- Mobile and Web Apps
- Advocacy at the ACC
- Cardiology as a Career Path
- Cardiology Careers
- Practice Solutions
- 2400 N St. NW
- Washington , DC 20037
- Email: [email protected]
- Phone: 1-202-375-6000
- Toll Free: 1-800-253-4636
- Fax: 1-202-375-6842
- Media Center
- ACC.org Quick Start Guide
- Advertising & Sponsorship Policy
- Clinical Content Disclaimer
- Editorial Board
- Registered User Agreement
- Terms of Service
© 2023 American College of Cardiology Foundation. All rights reserved.