Skip to main content
DualEntry generates every report directly from the general ledger in real time. When you post a journal entry, pay a bill, or record a customer payment, the reporting layer reflects the change immediately. There is no overnight batch or separate reporting database to wait for.

​
What you can report on

The reporting suite covers the full lifecycle of financial data. You produce standard financial statements (the income statement, balance sheet, and statement of cash flows, plus the trial balance) formatted for reading and external distribution. For repeat analysis, you save any configured statement as a custom report, and on the four statements that support it, the Customize builder reshapes the rows and columns themselves. Flux reporting compares account balances across periods and surfaces material variances that need explanation. Aging reports break open receivables and payables into configurable age columns so you can manage collections and vendor payments. Multi-currency reporting translates any report into a reporting currency using standard translation methods, with automatic CTA computation. Every report shares a common set of capabilities. You filter by company, period, classification, and account range, and switch between a summary view and a detail view that resolves each line to the journal entries, invoices, bills, and payments behind it. Budget comparison is its own view of the income statement and balance sheet, showing budgeted amounts beside actuals with the dollar and percentage variance per line.

​
Organizing and sharing output

You assemble related reports into report packages; for example, a monthly close package that bundles the trial balance, financial statements, flux report, and aging schedules into one PDF or Excel file. Any individual report exports to CSV, Excel, or PDF on demand, and packages add scheduled email delivery on top, since a schedule belongs to a package rather than to a single report. See exporting and report packages for how the two fit together. Dashboards give you a live, visual view of key metrics. You compose a dashboard from KPI, chart, table, and multi-currency widgets, keep several dashboards side by side as tabs, and present any of them full-screen in Display Mode. Permissions govern what each person can open. Report access is gated per report type, and package permissions control who can run, edit, schedule, or archive a package. Note that a package’s output file is not filtered to the recipient, so whoever builds a package decides what data it carries.

​
How reports fit into the close

Reporting ties directly into the close management workflow. Completing flux commentary, reviewing aging balances, and exporting the close package are all tasks you can track on the close checklist. Every report respects the same entity, period, and classification filters, so the data in your close package always reconciles to the ledger. During the close, you typically run flux reports to explain material variances, review AR and AP aging for stale balances, and generate the standard financial statements for the period. You bundle these into a report package and produce the complete close deliverable in a single run. Because all reports pull from the same real-time ledger, the numbers in the close package are always consistent with one another and with the trial balance. That consistency is worth relying on when a figure looks wrong: rerunning the trial balance with the same filters tells you quickly whether the problem is in the ledger or in how a statement presents it.

​
Pages in this section

Last modified on August 27, 2026