Bufdir Export

Separating export from generation creates an audit checkpoint that protects organizations from accidental or premature submissions, which could trigger correction filings with Bufdir. All four organizations currently handle Bufdir reporting manually; a dedicated export action with audit logging gives Org Admins documented proof that the correct version was submitted. The bufdir_exports table provides a submission history per organization, directly valuable during Bufdir audits or disputes about reported figures. For organizations receiving multi-million NOK grants, having a traceable export trail is both a governance requirement and a practical protection against administrative errors in annual reporting cycles.

The export action is a Next.js API route that retrieves the finalized report record from bufdir_exports and streams it as a downloadable file (CSV or XLSX depending on Bufdir's accepted format at deployment time). An export_status flag on the bufdir_exports record prevents re-export of already-submitted reports unless an Org Admin explicitly unlocks the record. A confirmation modal displays the report period and key aggregate totals before triggering the download. Every export event is written to audit_logs with user ID, timestamp, organization ID, and report reference. Future direct API integration with Bufdir's submission portal would replace the download step with a POST, leaving the audit and confirmation logic intact.