Batch bank statement conversion with controlled client links
Bring team uploads and client-submitted PDFs into one organization balance. Validate each batch item separately, assign team roles, and create client links with an expiry and upload allowance.
Batch and client-link uploads use shared page credits. Each accepted statement still needs review before CSV or XLSX export.
Per-file batch results
Each PDF is validated separately and returned as accepted or rejected.
Expiring client links
Owners and admins choose an expiry and upload allowance and can revoke a link.
Shared page credits
Organization processing uses the workspace balance, separate from personal credits.
Two intake paths, one organization workspace
Team members with upload permission can submit a batch of PDF statements. The current configured batch limit is shown in the workspace, and every file passes its own PDF, size, page-count, password, role, and credit checks. One rejected item does not hide the result of the other files.
For external intake, an owner or admin creates a client upload link with an optional internal label, expiry, and maximum number of uploads. The recipient submits one PDF at a time; the link stops accepting files when it expires, is revoked, or uses its allowance.
Accepted and rejected files stay distinguishable
This fictional queue illustrates per-file validation. Names and results are synthetic and are not customer records.
| File | Pages | Result | Next step |
|---|---|---|---|
| north-ledger-june.pdf | 8 | Accepted | Review conversion |
| harbor-card-june.pdf | — | Rejected | Provide unlocked PDF |
| studio-current-june.pdf | 3 | Accepted | Review conversion |
Synthetic illustration only. Accepted files enter separate conversions and can produce different extraction or review outcomes.
Keep intake permissions explicit
Four implemented roles
Owner, admin, member, and viewer roles separate management, editing, and read-only access.
Team batch uploads
Owners, admins, and members can upload batches; viewers can only inspect organization data.
Managed client links
Owners and admins create, list, and revoke links and can see used versus allowed uploads.
Visible shared balance
The workspace shows available and reserved page credits for organization conversions.
Collect, validate, then review each conversion
-
1. Set organization access
Use owner, admin, member, or viewer roles according to each person’s work.
-
2. Upload a batch or issue a link
Team members select several PDFs, or an owner/admin creates an expiring, revocable client link.
-
3. Check per-file intake results
Open accepted conversions and resolve rejected PDFs, credit shortages, or validation problems separately.
-
4. Review and export
Correct each statement conversion, confirm its review, and export standard CSV or XLSX files.
Batch intake is not a document-management suite
The implemented workflow groups conversions under an organization and records their intake source. It does not add unimplemented case-management features.
- There are no client folders, ZIP manifests, saved per-client presets, or full audit-history claims in this workflow.
- The maximum files per batch is configuration-driven and displayed in the workspace; each PDF is separately limited to 25 MB and 50 pages.
- Client links accept one unlocked PDF per submission and depend on the organization having enough shared page credits.
- A batch result confirms intake only. Extraction, OCR, and reconciliation can still require correction and professional review.
Operational details before inviting clients
Who can upload a batch?
Who can manage client upload links?
When does a client link stop working?
How are shared credits charged?
Does one invalid PDF reject the whole batch?
Batch bank statement conversion with controlled client links
Batch and client-link uploads use shared page credits. Each accepted statement still needs review before CSV or XLSX export.
Open organizations