This workflow shows accountants and developers how to identify outstanding invoices and export them for further analysis.
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 invoices.
Step 1: List your invoices.
The default table output includes a Status column (e.g., posted, archived) so you can see at a glance which invoices are still outstanding.
Step 2: Discover available filters for the invoices resource.
invoices list filters by date with --start-date and --end-date (YYYY-MM-DD), by status with --status (draft, posted, or archived), and by --customer, --company, or --search. Flags can change between versions, so --help is the source of truth for your installed version.
Step 3: Pull the full details on a specific invoice.
Replace INV-ID with the ID from the list output. This shows all the detail for a single invoice: line items, customer, amounts, and status.
Step 4: Export to JSON for further analysis.
This dumps the full dataset as JSON and saves it to a file. From here you can feed it into Excel, a Python script, a BI tool, or whatever your team uses for reporting. The > operator redirects the output to a file instead of printing it to screen.
Result: You have an exported JSON file of your invoice data, ready for downstream filtering and analysis with tools like jq, Python, or Excel.
- Start with
--help: the CLI is evolving fast and flags may change between versions. dualentry invoices list --help is your source of truth.
- Use
--format json for anything automated: table output is great for humans but brittle for scripts.
--search works on nearly every resource: it is the quickest way to narrow a list before adding more specific filters.
Last modified on October 28, 2026
