POWER BI QUESTIONS

How to Export Power BI Report Builder Reports to PDF

The invoice register is ready, but the accounts team still needs its PDF. Once again, someone has to choose the month, export the report and send the right copy.

Report Builder handles a one-off export. PBRS takes care of the recurring job, bringing the report’s parameters, PDF preparation and delivery together so your team can get on with the month-end review.

  
The month-end review

Get the invoice register into your colleague’s hands

Your colleague is working through the month-end accounts. She needs the invoice register beside her: invoice numbers she can follow down the page, amounts she can compare, and a total she can reconcile. A PDF is useful because everyone can refer to the same document during the review.

Getting that first copy is straightforward. In Power BI Report Builder, open the report, select the month’s parameters and run it. Choose Export → PDF, then save the file. If the report is already published to the Power BI service, open the paginated report, select the parameters and export from its viewer.

The repeated work begins next month. Someone must remember the new period, check the output, name the file and send it to the team. When several departments need different copies, those small jobs start to take over the morning.

PBRS can make that a saved reporting routine. You keep designing the register in Report Builder, publish it to the supported reporting platform, and configure PBRS to generate and deliver the PDF. The author controls what the document contains; the reporting schedule controls when and where it arrives.

Working with an .rdl or a .pbix file?

Report Builder creates paginated report definitions with the .rdl extension. Power BI Desktop creates .pbix reports with different export behavior. This article follows a Report Builder paginated report. You can export locally while designing it; the PBRS workflow below uses a published report.

Make the month obvious

A register delivered in October might cover September. Put the reporting period in the document heading and filename so your colleague can recognise the right copy without opening an email thread.

  
Your options

When exporting the PDF becomes a monthly job

For one PDF you need today, the Export menu does the job. For a monthly register that people rely on, the useful question is how much preparation and follow-up you want someone to repeat.

Follow the close, rather than chase a reminder

The accounts team may finish on the fourth working day, or the final approval may arrive later than expected. PBRS offers working-day schedules and custom calendars; an event or your application can also start the configured job. You can make delivery follow the reporting process instead of asking a colleague to remember the export.

Give each team its own useful copy

A department manager may need only their invoices, while finance needs the full register. With PBRS data-driven scheduling, parameter values and delivery details can come from your data. That makes a growing list of tailored PDFs easier to manage than repeatedly selecting departments and forwarding attachments.

Deliver a finished document, not another assembly task

Perhaps the review now needs the invoice register and an overdue-balances report together. PBRS can merge report outputs into one ordered PDF, with bookmarks to help readers find their section. PDF password protection, document permissions and watermarks can also be part of preparation. Your colleague receives the review pack without having to combine separate exports.

The PBRS PDF delivery guide explains these options. They are especially useful when the job includes several reports, sensitive documents or destinations beyond a single inbox.

Where native delivery fits

A native Power BI subscription can be enough for a straightforward scheduled copy of an eligible paginated report. Power BI also supports dynamic subscriptions for eligible scenarios, so personalised delivery alone is not unique to PBRS. PBRS becomes the stronger choice when you need to bring business timing, document preparation, multiple reports and destinations into one managed routine.

Power Automate can connect export and delivery to a wider business workflow, but your team owns the connections, parameter mapping, retry behavior and delivery steps. Adding PDF merging or protection means more processing to maintain. PBRS keeps those reporting tasks in the reporting system, with a saved job and execution history to investigate when a file is missing.

Check the native requirements before choosing a route

Microsoft’s subscription guidance covers licensing, permissions, attachment and recipient requirements. Check the rules for paginated reports specifically, rather than applying interactive-report limits to this workflow.

For paginated exports through Power Automate, Microsoft documents eligible capacity requirements or a PPU alternative limited to one export in a five-minute window. An export that takes more than two minutes to download can fail because of Power Automate’s synchronous request limit. Large batches also need considered retry handling. These are constraints of that native route; PBRS still needs a supported source, appropriate access and a report that runs successfully.

Start with the finished pack

Ask what your colleague should receive: one register, a department’s copy, or several reports in one PDF. That answer makes it much easier to choose between a simple subscription and a PBRS reporting routine.

  
Set it up

Prepare one good PDF, then let PBRS deliver it

Start with the invoice register your accounts team already trusts. First make its PDF comfortable to read, then save the delivery instructions in PBRS. You only need one report and a test destination to establish the routine.

Make the PDF as useful as the screen preview

Export a month with enough invoices to fill several pages. Read across a page break and look at the last page: can your colleague still follow the columns and find the total? PDF uses physical page dimensions, so a layout that looks fine in the screen preview can spill onto an extra page.

If blank pages appear, check the paper size, orientation and margins in Report Builder. On an 8.5-inch-wide page with half-inch left and right margins, the report body has 7.5 inches available. Move or resize objects extending beyond that space before reducing the body width. Check unnecessary page breaks and trailing whitespace too.

Report Builder page setup and body width properties from Microsoft documentation.

Microsoft’s blank-page guide shows the relevant controls. Missing invoices are a different problem: check the query, month parameters and data access. PBRS can repeat a tested export; it does not repair an incorrect report layout or query.

Choose the published register in PBRS

For a Power BI service report, create a Single → For Power BI Service → Paginated Reports schedule and select the published register. Set its actual parameter names, values and types, then preview the result. The paginated schedule walkthrough explains the controls.

Decide how the reporting period will advance. A fixed September value will still request September next month. Use the parameter approach appropriate to your report and schedule, and test the next period before relying on unattended delivery.

Save the PDF and its destination together

Add the intended destination, such as Email or Disk, and choose Acrobat Format (*.pdf). Give the file a recognisable name, such as Invoice-register-2026-09.pdf. If this copy needs PDF protection, configure it as part of the output and confirm that the intended reader can open it.

Choose timing that follows month-end close. If the closing date is predictable, a working-day schedule may suit it. If approval determines readiness, use the event or application approach that reflects that approval. Keep automatic execution disabled while you test.

Let a colleague try the first delivered copy

Send to a controlled test destination. Compare a known invoice, the final invoice and the monthly total, then ask a colleague to open the delivered file and read a page transition. This checks the document people will actually use, including any password or destination access.

Once the copy is right, enable the routine. If the register later becomes part of a larger month-end pack, a PBRS package schedule can assemble the related reports and deliver them together.

Keep the headings with the reader

Your colleague may spend most of the review on page six. Repeated column headings and a clear reporting period help that page make sense on its own, especially when someone prints just part of the register.

  
For developers

Let month-end close request the report

Your billing application already knows when the month is closed. It can ask PBRS to run the saved invoice-register job at that point, instead of relying on a person to press Export or a fixed time that might arrive too soon.

Configure and test the hosted report, parameters, PDF settings and destination in PBRS first. Your application can then request execution while the reporting team continues to maintain the document and delivery settings in one place. This keeps PDF preparation and distribution out of the application’s own reporting code.

Developer example: execute the saved job and monitor it

This illustrative request uses an existing single-report schedule. Replace the base URL, access token and schedule ID with values from your installation. Confirm that the saved job has the correct month and a controlled test destination before running it.

POST {pbrsBaseUrl}/api/Schedule/ExecuteScheduleAsync
Authorization: bearer {pbrsAccessToken}
Content-Type: application/json

{
  "ScheduleType": "report",
  "uniqueid": 101,
  "RunBy": "Month-end invoice register"
}

GET {pbrsBaseUrl}/api/Schedule/GetExecutionStatus?ExecutionId={ExecutionId}
Authorization: bearer {pbrsAccessToken}

Keep the returned ExecutionId with the reporting period and use it to monitor this run. An accepted request is not proof that the PDF arrived. Follow the PBRS execution guide to inspect the final result and verify delivery. If submission times out, investigate the existing request before submitting again.

The execution request does not change the report’s month. Where the application must update it, follow the paginated parameter update guide before execution. Coordinate changes and runs so two requests cannot overwrite the parameters of a shared schedule.

For creating jobs programmatically, use the source-specific contracts in the single-schedule API guide. Power BI service paginated reports and SSRS/Power BI Report Server use different source contracts. This workflow runs a configured hosted report; it does not export an unsaved .rdl on someone’s desktop.

The practical benefit is a clear division of responsibility: the application decides that the month is ready, and PBRS runs the reporting job. When a colleague asks where the register went, the team has an execution record to follow.

Keep the month with the run

Save the reporting period alongside the execution identifier in your application. If finance asks about September’s register, support can find that specific run instead of searching through every report generated in October.

  
Your next step

Spend the morning reviewing invoices, not sending files

Next month, your colleague should be able to open the invoice register and start the review. She should not have to ask who is exporting it, whether the right period was selected or where the rest of the pack went.

Use Report Builder to make the document clear and dependable. Choose PBRS when you want its preparation and delivery to follow the way your accounts team works—with the right parameters, useful PDF options and related reports brought together. That is where it offers more than a basic export or subscription.

Begin with the PBRS paginated report scheduling guide and one monthly register. You can build on that first routine as part of your wider Power BI Report Automation.

Use the evaluation guide to plan a trial around the PDF your accounts team already needs.

Download the PBRS Internal Evaluation Guide

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software