How to Export Reports and Bundle Them into Packages

You export individual reports from DualEntry in three formats, and you bundle related reports into a report package that runs and delivers as one deliverable. Packages are how you assemble recurring output such as close packages, board decks, and audit binders.

​

Export an individual report

From any report view, choose Export and choose a format:

• Export to Excel: a formatted workbook that preserves column headers, grouping, and number formatting.
• Export to PDF: a print-ready document with headers, footers, and page breaks.
• Export to CSV: raw data in comma-separated format, suited for spreadsheets or BI tools.

The export includes the visible columns and respects the current filters. If you filtered a report to a single entity and a date range, the export contains only that data. On flux reports the Excel and PDF options each split in two, labeled (with explanations) and (hide explanations), so you can include or omit the variance commentary. CSV has no explanation variant, and non-flux reports show the three plain options only.

​

Track an export in the Exports panel

Exports run as background jobs, so a large report does not block your session. Starting one opens the Exports panel and confirms that the export has started and that you can track its progress there. The panel updates live as the job runs. From it you:

• Download a finished export.
• Cancel a job still in progress.
• Minimize the panel and keep working; it stays available while the job runs.

The panel also lists your recent exports, so you can return to one you started earlier and download it again without rerunning the report.

​

Bundle reports into a package

To produce several reports as one deliverable, create a report package rather than exporting each report by hand. Go to Report Center → Packages and choose New Package. The wizard walks you through naming the package, setting its schedule, choosing which reports it contains, configuring a cover page, and setting permissions. Any saved report can go into a package: standard financial statements, custom reports, flux reports, aging reports, and others. One report can belong to several packages. Reports come out in the order you arrange them in the wizard, which sets page order in the output. For the full walkthrough, including the schedule, cover page, notification, and permission options, see report packages.

​

Package output formats

A package exports as PDF or Excel. When you choose Excel, a File Preference setting controls how multiple reports are packaged:

• One Excel Workbook (Multiple Sheets): each report becomes its own tab in a single .xlsx file.
• Multiple Files (ZIP): each report is exported as its own Excel file, bundled into a single ZIP download.

PDF always produces one combined document.

​

Run a package on demand

Open the package and choose Run Package. You choose the reporting period at run time, so the same package produces last month’s or last quarter’s numbers without editing its configuration.

​

Schedule delivery

Scheduling lives on the package, never on an individual report. There is no way to put a single saved report on a recurring email; bundling it into a package, even a package of one, is how you automate delivery. A package schedule sets four things:

• Frequency: daily, weekly, or monthly.
• Day and time: the day of the week for weekly schedules, or the day of the month for monthly ones, plus the exact time.
• Time zone: the zone used to interpret that time, so a schedule fires when your team expects it rather than in server time.
• Reporting period: the date range applied to every scheduled run, such as “Last Month”. Leave it unset and the schedule defaults to the current month.

DualEntry shows the next scheduled run during setup, so you can confirm the timing before saving rather than waiting for the first delivery to find out. Recipients and their access are configured in the package’s permissions step, which is also where sharing is controlled. Individual saved reports carry no recipient list of their own. See report packages for how scheduled runs, notifications, and permissions behave in detail.

​

Common packages

Assembling standard bundles as packages saves time and keeps deliverables consistent from period to period:

• Monthly close package: trial balance, balance sheet, income statement, flux report, AR aging, AP aging.
• Quarterly board deck: income statement with a prior-year comparison, balance sheet, cash flow statement.
• Annual audit package: full-year financial statements, detailed trial balance, flux analysis.

Create a separate package per deliverable cadence rather than one package you reconfigure each time. A package that always produces the same reports in the same order is one that a reviewer learns to read quickly, and one whose output you can compare against the prior period without accounting for a layout change. When the period closes, you run the package instead of assembling reports one at a time. New team members produce the same output by running the predefined package, so the deliverable does not depend on remembering which reports belong in it.