Can I use Fulla Ledger from my own product?
Yes. Workspace API keys with documented rate limits, idempotency requirements, and an OpenAPI document cover upload, status, review, approval, and convert.
Fulla Ledger vs. building statement extraction yourself
Last reviewed 2026-09-20. Fulla Ledger details below are properties of this service; check the alternative's own documentation for its current behavior.
Short answer
Building it yourself is the right call when extraction is your product. If it is a step inside another product, the review, retention, and reconciliation work is usually the expensive part.
Choose Fulla Ledger when
- Extraction is a means to an end and you would rather not run a model evaluation loop.
- You need reconciliation, review, approval, and export behavior on day one.
- You would rather not store customer statements at all beyond a short window.
Choose Building your own extraction pipeline on a vision model API when
- Extraction accuracy is your differentiator and you want to own the model loop.
- You already run provider agreements and evaluation harnesses.
- Your inputs are not bank statements.
Feature by feature
| Dimension | Fulla Ledger | Building your own extraction pipeline on a vision model API |
|---|---|---|
| Model selection | A promoted model policy chosen by evaluation, with the eligible routes and their retention posture published. | Your own evaluation, cost control, and provider due diligence. |
| Deterministic checks | Confidence scoring, amount-sign reconciliation, and balance-equation checks run before a draft is accepted. | You design the checks and the failure thresholds. |
| Review workflow | Row evidence, correction, split, merge, undo, and approval are part of the product. | You build and test the UI. |
| Retention | 24-hour content lifetime for sources, rows, review events, and exports. | Your storage design and your deletion guarantees. |
| Privacy handling | Account, card, routing, ABA, and IBAN-like values are reduced or masked before scoring, persistence, and telemetry. | Your redaction layer, and your exposure if it is wrong. |
| Operations | Queues, retries, leases, dead letters, and expiry are already built. | Your infrastructure and on-call. |
Questions people ask
Do API results differ from the website?
No. Both use the same approved persisted revision for a statement.
Which providers can see statement pages?
Only the routes pinned by the active evaluated policy: GLM through DeepInfra ZDR, Mistral through Mistral ZDR, and Gemini Flash through Google Vertex. This is documented in the privacy notice rather than left vague.
Check it against your own statement
Upload one statement, review every row against its source page, and export the approved revision.
Convert a statement