How to Export a Cross-Module Audit Bundle
Auditors ask for four CSVs and you hunt four modules
External auditors want tax filing extracts, packaging footprint, recall cases, and supplier scorecards for the same date window. Pulling each export manually creates mismatched ranges and missing files.
Teams email unfinished spreadsheets while a job is still running, with no manifest of what was skipped because a module was off.
Regulator ESS packs (FDA / CFIA / EPR) get mixed into the same ZIP request and confuse both auditors and food-safety leads.
Why this happens
- No single date-range request covering multi-module compliance CSVs.
- Synchronous downloads that time out on large tenants.
- No include/skip/error reasons for missing sections.
- Mixing regulator ESS portals with internal audit packs.
Biznsbook addresses this through Audit Bundle ZIP, async queue, manifest.json, tax filings and packaging CSVs when View reports and at least one relevant module are licensed — async ZIP with manifest.json, while FDA/SFCR/EPR ESS stay on dedicated portals.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Export a Cross-Module Audit Bundle
Built for compliance and finance leads packaging tax filings, packaging footprint, recalls, and supplier scorecards into one Audit Bundle for external reviewers.
- Confirm access. Need View reports plus at least one of Inventory, Taxation, Packaging, EPR, FSMA, SFCR, or Finance/Accounting. Sidebar shows Audit Bundle when that gate passes.
- Open Audit Bundle. Go to Management → Audit Bundle (/Company/AuditBundle).
- Set the date range. Choose From and To dates that match the auditor engagement letter.
- Select sections. Tick Tax filings, Packaging footprint, Recalls, and Supplier scorecard as needed for the engagement.
- Queue ZIP. Click Queue ZIP. Status moves Pending → Processing → Completed or Failed via the Hangfire audit-bundle processor (~every 5 minutes).
- Download and review manifest. When Completed, Download. Open manifest.json to see included, skipped (module off), or failed sections.
- Keep ESS separate. Use FDA / SFCR / EPR export portals for regulator ESS files — they are not replaced by Audit Bundle.
Review results after the first full per audit engagement cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: No single date-range request covering multi-module compliance CSVs. Repeating this each month usually shows up first in incomplete auditor ZIPs or mixed ESS expectations.
- Mistake 2: Synchronous downloads that time out on large tenants. Repeating this each month usually shows up first in incomplete auditor ZIPs or mixed ESS expectations.
- Mistake 3: No include/skip/error reasons for missing sections. Repeating this each month usually shows up first in incomplete auditor ZIPs or mixed ESS expectations.
- Mistake 4: Mixing regulator ESS portals with internal audit packs. Repeating this each month usually shows up first in incomplete auditor ZIPs or mixed ESS expectations.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- Confirm access — Need View reports plus at least one of Inventory, Taxation, Packaging, EPR, FSMA, SFCR, or Finance/Accounting.
- Open Audit Bundle — Go to Management → Audit Bundle (/Company/AuditBundle).
- Set the date range — Choose From and To dates that match the auditor engagement letter.
- Select sections — Tick Tax filings, Packaging footprint, Recalls, and Supplier scorecard as needed for the engagement.
- Queue ZIP — Click Queue ZIP.
Teams that agree the section checklist with auditors before Queue ZIP and download only after Completed avoid partial packs.
How Biznsbook supports this workflow
Audit Bundle ZIP is documented in Biznsbook Company Administration & Compliance capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
async queue is documented in Biznsbook Company Administration & Compliance capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
manifest.json is documented in Biznsbook Company Administration & Compliance capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
tax filings and packaging CSVs is documented in Biznsbook Company Administration & Compliance capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
Audit Bundle is gated by View reports plus relevant modules; regulator ESS portals remain separately permissioned.
Suggested implementation timeline
- Week 1: Document current process gaps and configure Audit Bundle ZIP with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using engagement tip and leadership dashboard.
What lands in the ZIP
Selected sections produce CSV files for tax filings, packaging footprint, recall cases, and supplier scorecard within your From/To window. The pack always includes manifest.json describing included, skipped, and failed sections with reasons.
Skipped usually means the module or capability is not licensed on the tenant. Failed means the section was selected but export threw an error — fix data or permissions and re-queue rather than hand-editing the CSV.
Async status discipline
Statuses move Pending → Processing → Completed or Failed. The Hangfire audit-bundle processor runs about every five minutes. Do not email a partial folder from a failed run; download only after Completed and attach the manifest.
If your login name is an email address, watch for the optional bundle-ready notification. Otherwise poll the Audit Bundle portal until Completed appears, then Download once and store the ZIP in your engagement folder.
Failed runs should be re-queued after you fix the underlying export error. Do not hand-merge CSVs from an older Completed pack with a newer Failed attempt — auditors need one coherent From/To window and one matching manifest.
ESS portals stay separate
FDA Electronic Sortable Spreadsheet, CFIA ESS for SFCR, and EPR regulator exports remain on their dedicated portals. Audit Bundle is the internal multi-module pack for auditors and advisers — not a substitute for 24-hour regulator response files.
Tell auditors which pack they are receiving. Mixing ESS and Audit Bundle expectations creates rework and false confidence about FSMA or SFCR completeness.
When both packs are required, deliver Audit Bundle for advisory CSVs and attach ESS from the regulator portal with a short cover note listing export timestamps for each.
Metrics to track monthly
- Completed Audit Bundle per engagement date range
- manifest.json reviewed for skipped or failed sections
- ESS packs kept on FDA/SFCR/EPR portals
- Recall and scorecard CSVs matching auditor window
- Re-queues only when range or modules change
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook Audit Bundle ZIP and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Collection | ❌ Four manual module exports | ✅ One queued ZIP request |
| Date alignment | ❌ Easy to mismatch ranges | ✅ Single From/To for all sections |
| Transparency | ❌ Guess why a file is missing | ✅ manifest.json include/skip/error |
| Runtime | ❌ Browser timeout risk | ✅ Async Pending → Completed |
| Notification | ❌ Refresh until ready | ✅ Optional email when login is an email |
| Regulator ESS | ❌ Mixed into the same pack | ✅ ESS stays on dedicated portals |
Engagement tip
Agree the section checklist with the auditor before Queue ZIP. Re-queue only when the date range or licensed modules change — do not treat every refresh as a new engagement pack. Store each Completed ZIP with the engagement letter date range in the filename so re-queues for corrected data remain distinguishable.
Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.
Frequently asked questions
How often does the processor run?
About every 5 minutes via the audit-bundle Hangfire job. Large packs may take more than one cycle.
What if a section is skipped?
manifest.json records skipped when the module is off, or failed with an error reason — so auditors know what is absent.
Does Audit Bundle include FDA ESS?
No. FDA, SFCR, and EPR regulator ESS exports remain on their own portals. Audit Bundle covers tax filings, packaging footprint, recalls, and supplier scorecard CSVs.
Will I get an email?
If your login name is an email address, you may receive a bundle-ready notification when processing finishes.
Can I include only recalls?
Yes. Tick only the sections required for the engagement; unticked sections are not generated.
How this differs by industry
Retail
Grocery chains queue recall and scorecard sections before supplier audits without opening each Inventory screen.
Wholesale & distribution
Importers include packaging footprint and tax filings in one ZIP for customs and tax advisers on the same date range.
Manufacturing
Plants attach Audit Bundle CSVs to year-end auditor data rooms while keeping FSMA ESS on the FDA portal.