Reports and Exports
Portfolio reports, export jobs, cohort comparisons, and audit-ready packages for finance, risk, and compliance teams.
Weekly portfolio summaries, audit packages, and monthly billing reports stay visible from one report lane.
Report state stays explicit so teams can see delivered, retrying, and correction-required jobs clearly.
Reports stay operational for both machine workflows and finance/compliance review.
Delivers to risk and finance every Monday at 8:00 AM Eastern.
Bundles billing detail, consent-scope coverage, and export history before invoicing.
Prepares a bounded export with subject scope, access history, and approval context.
Every report remains linked to the requesting organization, the requesting user, and the consent scope that made the underlying records visible.
That keeps the reporting system operational instead of forcing teams to trust a hidden background job they cannot inspect.
It is the difference between a polished-looking dashboard and a platform that can actually stand up under enterprise review.
That is especially true for finance, audit, and compliance workflows where the report itself becomes a formal operating artifact.
{
"report_type": "portfolio_summary",
"delivery": "weekly",
"format": ["csv", "pdf"],
"filters": {
"segment": "underwriting_review",
"consent_scope": "hrs.lookup.identity"
},
"recipients": ["risk@northstar.example", "finance@northstar.example"]
}Reports and exports should keep schedule, status, recipients, and scope visible from the same operator surface.
Operators should see how many reporting jobs are moving before they open one detail lane.
Correction pressure belongs on the top-level reporting screen because it changes what can be relied on externally.
The next time-bound report should be visible without opening a second page.
Heavy packages should stand out so teams can predict cost and delivery pressure.
The report audience should be visible alongside the workflow itself.
Delivery health should remain on the report surface instead of hiding in a separate integration lane.
The reporting view covers customer exports, portfolio summaries, cohort comparisons, webhook delivery summaries, billing usage reports, and historical snapshots.
Every report remains linked to the requesting organization, the requesting user, and the consent scope that made the underlying records visible.
Teams can schedule repeat reports, route them to finance or compliance owners, and keep retries, failures, and delivery history visible in the same workspace.
That keeps the reporting system operational instead of forcing teams to trust a hidden background job they cannot inspect.
Audit packages bundle the visible portfolio slice, the consent metadata, and the relevant access history together so the downstream reviewer sees the full story.
It is the difference between a polished-looking dashboard and a platform that can actually stand up under enterprise review.
Reports should not disappear into a background queue with no status. Operators need to see whether a report is preparing, delivered, retried, corrected, or waiting on new data.
That is especially true for finance, audit, and compliance workflows where the report itself becomes a formal operating artifact.