Skip to main content
This workflow shows accountants (and the developers supporting them) how to review every journal entry booked in a given month before closing the books.

​
Prerequisites

Before you start, complete the steps in the CLI Quickstart:
  • The CLI is installed and on your PATH.
  • You’re authenticated (dualentry auth login) or have X_API_KEY set for CI/CD.
  • You have read access to journal entries.

​
Steps

Step 1 - List journal entries for the month:
The --start-date and --end-date flags are confirmed on journal-entries. This returns every journal entry booked in March. Step 2 - Fetch all pages if the list is long:
By default, the CLI returns one page of results. Adding --all fetches every page so you don’t miss anything, which is important during close when completeness matters. Step 3 - Spot-check a specific entry:
Replace JE-ID with the ID from your list. This pulls the full detail (debits, credits, accounts, memo, posting date) for a single journal entry so you can verify it’s correct. Step 4 - Export the full month for the workpaper file:
Save the complete dataset as JSON for your close binder, audit trail, or to share with your auditors.
Combining --all with --format json gives you a complete, machine-readable export. This is the fastest way to pull data out of DualEntry for external analysis.
Result: You have a complete, machine-readable export of every journal entry booked in the period, suitable for review, audit, or close documentation.

​
Tips

  • Combine --all with JSON for complete exports: don’t assume the first page is everything, and compare .items | length against .count if you need to be sure.
  • --search works on every resource: it is the quickest way to narrow a list before adding more specific filters.
Last modified on September 23, 2026