Skip to main content
DualEntry produces accounts receivable (AR) and accounts payable (AP) aging reports that break open balances into configurable age buckets. You use AR aging to manage collections and assess credit risk, and AP aging to plan vendor payments and manage cash outflows.

​
AR aging

The AR aging report shows outstanding customer invoices grouped by how long they have been open. Each invoice falls into an age bucket based on the number of days past its reference date. The age columns are configurable, and DualEntry builds them from a count of periods and a length per period rather than from a fixed list of named buckets. See aging periods below for how to change them. AR aging draws on the full receivable picture, not invoices alone. It includes invoices, customer credits, customer payments, journal entries, intercompany journal entries, and currency revaluations, so a customer’s row nets open invoices against unapplied credits and payments rather than overstating what is collectible. AR aging drives collection efforts. Balances in older columns signal overdue amounts that may need follow-up or escalation. Combine the report with a company filter to hand each collections owner only the balances they are responsible for.

​
AP aging

The AP aging report shows outstanding vendor bills using the same age-column structure, configured independently of AR aging. Its inputs are narrower than AR’s: bills, vendor credits, and journal entries. Vendor payments are deliberately excluded, so an AP aging balance reflects what has been billed and credited rather than what has been paid against it. Reconcile against the vendor sub-ledger when you need the payment side of the picture. AP aging supports cash management and vendor payment prioritization. You identify which bills are approaching or past their due dates, which tells you what to schedule next when you run vendor payments. Reading it by due date shows what is genuinely late, while reading it by transaction date shows how long each bill has been sitting regardless of its terms.

​
Aging periods

The age columns are set in the Aging Periods drawer, opened from the summary view of either aging report. The drawer configures Date Range Bands from three values:
  • Number of periods: how many age columns the report shows
  • Units per period: how long each column spans
  • Unit: whether those units are days or weeks
The default is three periods of 30 days, which produces the familiar 30, 60, and 90 day columns plus a current column. Raising the number of periods to four adds a 120 day column; setting units per period to 15 halves the width of every column instead. A drawer setting also chooses which date each document ages from. The options are the document’s date, its transaction date, and its due date, and the default is the document date. Due-date aging shows how many days past due each item is, which is what collections and payment prioritization need. Date or transaction-date aging shows how long an item has been outstanding since it was issued, which is what you want for cycle-time analysis, independent of the terms granted.

​
Dimensions and drill-down

You group the aging report by customer (AR) or vendor (AP), by company, by account number, or by the customer or vendor named on an individual line. The report supports two views:
  • Summary view: shows a single row per customer (AR) or vendor (AP) with the total balance in each age column.
  • Detail view: shows every open invoice or bill as its own row, with its age and amount.
Select any row in summary view to expand the underlying open documents. Select any document to navigate to the full invoice or bill record. You combine grouping with filters to narrow the report. For example, group by customer and filter to a single entity to see only that entity’s receivables. The drill-down preserves all active filters, so the detail rows always reconcile to the summary totals.
Aging reports include only open (unpaid or partially paid) documents. Fully paid invoices and bills do not appear.

​
Exclude a journal entry from aging

Journal entries with a customer_id or vendor_id on a line feed into AR or AP aging by default. Sometimes an entry touches the sub-ledger but shouldn’t be treated as an open receivable or payable: for example, a reclass, a bad debt write-off, or a correcting entry. In that case, open the journal entry and toggle Exclude from AR aging or Exclude from AP aging on. The entry remains on the customer or vendor sub-ledger and in the General Ledger, but DualEntry omits it from the aging columns. Toggle the setting off at any time to reintroduce the entry to aging. Removing the customer_id or vendor_id from the line is also an option, but it drops the entry from the sub-ledger entirely. Use the exclude toggle when you want to keep the sub-ledger link intact.

​
Export

You export the aging report in Excel, PDF, or CSV format from the report header. The export respects the current view (summary or detail), all active filters, and the grouping you selected, so what lands in the file is what was on screen. PDF exports are formatted for direct inclusion in a close package or board presentation. Exports run as background jobs and arrive in the Exports panel, where you download or cancel them, so a large detail-view export does not tie up your session while it generates. CSV produces a flat file suited for importing into external tools or BI platforms. For recurring delivery rather than a one-off download, save the configured aging report as a custom report and add it to a report package. The saved report keeps its aging periods and filters, so each scheduled run produces the same schedule against current balances.
Last modified on August 27, 2026