Exports lenders and accountants accept: PDF and CSV without the rework

Exports fail when teams treat them as a dump button. Successful galleries treat them as contracts between your catalogue and external institutions — each with its own schema, expectations, and tolerance for surprises. The notes below are the difference between an export your accountant signs off in five minutes and one that triggers a week of "quick clarifications".

Know your audience per export

Lenders care about collateral identity and movement history. Accountants care about settlement timing and tax lines. Insurers care about condition language and storage. Do not ship one CSV labelled "everything" and hope each audience extracts what they need; that is how you lose all three.

Insurers may require condition language and storage specifications. Verify field packs against current policy riders rather than last year's template — covers change quietly.

Partners receiving marketing extracts need redacted pricing tiers. Assume accidental oversharing until proven otherwise, and review the pack with someone who was not in the room when it was built.

Field packs and naming

Standardise filenames with date and scope. inventory-full-2026-04-18.xlsx beats export_final2 by a long mile, especially three quarters later when someone has to find it.

Freeze schema versions when collaborating across organisations. Silent column shifts break macros partners built on top of last quarter's file, and you will be the one fielding the email.

Document assumptions inside a README sheet or a short partner note: units, currency, VAT handling. Every ambiguity becomes an email chain, so spend the five minutes up front.

Batch discipline

Schedule heavy exports off peak interaction windows when possible. Large pulls strain the attention spans of recipients reviewing them, and a Monday-morning monster pack is a bad bet.

Diff subsequent pulls when reconciling lenders monthly. Unexpected deltas should trace to catalogue edits with ticket references; "looks different" is not a reason your counterparty will accept.

Never email raw CSVs of sensitive pricing without an encrypted channel agreed with the recipient. Defaults are the enemy of dignity here.

PDF narratives

Portfolio PDFs should mirror the catalogue ordering clients already saw digitally. Surprise reshuffles confuse the trust you spent a viewing room building.

Embed fonts when aesthetic control matters. Insurers reading faxed scans rarely appreciate ligature swaps in the margin.

Watermark "draft" until partner approval. Ambiguous states have caused expensive misunderstandings historically; an obvious badge costs nothing.

Post-export verification

Spot-check ten random rows against live records before sending. Formula drift in spreadsheets propagates silently and rarely gets caught at the destination.

Confirm totals reconcile with invoicing periods when finance consumes the numbers. Inventory snapshots without settlement context mislead audits and undermine the rest of the pack.

Archive copies internally with checksum notes when disputes arise quarters later. Future arguments are won by whoever can produce the file from the day in question.

Treat exports like the contracts they are

The export pack is a small, dated promise to a counterparty. Build it like one — named, scoped, verified, and explained — and it stops being a fire drill at the end of every quarter.