Develop / process
Automated bank statement processing with a human approval step
Automate PDF extraction and structural checks, then verify source-linked transactions and approve the exact revision before export.
Plan the handoff
One intake, clear responsibilities
Complete source files
Check account, period and page coverage; resolve a required password.
A draft to review
Extraction and checks prepare rows with source context.
Corrections and approval
Check the source and approve the current saved revision.
The right output, in time
Download and map the approved data before access ends.
Plan an owner for unclear scans, incomplete sources and approaching expiry. Extraction does not remove the review decision.
Step by step.
Gather complete statement PDFs
Confirm the account, period, and page order for each file. Upload up to 10 PDFs at once, with each file no larger than 50 MiB or 250 pages.
Generate transaction drafts
Let Fulla extract rows from text, scanned, mixed, or password-protected PDFs; provide the document password in the document flow when requested.
Inspect exceptions against the pages
Check source-linked rows for missing dates, wrapped descriptions, debit and credit signs, and gaps in page coverage.
Correct and approve
Correct, split, merge, or undo rows as needed. A person reviews the result and approves the exact saved revision.
Export within the content window
Download the approved data in the format your next workflow accepts before the private source and derived content expire 24 hours after presign.
Define the handoff before automating
Start with a complete statement for a known account and period rather than a collection of isolated page images. Keep the original PDF available as evidence while checking the draft. A missing page or an overlapping period can distort downstream totals even when individual rows look plausible.
Decide who will check the extracted rows and which approved export the receiving workflow needs. Automating transcription does not automatically categorize transactions, post them to a ledger, or resolve differences with an accounting system.
Use extraction to reduce transcription, not judgment
Fulla prepares a transaction draft and checks row structure, dates, amounts, balances, and page coverage. Source links let the reviewer move from a questionable row back to the corresponding statement page instead of guessing from a spreadsheet alone.
Prioritize the rows that can change a balance or duplicate a transaction: negative signs, decimal places, continued descriptions, and first or last rows across page breaks. Make corrections in review, then inspect the resulting sequence before approval.
Make approval an explicit control
Extraction is not approval. The reviewer approves a particular saved revision, and exports use that approved revision rather than an unsaved draft. If a row still needs correction, finish the review before approving.
Plan the handoff within the 24-hour private-content lifetime measured from presign. Download what the next authorized reviewer needs while the document is available, and verify that the receiving system can interpret its dates and amount signs.
Questions about this guide
Does automated processing mean the transactions are ready to book?
No. Extraction produces a draft. A person must compare it with the statement, correct it where necessary, and approve the saved revision before export.
Can I upload a scanned or password-protected PDF?
Yes. Fulla accepts scanned, mixed, and password-protected PDFs, subject to the per-file limits. A protected document may require its password through the document flow.
Will this automatically sync transactions to my accounting software?
No direct accounting-software sync is part of this workflow. Export approved data and check the import requirements of the destination yourself.