Keep for bank operations
What a bank's operations, compliance and support teams can hand to Keep today, what comes back, and what Keep does
not do. Everything here runs in a sealed cell with 0 outbound connections, on hardware the bank controls.
Ready-made packs
| Pack | Team | You drop in | You get | Reads with | Sample |
|---|---|---|---|---|---|
neft-rtgs-returns | Payments ops | a returns / rejects report (.txt, .csv) | returned and rejected lines, beneficiary problems, UTRs, IFSCs, amounts | text | yes |
nach-return-report | Collections | a NACH debit return report (.csv) | returns by reason, status and sponsor; first rows | text + csv_columns | yes |
recon-exceptions | Reconciliation | an exceptions export (.csv) | exceptions by type, channel and ageing; first rows | text + csv_columns | yes |
upi-dispute-mail | Customer care | dispute mail (.eml, .mbox) | what customers report, reference numbers, amounts, escalation asks | eml | yes |
loan-sanction-letter | Credit ops | a sanction letter PDF | terms, conditions, charges, amounts, rates, dates | pdftotext | no |
rbi-circular-brief | Compliance | a circular PDF | references, applicability, deadlines, "shall" lines, repeals | pdftotext | no |
Packs that already ship and fit bank work: contract clauses, the PDF brief, the security questionnaire (vendor
due diligence), bank-sms-ledger and
card-statement (customer-side files), the office packs for
receivables, PO line items and reimbursement claims, and log triage for branch and app logs.
How a bank would run them
- Daily files. A scheduler posts each morning's returns or exceptions file to a webhook trigger; Keep runs the pack and keeps the artifact. Compare two days in Keep history to see what moved. Keep does not fetch files from core banking itself: you give it the file.
- Sending the result on. Sharing a brief with another team is an action, so it waits for a person's approval.
- A model, only if you choose one. The packs above are extractive. If a team wants a written summary as well, the model step sends the extracted text to one endpoint the bank declares and approves once; the cell stays offline and the key is added on the host (MODEL.md).
What Keep does not do
- No OCR. KYC documents, cheque images and scanned letters have no text layer, so no pack reads them.
- No decisions. Packs list and count. They do not approve loans, decide disputes, file returns with a regulator, total amounts or reconcile entries.
- No connection to core banking, NPCI or the RBI. Files go in; artifacts come out.
- No compliance claim. Evidence class is
software-test: the host's operator could still read a cell's memory. Keep is not certified against any RBI direction, PCI DSS or ISO standard. Bring it to your information-security and compliance teams before real customer data goes in, and start with masked or synthetic files.
Every sample in these packs is synthetic: EXMP, DEMO, SAMP and TEST are not real bank codes, and no real
customer, account or UTR appears.